|
I am burning the midnight oil almost every night (3am last night:-) so I hope to have it out soon (1 week hopefully). I am making it much easier to install with this next version (CALL INSTALL), and there will also be more example programs and hopefully some Power Point slides from a presentation I am giving tomorrow. If you can wait for the next release I would recommend doing so. I am more than doubling the functionality (serializing, error handling, etc. . .) and some of the API's names have changed (For example: DOMInitParser is now DOMParser_init). Aaron Bartell -----Original Message----- From: Tucker Gerry [mailto:Gerry.Tucker@xxxxxxxxxxx] Sent: Monday, June 16, 2003 10:34 AM To: Web Enabling the AS400 / iSeries Subject: RE: [WEB400] XML Interface for RPG Aaron, Any timescales for the next version? Gerry > -----Original Message----- > From: Bartell, Aaron L. (TC) [mailto:ALBartell@xxxxxxxxxxxxxx] > Sent: 16 June 2003 15:36 > To: Web Enabling the AS400 / iSeries > Subject: RE: [WEB400] XML Interface for RPG > > > In the version you have, you can't specify a encoding from my > API's, you > would instead have to create your own DOMInitParser() and do > the necessary > encodings in there. The next version allows for this. > > Yes, the next version has complete serialization routines. > > Aaron Bartell > > -----Original Message----- > From: Tucker Gerry [mailto:Gerry.Tucker@xxxxxxxxxxx] > Sent: Monday, June 16, 2003 8:40 AM > To: Web Enabling the AS400 / iSeries > Subject: RE: [WEB400] XML Interface for RPG > > > Aaron, > > I am using your procedures, I had to re-engineer them back to > V4R5 (i.e. not > free-form code). I can't see where I can specifiy the > encoding when using > MemBuf etc as it seems to be a default within the procedures > and I won't > necessarilty know until runtime what the encoding is. Other > than that, for > CCSID 37 they work great. > > Will the next release allow for creation of XML too? > > Regards, > > Gerry Tucker > Senior Analyst Programmer > Technicolor > Wembley, UK > Tel: +44(0)208-900-6555 > > > > > > -----Original Message----- > > From: Bartell, Aaron L. (TC) [mailto:ALBartell@xxxxxxxxxxxxxx] > > Sent: 16 June 2003 14:21 > > To: Web Enabling the AS400 / iSeries > > Subject: RE: [WEB400] XML Interface for RPG > > > > > > Just make sure to specify the same encoding on the parse as > > you do on the > > associated input source (MemBuf, SystemId, etc) and you > > should be fine. > > > > I am about to release the next version of the rpg-xml-parser on > > sourceforge.net which is based on IBM's XML Interface for > > RPG. You should > > check it out to see the ease of use functionality it gives > > you compared to > > IBM's API's. > > > > http://sourceforge.net/projects/rpg-xml-parser/ > > > > Aaron Bartell > > > > -----Original Message----- > > From: Tucker Gerry [mailto:Gerry.Tucker@xxxxxxxxxxx] > > Sent: Monday, June 16, 2003 8:10 AM > > To: web400@xxxxxxxxxxxx > > Subject: [WEB400] XML Interface for RPG > > > > > > Hi guys, > > > > Really don't know if this is the correct list to post to > but I'll try > > anyway. > > > > I'm starting out on a project to process XML order files and > > I'm parsing > > them using the XML Interface APIs. So far I've managed to do > > this pretty > > well so long as the XML file in the IFS is CCSID is 37 and > > the 'encoding' > > value is 'ibm037'. If any other value is entered then the > > QxmlDOM_Node_getNodeName procedure returns MCH3601 'Pointer > > not set for > > location referenced'. I've seen it mentioned before but no > definitive > > answers were provided. > > > > The files we get are likely to have encoding attribute set > to 'UTF-8'. > > > > Any ideas? Again apologies if this isn't the place to ask > > this question. > > > > FYI we're on V4R5 using service program XML4PR400. > > > > > > Regards, > > > > Gerry Tucker > > Senior Analyst Programmer > > Technicolor > > Wembley, UK > > Tel: +44(0)208-900-6555 > > _______________________________________________ > > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list > > To post a message email: WEB400@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/web400 > > or email: WEB400-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/web400. > > _______________________________________________ > > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list > > To post a message email: WEB400@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/web400 > > or email: WEB400-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/web400. > > > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list > To post a message email: WEB400@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/web400 > or email: WEB400-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/web400. > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list > To post a message email: WEB400@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/web400 > or email: WEB400-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/web400. > _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
