[opencms-dev] FW: Static publishing JSP content issues in OC6

[Michael Moossen]

Hi, Jeff!

  The Static Export feature has been improved since 6.0 final release, you
should try the CVS head or wait for the 6.1 release.
  to solve your problems with 6.0:
1. keep a copy of the style sheets in your live webapps
2. extend the CmsAfterPublishStaticExportHandler class, overwriting the
scrubExportFolders method, just using the same code as the original but adding
an additional condition when calling CmsFileUtil.purgeDirectory(exportFolder);

hth
-- 
Regards
Michael Moossen
An der Wachsfabrik 13
50996 Köln

Tel: +49 2236 3826-0
Fax: +49 2236 3826-20
Email: m.moossen at alkacon.com

http://www.alkacon.com



Quoting Jeff White <jeff.white at jvolution.co.uk>:

> 
> Hi
> 
> We are trying to publish content managed JSP pages directly to a Tomcat
> Webapp folder using static export, by setting the following
> opencms-importexport.xml properties and using the
> CmsAfterPublishStaticExportHandler ;
> 
> 		<exportpath>C:/Apache Group/Tomcat 5.5/webapps/live</exportpath>
> 
> and
> 
> 			<rfs-prefix>/live</rfs-prefix>
> 
> This produces reasonably tidy links in the exported HTML .jsp files but the
> <rfs-prefix> seems to be used by the workplace to locate it's CSS style
> sheet and the login page and workplase renders incorrectly (with no style
> sheet).
> 
> Why is there a workplace dependency on the opencms-importexport.xml static
> export properties ?
> 
> The CmsAfterPublishStaticExportHandler static export class also deletes the
> target directory including the WEB-INF directory causing the webapp to not
> be runnable after a publishing process -  is there any way to stop this
> action ?
> 
> Regards
> 
> Jeff White
> JVolution Ltd.
> Tel : (+44) 0208 714 4488
> Mob: 07951 764806
> This email and any attachments or links are confidential and intended only
> for the individual to whom it is addressed. If you are not the intended
> recipient, any use or dissemination of this communication is strictly
> prohibited and you are requested to notify the sender immediately and then
> delete this email.
> 
> JVolution does not accept liability for any data corruption, unauthorised
> amendment, viruses and unforeseen delays to which this email may be subject.
> This email and any attachments or links are opened at your own risk.
> JVolution can take no responsibility for the consequences of actions carried
> out as a result of this e-mail.
> 
> 
> 
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
> 


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.