This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: using different xsl based on xml


You could have a single generic stylesheet with lots of sub templates.  You
could then perform the transformation and the XSL will match to the elements
available in the incoming XML e.g.

1) <xsl:template match="/root">
   ....

2) <xsl:template match="/data">
   ....

1 would match a root element called "root" and 2 would match a root element
called "data".  Each one could treat the XML differently.

The precise solution depends on the XML you're receiving.  If they share the
same name for elements you may need to increase the complexity of the
'select's and 'match'es.


> -----Original Message-----
> From: John Wang [mailto:jwang@mincron.com]
> Sent: Tuesday, May 01, 2001 8:25 PM
> To: list
> Subject: [xsl] using different xsl based on xml
> 
> 
> Hello, All
> 
> I got different xml data from different customers. What I am 
> trying to do is
> convert the coming xml to my common xml, and use the common 
> one to send
> data to my database.
> 
> My question is, how can I tell where the xml comes from, and how can I
> determined
> which xsl I should use to deal with the xml, without adding 
> anything in
> customer's xml?
> 
> Here I suppose at first time I got the xml, I made specific 
> xsl fot the xml.
> so the xsl exists.
> 
> Thanks in advance.
> 
> -John
> 
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]