> -----Original Message-----
> From: Rapha�l Luta [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 06, 2000 3:51 PM
> 
> Neeme Praks wrote:
> > 
> > Why do I need to specify a stylesheet for CocoonPortlets 
> (XSP, static
> > XML, etc) in the registry?
> > Why can't I do it in the XSP/XML file itself?
> 
> You could in the first instance. The feature has been 
> disabled to force
> local caching of the stylesheet.

Ok, could be that it isn't a must anymore, I have somewhat older CVS
version and it requires this attribute to be present.
Should upgrade probably.

> > And related: can I specify more than one stylesheet in the registry?
> 
> For media selecting ? Not yet.
> You're welcome to submit a patch though... :)

I could to do it in my XSP logicsheet, or maybe not.
I was more thinking about consecutive stylesheets, but this is usually
handled by the first stylesheet that inserts PIs for Cocoon to handle
the next one.

Anyway, I find that the path handling is a total mess... Right now I'm
trying to figure out why JetspeedDiskCache behaves very strangely in my
environment where I have Jetspeed running in separate context... It
seems that it is assuming the root context when converting URL into a
physical location. 
I have context for jetspeed set to "/jetspeed" and I have my XSP file in
http://myhost/jetspeed/myfile.xml, the physical path is
root-to-tomcat\webapps\jetspeed\myfile.xml (Win2K system). When
resolving the URL to physical, JetspeedDiskCache returns
file://root-to-tomcat/webapps/jetspeed/jetspeed/myfile.xml.
As much as I understand, EngineContext.getInstance().getDocumentRoot()
returns root-to-tomcat\webapps\jetspeed and then the
/jetspeed/myfile.xml from URL is appended to this, resulting in one
extra "jetspeed". Haven't figured a way out yet how to fix this...

Neeme


--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to