Is it possible to use JSP code in SitePub component development?

TS672SP2/LS31
Windows Server 2003

We currently have a site hosted by a third party, and they use JSP in WebSphere to display our content. We're ending our contract with the third party and we need to create components in SitePub to re-create the site's pages. I'm not sure if it's worth buying the third party's custom JSP files as part of our exit strategy because I don't know if the JSP can be repurposed for the component development (in XSLT). Has anyone ever converted JSP to XSLT (is that even possible), or are these two things that should work in tandem? Has anyone ever used JSP with XSLT in a component? Any advice is greatly appreciated. Thanks!

Find more posts tagged with

Comments

vpatel

When you say "converted JSP to XSLT" -- what exactly do you mean? If your JSP just has some HTML tags then that should be easily able to port over to XSL. However if you have some Java logic (whether inline or via JSP tags) then you need to understand that XSLT in general is not a programming language. You can do limited "basic logic" with native XSL (ie. if, else, loop, etc.) and some "advanced logic" using extensions. Additionally with SP/LS you can also use Controller/Externals mechanism to retrieve/process data/content.

IMHO, you probably need somebody who understands JSP/Java, XSL, IWOV WCM stack, and any relevant technologies to make the appropriate decision for you.

HTH!

JessicaD

Thank you - that does help. What I mean is that my manager is asking if it's worth paying for the JSP files, so I need to know if it's even possible to use the JSP code in conjunction with XSL in SitePublisher. They're also asking if there's a converter out there that might just take the JSP and somehow make it usable in SitePublisher as XSL.

I think your suggestion is correct, though - we need additional resources with Java and IWOV WCM stack expertise.

Crsb

VPatel said the important part, concerning your question if it is worth paying for it. IMO, if it is working then why not? unless the cost of getting it outweighs the savings.
If you don't plan on redesigning the website, then getting the working code will save you design time and significant development time. it will be like working off functioning templates.
do you know how the code looks? if it is just html code then it is just a matter of putting it into components either by manually creating the components or by using the option to create component from html src, then building pages with the created components. even it has some java logic, you can still use that code in external components.
I dont know of any mechanism that will automatically convert an entire site or a page to LS page or SP component, you will have to come up with your own or to get with someone who has done LS migration before.
I suggest you make a list of what it will take to achieve the final results with and without the JSP code and see what your savings will be.

JessicaD

Thanks for the suggestions!

Also, I have a stupid question - please forgive me. When you say "external component" where exactly is that saved or found within the TeamSite structure? I've heard people refer to "creating an external" or "just make an applet" but I can't figure out where they would actually reside in the directory structure or how to access tehm via the component.

Thanks for your help!

Crsb

an external component is dynamic component that is processed at run time. the component makes calls to get data from external data source. the component itself lives in the same area where all SP components live, but the data source could be anywhere depends on what it is (s a java class, xml, db...)