Man Suraj
Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"
Man Suraj
Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"
Man Suraj
Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"
Maan Suraj wrote:but the problem is that above gives compilation issues. Is it possible for you to give me a small working sample?
Maan Suraj wrote:Above is ok if the user selects only one option .What if the user clicks on 2 or more options. For eg if User selects both "SchoolState" and "SchoolLocation", then i want to dynamically generate a xsl combining "SchoolStateInfo.xsl" and "SchoolLocation.xsl". Is there a way i can do this?
At least I expect there probably is
Please tell me what is not clear to you?. Hope above helps.it isn't clear what's supposed to happen in that case
What are those?I can think of at least two solutions to that problem which don't involve generating XSL at the time of the request.
Man Suraj
Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"
Maan Suraj wrote:I am also quite sure there should be a way to do this...but i am not getting it. I am new to xslt. That's the whole reason i am asking in this forum.There should be a way to do this...agreed,but what is it . I am quite sure you or people in this forum might have come across this scenario. I thought of using something like <xsl:param> or something but not sure if there is a better way to do that. I want something like "base.xsl", and based on params i want to combine the xsls. For eg if the param contains SchoolState and School Location, then base.xsl should import contents of SchoolStateInfo.xsl and SchoolLocation.xsl .
Similarly another eg can be if the param contains SchoolCountry and SchoolInfo then base.xsl should import SchoolCountryInfo.xsl and SchoolInfo.xsl content. So i need to figure out how can i do that.I mean all these permutations.
Please tell me what is not clear to you?. Hope above helps.it isn't clear what's supposed to happen in that case
What are those?I can think of at least two solutions to that problem which don't involve generating XSL at the time of the request.
Man Suraj
Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"
Paul Clapham wrote:What isn't clear is what is actually supposed to happen. Are we supposed to see the output of SchoolCountryInfo.xsl followed by SchoolInfo.xsl? Or something else? It does make a difference, you know.
Now the requirement has changed,user now has option to select params. He has a choice from UI to select Location,SchoolInfo etc. So i thought it's better for me to split the big base.xsl file into smaller files.
What isn't clear is what is actually supposed to happen. Are we supposed to see the output of SchoolCountryInfo.xsl followed by SchoolInfo.xsl? Or something else? It does make a difference, you know.
Man Suraj
Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"
I am suggesting you should write an XSLT document with templates for all of the options that the user might select at run time, and only call the templates which the user actually does select.
Man Suraj
Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"
Maan Suraj wrote:But what i thought was perhaps,there could be a way to import dynamic things,just like the way we do dynamic imports in jsps and all.
Man Suraj
Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"
We should throw him a surprise party. It will cheer him up. We can use this tiny ad:
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
|