1. Yakov Werde
  2. PowerBuilder
  3. Wednesday, 1 March 2023 22:12 PM UTC

Hi,

I revisited this feature during an Advanced DataWindow course delivery today. Wondering..... 

There is a DataWindow painter feature on the File menu --> Save As File --> Save As Type - DataWindow Syntax In XML.

It outputs nicely formatted & readable syntax like the sample attached.

Besides developer readability, what is this useful for?  There is no feature to import it to create a DW?

 

Thanks for clarifying

Yakov

eLearnIT LLC

Your source for independent PowerBuilder Classic training

Attachments (1)
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 2 March 2023 00:41 AM UTC
  2. PowerBuilder
  3. # 1

Hi Yakov;

  AFAIK: This is an old left over feature from way, way back to the early Sybase days when they were adding XML support. However, I have no idea what it was intended for. That aspect has been lost along with the original developers. My guess though is that since you can reconstitute DWO source from an ANSI Result Set (from the days of Jaguar support because of Java interoperability) - I think that the idea was to be able to reconstitute a DWO from XML (just my guess) - but of course, that feature never really materialized.

Regards ... Chris

Comment
There are no comments made yet.
Yakov Werde Accepted Answer Pending Moderation
  1. Thursday, 2 March 2023 04:28 AM UTC
  2. PowerBuilder
  3. # 2

Hi Chris,

I just recalled an EAServer PB .NET failed integration project.  The client wanted to use GetFullState / SetFullState to pass datawindow state between EAServer components and a PB .NET client.   The failure point was that the PB .NET BLOB contents were not compatible with the PBClassic BLOB contents The PB.NET developers changed BLOB structure.  They put DW Syntax and buffer state as XML inside the BLOB.  This rendered PB Class and PB.NET unable to exchange data using GetFullState SetFullState

I'm thinking this interesting but useless feature has something to do with that effort.

 

Yakov

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 2 March 2023 16:38 PM UTC
Hi Yakov;

Yes, the internal structure of DWO's in PB.NET was XAML based and thus, not compatible with PB "Classic" DWO source and it's internal buffer format. Therefor you would need a "common ground" to pass Result Set data back & forth in between Apps or within EAServer threads. So you could very well also be correct about why this legacy DWO save object as XML was added. Either way, it's a "dead end" I am afraid at the moment.

However, there are currently a few enhancement requests in the Appeon System already to be able to to create DWO source from either an XML or a JSON result set.

Regards ... Chris
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.