<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=856004410-06062006><FONT face=Arial
color=#0000ff size=2>Hope this works for you. I do remember it took me
ages to figure out...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=856004410-06062006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=856004410-06062006><FONT face=Arial
color=#0000ff size=2>Jon</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> opencms-dev-bounces@opencms.org
[mailto:opencms-dev-bounces@opencms.org] <B>On Behalf Of </B>Marc
Johnen<BR><B>Sent:</B> 06 June 2006 12:27<BR><B>To:</B>
opencms-dev@opencms.org<BR><B>Subject:</B> Re: [opencms-dev] mod_proxy and
workspace.css<BR></FONT><BR></DIV>
<DIV></DIV><PRE>Hi Jon,
sorry for my late response and thanks for your answer!
I'm starting to understand how it works, but my problem
is not yet solved. I followed your instructions, but without
effect. Probably I made a mistake somewhere, for now I don't
have any time to check it. My plan is to configure only the
exported page with mod_jk (which seems more flexible to me) and
leave the workspace-access at port 8080.
Greetings
Marc, Berlin
Like some other system resources, workspace.css is 'statically exported'
(written from VFS to RFS) on demand; and the RFS location it's written to
will be <opencms root>/WEB-INF/export/system/work...... So clearly the
stsatic export part of your set-up isn't working. This may be linked to the
missing step re the workspace JSP, which is this: edit
/system/workplace/views/top_js.jsp (for 6.2.x) or
/system/workplace/views/top_fs.jsp (for 6.0.4) and locate the line which
says
this.servpath="<%= OpenCms.getSystemInfo().getOpenCmsContext() %>";
to say
this.servpath="<%= OpenCms.getStaticExportManager().getVfsPrefix()
%>";
This says to OpenCms that it should regard OpenCms-managed URIs as beginning
with the VFS prefix configured in opencms-importexport.xml (which, slightly
misleadingly, also controls URI generation for non-exported resources.
Hope this helps.
Jon
-----Original Message-----
From: <A href="http://lists.opencms.org/mailman/listinfo/opencms-dev">opencms-dev-bounces at opencms.org</A>
[mailto:<A href="http://lists.opencms.org/mailman/listinfo/opencms-dev">opencms-dev-bounces at opencms.org</A>] On Behalf Of Marc Johnen
Sent: 27 May 2006 13:55
To: <A href="http://lists.opencms.org/mailman/listinfo/opencms-dev">opencms-dev at opencms.org</A>
Subject: [opencms-dev] mod_proxy and workspace.css
hello everyone,
i (carefully) followed the instructions of the documentation to "cut off"
the "opencms/opencms" and it is working fine so far. i'm only encountering
one problem. the workspace.css can not be found at
"/export/system/workplace/commons/style/workplace.css",
after the modifications
it should be "/system/workplace/commons/style/workplace.css", if i'm
correct.
also i think in earlier versions of the documentation there was some kind of
reference of changing one of the workspace-jsps, i can't find that anymore
though.
the workspace is not really usable without the correct css and my
understanding of opencms is not sufficient to correct the problem. hope
someone knows what to do.
thanks and greetings
marc, berlin</PRE></BODY></HTML>