-
15. Re: jbossws-2.0.1 released
rukus Oct 11, 2007 10:01 AM (in response to thomas.diesler)"sstrenn" wrote:
In order to get ant deploy-jboss42 to work on jbossws-2.0.1, I had to modify line 53 of build-deploy.xml:
was:
thirdpartylibs="${lib.dir}" />
changed to:
thirdpartylibs="${lib.dir}" stacklibs="${lib.dir}" />
thanks - i had same issue -
16. Re: jbossws-2.0.1 released
abdujaparov Oct 11, 2007 10:21 AM (in response to thomas.diesler)Hi, I've downloaded jbossws-2.0.1 and I've tryed to install it on jboss4.2.1, but I have problems.
The installation guide say that I must copy ant.properties.examples to ant.properties but in the root of jbossws there's not a file named ant.properties.examples, these are the file I have in jboss root directory:17/08/2007 18.58 <DIR> . 17/08/2007 18.58 <DIR> .. 11/10/2007 15.51 866 ant.properties 17/08/2007 18.58 <DIR> bin 17/08/2007 18.58 <DIR> build 17/08/2007 18.58 2.768 build.bat 17/08/2007 18.58 3.689 build.sh 17/08/2007 18.58 7.237 build.xml 17/08/2007 18.58 <DIR> docs 17/08/2007 18.58 <DIR> lib 17/08/2007 18.58 <DIR> tests 17/08/2007 18.58 <DIR> tools 17/08/2007 18.58 1.719 version.properties
I've only set the patch of jboss4.2.1 in the ant.properties file, then I've executed: ant deploy-jboss42 but this is the result:C:\jbossws-native-2.0.1.GA>ant deploy-jboss42 Buildfile: build.xml prepare: undeploy-jboss42-endorsed: BUILD FAILED C:\jbossws-native-2.0.1.GA\build\build-deploy.xml:62: The following error occurr ed while executing this line: C:\jbossws-native-2.0.1.GA\build\macros-deploy-native.xml:385: Directory does no t exist:C:\jbossws-native-2.0.1.GA\jboss-4.2.1.GA\lib\endorsed Total time: 0 seconds
How can I deploy jbossws2.0.1 on jboss4.2.1?
Thanks everybody, bye bye.
-
17. Re: jbossws-2.0.1 released
ptenn10 Oct 12, 2007 8:09 AM (in response to thomas.diesler)Hi all,
Thank you for posting the XML files and the fix to the build-deploy.xml.
We are running jbossws 1.4 on JBoss AS 4.0.4GA. We are not using EJB3.
Yesterday I attempted to upgrade to 2.0.1GA on my local development box.
I applied the 3 fixes that were described in this post:
[list=]Drop in jboss-service-no-ejb3.xml
[list=]Drop in jboss-beans-no-ejb3.xml
[list=]Modify line 53 in build-deploy.xml
And was able to successfully run the deploy-jboss40 task.
However, when I went to run, my server.log file has the following warning:2007-10-12 07:34:25,492 WARN [org.jboss.ejb.EjbModule] Could not load the org.jboss.ws.integration.jboss.ServiceEndpointInterceptor interceptor java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.integration.jboss.ServiceEndpointInterceptor
for every Stateless Session Bean that is deployed.
Here is the full stacktrace for one of the Stateless Session Bean deployments:2007-10-12 07:34:25,477 INFO [org.jboss.ejb.EjbModule] Deploying SBNotificationService 2007-10-12 07:34:25,492 WARN [org.jboss.ejb.EjbModule] Could not load the org.jboss.ws.integration.jboss.ServiceEndpointInterceptor interceptor java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.integration.jboss.ServiceEndpointInterceptor at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:89) at org.jboss.mx.loading.LoaderRepositoryClassLoader.loadClass(LoaderRepositoryClassLoader.java:90) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:89) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.ejb.EjbModule.addInterceptors(EjbModule.java:923) at org.jboss.ejb.EjbModule.initializeContainer(EjbModule.java:810) at org.jboss.ejb.EjbModule.createStatelessSessionContainer(EjbModule.java:614) at org.jboss.ejb.EjbModule.createContainer(EjbModule.java:569) at org.jboss.ejb.EjbModule.createService(EjbModule.java:344) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:330) at org.jboss.system.ServiceController.create(ServiceController.java:273) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy25.create(Unknown Source) at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:641) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.wsf.container.jboss40.DeployerInterceptor.create(DeployerInterceptor.java:76) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy26.create(Unknown Source) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:943) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:464) at java.lang.Thread.run(Thread.java:595)
Has anyone else experienced this? Is jbossws-2.0.1 still using the class org.jboss.ws.integration.jboss.ServiceEndpointInterceptor? I found this interceptor referenced in conf/standardjboss.xml and thought about commenting it out, but wanted to get a better understanding before doing so.
Thanks,
Philip Tenn -
18. Re: jbossws-2.0.1 released
richard_opalka Oct 12, 2007 8:33 AM (in response to thomas.diesler)How did you get org.jboss.ws.integration.jboss.ServiceEndpointInterceptor?
It should be org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor.
Richard -
19. Re: jbossws-2.0.1 released
ptenn10 Oct 12, 2007 4:01 PM (in response to thomas.diesler)Richard,
Thanks very much for your response.
I downloaded a pure copy of the JBoss AS 4.0.4GA and compared default/conf/standardjboss.xml to our /conf/standardjboss.xml.
It appears that in the pure 4.0.4GA, the interceptor is: org.jboss.ws.server.ServiceEndpointInterceptor
and we had changed this to
org.jboss.ws.integration.jboss.ServiceEndpointInterceptor
when we upgraded to jbossws-1.4. Although I wasn't the person on our team who did this upgrade to jbossws-1.4, this is what I can gather based on subversion revision messages.
So, as you suggested, I changed the interceptor to org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor in our /conf/standardjboss.xml:<container-configuration> <container-name>Standard Stateless SessionBean</container-name> <call-logging>false</call-logging> <invoker-proxy-binding-name>stateless-rmi-invoker</invoker-proxy-binding-name> <container-interceptors> <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor> <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor> <!-- CMT --> <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor> <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> <interceptor transaction="Container">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor</interceptor> <interceptor transaction="Container">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor> <!-- BMT --> <interceptor transaction="Bean">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor> <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor> <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> <interceptor transaction="Bean">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor</interceptor> <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor> </container-interceptors> <instance-pool>org.jboss.ejb.plugins.StatelessSessionInstancePool</instance-pool> <instance-cache></instance-cache> <persistence-manager></persistence-manager> <container-pool-conf> <MaximumSize>100</MaximumSize> </container-pool-conf> </container-configuration> <container-configuration> <container-name>Clustered Stateless SessionBean</container-name> <call-logging>false</call-logging> <invoker-proxy-binding-name>clustered-stateless-rmi-invoker</invoker-proxy-binding-name> <container-interceptors> <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor> <interceptor>org.jboss.ejb.plugins.CleanShutdownInterceptor</interceptor> <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor> <!-- CMT --> <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor> <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> <interceptor transaction="Container">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor </interceptor> <interceptor transaction="Container">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor> <!-- BMT --> <interceptor transaction="Bean">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor> <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor> <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> <interceptor transaction="Bean">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor </interceptor> <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor> </container-interceptors> <instance-pool>org.jboss.ejb.plugins.StatelessSessionInstancePool</instance-pool> <instance-cache></instance-cache> <persistence-manager></persistence-manager> <container-pool-conf> <MaximumSize>100</MaximumSize> </container-pool-conf> <cluster-config> <partition-name>${jboss.partition.name:DefaultPartition}</partition-name> </cluster-config> </container-configuration>
However, this class is not found either. I get the exception2007-10-12 15:40:44,728 WARN [org.jboss.ejb.EjbModule] Could not load the org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor interceptor java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor
Could you tell me which JAR this class (org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor) is supposed to reside in? I've tried going through the JARs inside the jbossws.sar directory, but have not been able to find it.
Thanks again for your help!
Philip Tenn -
20. Re: jbossws-2.0.1 released
richard_opalka Oct 15, 2007 3:52 AM (in response to thomas.diesler)Sorry for mistake. The correct class name is:
org.jboss.wsf.container.jboss40.ServiceEndpointInterceptor
Another important fact is we have tested JBossWS 2.0.1 on JBoss 4.0.5 GA not JBoss 4.0.4 GA.
Richard -
21. Re: jbossws-2.0.1 released
ptenn10 Oct 15, 2007 6:57 AM (in response to thomas.diesler)Richard,
Thank you again for all of your help. I changed my conf/standardjboss.xml to use:
org.jboss.wsf.container.jboss40.ServiceEndpointInterceptor
and no longer get the exceptions during deployment.Another important fact is we have tested JBossWS 2.0.1 on JBoss 4.0.5 GA not JBoss 4.0.4 GA.
I'll be doing a lot of testing on Jboss 4.0.4 GA, so I can definitely post successful results and/or issues I run into.
Thanks,
Philip Tenn -
22. Re: jbossws-2.0.1 released
ptenn10 Oct 15, 2007 9:19 AM (in response to thomas.diesler)PS one more question: I recall reading that jbossws 2.1 is going to support Apache CXF as a native stack.
Do you know approximately when jbossws 2.1 might go GA?
The main driving factor that has been pushing our upgrade from jbossws 1.4 to 2.0.1 GA has been the compatibility issues I encountered with jbossws 1.4 and Apache CXF.
If jbossws 2.1 is on the very near horizon, I might push for waiting for that instead of trying to integrate CXF with jboss 2.0.1 GA.
Thanks,
Philip Tenn -
23. Re: jbossws-2.0.1 released
ropalka Oct 17, 2007 5:53 AM (in response to thomas.diesler)I don't know that exactly. But it should be next year.
Richard