I have tried with Sun's 1.5_06 JVM and jrockit-R26.0.0-jdk1.5.0_04 JVM.
Nothing change.
The thing is the deployement works only once when the previous one
failed and then stop/restart tomcat then redeploy (this one works)...
the following redeployement then fail...
So, I have try Ruwan solution (strip out all faces-config.xml in the jar
files...). The deployement works then well.
I have tried with jsf-demo but I have the following error now:
javax.faces.FacesException: Unsupported context type
org.apache.jetspeed.container.JetspeedPortletConfig
at
org.apache.myfaces.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:72)
at
org.apache.portals.bridges.jsf.FacesPortlet.process(FacesPortlet.java:418)
at
org.apache.portals.bridges.jsf.FacesPortlet.doView(FacesPortlet.java:277)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
I don't know deeply jsf and jetspeed yet in order to analyse further
this bug...
Thanks for your answer,
Seb.
Aaron Evans a écrit :
BTW, I am seeing this behaviour with Sun's 1.5 JVM, tomcat 5.5.9 on
windows *and* linux.
On 3/28/06, Ruwan Abeykoon <[EMAIL PROTECTED]> wrote:
Yes, the same problem, DTD files in struts.jar.
Things work fine if you remove them and repackage the jar. But then, Tomcat
needs internet connectivity to locate the DTDs, otherwise struts servlet
does not get started.
I am also looking for a better solution, perhaps Tomcat antiResourceLocking
might help.
Regards,
Ruwan
----- Original Message -----
From: "Aaron Evans" <[EMAIL PROTECTED]>
To: "Jetspeed Users List" <[email protected]>
Sent: Tuesday, March 28, 2006 7:52 PM
Subject: Re: Deployment doesn't unpack everything...
Interesting... I have this problem with one of my apps that is struts
based (but outside of the jetspeed portal). I wonder if it is
something similar...
On 3/27/06, Ruwan Abeykoon <[EMAIL PROTECTED]> wrote:
Hi Sebastien,
I also encountered same problem with jsf (tomahawk), java 1.4.2, Tomcat
5.5.9/5.5.12 on Microsoft windows 2000/2003. The reason is that
tomahawk.jar
(and jsf bridge jar) contains faces-config.xml files in META-INF folder.
The
faces servlet, upon initialization reads those files and in turn the jar
is
locked by VM. When you try to undeploy the webapp, those jars are locked
and
then subsequent deployment fails. Setting Tomcat antiJARLocking="true"
does
not help for this situation.
I assume that this problem is with JVM as the problem did not occur with
BEA
jrokit 1.4., but with sun jvm 1.4 .
One other solution is to strip out all faces-config.xml in the jar files
and
merge/rename them.Then put them in the place where your applications
faces-config.xml file is, and refer them with context param
(javax.faces.CONFIG_FILES) in web.xml. (not tested with portlets though)
Regards,
Ruwan
----- Original Message -----
From: "Sébastien Pérochon" <[EMAIL PROTECTED]>
To: "Jetspeed Users List" <[email protected]>
Sent: Tuesday, March 28, 2006 2:49 AM
Subject: Deployment doesn't unpack everything...
Hi all,
I use J2.0 with jsf-demo already installed.
In order to redeploy the jsf-demo:
When I copy the file "jsf-demo.war" (given here
http://portals.apache.org/bridges/download.html) in the deploy
directory, just a part of the war file is unzip...
In the "jetspeed2/webapps/jetspeed/jsf-demo" directory, I got only
"WEB-INF" directory which contains only "lib" directory which contains
only: "portals-bridges-jsf-1.0.jar" and "tomahawk-1.1.0.jar"... and so
the portlet is not working...
Did I do something wrong ?
Thanks,
Sebastien.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
