Subject: Re: create XML from XML using XSL From: Matthew MacKenzie <matt@xxxxxxxxxxxxxxx> Date: Thu, 08 Apr 1999 11:03:34 -0300 |
Guy, We solved this problem by modifying the server-side's output, and using a style sheet thats a bit more complicated. You can see what we are up to by pulling this up in IE5: http://www.cartnetwork.com/cgi-bin/xml/prod2xml.pl?DB=democart ..its still a pretty early interface though. Matt matt@xxxxxxxxxxxxxxx Guy_Murphy@xxxxxxxxxx wrote: > > Hi. > > Have you tried something in the areas of... > > <xsl:for-each select="root_tag/next_tag"> > <xsl:apply-templates select="someTag" /> > </xsl:for-each> > > ...or.... > > <xsl:for-each select="root_tag/next_tag"> > <xsl:for-each select="someTag"> > .... > </xsl:for-each> > </xsl:for-each> > > ...?...Just fishing here, I'm sure you've covered the options available to > you. > > On the issue of bringing together the URL and query into a single URL, have > you an example of an XML document? I've had to deal with very similar issue > producing intranet applications in an ASP server-side enviroment. In this > case I was cascading attribute values through several layers of processing, > and yes it is most definately a head-ache. > > Cheers > Guy. > > xsl-list@xxxxxxxxxxxxxxxx on 04/08/99 03:23:31 AM > > To: xsl-list@xxxxxxxxxxxxxxxx > cc: (bcc: Guy Murphy/UK/MAID) > Subject: Re: create XML from XML using XSL > > Hello Guy: > The reason why we are trying this again and again is the end use for a > project. What we are trying to do is amalgamate two nodes from the XML > document which may be named <url> and <id>. In the xsl doc, we wanted > to create the xlink with the Xpointer > http://www.somewhere.com/cgi-bin?ID123 > Out of the input tree of > <url>http://www.somewhere.com/cgi-bin</url> > and <id>?ID123</id> > <The_BIG PROBLEM> > I know how to do this based on 1 input tree node pattern, however, we > are dealing with a dynamically generated XML document from our engine > which may output between zero and one thousand tree branches based on > previous user input. > Therefore, we have to use the <xsl:for-each> in the XSL document. This > seemingly is harmless enough but the beautiful designers at Microsoft > have thrown a damper on our party by not allowing us to use: > <xsl:for-each select="root_tag/next_tag"> > > <xsl:template match="someTag"> > > <a> > > <xsl:attribute name="href"> > > <xsl:value-of select=".[@file]" /> > > </xsl:attribute> > > <xsl:value-of /> > > </a> > > </xsl:template> > </xsl:for-each> > We tried this in hundred's of variations and finally resorted to using a > scripting language to manipulate the data and assemble the completed > link by accessing the node values and joining them together into the > correct <href="url+id">Buy one now</a> > This is currently unsatisfactory and there is high I/O overhead and > other inherent problems. I know we aren't the first to try this. > My next step is to investigate the possibility of using the MS XML-DOM > to facilitate a solution. > *sigh* back to the ole drawing board. It's really eating into my > snowboarding time and that's annoying me. > Duane Nickull > cartnetwork.com > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: create XML from XML using XSL, Guy_Murphy | Thread | empty elements again..., Linda van den Brink |
RE: XPDL (was Re: XML is broken), Simon St.Laurent | Date | Re: The Cathedral and the Bizarre (, Duane Nickull |
Month |