 |
 |
 |
Until you haven't shown a concrete example of the xml and the desired result
you're simply wasting (not only) your time.
"Harsh Chaudhary" <hchaudh1@g...> wrote in message
news:FCkkf.10$FX1.8994@n......
> Hi,
> I am sorry about the non-specific posting. I should have spelt things
> out more clearly. Sorry that you had to guess.
>
> But you guessed right. I am using XSLT 1.0. My processor is dom4j. But I
> don't want to use that as I want to keep it pure XSLT. So, no extension
> functions. I am aware of the EXSLT function that you mentioned, but I
> don't want to use it. I don't want to double pass as it would increase
> my cost of the transformation by I think a factor of 2. What I am
> looking for is like a hack or something to acheive this. Its a
> complicated problem with us being limited to only 4 variable types and
> none of them suitable for getting this done. And the fact that variable
> values can't be changed.
>
> But if you know how to implement a name-value pair in XSLT, this would
> be solved.
> Thanks,
> Harsh.
>
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |