Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Previewing using JSP
Fessorx1
I am interested in previewing content using XSL orJSP opposed to using TPL and interwoven Tags.
My interest stems from the use of Websphere and Java/JSP/XSL to display content.
What are best practices concerning creating xml content throught IW's DCT's but using XSL or JSP's in displaying this content? How do you preiview the content? I wouldn't want to have to make changes to layout in 2 places...a TPL for prievew and in the JSP/XSL for Production Display
Thanks,
Big Jim
Find more posts tagged with
Comments
Johnny
Im not exactly sure what it is you are trying to achieve.
If you are saying you would rather not use TS Templating, there is nothing stopping you from parsing the DCR's under any application server as they are in XML form. There may be some instances where this is useful.
But if you are after content displaying I would just use TS Templating, you are able to output any text format, not just html. So your generated page could well be a JSP or a JSP include, etc etc
Essentially TPL's are intended to generate the production code. Its the whole point of templating. You should generate a JSP that your production server can use, and integrate that application server with in TeamSite so you can preview it correctly.
Was I close?
John
Sydney, Australia
tvaughan
I think he was asking if there was a way to redirect what the functionality of the "Preview" button within the DCT does. In otherwords, if you fill in all the fields of a DCT and click, "Preview", is there a way to send the form data you just entered to an 'XSL preview engine' or a 'JSP preview engine' instead of the (default) 'TPL preview engine'.
All I can say is . . . "great suggestion for future product enhancement."
I don't think there is any straight-forward way to accomplish this. Even if you could hack the preview code and redirect what the 'Preview' button does, you'll have quite a bit of work coming up with your own parsing engine to turn DCT replicants and if-else radio buttons into proper JSP or XSL code.
Tom
Johnny
hmmm if thats the case... then... hmmmmm!
I dont see the point in using two different methods.. one for preview.. and one for final generation...
John
Sydney, Australia