2:56 p.m.
I see a mix-up in our libraries, that leads to classloading errors in the testsuites (see
in
the bottom):
- sun-servlet in thirdparty was v2.4, although jboss-web comes with it's own
servlet-api
jars at v2.5. I changed thirdparty to v2.5, too
- jboss-ejb3x in deploy/ejb3.deployer/ should really be in server/xxx/lib, right? (I have
moved it).
- jboss-ejb3x and jboss-web.deployer/annotations-api.jar contain *some* duplicates (I
think
this causes the classloading errors). Unless we are going to create a new shared module,
I
believe we need to add the missing source code in our ejb3x module and not deploy
annotations-api.jar
- server-api.jar, jsp-api.jar, el-api.jar. We could have only one copy of them in the
server/xxx/lib directory, and not have it also tin the jboss-web.deployer/ dir
Comments/Suggestions?
06:43:05,648 INFO [TomcatDeployer] deploy, ctxPath=/,
warUrl=.../deploy/jboss-web.deployer/ROOT.war/
06:43:06,847 ERROR [Registry] Null component
jboss.web:type=JspMonitor,name=jsp,WebModule=//localhost/,J2EEApplication=none,J2EEServer=none
06:43:06,848 ERROR [BaseModelMBean] Exception invoking method addChild
java.lang.NoClassDefFoundError: javax/annotation/security/DeclareRoles
at
org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(WebAnnotationSet.java:244)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationListenerAnnotations(WebAnnotationSet.java:73)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:56)
at
org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:297)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1064)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:261)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4263)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at
jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown
Source)
at
java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown
Source)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5312)
at
jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown
Source)
at
java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown
Source)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:372)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
06:43:06,981 ERROR [BaseModelMBean] Exception invoking method init
javax.management.RuntimeErrorException: Error invoking method addChild
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:308)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5312)
at
jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown
Source)
at
java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown
Source)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:372)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at
jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown
Source)
at
java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown
Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start()V(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
Caused by: java.lang.NoClassDefFoundError: javax/annotation/security/DeclareRoles
at
org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation(WebAnnotationSet.java:244)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationListenerAnnotations(WebAnnotationSet.java:73)
at
org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:56)
at
org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:297)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1064)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:261)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4263)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at
jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown
Source)
at
java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown
Source)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5312)
at
jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown
Source)
at
java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown
Source)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at
org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:372)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
4:41 p.m.
We tend to make self-contained deployers. When bundling in jbossas only
the implementation should be in the .deployer. The javaee classes should
be in the server/lib dir.
Dimitris Andreadis wrote:
I see a mix-up in our libraries, that leads to classloading errors
in
the testsuites (see in
the bottom):
- sun-servlet in thirdparty was v2.4, although jboss-web comes with it's
own servlet-api
jars at v2.5. I changed thirdparty to v2.5, too
- jboss-ejb3x in deploy/ejb3.deployer/ should really be in
server/xxx/lib, right? (I have
moved it).
- jboss-ejb3x and jboss-web.deployer/annotations-api.jar contain *some*
duplicates (I think
this causes the classloading errors). Unless we are going to create a
new shared module, I
believe we need to add the missing source code in our ejb3x module and
not deploy
annotations-api.jar
- server-api.jar, jsp-api.jar, el-api.jar. We could have only one copy
of them in the
server/xxx/lib directory, and not have it also tin the
jboss-web.deployer/ dir
Comments/Suggestions?
4:47 p.m.
So
a) the api's (servlet-api.jar, jsp-api.jar, el-api.jar) go to server/lib?
b) should I try to enhance our ejb3x with the classes from annotations-api, and rename to
javaee5.jar? Where do I find those? (from the jboss-web sources?)
Scott M Stark wrote:
We tend to make self-contained deployers. When bundling in jbossas
only
the implementation should be in the .deployer. The javaee classes should
be in the server/lib dir.
Dimitris Andreadis wrote:
> I see a mix-up in our libraries, that leads to classloading errors in
> the testsuites (see in
> the bottom):
>
> - sun-servlet in thirdparty was v2.4, although jboss-web comes with it's
> own servlet-api
> jars at v2.5. I changed thirdparty to v2.5, too
>
> - jboss-ejb3x in deploy/ejb3.deployer/ should really be in
> server/xxx/lib, right? (I have
> moved it).
>
> - jboss-ejb3x and jboss-web.deployer/annotations-api.jar contain *some*
> duplicates (I think
> this causes the classloading errors). Unless we are going to create a
> new shared module, I
> believe we need to add the missing source code in our ejb3x module and
> not deploy
> annotations-api.jar
>
> - server-api.jar, jsp-api.jar, el-api.jar. We could have only one copy
> of them in the
> server/xxx/lib directory, and not have it also tin the
> jboss-web.deployer/ dir
>
> Comments/Suggestions?
>
>
5:21 p.m.
Dimitris Andreadis wrote:
So
a) the api's (servlet-api.jar, jsp-api.jar, el-api.jar) go to server/lib?
Yes.
b) should I try to enhance our ejb3x with the classes from
annotations-api, and rename to javaee5.jar? Where do I find those? (from
the jboss-web sources?)
If we are merging, the javaee 5 apis, then the question is why not
collapse jboss-j2ee.jar, ejb3, common annotation (which is in the ejb3x
module), webserivcies, etc. The main reason we have not done this in the
past is related to allowing for minimal selection of features. However,
with the current dependencies this is an illusion as there is coupling
between ejb3, web, and webservices.
5:27 p.m.
I think we need to create a new independent module for merging all that stuff and use it
across projects.
The quick&dirty solution would be for me to just copy the missing files in the jboss
ejb3x
module.
Scott M Stark wrote:
Dimitris Andreadis wrote:
> So
>
> a) the api's (servlet-api.jar, jsp-api.jar, el-api.jar) go to server/lib?
>
Yes.
> b) should I try to enhance our ejb3x with the classes from
> annotations-api, and rename to javaee5.jar? Where do I find those? (from
> the jboss-web sources?)
>
If we are merging, the javaee 5 apis, then the question is why not
collapse jboss-j2ee.jar, ejb3, common annotation (which is in the ejb3x
module), webserivcies, etc. The main reason we have not done this in the
past is related to allowing for minimal selection of features. However,
with the current dependencies this is an illusion as there is coupling
between ejb3, web, and webservices.
6524
days inactive
6524
days old
jboss-development@lists.jboss.org
4 comments
2 participants
participants (2)
-
Dimitris Andreadis -
Scott M Stark