× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I am not necessarily trying to steer you away from XSLT, but note that
you just introduced a potentially unnecessary failure point and
potentially CPU intensive processing that could be eliminated by just
just buckling down and doing it all in RPG.

Another thing to watch out for is if you "flatten" the XML out, make
sure you are still adhering to the XSD (i.e. be mindful of repeating
sections).

Just some thoughts that don't really answer your question (sorry) :-)
Aaron Bartell
http://mowyourlawn.com


On Thu, Jul 10, 2008 at 11:48 AM, Adam Glauser <adamglauser@xxxxxxxxxxxx> wrote:
I have an XML document I'm trying to simplify so that I can make it
easier to process using and RPG program and XML-INTO.

I'm in the Resources perspective, I have selected both a .xsl and a .xml
file, but I can't seem to use "Run->XSL Transformation" as suggested by
the article I'm following. There is no XSL option in the Run menu.

I have the XML Developer capability selected. I'm using WDSC v7. Any
suggestions on what might be causing the problem?
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.