You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Poh Justin KT <ni...@hotmail.com> on 2001/04/12 10:41:49 UTC

should I use XSLT for this case..??

hi, sorry if I ask some stupid questions..

let say I have a XML converted from a relational database, where the Node 
names are trivial(as the database will change).  Can I still use XSLT to 
transform it?  As, from my little knowledge in XSL, it seem to me that XSL 
has to be fix, so if a change in the Node names in the XML file, the XSL 
will not worked properly..  or is there a way to do so?

Or would it be easier to use DOM Parser and servlet to perform this task?

Thanks
Justin

Hope to hear from you soon.
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.


Re: should I use XSLT for this case..??

Posted by James Melton <ja...@cylogix.com>.
This sounds like a pure XSL question rather than being Xalan-specific. A
better place to ask would be:
  http://www.mulberrytech.com/xsl/xsl-list/index.html

Also, when posting there, a simple example may help clarify what you are
trying to do.

Jim.

Poh Justin KT wrote:
> 
> hi, sorry if I ask some stupid questions..
> 
> let say I have a XML converted from a relational database, where the Node
> names are trivial(as the database will change).  Can I still use XSLT to
> transform it?  As, from my little knowledge in XSL, it seem to me that XSL
> has to be fix, so if a change in the Node names in the XML file, the XSL
> will not worked properly..  or is there a way to do so?
> 
> Or would it be easier to use DOM Parser and servlet to perform this task?
> 
> Thanks
> Justin
> 
> Hope to hear from you soon.
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

-- 

____________________________________________________________
James Melton                 CyLogix
609.750.5190                 609.750.5100
james.melton@cylogix.com     www.cylogix.com