You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Ben Eng <be...@jetpen.com> on 2005/01/03 18:23:49 UTC
Re: error initializing tapestry in second webapp
I am also encoutering this java.lang.ExceptionInInitializerError, when
I have a second Tapestry webapp in the same EAR.
It appears to be caused by:
Caused by: java.lang.IllegalArgumentException: The Enum name must be unique, 'NONE' has already been added
at org.apache.commons.lang.enum.Enum.<init>(Enum.java:168)
at org.apache.tapestry.spec.BeanLifecycle.<init>(BeanLifecycle.java:67)
at org.apache.tapestry.spec.BeanLifecycle.<clinit>(BeanLifecycle.java:36)
... 20 more
Is there something special needed to package two Tapestry based
webapps together into the same EAR?
Ben
On Fri, Dec 24, 2004 at 05:44:52PM -0500, Ben Eng wrote:
> After successfully hot redeploying my EAR in BEA WebLogic Server
> 8.1SP4, I am seeing the following exception:
>
> java.lang.ExceptionInInitializerError
> at org.apache.tapestry.parse.SpecificationParser.(SpecificationParser.java:561)
> at org.apache.tapestry.ApplicationServlet.parseApplicationSpecification(ApplicationServlet.java:591)
> at org.apache.tapestry.ApplicationServlet.constructApplicationSpecification(ApplicationServlet.java:484)
> at org.apache.tapestry.ApplicationServlet.init(ApplicationServlet.java:426)
> at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1028)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
> at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:904)
>
> If I restart the application server, it runs fine.
>
> Is there some static information that causing a hot redeploy to fail
> to work properly?
>
> Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: error initializing tapestry in second webapp
Posted by Ben Eng <be...@jetpen.com>.
I have figured out the solution to this problem.
If commons-lang.jar is classloaded by both WARs via each respective
MANIFEST Class-Path from the parent's (EAR's) ClassLoader, the problem
arises. The solution is to rearrange the packaging so that
commons-lang.jar does NOT appear as a utility jar within the EAR, but
rather appears within each WAR's WEB-INF/lib.
Now both Tapestry-based Webapps are able to coexist in the same EAR.
Ben
On Mon, Jan 03, 2005 at 12:23:49PM -0500, Ben Eng wrote:
> I am also encoutering this java.lang.ExceptionInInitializerError, when
> I have a second Tapestry webapp in the same EAR.
>
> It appears to be caused by:
>
> Caused by: java.lang.IllegalArgumentException: The Enum name must be unique, 'NONE' has already been added
>
> at org.apache.commons.lang.enum.Enum.<init>(Enum.java:168)
> at org.apache.tapestry.spec.BeanLifecycle.<init>(BeanLifecycle.java:67)
> at org.apache.tapestry.spec.BeanLifecycle.<clinit>(BeanLifecycle.java:36)
> ... 20 more
>
> Is there something special needed to package two Tapestry based
> webapps together into the same EAR?
>
> Ben
>
>
> On Fri, Dec 24, 2004 at 05:44:52PM -0500, Ben Eng wrote:
> > After successfully hot redeploying my EAR in BEA WebLogic Server
> > 8.1SP4, I am seeing the following exception:
> >
> > java.lang.ExceptionInInitializerError
> > at org.apache.tapestry.parse.SpecificationParser.(SpecificationParser.java:561)
> > at org.apache.tapestry.ApplicationServlet.parseApplicationSpecification(ApplicationServlet.java:591)
> > at org.apache.tapestry.ApplicationServlet.constructApplicationSpecification(ApplicationServlet.java:484)
> > at org.apache.tapestry.ApplicationServlet.init(ApplicationServlet.java:426)
> > at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1028)
> > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
> > at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:904)
> >
> > If I restart the application server, it runs fine.
> >
> > Is there some static information that causing a hot redeploy to fail
> > to work properly?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org