Creating .jsp file out of .page

Hi

Is there any way to generate .jsp file extension instead of .page using sitepublisher component ?

Please let me know if any options are available either OOTB or customization

Find more posts tagged with

Comments

Bowker

I'm a little confused by your question.

SitePublisher generates .page files (actually they are XML files with .page extensions) that are read by LiveSite (TeamSite, SitePublisher too) to produce (usually) HTML, XML, XHTML ... type output.

You could create a component (probably XSL over HTML) that will generate .jsp as it's output rather than .html.

If you want to copy / rename the .page file to be .jsp (although I don't know why you would want to) you probably could do something with an IWAT job to watch for new/updated .page files and copy/rename them. I would suggest copy so you can reedit them later with SP without a bunch of other changes. (Disk space is cheap and .page files are small)

pinaki

Hi Bowker

Currently we are using .jsp as file extension in target environment (created from Form Publisher)

We want to maintain same file extension using Sitepublisher.

As Sitepublisher provides option to "generate HTML" like that is there any way to convert/Generate page extension as .jsp

We assume that Sitepublisher code will contain/support jsp tags embedded into the Appearance XSL

I'm a little confused by your question.

SitePublisher generates .page files (actually they are XML files with .page extensions) that are read by LiveSite (TeamSite, SitePublisher too) to produce (usually) HTML, XML, XHTML ... type output.

You could create a component (probably XSL over HTML) that will generate .jsp as it's output rather than .html.

If you want to copy / rename the .page file to be .jsp (although I don't know why you would want to) you probably could do something with an IWAT job to watch for new/updated .page files and copy/rename them. I would suggest copy so you can reedit them later with SP without a bunch of other changes. (Disk space is cheap and .page files are small)

Bowker

Ah Ha - you want the "generated page" that typically has .html to generate .jsp.

I'm sure there is a very elegant way to do this, but I would consider creating an IWAT task (Scheduled task that gets triggered when specific events occur) to monitor your workarea and when a .HTML file is generated, rename it to .JSP

That way you don't screw around with "their code" and that solution will most likely work into the future without any changes.

P.S. Yes the templates will allow you to generate JSP tags. I've never done it but it's just straight XSL.

pinaki

Hi Bowker,

Thanks a lot for your response

Could you please let me know same way can we embed .asp tag into the Appearance XSL of Sitepublisher component and generate .asp page using your method?

ie. Can Sitepublisher support .asp tags like .jsp tags in Appearance XSL any idea?

Ah Ha - you want the "generated page" that typically has .html to generate .jsp.

I'm sure there is a very elegant way to do this, but I would consider creating an IWAT task (Scheduled task that gets triggered when specific events occur) to monitor your workarea and when a .HTML file is generated, rename it to .JSP

That way you don't screw around with "their code" and that solution will most likely work into the future without any changes.

P.S. Yes the templates will allow you to generate JSP tags. I've never done it but it's just straight XSL.

Rick Poulin

I'm sure there is a very elegant way to do this

There is, but only through workflow (i.e. doesn't work via the CCPro menu). There's a variable called "suffix" on the Generate HTML workflow task in the PLC. Allowed values are ".html", ".htm", ".shtml", ".asp", ".jsp".

Could you please let me know same way can we embed .asp tag into the Appearance XSL of Sitepublisher component and generate .asp page using your method?

ie. Can Sitepublisher support .asp tags like .jsp tags in Appearance XSL any idea?

The short answer is yes. The longer answer is you have to fiddle with namespaces. http://forums.asp.net/t/50239.aspx/1