cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grofčík Martin <mgrof...@pflow.sk>
Subject RE: JSR 168 in new portal
Date Fri, 25 Jun 2004 08:35:15 GMT
Thak you a lot.
It helps.
Regards Martin 

-----Original Message-----
From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] 
Sent: Friday, June 25, 2004 10:27 AM
To: dev@cocoon.apache.org
Subject: RE: JSR 168 in new portal

You have to enable cross context access for Cocoon. Add a cocoon.xml in the
webapps directory with the following content:

<Context path="/cocoon" docBase="cocoon" crossContext="true"> </Context>

Then it should work.

HTH
Carsten 

> -----Original Message-----
> From: Grofcík Martin [mailto:mgrofcik@pflow.sk]
> Sent: Friday, June 25, 2004 8:09 AM
> To: dev@cocoon.apache.org
> Subject: RE: JSR 168 in new portal
> 
> The version of the Tomcat is 4.1.30.
> 
> Pluto (version 1.0.1) was build and deployed by maven rc1. 
> (maven fullDeployment command).
> 
> Then I check pluto instalation - test portlets were OK.
> 
> I stopped tomcat.
> I unpacked cocoon war into the tomcat's webapps dir and removed 
> pluto*.jar and porlet-api*.jar.
> I start Tomcat. And there were no output for test portlet #1, #2.
> 
> 
> 
> -----Original Message-----
> From: Menke, John [mailto:John.Menke@acs-inc.com]
> Sent: Thursday, June 24, 2004 4:44 PM
> To: 'dev@cocoon.apache.org'
> Subject: RE: JSR 168 in new portal
> 
> >>I deployed cocoon app as JSR 168 compatibile portlet into
> the pluto. 
> 
> What version of Tomcat are you using?  
> You deployed by creating the .war and putting it in the webapp folder 
> right?
> 
> i am using 4.1.30 and Cocoon is not coming up
> 
> -jm
> 
> __________ Informacia od NOD32 1.574 (20031206) __________
> 
> Tato sprava bola preverena antivirusovym systemom NOD32.
> http://www.eset.sk
> 
> 
> 


__________ Informacia od NOD32 1.574 (20031206) __________

Tato sprava bola preverena antivirusovym systemom NOD32.
http://www.eset.sk



Mime
View raw message