August 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Re: jbossWS 2.0.1 and JDK 1.6

by koganty

I'm using the endorsed lib mechanism as suggested and I have the following in the endorsed folder and it works .. jboss-ssaj.jar jboss-jaxws.jar jboss-jaxrpc.jar jaxb-impl.jar jaxb-api.jar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080180#4080180 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080180

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Problem with inheritance and JBossWS

by koganty

JBossWS 2.0.1 release notes say that JBWS-1702 is fixed which solves the inheritance problem, but looks like it is still not fixed. I'm usinf JBossWS 2.0.1 with JBoss 4.0.5. I've tried both jdk 1.5 anf jdk 1.6. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080179#4080179 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080179

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: NullPointerException with jbossws 2.0.1

by koganty

And here is the bug : http://jira.jboss.com/jira/browse/JBWS-1800 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080172#4080172 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080172

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: NullPointerException with jbossws 2.0.1

by koganty

Yes that was the problem. I think we'd need to file Bug for this. Having -Dcom.sun.management.jmxremote in the startup args prevents the jbossws from coming up properly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080170#4080170 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080170

18 years, 8 months

1
0
0 / 0

[JBossWS] - Please Help WS Deployment Error...

by mendaye

Hello All: I have converted existing EJB to Web Services by adding service end point to ejb-jar.xml file, creating all the artifact using ant task. I put the WSDL and other XML files in the right place before I deploy it. However, I am getting the following error when I deploy it. I've already spent looking this issue several hours but I was not able to figure this out. Please please help me. Here is the error I am seeing... 2007-08-31 14:48:18,156 DEBUG [org.jboss.ejb.StatelessSessionContainer] Mapped Container method getPrimaryKey HASH -131865408 2007-08-31 14:48:18,156 DEBUG [org.jboss.ejb.StatelessSessionContainer] Mapped Container method isIdentical HASH 285457048 2007-08-31 14:48:18,156 DEBUG [org.jboss.ejb.StatelessSessionContainer] Mapped getLocationNameForDevice HASH -1630061606to public java.lang.String com.panduit.pvng.service.api.db.ejb.PVNGDeviceBean.getLocationNameForDevice(java.lang.String) throws com.panduit.pvng.service.exception.PVNGAPIException 2007-08-31 14:48:18,156 DEBUG [org.jboss.ejb.StatelessSessionContainer] Mapped getConnectivityStatus HASH -754342036to public boolean com.panduit.pvng.service.api.db.ejb.PVNGDeviceBean.getConnectivityStatus(java.lang.String,int) throws com.panduit.pvng.service.exception.PVNGAPIException 2007-08-31 14:48:18,156 DEBUG [org.jboss.ejb.StatelessSessionContainer] Mapped getLocationHierarchyForDevice HASH -275144890to public java.lang.String com.panduit.pvng.service.api.db.ejb.PVNGDeviceBean.getLocationHierarchyForDevice(java.lang.String) throws com.panduit.pvng.service.exception.PVNGAPIException 2007-08-31 14:48:18,156 DEBUG [org.jboss.ejb.StatelessSessionContainer] Initialization failed jboss.j2ee:jndiName=ejb/PVNGDevice,service=EJB java.lang.NoSuchMethodException: Not found in bean class: public abstract void javax.ejb.EJBObject.remove() throws java.rmi.RemoteException,javax.ejb.RemoveException at org.jboss.ejb.SessionContainer.setUpBeanMappingImpl(SessionContainer.java:213) at org.jboss.ejb.SessionContainer.setupBeanMapping(SessionContainer.java:264) at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:166) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) at sun.reflect.GeneratedMethodAccessor3.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.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:330) 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.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy53.create(Unknown Source) at org.jboss.ejb.EjbModule.createService(EjbModule.java:379) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) at sun.reflect.GeneratedMethodAccessor3.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.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 $Proxy33.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.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:99) 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 $Proxy34.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.GeneratedMethodAccessor8.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 $Proxy6.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.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.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) 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.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) 2007-08-31 14:48:18,156 WARN [org.jboss.system.ServiceController] Problem creating service jboss.j2ee:jndiName=ejb/PVNGDevice,service=EJB java.lang.NoSuchMethodException: Not found in bean class: public abstract void javax.ejb.EJBObject.remove() throws java.rmi.RemoteException,javax.ejb.RemoveException at org.jboss.ejb.SessionContainer.setUpBeanMappingImpl(SessionContainer.java:213) at org.jboss.ejb.SessionContainer.setupBeanMapping(SessionContainer.java:264) at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:166) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) at sun.reflect.GeneratedMethodAccessor3.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.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:330) 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.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy53.create(Unknown Source) at org.jboss.ejb.EjbModule.createService(EjbModule.java:379) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) at sun.reflect.GeneratedMethodAccessor3.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.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 $Proxy33.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.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:99) 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 $Proxy34.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.GeneratedMethodAccessor8.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 $Proxy6.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.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.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) 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.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) 2007-08-31 14:48:18,171 DEBUG [org.jboss.ejb.EjbModule] Bound jmxName=jboss.j2ee:jndiName=ejb/PVNGDevice,service=EJB, hash=1203048510into Registry 2007-08-31 14:48:18,171 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:jndiName=ejb/PVNGDiscoveryAPI,service=EJB View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080159#4080159 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080159

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Problem with publishing a web service

by AnisBM

Hi all, I finally found it. I'm using a JBoss 4.0.5 server with the JBossWS 1.2.0 SP1 plugin. The jar file jbossws-client was uncomplete. So I replaced it by the one I found in the (eclipse) plugin soapui.jbosside.wstools lib directory. Now it works !!!!!!! :-))))) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080067#4080067 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080067

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Strange - Entry Point not receive WS Message data

by tokrishnakumar

what is your input SOAP XML?Can you post it.. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080058#4080058 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080058

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: 2 ejb3s exposed as web services. Can't have same methods

by sursha

Created JIRA issue JBWS-1799. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080053#4080053 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080053

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: How to import relative schemas?

by oskar.carlstedt

I posted i Jira issue about this [url]http://jira.jboss.org/jira/browse/JBWS-1798[url]. ******************************************* I deploy an ear file in JBoss5 that contains a war and a jar fil. The jar file contains a SLSB and the war file contains the web service (implemented as a Provider[SOAPMessage]). The war file has the following file structure in the the WEB-INF/wsdl folder: | WEB-INF/wsdl | my-service.wsdl | /imported | /my-service | /1.0-SNAPSHOT | my-service.xsd | /common | /1.0-SNAPSHOT | common.xsd | the wsdl file has a schema import like <xsd:import schemaLocation="imported/my-service/1.0-SNAPSHOT/my-service.xsd" .../> the my-service.xsd imports the common.xsd file with the following import statement <xsd:import schemaLocation="../../common/1.0-SNAPSHOT/common.xsd" .../> Having this configuration will put JBoss into trouble. The error message sent is telling med that parent paths are not allowed, and pointing out to use getParent() instead. So I setting the schemaLocation attribute to getParent()/getParent()/.... will point out another path, but it is completely wrong. ******************************************* Best /Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080051#4080051 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080051

18 years, 8 months

1
0
0 / 0

[JBossWS] - Dreaded Multiple context root

by nickarls

Hi, I'm using Seam 2.0.0b1 and JBoss 4.2.1GA and have tried to follow the wiki on encrypted web services and the Seam manual and have come up with | @Remote | public interface FooBeanI { | ... | | @Stateless | @WebService(name="fooService", serviceName="fooService") | @WebContext(contextRoot="/foo") //added this after suggestion after reading the forum | @Name("fooService") | public class FooBean implements FooBeanI { | ... | and put the | jboss-wsse-client.xml | jboss-wsse-server.xml | wsse.keystore | wsse.truststore | under WEB-INF and standard-jaxws-endpoint-config.xml under the jar META-INF But I still get the | 09:12:52,498 ERROR [ServiceEndpointPublisher] Cannot obtain waURL for: OSTi.ear/ | OSTi.jar | 09:12:52,498 ERROR [MainDeployer] Could not create deployment: file:/C:/Java/jbo | ss-4.2.1.GA/server/default/deploy/OSTi.ear/OSTi.jar/ | org.jboss.deployment.DeploymentException: Cannot create service endpoint; - nest | ed throwable: (org.jboss.ws.WSException: Multiple context root not supported) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079833#4079833 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079833

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Problem with publishing a web service

by mendaye

I would use ant task to do this.   View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079795#4079795 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079795

18 years, 8 months

1
0
0 / 0

[JBossWS] - Problem Converting EJB2.1 to Web Services

by mendaye

We have existing Session EJB and trying to convert it to Web Services. I have created all the WS artifact using ant task and also modify ejb-jar.xml to include the service point. However, when I deploy as part of an ear file I am getting the following errors. We are using JBOSS 4.0.4. Based on JBOSS documenetaion, I don't need to include any exteranal jar for we services support. Our ear deployed on a different directory "pvng" but we copy all the files, and dir from default. As shown below in the server log commons-discovery.jar, saaj.jar, wsdl4j.jar, commons-logging.jar, jaxrpc.jar? Do I need to get all this JARs? I am not sure what is going on here? Do I need to include all jars into a lib directory inside ear file? Help... Pls look the error message I got in server log below. 2007-08-30 15:41:31,592 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/de.danet.an.wfcore-ejbs.jar references URL file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/lib/commons-discovery.jar which could not be opened, entry ignored org.jboss.deployment.DeploymentException: url file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/lib/commons-discovery.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:211) at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1119) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:873) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:881) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:798) 2007-08-30 15:41:31,592 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at de.danet.an.wfcore-ejbs.jar entry is lib/saaj.jar 2007-08-30 15:41:31,592 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/de.danet.an.wfcore-ejbs.jar references URL file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/lib/saaj.jar which could not be opened, entry ignored org.jboss.deployment.DeploymentException: url file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/lib/saaj.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:211) at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1119) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:873) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:881) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:798) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2007-08-30 15:41:31,592 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/de.danet.an.wfcore-ejbs.jar references URL file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/lib/wsdl4j.jar which could not be opened, entry ignored org.jboss.deployment.DeploymentException: url file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/lib/wsdl4j.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:211) at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1119) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:873) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:881) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:798) 2007-08-30 15:41:31,592 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at de.danet.an.wfcore-ejbs.jar entry is lib/commons-logging.jar 2007-08-30 15:41:31,592 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/de.danet.an.wfcore-ejbs.jar references URL file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/lib/commons-logging.jar which could not be opened, entry ignored org.jboss.deployment.DeploymentException: url file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/lib/commons-logging.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:211) 2007-08-30 15:41:31,592 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at de.danet.an.wfcore-ejbs.jar entry is lib/jaxrpc.jar 2007-08-30 15:41:31,592 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/de.danet.an.wfcore-ejbs.jar references URL file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/lib/jaxrpc.jar which could not be opened, entry ignored org.jboss.deployment.DeploymentException: url file:/C:/DEV/JBoss/jboss-4.0.4.GA/server/pvng/tmp/deploy/tmp30558pvng.ear-contents/lib/jaxrpc.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:211) at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1119) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:873) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:881) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079794#4079794 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079794

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Problem with publishing a web service

by AnisBM

Hi, I can only set the jbossws-tools dirctory to C:\FitNetManager\Jboss-4.0.5.GA\bin. It was already done. But JBOSS_HOME is automaticaly in batch wstools.bat (JBOSS_HOME=%DIRNAME%\..). So I can't change it !!! I don't know what to do... I think it may be a problem of library but I have no idea which one is concerned. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079608#4079608 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079608

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Problem with publishing a web service

by omatzura

Hi, you need to set JBOSS_HOME to C:\FitNetManager\Jboss-4.0.5.GA and set the jbossws-tools directory to C:\FitNetManager\Jboss-4.0.5.GA\bin if you do this.. what error do you get? regards! /Ole eviware.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079600#4079600 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079600

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Problem with publishing a web service

by AnisBM

Hi, The JBOSS_HOME has to be set on 'C:\FitNetManager\Jboss-4.0.5.GA\bin' to find the wtools.bat. However, I changed it but it still doesn't work... :-( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079596#4079596 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079596

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS-Security with JAX-RPC

by FabrizioLXXIII

It seems to work! Thanks a lot! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079592#4079592 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079592

18 years, 8 months

1
0
0 / 0

[JBossWS] - Deploying EJB Endpoint Web Services on Jboss-4.0.5.GA

by letincho5

Hi, I'm in a very similar situacion than: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060099#4060099 My web services runs on jboss 4.0.3_SP1 without problems. Unfortunatly on jboss 4.0.5.GA it doesn't work. I guess there is a deploy problem: 08:49:45,421 INFO [EARDeployer] Init J2EE application: file:/C:/Proyectos/Gauss/jboss-4.0.5.GA/jboss-4.0.5.GA/server/default/deploy/WsVmonEAR.ear/ 08:49:46,015 INFO [EjbModule] Deploying VideoServerEJB 08:49:46,625 WARN [PortComponentMetaData] <wsdl-port> element in webservices.xml not namespace qualified: VideoServerServicePort 08:49:47,281 ERROR [MainDeployer] Could not create deployment: file:/C:/Proyectos/Gauss/jboss-4.0.5.GA/jboss-4.0.5.GA/server/default/deploy/WsVmonEAR.ear/WsVmon.jar/ java.lang.NoSuchMethodError: com.ibm.wsdl.xml.WSDLReaderImpl.setEntityResolver(Lorg/xml/sax/EntityResolver;)V at org.jboss.ws.metadata.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:142) at org.jboss.ws.metadata.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:273) at org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBuilder.java:94) at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:85) The wsdl and mapping files were generated by the SUN's JWSDP (http://java.sun.com/webservices/downloads/previous/index.jsp) This is the service endpoint | package com.gauss.vmon.ws.endpoint; | | import java.rmi.Remote; | import java.rmi.RemoteException; | | import com.gauss.vmon.ws.data.CameraData; | import com.gauss.vmon.ws.data.Credential; | | public interface VideoServerService extends Remote { | | | /** | * @param vsfId | * @return | */ | public CameraData getCameraData(String vsfId) throws RemoteException; | | /** | * @param vsfId | * @return | */ | public Credential getCredential(String vsfId) throws RemoteException;; | | } The JWSDP's config.xml file | <?xml version="1.0" encoding="UTF-8"?> | <configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config"> | <service name="VideoServerService" | targetNamespace="http://ws.vmon.gauss.com" | typeNamespace="http://ws.vmon.gauss.com/types" | packageName="com.gauss.vmon.ws"> | <interface name="com.gauss.vmon.ws.endpoint.VideoServerService"/> | </service> | </configuration> My webservices.xml: | <webservices xmlns="http://java.sun.com/xml/ns/j2ee" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd" | version="1.1"> | <webservice-description> | <webservice-description-name> | VideoServerService | </webservice-description-name> | <wsdl-file>META-INF/wsdl/VideoServerService.wsdl</wsdl-file> | <jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file> | <port-component> | <port-component-name>VideoServerService</port-component-name> | <wsdl-port>VideoServerServicePort</wsdl-port> | <service-endpoint-interface> | com.gauss.vmon.ws.endpoint.VideoServerService | </service-endpoint-interface> | <service-impl-bean> | <ejb-link>VideoServerEJB</ejb-link> | </service-impl-bean> | </port-component> | </webservice-description> | </webservices> | And the wsdl and mapping files: wsdl | <?xml version="1.0" encoding="UTF-8"?> | | <definitions name="VideoServerService" targetNamespace="http://ws.vmon.gauss.com" xmlns:tns="http://ws.vmon.gauss.com" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:ns2="http://ws.vmon.gauss.com/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"> | <types> | <schema targetNamespace="http://ws.vmon.gauss.com/types" xmlns:tns="http://ws.vmon.gauss.com/types" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema"> | <complexType name="CameraData"> | <sequence> | <element name="apiCode" type="string" nillable="true"/> | <element name="channel" type="int"/> | <element name="ip" type="string" nillable="true"/> | <element name="password" type="string" nillable="true"/> | <element name="port" type="int"/> | <element name="status" type="int"/> | <element name="statusDescription" type="string" nillable="true"/> | <element name="username" type="string" nillable="true"/> | <element name="vsfId" type="string" nillable="true"/></sequence></complexType> | <complexType name="Credential"> | <sequence> | <element name="password" type="string" nillable="true"/> | <element name="status" type="int"/> | <element name="statusDescription" type="string" nillable="true"/> | <element name="username" type="string" nillable="true"/></sequence></complexType></schema></types> | <message name="VideoServerService_getCameraData"> | <part name="vsfId" type="xsd:string"/></message> | <message name="VideoServerService_getCameraDataResponse"> | <part name="result" type="ns2:CameraData"/></message> | <message name="VideoServerService_getCredential"> | <part name="vsfId" type="xsd:string"/></message> | <message name="VideoServerService_getCredentialResponse"> | <part name="result" type="ns2:Credential"/></message> | <portType name="VideoServerService"> | <operation name="getCameraData" parameterOrder="vsfId"> | <input message="tns:VideoServerService_getCameraData"/> | <output message="tns:VideoServerService_getCameraDataResponse"/></operation> | <operation name="getCredential" parameterOrder="vsfId"> | <input message="tns:VideoServerService_getCredential"/> | <output message="tns:VideoServerService_getCredentialResponse"/></operation></portType> | <binding name="VideoServerServiceBinding" type="tns:VideoServerService"> | <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/> | <operation name="getCameraData"> | <soap:operation soapAction=""/> | <input> | <soap:body use="literal" namespace="http://ws.vmon.gauss.com"/></input> | <output> | <soap:body use="literal" namespace="http://ws.vmon.gauss.com"/></output></operation> | <operation name="getCredential"> | <soap:operation soapAction=""/> | <input> | <soap:body use="literal" namespace="http://ws.vmon.gauss.com"/></input> | <output> | <soap:body use="literal" namespace="http://ws.vmon.gauss.com"/></output></operation></binding> | <service name="VideoServerService"> | <port name="VideoServerServicePort" binding="tns:VideoServerServiceBinding"> | <soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions> | mapping.xml | <?xml version="1.0" encoding="UTF-8"?> | <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd"> | <package-mapping> | <package-type>com.gauss.vmon.ws</package-type> | <namespaceURI>http://ws.vmon.gauss.com/types</namespaceURI> | </package-mapping> | <package-mapping> | <package-type>com.gauss.vmon.ws</package-type> | <namespaceURI>http://ws.vmon.gauss.com</namespaceURI> | </package-mapping> | <java-xml-type-mapping> | <java-type>com.gauss.vmon.ws.data.CameraData</java-type> | <root-type-qname xmlns:typeNS="http://ws.vmon.gauss.com/types">typeNS:CameraData</root-type-qname> | <qname-scope>complexType</qname-scope> | <variable-mapping> | <java-variable-name>apiCode</java-variable-name> | <xml-element-name>apiCode</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>channel</java-variable-name> | <xml-element-name>channel</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>ip</java-variable-name> | <xml-element-name>ip</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>password</java-variable-name> | <xml-element-name>password</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>port</java-variable-name> | <xml-element-name>port</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>status</java-variable-name> | <xml-element-name>status</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>statusDescription</java-variable-name> | <xml-element-name>statusDescription</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>username</java-variable-name> | <xml-element-name>username</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>vsfId</java-variable-name> | <xml-element-name>vsfId</xml-element-name> | </variable-mapping> | </java-xml-type-mapping> | <java-xml-type-mapping> | <java-type>com.gauss.vmon.ws.data.Credential</java-type> | <root-type-qname xmlns:typeNS="http://ws.vmon.gauss.com/types">typeNS:Credential</root-type-qname> | <qname-scope>complexType</qname-scope> | <variable-mapping> | <java-variable-name>password</java-variable-name> | <xml-element-name>password</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>status</java-variable-name> | <xml-element-name>status</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>statusDescription</java-variable-name> | <xml-element-name>statusDescription</xml-element-name> | </variable-mapping> | <variable-mapping> | <java-variable-name>username</java-variable-name> | <xml-element-name>username</xml-element-name> | </variable-mapping> | </java-xml-type-mapping> | <service-interface-mapping> | <service-interface>com.gauss.vmon.ws.VideoServerService</service-interface> | <wsdl-service-name xmlns:serviceNS="http://ws.vmon.gauss.com">serviceNS:VideoServerService</wsdl-service-name> | <port-mapping> | <port-name>VideoServerServicePort</port-name> | <java-port-name>VideoServerServicePort</java-port-name> | </port-mapping> | </service-interface-mapping> | <service-endpoint-interface-mapping> | <service-endpoint-interface>com.gauss.vmon.ws.endpoint.VideoServerService</service-endpoint-interface> | <wsdl-port-type xmlns:portTypeNS="http://ws.vmon.gauss.com">portTypeNS:VideoServerService</wsdl-port-type> | <wsdl-binding xmlns:bindingNS="http://ws.vmon.gauss.com">bindingNS:VideoServerServiceBinding</wsdl-binding> | <service-endpoint-method-mapping> | <java-method-name>getCameraData</java-method-name> | <wsdl-operation>getCameraData</wsdl-operation> | <method-param-parts-mapping> | <param-position>0</param-position> | <param-type>java.lang.String</param-type> | <wsdl-message-mapping> | <wsdl-message xmlns:wsdlMsgNS="http://ws.vmon.gauss.com">wsdlMsgNS:VideoServerService_getCameraData</wsdl-message> | <wsdl-message-part-name>vsfId</wsdl-message-part-name> | <parameter-mode>IN</parameter-mode> | </wsdl-message-mapping> | </method-param-parts-mapping> | <wsdl-return-value-mapping> | <method-return-value>com.gauss.vmon.ws.data.CameraData</method-return-value> | <wsdl-message xmlns:wsdlMsgNS="http://ws.vmon.gauss.com">wsdlMsgNS:VideoServerService_getCameraDataResponse</wsdl-message> | <wsdl-message-part-name>result</wsdl-message-part-name> | </wsdl-return-value-mapping> | </service-endpoint-method-mapping> | <service-endpoint-method-mapping> | <java-method-name>getCredential</java-method-name> | <wsdl-operation>getCredential</wsdl-operation> | <method-param-parts-mapping> | <param-position>0</param-position> | <param-type>java.lang.String</param-type> | <wsdl-message-mapping> | <wsdl-message xmlns:wsdlMsgNS="http://ws.vmon.gauss.com">wsdlMsgNS:VideoServerService_getCredential</wsdl-message> | <wsdl-message-part-name>vsfId</wsdl-message-part-name> | <parameter-mode>IN</parameter-mode> | </wsdl-message-mapping> | </method-param-parts-mapping> | <wsdl-return-value-mapping> | <method-return-value>com.gauss.vmon.ws.data.Credential</method-return-value> | <wsdl-message xmlns:wsdlMsgNS="http://ws.vmon.gauss.com">wsdlMsgNS:VideoServerService_getCredentialResponse</wsdl-message> | <wsdl-message-part-name>result</wsdl-message-part-name> | </wsdl-return-value-mapping> | </service-endpoint-method-mapping> | </service-endpoint-interface-mapping> | </java-wsdl-mapping> | Thanks for your help Martín View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079585#4079585 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079585

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Problem with publishing a web service

by omatzura

Hi! hmm.. the JBOSS_HOME variable looks a bit strange: "C:\FitNetManager\Jboss-4.0.5.GA\bin\\.." can you set it to "C:\FitNetManager\Jboss-4.0.5.GA" somehow? regards! /Ole eviware.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079562#4079562 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079562

18 years, 8 months

1
0
0 / 0

[JBossWS] - Problem with publishing a web service

by AnisBM

Hi all, I have this message when I try to publish a class as a web service : Running JBossWS wstools for [jbossws-test1] directory: C:\FitNetManager\workspaces\workspaceFitNet\jbossws-test1 command: cmd.exe /C C:\FitNetManager\Jboss-4.0.5.GA\bin\wstools.bat -cp bin -config C:\DOCUME~1\Anis\LOCALS~1\Temp\wstools-config55960.xml -dest C:\FitNetManager\workspaces\workspaceFitNet\jbossws-test1\src\java =========================================================================" . WSTools Environment . JBOSS_HOME: C:\FitNetManager\Jboss-4.0.5.GA\bin\\.. . JAVA: C:\Program Files\Java\jdk1.5.0_05\bin\java . JAVA_OPTS: . =========================================================================" . Exception in thread "main" java.lang.NoClassDefFoundError: javax/jws/soap/SOAPBinding$ParameterStyle at org.jboss.ws.tools.helpers.ToolsHelper.handleJavaToWSDLGeneration(ToolsHelper.java:106) at org.jboss.ws.tools.WSTools.process(WSTools.java:133) at org.jboss.ws.tools.WSTools.generate(WSTools.java:69) at org.jboss.ws.tools.WSTools.generate(WSTools.java:119) at org.jboss.ws.tools.WSTools.main(WSTools.java:58) I don't understand what is the matter. I'm working on Eclipse 3.2 with JBoss 4.0.5GA, JBossWS 1.2.0SP1, jdk 1.5. Could someone help me ??? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079482#4079482 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079482

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: jbossws with apache

by palin

"gerry744" wrote : I'm using Jboss behind apache. | '/jbossws/services' works fine, the wsdls's work fine, but the actual services don't work. They do work if I connect directly on port 8080, but not through apache. Everything else is working fine through apache. | If I try connecting a browser to the actual service via apache, instead of seeing the service I just get "http GET not supported". | | Anyone know what I'm doing wrong ? | | I'm using jboss 4.2.1, jbossws 2.0.1, apache2 on another machine, jk 1.2, all on gentoo. | | Thanks! I would check what url apache is actually trying to connect to; I mean, it's ok that you get a "http GET not supported" if you access an endpoint using your browser. As a matter of fact, endpoints support POST, GET is supposed to work only for wsdl retrieval calls. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079450#4079450 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079450

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: NullPointerException with jbossws 2.0.1

by gumnaam

By any chance do you set the following property in your run.{sh/conf/bat} file ? -Dcom.sun.management.jmxremote I was having the exact same problem, when I had the above string, in my run.conf. I had put it there to enable jmx local agent, so that I can use jconsole against jboss. But somehow , having this property, prevented, the NativeServerConfig MBean from being published. Once I removed the string from my run.conf , the problem went away. thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079327#4079327 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079327

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WIKI down

by fgsouza

Any schedule to have the Wiki back online? Could you please mirror the JBossWS FAQ at the temporary address? (http://labs.jboss.com/jbossws/docs/index.html ) []s Fabiano G. Souza View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079305#4079305 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079305

18 years, 8 months

1
0
0 / 0

[JBossWS] - New user needs help

by AnisBM

Hi all, I'm working on project already developped by someone else and i need some help. I have to test a web service in this project. I found the interface of the web service but not a class implementing it nor a wsdl file. Is this normal ??? I'm working with JBossWS 1.2.0 & JBoss IDE 2.0. Sorry for my broken english and for the question if it is too simple :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079259#4079259 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079259

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Cannot find child element - with namespace

by omatzura

Hi! actually no.. the WSDL Contract uses rpc/literal (not rpc/encoded) which should be supported by xfire.. strange.. regards, /Ole eviware.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079150#4079150 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079150

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Cannot find child element - with namespace

by jmaasing

Thank you, since XFire seems to not support rpc/encoded this is most probably the problem. Thanks for the pointer. http://xfire.codehaus.org/Client+and+Server+Stub+Generation+from+WSDL View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079145#4079145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079145

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Cannot find child element - with namespace

by omatzura

Hi! this looks like a problem with the xfire client; when using RPC-style operations, the different part elements must not have a namespace in accordance with the basic profile, which states; R2735 An ENVELOPE described with an rpc-literal binding MUST place the part accessor elements for parameters and return value in no namespace. Hope this helps! regards, /Ole eviware.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079124#4079124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079124

18 years, 8 months

1
0
0 / 0

[JBossWS] - Cannot find child element - with namespace

by jmaasing

We have a problem with an XFire generated client. The SOAP request generated from the XFire client When we try to access the JBoss 4.0.5GA-WS service we send the following SOAP request: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | <soap:Body> | <ns1:getInvoiceData xmlns:ns1="http://ws.test.se/jaws"> | <ns1:InvoiceRequest xmlns:ns2="http://jaws.ws.test.se/jaws"> | <ns1:fromInvDate>2006-02-28T14:41:13.860+01:00</ns1:fromInvDate> | </ns1:InvoiceRequest> | </ns1:getInvoiceData> | </soap:Body> | </soap:Envelope> | This request generates an error: <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'> | <env:Header/> | <env:Body> | <env:Fault xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'> | <faultcode>env:Client</faultcode> | <faultstring>Cannot find child element: InvoiceRequest</faultstring> | </env:Fault> | </env:Body> | </env:Envelope> If we open the WSDL in SoapUI it generates a request that looks like this: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:jaws="http://ws.test.com/jaws"> | <soapenv:Header/> | <soapenv:Body> | <jaws:getInvoiceData> | <InvoiceRequest> | <jaws:fromInvDate>?</jaws:fromInvDate> | </InvoiceRequest> | </jaws:getInvoiceData> | </soapenv:Body> | </soapenv:Envelope> Notice the missing jaws namespace on InvoiceRequest (exactly what the errormessage said :)). The question is if XFire is producing invalid SOAP Request based on the WSDL? Is there a problem on the JBoss-WS side? Or is there something amiss in the document encoding perhaps? WSDL. | <definitions name='InvoiceService' | targetNamespace='http://ws.test.com/jaws' | xmlns='http://schemas.xmlsoap.org/wsdl/' | xmlns:ns1='http://jaws.ws.test.com/jaws' | xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' | xmlns:tns='http://ws.test.com/jaws' | xmlns:xsd='http://www.w3.org/2001/XMLSchema'> | <types> | <schema elementFormDefault='qualified' targetNamespace='http://jaws.ws.test.com/jaws' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:ns1='http://ws.test.com/jaws' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:tns='http://jaws.ws.test.com/jaws' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> | <import namespace='http://ws.test.com/jaws'/> | <simpleType name='String1'> | <restriction base='string'> | <minLength value='0'/> | <maxLength value='1'/> | </restriction> | </simpleType> | | </schema> | <schema elementFormDefault='qualified' targetNamespace='http://ws.test.com/jaws' xmlns='http://www.w3.org/2001/XMLSchema' xmlns:ns2='http://jaws.ws.test.com/jaws' xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/' xmlns:tns='http://ws.test.com/jaws' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> | <import namespace='http://jaws.ws.test.com/jaws'/> | | <complexType name='InvoiceData'> | <sequence> | <element name='address' type='ns2:String1'/> | </sequence> | </complexType> |  | <complexType name='InvoiceRequest'> | <sequence> | <element name='fromInvDate' nillable='true' type='ns2:String1'/> | </sequence> | </complexType> | </schema> | </types> | <message name='Invoice_getInvoiceData'> | <part name='InvoiceRequest' type='tns:InvoiceRequest'/> </message> <message name='Invoice_getInvoiceDataResponse'> | <part name='result' type='tns:InvoiceData'/> </message> | | <portType name='Invoice'> | <operation name='getInvoiceData' parameterOrder='InvoiceRequest'> | <input message='tns:Invoice_getInvoiceData'/> | <output message='tns:Invoice_getInvoiceDataResponse'/> | <fault message='tns:WebServiceFault' name='WebService'/> | </operation> | </portType> | <binding name='InvoiceBinding' type='tns:Invoice'> | <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/> | | <operation name='getInvoiceData'> | <soap:operation soapAction=''/> | <input> | <soap:body namespace='http://ws.test.com/jaws' use='literal'/> | </input> | <output> | <soap:body namespace='http://ws.test.com/jaws' use='literal'/> | </output> | </operation> | </binding> | | <service name='InvoiceService'> | <port binding='tns:InvoiceBinding' name='InvoicePort'> | </port> | </service> | | </definitions> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079120#4079120 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079120

18 years, 8 months

1
0
0 / 0

[JBossWS] - jbossws with apache

by gerry744

I'm using Jboss behind apache. '/jbossws/services' works fine, the wsdls's work fine, but the actual services don't work. They do work if I connect directly on port 8080, but not through apache. Everything else is working fine through apache. If I try connecting a browser to the actual service via apache, instead of seeing the service I just get "http GET not supported". Anyone know what I'm doing wrong ? I'm using jboss 4.2.1, jbossws 2.0.1, apache2 on another machine, jk 1.2, all on gentoo. Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079088#4079088 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079088

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: How to import relative schemas?

by oskar.carlstedt

Some more info... The schemas I'm using are including other schemas too, that are also referenced by a relative schema location. So it's is i kind of nested schema imports in several schemas. All schemas are not directly located under WEB-INF/wsdl, instead they are located under their resp. http-path on another schema-server, e.g. WEB-INF/wsdl/a/a.xsd, WEB-INF/wsdl/b/b.xsd //Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079035#4079035 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079035

18 years, 8 months

1
0
0 / 0

[JBossWS] - How to import relative schemas?

by oskar.carlstedt

Hi All! I cannot not manage to create a deployment in Boss-5.0.0.Beta2 where I import schemas by relative paths. Using "../"-paths are not allowed (getting an exception telling me that parent paths are not allowed). Parent paths are allowed in JBossWS 1.2.1.GA on JBoss 4.0.5.GA. What I'm actually doing is that I create my wsdl and schema files by hand, i.e. contract first development. Then I create an endpoint provider to handle incoming requests. In the endpoint I set the wsdl location to WEB-INF/wsdl/... This is working, JBoss finds my wsdl file but cannot resolve schema the relative path of imported schemas. Does anyone know how to solve this problem? Thanks Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079033#4079033 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079033

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Type Substitution doesn't work with Schema2Java Client a

by M_schumpa

hi thomas, do you think there is a quick fix for this problem? I'm asking because I'm writing a diploma thesis about Web Services and the deadline is the end of september. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079027#4079027 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079027

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: NullPointerException with jbossws 2.0.1

by koganty

Thomas, Any updates on this? How do you suggest we proceed? Any other information we should be looking for? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078959#4078959 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078959

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Using WS behing a reverse proxy

by bblasko

Yes, that approach will work and is a potential workaround so long as you have static WSDL. I am using annotated POJO for the web services so having the WSDL dynamically generated on deployment is preferred. What I really need is the ability to specify the host override in the web.xml or webservices.xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078888#4078888 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078888

18 years, 8 months

1
0
0 / 0

[JBossWS] - jbossWS 2.0.1 and JDK 1.6

by gumnaam

The release notes of 2.0.1 say it was fixed to work with JDK 1.6. How ever I can't get it to work with JDK 1.6 under jboss 4.0.5. If I run against JDK 1.6, I get the error saying jaxb-api.jar ver. 2.0 is loaded from bootstrap classpath however the JAX RI requires ver 2.1. To override , use the endoresed mechanism. This is a deployment error, i.e. the application is not deployed. So I copied jaxb-api.jar and jaxws-api.jar to jboss/lib/endorsed directory, after this the application is deployed fine, but when I call the web service , I get anonymous wrote : | aused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:424) | at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:161) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:232) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:161) | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) | What exactly needs to be done to make JDK 1.6 work with Jbossws 2.0.1 ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078886#4078886 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078886

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Secure Webservice

by sgarelle

Hi, I am facing exactly the same problem... So, what's the solution? I am using JBoss_4_2_1_GA. On client side, I also use the request context to set the user name and password: | CmiEndPoint proxy = (CmiEndPoint) service.getPort(CmiEndPoint.class); | BindingProvider bp = (BindingProvider) proxy; | Map<String, Object> reqCtxt = bp.getRequestContext(); | reqCtxt.put(BindingProvider.USERNAME_PROPERTY, user); | reqCtxt.put(BindingProvider.PASSWORD_PROPERTY, password); | proxy.execCmd("Do this command"); | On server side, the WebService is simply declared with the "@WebService" annotation. A security-domain is defined in jboss.xml. Users are defined. The command failed because of an authentification failure: javax.xml.ws.soap.SOAPFaultException: Authentication failure The same user/password used for a RMI client calling directly the underlying stateless session bean works. The same WS client with security disabled on server works. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078883#4078883 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078883

18 years, 8 months

1
0
0 / 0

[JBossWS] - context-root in jboss.xml

by gumnaam

Hi, I have a following EAR setup. myApp.ear | `META-INF/application.xml | `myWeb.war (ctx root set to /myWeb in application.xml of ear) | `myEjb.jar | `SLSB EJB3s (also exposed as WS). META-INF | `jboss.xml I want to override the default context root for my Web Services. So in my jboss.xml for (myEjb.jar) I have [QUOTE] <context-root>/webservices</context-root> [/QUOTE] inside the jboss->webservices node. But this doesn't seem to be working, the WSDLs are published at http://host/myApp-myEjb/ I don't want to use the @WebContext, I would rather specify the context-root in jboss.xml , but it is not working. Any clues ? Also can the context-root be any thing arbitrary , or does it need to have some connection, with the deployed web application's (in my case myWeb.war) context root ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078878#4078878 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078878

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: jboss 4.0.5 and jbossws 2.0.1, Exception invoking a web

by gumnaam

Problem solved. Initially I had annotated my Interface, and my implementation, with the default values for the @WebService annotation. The interface and implementation, were in different packages, so they had different target namespaces. The problem went away when I specified the same targetNamespace for both the interface and implementation. This should be in the FAQ, if the interface and implementation are in differnet packages, then they must have same targetNamesapce explicitly specified. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078864#4078864 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078864

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Using WS behing a reverse proxy

by richard_opalka

Copy/Paste from the configuration file you were modifying: --- The WSDL, that is a required deployment artifact for an endpoint, has a <soap:address> | element which points to the location of the endpoint. JBoss supports rewriting of that SOAP address. | | If the content of <soap:address> is a valid URL, JBossWS will not rewrite it unless 'modifySOAPAddress' is true. | If the content of <soap:address> is not a valid URL, JBossWS will rewrite it using the attribute values given below. --- Did you try to set up <soap:address> manually in WSDL and set modifySOAPAddress to false? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078808#4078808 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078808

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Setting .NET friendly Endpoint in web.xml

by heiko.braun＠jboss.com

Thanks. This looks like a bug to me: http://jira.jboss.com/jira/browse/JBWS-1797 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078795#4078795 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078795

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: jboss 4.0.5 and jbossws 2.0.1, Exception invoking a web

by heiko.braun＠jboss.com

Did you try to recreate the SOAPUI stubs from the WSDL generated by 2.0.1? Does the same error occur? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078793#4078793 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078793

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: jbossws-2.0.1 released

by palin

"bernhard_pauler" wrote : I tried to deploy jbossws-native-2.0.1.GA on jboss-4.0.5.GA but failed: | | BUILD FAILED | | C:\temp0\jbossws-native-2.0.1.GA\build\build-deploy.xml:79: The following error occurred while executing this line: | | C:\temp0\jbossws-native-2.0.1.GA\build\macros-deploy-native.xml:298: Warning: Could not find file C:\jboss-4.0.5.GA\server\default\deploy\jbossws.sar\META-INF\jboss-service-no-ejb3.xml to copy. | | Deployment on jboss-4.2.1.GA was successful. On jira you'll find an issue for this and a workaround to be used with jbws 2.0.1.GA. http://jira.jboss.com/jira/browse/JBWS-1796 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078710#4078710 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078710

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: New Wiki site for JBossWS is down or not working since f

by palin

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=117230 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078701#4078701 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078701

18 years, 8 months

1
0
0 / 0

[JBossWS] - WIKI down

by heiko.braun＠jboss.com

The WIKI is currently unvailable. However i put the documentation online that was compiled from WIKI contents. It can accessed here: http://labs.jboss.com/jbossws/docs/index.html Sorry, for the inconvinience. I'll keep you posted once the WIKI is back online. Please refer to the static contents in the meantime. Heiko View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078694#4078694 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078694

18 years, 8 months

1
0
0 / 0

[JBossWS] - New Wiki site for JBossWS is down or not working since frida

by vashistvishal

New Wiki site for JBossWS is down since friday... I don't thisk it working. http://jbws.dyndns.org/mediawiki All the documentation (user guide,tutorial) for new release of JBossWS 2.0.1 is not accesible because of this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078571#4078571 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078571

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Wsconsume generated Stubs failing with JBoss-4.2.0

by vashistvishal

Hi Thomas, I have got the new Web services stack (jbossws-2.0.1.GA) and deployed it in Jboss 4.2.1.GA and wsconsume fails with it as well I have validated my WSDL file (using WTP in Eclipse 3.3) as well and doesnt complain at all. To me its a bug in stack, which is generating wrong input paramaeter for the interface. It generates the right response for return type but fails with input type. This is what i get when i use wsconsume. vsm@jm000606:resources$ ~/javadev/jboss-4.2.1.GA/bin/wsconsume.sh -p au.com.new201 -k getMemberInfo.wsdl JBossWS-Native stack deployed parsing WSDL... [WARNING] src-resolve: Cannot resolve the name 'edm:getMemberInfo' to a(n) 'element declaration' component. | line 52 of file:/C:/cygwin/home/vishal/download/source.new/common/resources/getMemberInfo.wsdl#types?schema2 | | generating code... | au\com\new201\EmploymentHistory.java | au\com\new201\GetMemberInfoRequest.java | au\com\new201\GetMemberInfoRequestType.java | au\com\new201\GetMemberInfoResponse.java | au\com\new201\GetMemberInfoResponseType.java | au\com\new201\InsuranceServicesGetmemberinfo.java | au\com\new201\InsuranceServicesGetmemberinfoService.java | au\com\new201\MemberPackages.java | au\com\new201\ObjectFactory.java | au\com\new201\package-info.java | vsm@jm000606:resources$ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078557#4078557 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078557

18 years, 8 months

1
0
0 / 0

[JBossWS] - jboss 4.0.5 and jbossws 2.0.1, Exception invoking a web serv

by gumnaam

I have a very simple EJB3 SLSB EchoService, which has one method hello. Operation hello takes in a string and returns the same string. If I deploy this application, in jboss 4.0.5 stock which comes with jbossws 1.0.3, then I am able to successfully invoke the hello operation using soapui. Now If I install jbossws 2.0.1 in my jboss 4.0.5, the application starts up fine, the wsdl is also generated correctly, but upon invoking the hello method from soapui, I get the following error on the server. anonymous wrote : | 18:08:15,776 ERROR [SOAPFaultHelperJAXWS] SOAP request exception | org.jboss.ws.core.CommonSOAPFaultException: Endpoint {http://ejb.myproj.mycomp.com/}EchoServicePort does not contain operation meta data for: {http://ejb.myproj.mycomp.com/}hello | at org.jboss.ws.core.server.ServiceEndpointInvoker.getDispatchDestination(ServiceEndpointInvoker.java:457) | at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:408) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | I need to upgrade to jbossws 2.0.1 as we will soon be migrating to jdk 1.6, and jbossws 1.0.3 does not work with jdk 1.6. Any pointers will he appriciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078520#4078520 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078520

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Using WS behing a reverse proxy

by bblasko

If you set webServiceHost it applies to all web services hosted in the container. I need to be able to override the host for a specific web context within the container. In my example, I have two web context webcxta and webcxtb both are hosted on the same jboss container. What I need is to have the same fucntionality as provided by webServiceHost property but at the individual web app level. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078408#4078408 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078408

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Two webservice classes define method with same name (bug

by gbdt

I've emailed the files directly to you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078349#4078349 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078349

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: jbossws-2.0.1 released

by bernhard_pauler

I tried to deploy jbossws-native-2.0.1.GA on jboss-4.0.5.GA but failed: BUILD FAILED | C:\temp0\jbossws-native-2.0.1.GA\build\build-deploy.xml:79: The following error occurred while executing this line: | C:\temp0\jbossws-native-2.0.1.GA\build\macros-deploy-native.xml:298: Warning: Could not find file C:\jboss-4.0.5.GA\server\default\deploy\jbossws.sar\META-INF\jboss-service-no-ejb3.xml to copy. Deployment on jboss-4.2.1.GA was successful. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078345#4078345 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078345

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Two webservice classes define method with same name (bug

by richard_opalka

OK, could you send me minimized application so I could reproduce your problem? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078340#4078340 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078340

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Two webservice classes define method with same name (bug

by gbdt

I didn't use the wstools script and didn't have the configuration files. I did let JBossws to generate the wsdls "in-memory" (http://localhost:8080/..../TestClass1?wsdl) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078282#4078282 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078282

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Two webservice classes define method with same name (bug

by richard_opalka

Hi, how did you get it? I tried your usecase and it works for me :-( Here's my experiment: //--------- // File TestClass1.java //--------- package com.XXXX; import javax.ejb.Stateless; import javax.jws.WebMethod; import javax.jws.WebParam; import javax.jws.WebService; @WebService @Stateless public interface TestClass1 extends java.rmi.Remote { @WebMethod public Integer method(@WebParam(name="f")Float f) throws java.rmi.RemoteException; } //--------- // File TestClass2.java //--------- package com.XXXX; import javax.ejb.Stateless; import javax.jws.WebMethod; import javax.jws.WebParam; import javax.jws.WebService; @WebService @Stateless public interface TestClass2 extends java.rmi.Remote { @WebMethod public Double method(@WebParam(name="f")Float f) throws java.rmi.RemoteException; } //--------- // File wstools-config1.xml //--------- <?xml version="1.0" encoding="UTF-8"?> <configuration xmlns="http://www.jboss.org/jbossws-tools" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.org/jbossws-tools http://www.jboss.org/jbossws-tools/schema/jbossws-tool_1_0.xsd"> <java-wsdl> <namespaces target-namespace="http://XXXX.com/" type-namespace="http://XXXX.com/types/" /> <webservices servlet-link="TestClass1"/> </java-wsdl> //--------- // File wstools-config2.xml //--------- <?xml version="1.0" encoding="UTF-8"?> <configuration xmlns="http://www.jboss.org/jbossws-tools" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.org/jbossws-tools http://www.jboss.org/jbossws-tools/schema/jbossws-tool_1_0.xsd"> <java-wsdl> <namespaces target-namespace="http://XXXX.com/" type-namespace="http://XXXX.com/types/" /> <webservices servlet-link="TestClass2"/> </java-wsdl> //--------- // File generatewsdl.sh //--------- #!/bin/sh ./wstools.sh -cp output -config wstools-config1.xml ./wstools.sh -cp output -config wstools-config2.xml //--------- In both cases it generates correct WSDLs for me. I also tried to change the style from "rpc" to "document" but again it worked very well for me. Can you describe me your problem and how did you get it more detailly? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078281#4078281 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078281

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Using WS behing a reverse proxy

by richard_opalka

See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116005 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078245#4078245 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078245

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS4EEDowngrade setup problem

by ambika

Hi, Is downgrade setup of WS4EE will work for jboss application server 4.2.0.GA? Regards, Ambika View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078208#4078208 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078208

18 years, 8 months

1
0
0 / 0

[JBossWS] - Two webservice classes define method with same name (bug?)

by gbdt

Hi, I have a test case in which I get wrong WSDLs: (Both classes are in the same package) File1: | package com.XXXX; | | import javax.ejb.Stateless; | import javax.jws.WebMethod; | import javax.jws.WebParam; | import javax.jws.WebService; | | @WebService | @Stateless | public class TestClass1 { | | @WebMethod | public ****Integer**** method(@WebParam(name="f")Float f) { | return null; | } | } | File2: | package com.XXXX; | | import javax.ejb.Stateless; | import javax.jws.WebMethod; | import javax.jws.WebParam; | import javax.jws.WebService; | | @WebService | @Stateless | public class TestClass2 { | | @WebMethod | public ****Double**** method(@WebParam(name="f")Float f) { | return 17.0; | } | } | The problem is that for both services the WSDL definition of the return type is xs:int, while for the second class it should be a double. For TestClass1: | <types> | <xs:schema targetNamespace="http://XXXX.com/" version="1.0" xmlns:tns="http://XXXX.com/" xmlns:xs="http://www.w3.org/2001/XMLSchema"> | <xs:element name="method" type="tns:method" /> | <xs:element name="methodResponse" type="tns:methodResponse" /> | <xs:complexType name="method"> | <xs:sequence> | <xs:element minOccurs="0" name="f" type="xs:float" /> | </xs:sequence> | </xs:complexType> | <xs:complexType name="methodResponse"> | <xs:sequence> | <xs:element minOccurs="0" name="return" type="****xs:int****" /> | </xs:sequence> | </xs:complexType> | </xs:schema> | </types> | And for TestClass2: | ... | <types> | <xs:schema targetNamespace="http://XXXX.com/" version="1.0" xmlns:tns="http://XXXX.com/" xmlns:xs="http://www.w3.org/2001/XMLSchema"> | <xs:element name="method" type="tns:method" /> | <xs:element name="methodResponse" type="tns:methodResponse" /> | <xs:complexType name="method"> | <xs:sequence> | <xs:element minOccurs="0" name="f" type="xs:float" /> | </xs:sequence> | </xs:complexType> | <xs:complexType name="methodResponse"> | <xs:sequence> | <xs:element minOccurs="0" name="return" type="****xs:int****" /> | </xs:sequence> | </xs:complexType> | </xs:schema> | </types> | ... | The second method definition, for a totally different service has an incorrect return type. Is is a bug or some kind of error on my side? Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078139#4078139 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078139

18 years, 8 months

1
0
0 / 0

[JBossWS] - Using WS behing a reverse proxy

by bblasko

We host our web services behind a reverse proxy which serves as our security and HTTPS termination. Everything works OK with the exception of the dynamic WSDL generation. Since the URL used to access the WS service is not the same as the actual URL of the JBoss service, the WSDL soap:address is incorrect. Is there a way to override the webServiceHost and webServicePort at the application instance vs the entire container? Example https://proxyhost/webcxta/service1?wsdl maps to http://jbossserver:8080/webcxta/service1?wsdl https://proxyhost/webcxtb/service2?wsdl maps to http://jbossserver:8080/webcxtb/service2?wsdl View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078134#4078134 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078134

18 years, 8 months

1
0
0 / 0

[JBossWS] - Setting .NET friendly Endpoint in web.xml

by bblasko

If I attempt to set the jbossws-config-name to ".NET friendly Endpoint", it is correctly picking up the config but the WSDL is not generated as it should. It appears it does not rewrite the WSDL based on this setting. If I set the config as an annotation in my class it works. Is there a way to set the .NET Endpoint without using an annotation. This works: @EndpointConfig(configName=".NET friendly Endpoint") This does not. <context-param> | <param-name>jbossws-config-name</param-name> | <param-value>.NET friendly Endpoint</param-value> | </context-param> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078132#4078132 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078132

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: jbossws-2.0.1 released

by vashistvishal

Hi Thomas, Links you have mentioned are not working, may be the site is down please check. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078100#4078100 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4078100

18 years, 8 months

1
0
0 / 0

[JBossWS] - NullPointerException with a WS request

by sandypm0

I am using Jboss-4.0.5 and JbossWS-1.2.1. I get this error, and it occurs now and then. 80% of the time it works and 20% of the time it throws the following error. | 2007-08-24 17:09:41,540 ERROR [org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper] Err | or creating SOAPFault message | java.lang.NullPointerException | at com.sun.org.apache.xerces.internal.dom.NodeImpl.toString(Unknown Sour | ce) | at org.jboss.ws.soap.NodeImpl.toString(NodeImpl.java:561) | at java.lang.String.valueOf(String.java:1475) | at org.jboss.lang.JBossStringBuilder.append(JBossStringBuilder.java:116) | at org.jboss.ws.soap.SOAPContentElement.appendChild(SOAPContentElement.j | ava:713) | at org.jboss.ws.soap.SOAPElementImpl.addChildElement(SOAPElementImpl.jav | a:221) | at org.jboss.ws.soap.SOAPContentElement.addChildElement(SOAPContentEleme | nt.java:441) | at org.jboss.ws.soap.SOAPFaultImpl.setFaultCode(SOAPFaultImpl.java:253) | at org.jboss.ws.soap.SOAPBodyImpl.addFault(SOAPBodyImpl.java:133) | at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.toSOAPMessage(SOAPFaultE | xceptionHelper.java:214) | at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.exceptionToFaultMessage( | SOAPFaultExceptionHelper.java:188) | at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.jav | a:223) | at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(Service | EndpointManager.java:355) | at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointSe | rvlet.java:115) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointS | ervlet.java:76) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl | icationFilterChain.java:252) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF | ilterChain.java:173) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi | lter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl | icationFilterChain.java:202) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF | ilterChain.java:173) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV | alve.java:213) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV | alve.java:178) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit | yAssociationValve.java:175) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica | torBase.java:524) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv | e.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j | ava:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j | ava:105) | at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConne | ctionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal | ve.java:107) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav | a:148) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java | :869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p | rocessConnection(Http11BaseProtocol.java:664) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo | int.java:527) | at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor | kerThread.java:112) | at java.lang.Thread.run(Thread.java:797) | 2007-08-24 17:09:41,541 ERROR [org.jboss.ws.server.StandardEndpointServlet] Erro | r processing web service request | Servlet.service | () for servlet AutoLendingServlet threw exception | javax.xml.rpc.JAXRPCException: Cannot create SOAPFault message for: javax.xml.rp | c.soap.SOAPFaultException: java.lang.NullPointerException | at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.exceptionToFaultMessage( | SOAPFaultExceptionHelper.java:194) | at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.jav | a:223) | at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(Service | EndpointManager.java:355) | at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointSe | rvlet.java:115) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointS | ervlet.java:76) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl | icationFilterChain.java:252) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF | ilterChain.java:173) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi | lter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl | icationFilterChain.java:202) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF | ilterChain.java:173) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV | alve.java:213) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV | alve.java:178) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit | yAssociationValve.java:175) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica | torBase.java:524) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv | e.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j | ava:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j | ava:105) | at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConne | ctionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal | ve.java:107) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav | a:148) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java | :869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p | rocessConnection(Http11BaseProtocol.java:664) | at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo | int.java:527) | at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor | kerThread.java:112) | at java.lang.Thread.run(Thread.java:797) | The Client side is registering the SOAP request which was sent down to the server, and everything looks OK. Is there any known issue regarding this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077941#4077941 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077941

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Publishing my own wsdl which imports an xsd file.

by john.franklin

Got it. It is looking for the xsd files in WEB-INF thought the wsdl is in META-INF. Added it there and it works. Thanks, johnf View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077899#4077899 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077899

18 years, 8 months

1
0
0 / 0

[JBossWS] - Publishing my own wsdl which imports an xsd file.

by john.franklin

I am using jboss 4.2.1 and jbossws 2.0.0 I am trying to publish the wsdl I have created by setting the wsdLocation correctly in the @WebService implementation file of the web service. The wsdl and the xsd files are located in the META-INF directory in the war file. It located the wsdl file, but cannot locate the xsd file which is in the same place. However JBoss throws an exception and fails to deploy. Is this a bug or am I doing something wrong? 2007-08-24 07:35:39,200 ERROR [ServiceEndpointDeployer] Cannot start service endpoint | org.jboss.ws.WSException: Cannot publish wsdl to: /opt/SYNAPPS100008/jboss-4.2.1.GA/server/default/data/wsdl/synappsccv1.war/Syna | ppsSessionService.wsdl | at org.jboss.ws.core.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:126) | at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:134) | at org.jboss.ws.integration.jboss42.DeployerInterceptor.startServiceEndpoint(DeployerInterceptor.java:144) | at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:96) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | 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 $Proxy47.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor19.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 $Proxy10.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) | Caused by: java.io.IOException: Cannot get URL for: WEB-INF/wsdl/SynappsSession.xsd | at org.jboss.ws.integration.ResourceLoaderAdapter.findChild(ResourceLoaderAdapter.java:105) | at org.jboss.ws.core.server.UnifiedDeploymentInfo.getMetaDataFileURL(UnifiedDeploymentInfo.java:106) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:202) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:222) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:222) | at org.jboss.ws.core.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) | ... 31 more | 2007-08-24 07:35:39,207 ERROR [MainDeployer] Could not start deployment: file:/opt/SYNAPPS100008/jboss-4.2.1.GA/server/default/de | ploy/synappsccv1.war | org.jboss.deployment.DeploymentException: Cannot start service endpoint; - nested throwable: (org.jboss.ws.WSException: Cannot pu | blish wsdl to: /opt/SYNAPPS100008/jboss-4.2.1.GA/server/default/data/wsdl/synappsccv1.war/SynappsSessionService.wsdl) | at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) | at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:101) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | 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 $Proxy47.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor19.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 $Proxy10.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) | Caused by: org.jboss.ws.WSException: Cannot publish wsdl to: /opt/SYNAPPS100008/jboss-4.2.1.GA/server/default/data/wsdl/synappscc | v1.war/SynappsSessionService.wsdl | at org.jboss.ws.core.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:126) | at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:134) | at org.jboss.ws.integration.jboss42.DeployerInterceptor.startServiceEndpoint(DeployerInterceptor.java:144) | at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:96) | ... 28 more | Caused by: java.io.IOException: Cannot get URL for: WEB-INF/wsdl/SynappsSession.xsd | at org.jboss.ws.integration.ResourceLoaderAdapter.findChild(ResourceLoaderAdapter.java:105) | at org.jboss.ws.core.server.UnifiedDeploymentInfo.getMetaDataFileURL(UnifiedDeploymentInfo.java:106) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:202) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:222) | at org.jboss.ws.core.server.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:222) | at org.jboss.ws.core.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) | ... 31 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077860#4077860 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077860

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Is there a workaround for the UsernameToken security hea

by kimbaltrue

Thanks this helped though I did have to do a lot of snooping in the deploy directory. Apparently, all I had to do was add the following annotation: @EndpointConfig(configName="Standard WSSecurity Endpoint") The endpoint configuration file already exists in the webservices sar directory under deploy. Since the file and entry exist, all you need is the endpoint config statement with the name of the config. The next problem I have to solve has to do with this being JBoss specific rather than JEE 5. The JEE 5 has a @Handler annotation that should be used instead of the EndpointConfig annontation, but I haven't figured out how to work with that yet. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077795#4077795 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077795

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Wsconsume generated Stubs failing with JBoss-4.2.0

by M_schumpa

you can see which version of JBossWS is loaded at startup of JBoss. I should look something like this: INFO [ServiceEndpointManager] jbossws-1.2.1.GA (build=200704151756) That's the message from JBoss-4.2.0.GA/ distribution, so I think you are also using this one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077760#4077760 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077760

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Wsconsume generated Stubs failing with JBoss-4.2.0

by thomas.diesler＠jboss.com

please try jbossws-2.0.1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077758#4077758 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077758

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Null pointer exception with jbossws 2.0.1

by thomas.diesler＠jboss.com

test mail threading from forum posts View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077756#4077756 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077756

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Wsconsume generated Stubs failing with JBoss-4.2.0

by vashistvishal

Hi Thomas, Thanks for replying. I'm not sure what version JBossWS it is. I'm using JBoss-4.2.0.GA/ distribution, what version is shipped with it is not clear to me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077720#4077720 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077720

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS4EEDowngrade setup problem

by ambika

Hi, I wanted to know whether i can run MedRec application (which is built with to jboss ws4ee) in this New version of the apps server? Previously there was a disscusion about the same with jboss version 4.0.5.GA. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97276 Regards, Ambika View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077717#4077717 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077717

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS4EEDowngrade setup problem

by thomas.diesler＠jboss.com

Please talk to http://www.jboss.com/services/index View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077700#4077700 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077700

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: NullPointerException with jbossws 2.0.1

by mdaguete

"thomas.diesler(a)jboss.com" wrote : The manifest classpath is not the problem becasue the unified classloader can see/load the ServerConfigFactory | | The implementation of that factory however tries to load the ServerConfig from the microkernel with the bean name: WSServerConfig | | Is that bean there? | There are no WSServerConfig bean in the jmx-console. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077686#4077686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077686

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: JBossAS_4.0.5 does not clean up the temp files

by BossDenny

Yes, passivate file are not deleted by server!!!....and I have an exception when PostActivate metod occur on an ejb3 with PersistentContext(EXTENDED) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077683#4077683 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077683

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS4EEDowngrade setup problem

by ambika

Hi, MedRec is a Avitek Medical Records (or MedRec) is a WebLogic Server sample application suite which we use for testing. This application is a WS4EE based axis application. As from jboss 4.0.5.GA onwards, WS4EE is replace with the JbossWS, so I have done the changes said in (http://wiki.jboss.org/wiki/Wiki.jsp?page=WS4EEDowngrade ) After following those steps its giving above mentioned error. As there is no webservice directory in the server, we are getting this problem. Please can anyone help me? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077674#4077674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077674

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Unable to create connection to jUDDI registry

by thomas.diesler＠jboss.com

Have a look at the sample jaxr tests http://jbws.dyndns.org:8180/hudson/job/Core-Tests-AS-4.2/lastBuild/testRe... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077666#4077666 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077666

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Wsconsume generated Stubs failing with JBoss-4.2.0

by thomas.diesler＠jboss.com

what jbossws is this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077664#4077664 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077664

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS-Security with JAX-RPC

by thomas.diesler＠jboss.com

looks good View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077663#4077663 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077663

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: JBossAS_4.0.5 does not clean up the temp files

by thomas.diesler＠jboss.com

What temp files are not deleted? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077662#4077662 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077662

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Null pointer exception with jbossws 2.0.1

by thomas.diesler＠jboss.com

duplicates http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077660#4077660 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077661#4077661 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077661

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: NullPointerException with jbossws 2.0.1

by thomas.diesler＠jboss.com

The manifest classpath is not the problem becasue the unified classloader can see/load the ServerConfigFactory The implementation of that factory however tries to load the ServerConfig from the microkernel with the bean name: WSServerConfig Is that bean there? |  | <bean name="WSServerConfig" class="org.jboss.wsf.stack.jbws.NativeServerConfig"> | <property name="mbeanServer"><inject bean="WSMBeanServerLocator" property="mbeanServer"/></property> | |  | <property name="webServiceHost">${jboss.bind.address}</property> | <property name="modifySOAPAddress">true</property> | |  | </bean> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077660#4077660 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077660

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: 2 ejb3s exposed as web services. Can't have same methods

by thomas.diesler＠jboss.com

Could you please create a jira issue and attach a test case that allows us to reproduce what you are seeing. Maybe you can even find out why this is. http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Source View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077656#4077656 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077656

18 years, 8 months

1
0
0 / 0

[JBossWS] - Null pointer exception with jbossws 2.0.1

by mdaguete

Hello, When deploy a webservice in 2.0.1 a null pointer exception appears, it works in 2.0.0. Server config factory it's deployed | 2007-08-24 08:52:14,289 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.management.ServerConfigFactory' | 2007-08-24 08:52:14,292 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] class org.jboss.wsf.spi.management.ServerConfigFactory Implementation: org.jboss.wsf.framework.management.ServerConfigFactoryImpl@1c334 | de | | The manifes file in jbossws.sar/META-INF has a classpath entry witch cause errors in deploy, deleting the entry resolve this issued, but the null pointer exception appears again The null ponter exception. | 08:52:14,292 ERROR [MainDeployer] Could not start deployment: file:/opt/JBoss/jboss-4.2.1.GA/server/default/tmp/deploy/tmp4361PlataformaRecargas.ear-contents/PlataformaRecargas-ejb.jar | java.lang.NullPointerException | at org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect.generatWebDeployment(WebAppGeneratorDeploymentAspect.java:105) | at org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect.create(WebAppGeneratorDeploymentAspect.java:84) | at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) | at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) | at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | 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 $Proxy34.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor25.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 $Proxy66.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.ha.framework.server.FarmMemberService.deploy(FarmMemberService.java:412) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.ha.framework.server.FarmMemberService.startService(FarmMemberService.java:212) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor3.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:1025) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor25.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 $Proxy9.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.GeneratedMethodAccessor3.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:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) | 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:508) | at java.lang.Thread.run(Thread.java:595) | | Any Idea ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077645#4077645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077645

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: JBossAS_4.0.5 does not clean up the temp files

by BossDenny

My problem is to delete temp file of ejb passivate when the server is on, because her activity fills my hard disc. grazie.... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077643#4077643 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077643

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS-Security with JAX-RPC

by FabrizioLXXIII

When I deploy my Web Service, I see the following log messages in server.log file: 2007-08-24 09:01:55,166 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/D:/JBoss/server/all/deploy/ws_producer.ear | 2007-08-24 09:01:55,166 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/D:/JBoss/server/all/deploy/ws_producer.ear -> D:\JBoss\server\all\tmp\deploy\tmp63669ws_producer.ear | 2007-08-24 09:01:55,259 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.EARDeployer@d8a1a0 | 2007-08-24 09:01:55,259 INFO [org.jboss.deployment.EARDeployer] Init J2EE application: file:/D:/JBoss/server/all/deploy/ws_producer.ear | 2007-08-24 09:01:55,280 DEBUG [org.jboss.deployment.EARDeployer] Extracted non-deployable content: META-INF/MANIFEST.MF | 2007-08-24 09:01:55,301 DEBUG [org.jboss.deployment.EARDeployer] Extracted deployable content: ws_producer.war | 2007-08-24 09:01:55,301 DEBUG [org.jboss.deployment.EARDeployer] Extracted non-deployable content: META-INF/application.xml | 2007-08-24 09:01:55,301 DEBUG [org.jboss.deployment.EARDeployer] Deployment Info: org.jboss.deployment.DeploymentInfo@7a0b49e2 { url=file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer.war } | deployer: null | status: null | state: CONSTRUCTED | watch: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer.war | altDD: null | lastDeployed: 0 | lastModified: 0 | mbeans: | , isDirectory: false | 2007-08-24 09:01:55,301 DEBUG [org.jboss.deployment.DeploymentInfo] createLoaderRepository from config: LoaderRepositoryConfig(repositoryName: JMImplementation:service=LoaderRepository,name=Default, repositoryClassName: null, configParserClassName: null, repositoryConfig: null) | 2007-08-24 09:01:55,301 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@4e79f1, cl=org.jboss.mx.loading.UnifiedClassLoader3@18b70fb{ url=file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear ,addedOrder=0} | 2007-08-24 09:01:55,301 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@4e79f1, cl=org.jboss.mx.loading.UnifiedClassLoader3@18b70fb{ url=file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear ,addedOrder=0} | 2007-08-24 09:01:55,301 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3@18b70fb{ url=file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear ,addedOrder=0} | 2007-08-24 09:01:55,301 DEBUG [org.jboss.mx.loading.ClassLoaderUtils] Multiple class loaders found for pkg: | 2007-08-24 09:01:55,445 DEBUG [org.jboss.deployment.MainDeployer] found 1 subpackages of file:/D:/JBoss/server/all/deploy/ws_producer.ear | 2007-08-24 09:01:55,445 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer.war | 2007-08-24 09:01:55,445 DEBUG [org.jboss.deployment.MainDeployer] using deployer MBeanProxyExt[jboss.web:service=WebServer] | 2007-08-24 09:01:55,445 DEBUG [org.jboss.web.tomcat.service.JBossWeb] Begin init | 2007-08-24 09:01:55,445 DEBUG [org.jboss.web.tomcat.service.JBossWeb] Unpacking war to: D:\JBoss\server\all\tmp\deploy\tmp63669ws_producer.ear-contents\ws_producer-exp.war | 2007-08-24 09:01:55,600 DEBUG [org.jboss.web.tomcat.service.JBossWeb] Replaced war with unpacked contents | 2007-08-24 09:01:55,600 DEBUG [org.jboss.web.tomcat.service.JBossWeb] Was unable to delete war file | 2007-08-24 09:01:55,600 DEBUG [org.jboss.web.tomcat.service.JBossWeb] webContext: /ws_producer | 2007-08-24 09:01:55,600 DEBUG [org.jboss.web.tomcat.service.JBossWeb] warURL: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/ | 2007-08-24 09:01:55,632 DEBUG [org.jboss.web.tomcat.service.JBossWeb] End init | 2007-08-24 09:01:55,642 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Added url: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/, to ucl: org.jboss.mx.loading.UnifiedClassLoader3@18b70fb{ url=file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear ,addedOrder=52} | 2007-08-24 09:01:55,642 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer.war | 2007-08-24 09:01:55,642 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/D:/JBoss/server/all/deploy/ws_producer.ear | 2007-08-24 09:01:55,642 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/D:/JBoss/server/all/deploy/ws_producer.ear | 2007-08-24 09:01:55,642 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer.war | 2007-08-24 09:01:55,642 DEBUG [org.jboss.web.tomcat.service.JBossWeb] create, ws_producer.war | 2007-08-24 09:01:55,642 DEBUG [org.jboss.system.ServiceController] Creating service jboss.web.deployment:war=ws_producer.war,id=2047560162 | 2007-08-24 09:01:55,642 DEBUG [org.jboss.system.ServiceController] adding depends in ServiceController.register: [] | 2007-08-24 09:01:55,642 DEBUG [org.jboss.web.WebModule] Creating jboss.web.deployment:war=ws_producer.war,id=2047560162 | 2007-08-24 09:01:55,642 DEBUG [org.jboss.web.WebModule] Created jboss.web.deployment:war=ws_producer.war,id=2047560162 | 2007-08-24 09:01:55,642 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.web.deployment:war=ws_producer.war,id=2047560162 dependents are: [] | 2007-08-24 09:01:55,642 DEBUG [org.jboss.ws.integration.jboss42.DeployerInterceptorJSE] create: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer.war | 2007-08-24 09:01:55,663 DEBUG [org.jboss.ws.core.server.ServiceEndpointDeployer] create: ws_producer.ear/ws_producer.war | 2007-08-24 09:01:55,673 DEBUG [org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder] START buildMetaData: [name=ws_producer.ear/ws_producer.war] | 2007-08-24 09:01:55,756 DEBUG [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] parse: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/WEB-INF/wsdl/Service.wsdl | 2007-08-24 09:01:56,696 DEBUG [org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder] createConfiguration from: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/WEB-INF/jboss-wsse-server.xml | 2007-08-24 09:01:56,769 DEBUG [org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder] Add keystore: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/WEB-INF/wsse.keystore | 2007-08-24 09:01:56,769 DEBUG [org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder] Add truststore: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/WEB-INF/wsse.truststore | 2007-08-24 09:01:56,800 DEBUG [org.jboss.ws.core.server.ServiceEndpointManager] Using WebServicePort: 8080 | 2007-08-24 09:01:56,810 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Reconfiguration forced, new config is 'Standard WSSecurity Endpoint' | 2007-08-24 09:01:56,810 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Create new config [name=Standard WSSecurity Endpoint,file=META-INF/standard-jaxrpc-endpoint-config.xml] | 2007-08-24 09:01:56,810 DEBUG [org.jboss.ws.metadata.config.JBossWSConfigFactory] getConfig: [name=Standard WSSecurity Endpoint,url=META-INF/standard-jaxrpc-endpoint-config.xml] | 2007-08-24 09:01:56,810 DEBUG [org.jboss.ws.metadata.config.JBossWSConfigFactory] parse: file:/D:/JBoss/server/all/deploy/jbossws.sar/META-INF/standard-jaxrpc-endpoint-config.xml | 2007-08-24 09:01:58,206 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Configure EndpointMetaData | 2007-08-24 09:01:58,206 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Added 1 PRE handlers | 2007-08-24 09:01:58,206 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Added 0 ENDPOINT handlers | 2007-08-24 09:01:58,206 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Added 0 POST handlers | 2007-08-24 09:01:58,206 DEBUG [org.jboss.ws.metadata.builder.MetaDataBuilder] Replace service endpoint address 'REPLACE_WITH_ACTUAL_URL' with 'http://127.0.0.1:8080/ws_producer/service' | 2007-08-24 09:01:58,402 DEBUG [org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder] END buildMetaData: | UnifiedMetaData: | implementation: jbossws-1.2.1.GA (build=200704151756) | deploymentName: ws_producer.ear/ws_producer.war | securityDomain: null | | ServiceMetaData: | qname={http://service.wssecurity.jbossintegrationtest.auriga.it/}Service | refName=null | wsdName=Service | wsdlFile=WEB-INF/wsdl/Service.wsdl | wsdlLocation=null | jaxrpcMapping=file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/WEB-INF/jaxrpc-mapping.xml | publishLocation=null | securityConfig=found | properties=null | | TypesMetaData: | | | ServerEndpointMetaData: | type=JAXRPC | qname={http://service.wssecurity.jbossintegrationtest.auriga.it/}ServicePort | id=jboss.ws:context=ws_producer,endpoint=WsProducerServlet | address=http://127.0.0.1:8080/ws_producer/service | binding=http://schemas.xmlsoap.org/wsdl/soap/http | linkName=WsProducerServlet | implName=it.auriga.jbossintegrationtest.wssecurity.producer.ServiceImpl | seiName=it.auriga.jbossintegrationtest.wssecurity.producer.Service | serviceMode=null | portComponentName=ServicePort | contextRoot=/ws_producer | urlPattern=/service | configFile=META-INF/standard-jaxrpc-endpoint-config.xml | configName=Standard WSSecurity Endpoint | authMethod=null | transportGuarantee=null | secureWSDLAccess=false | properties={} | | OperationMetaData: | qname={http://service.wssecurity.jbossintegrationtest.auriga.it/}run | javaName=run | style=rpc/literal | oneWay=false | soapAction= | ParameterMetaData: | xmlName=String_1 | partName=String_1 | xmlType={http://www.w3.org/2001/XMLSchema}string | javaType=java.lang.String | mode=IN | inHeader=false | index=0 | ParameterMetaData: | xmlName=int_2 | partName=int_2 | xmlType={http://www.w3.org/2001/XMLSchema}int | javaType=int | mode=IN | inHeader=false | index=1 | ReturnMetaData: | xmlName=result | partName=result | xmlType={http://www.w3.org/2001/XMLSchema}string | javaType=java.lang.String | mode=OUT | inHeader=false | index=-1 | | HandlerMetaDataJAXRPC: | type=PRE | name=WSSecurityHandlerInbound | class=org.jboss.ws.extensions.security.jaxrpc.WSSecurityHandlerInbound | params=[] | headers=[] | roles=[] | ports=[] | 2007-08-24 09:01:58,650 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Configure SOAPBinding | 2007-08-24 09:01:58,723 DEBUG [org.jboss.ws.core.server.ServiceEndpointManager] WebService created: jboss.ws:context=ws_producer,endpoint=WsProducerServlet | 2007-08-24 09:01:58,816 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying ws_producer.war | 2007-08-24 09:01:58,816 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:service=EARDeployment,url='ws_producer.ear' | 2007-08-24 09:01:58,816 DEBUG [org.jboss.deployment.EARDeployment] Creating jboss.j2ee:service=EARDeployment,url='ws_producer.ear' | 2007-08-24 09:01:58,816 DEBUG [org.jboss.deployment.EARDeployment] Created jboss.j2ee:service=EARDeployment,url='ws_producer.ear' | 2007-08-24 09:01:58,816 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.j2ee:service=EARDeployment,url='ws_producer.ear' dependents are: [] | 2007-08-24 09:01:58,816 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying ws_producer.ear | 2007-08-24 09:01:58,816 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/D:/JBoss/server/all/deploy/ws_producer.ear | 2007-08-24 09:01:58,816 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer.war | 2007-08-24 09:01:58,816 DEBUG [org.jboss.system.ServiceController] starting service jboss.web.deployment:war=ws_producer.war,id=2047560162 | 2007-08-24 09:01:58,816 DEBUG [org.jboss.web.WebModule] Starting jboss.web.deployment:war=ws_producer.war,id=2047560162 | 2007-08-24 09:01:58,816 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] webContext: /ws_producer | 2007-08-24 09:01:58,816 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] warURL: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/ | 2007-08-24 09:01:58,816 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] webAppParser: org.jboss.web.AbstractWebDeployer$DescriptorParser@1ce56f8 | 2007-08-24 09:01:58,816 DEBUG [org.jboss.web.WebPermissionMapping] Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverriden=false,qualifiers=[]]} | 2007-08-24 09:01:58,816 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/ws_producer, warUrl=.../tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/ | 2007-08-24 09:01:58,816 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] AbstractWebContainer.parseWebAppDescriptors, Begin | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] Creating ENC using ClassLoader: java.net.FactoryURLClassLoader@1afbbe3 | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] ..org.jboss.mx.loading.UnifiedClassLoader3@18b70fb{ url=file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear ,addedOrder=52} | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] ..org.jboss.system.server.NoAnnotationURLClassLoader@5d173 | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] ..sun.misc.Launcher$AppClassLoader@92e78c | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] ..sun.misc.Launcher$ExtClassLoader@9fbe93 | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] Bound java:comp/ORB | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] Linked java:comp/UserTransaction to JNDI name: UserTransaction | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] addEnvEntries | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] linkResourceEnvRefs | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] linkResourceRefs | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] linkMessageDestinationRefs | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] linkEjbRefs | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] linkEjbLocalRefs | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] linkServiceRefs | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] linkSecurityDomain | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] No security-domain given, using default: java:/jaas/other | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] Linking security/securityMgr to JNDI name: java:/jaas/other | 2007-08-24 09:01:58,899 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] AbstractWebContainer.parseWebAppDescriptors, End | 2007-08-24 09:01:58,981 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] Using session cookies default setting | 2007-08-24 09:01:59,333 DEBUG [org.jboss.web.tomcat.filters.ReplyHeaderFilter] Adding header name: X-Powered-By='Servlet 2.4; JBoss-4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)/Tomcat-5.5' | 2007-08-24 09:01:59,343 DEBUG [org.jboss.web.tomcat.service.TomcatDeployer] Initialized: {WebApplication: /D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/, URL: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer-exp.war/, classLoader: java.net.FactoryURLClassLoader@1afbbe3:28294115} jboss.web:j2eeType=WebModule,name=//localhost/ws_producer,J2EEApplication=none,J2EEServer=none | 2007-08-24 09:01:59,343 DEBUG [org.jboss.web.WebModule] Started jboss.web.deployment:war=ws_producer.war,id=2047560162 | 2007-08-24 09:01:59,343 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.web.deployment:war=ws_producer.war,id=2047560162 dependent components: [] | 2007-08-24 09:01:59,354 DEBUG [org.jboss.ws.integration.jboss42.DeployerInterceptorJSE] start: file:/D:/JBoss/server/all/tmp/deploy/tmp63669ws_producer.ear-contents/ws_producer.war | 2007-08-24 09:01:59,354 DEBUG [org.jboss.ws.core.server.ServiceEndpointDeployer] start: ws_producer.ear/ws_producer.war | 2007-08-24 09:01:59,354 DEBUG [org.jboss.ws.core.server.WSDLFilePublisher] Publish WSDL file: WEB-INF/wsdl/Service.wsdl | 2007-08-24 09:01:59,374 INFO [org.jboss.ws.core.server.WSDLFilePublisher] WSDL published to: file:/D:/JBoss/server/all/data/wsdl/ws_producer.ear/ws_producer.war/Service.wsdl | 2007-08-24 09:01:59,374 DEBUG [org.jboss.ws.metadata.umdm.UnifiedMetaData] Eagerly initialize the meta data model | 2007-08-24 09:01:59,395 DEBUG [org.jboss.ws.metadata.umdm.OperationMetaData] Found best matching java method: public abstract java.lang.String it.auriga.jbossintegrationtest.wssecurity.producer.Service.run(java.lang.String,int) throws java.rmi.RemoteException | 2007-08-24 09:02:00,015 INFO [org.jboss.ws.core.server.ServiceEndpointManager] WebService started: http://127.0.0.1:8080/ws_producer/service | 2007-08-24 09:02:00,015 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: ws_producer.war | 2007-08-24 09:02:00,026 DEBUG [org.jboss.system.ServiceController] starting service jboss.j2ee:service=EARDeployment,url='ws_producer.ear' | 2007-08-24 09:02:00,026 DEBUG [org.jboss.deployment.EARDeployment] Starting jboss.j2ee:service=EARDeployment,url='ws_producer.ear' | 2007-08-24 09:02:00,026 DEBUG [org.jboss.deployment.EARDeployment] Started jboss.j2ee:service=EARDeployment,url='ws_producer.ear' | 2007-08-24 09:02:00,026 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.j2ee:service=EARDeployment,url='ws_producer.ear' dependent components: [] | 2007-08-24 09:02:00,026 INFO [org.jboss.deployment.EARDeployer] Started J2EE application: file:/D:/JBoss/server/all/deploy/ws_producer.ear | 2007-08-24 09:02:00,026 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: ws_producer.ear | 2007-08-24 09:02:00,026 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/D:/JBoss/server/all/deploy/ws_producer.ear | 2007-08-24 09:02:00,026 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/D:/JBoss/server/all/deploy/ws_producer.ear -> file:/D:/JBoss/server/all/deploy/ws_producer.ear View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077634#4077634 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077634

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Wsconsume generated Stubs failing with JBoss-4.2.0

by vashistvishal

The comilation error i get is this ... whne i run wsconsume.... | :resources$ /cygdrive/d/javadev/jboss-4.2.0.GA/bin/wsconsume.sh -k -t -p au.com.tusc getMemberInfo.wsdl | warning: src-resolve: Cannot resolve the name 'edm:getMemberInfo' to a(n) 'e lement declaration' component. | line ? of file:/C:/cygwin/home/vishal/download/source.new/common/resources /getMemberInfo.wsdl#types?schema2 | au\com\tusc\EmploymentHistory.java | au\com\tusc\GetMemberInfoRequest.java | au\com\tusc\GetMemberInfoRequestType.java | au\com\tusc\GetMemberInfoResponse.java | au\com\tusc\GetMemberInfoResponseType.java | au\com\tusc\InsuranceServicesGetmemberinfo.java | au\com\tusc\InsuranceServicesGetmemberinfoService.java | au\com\tusc\MemberPackages.java | au\com\tusc\ObjectFactory.java | au\com\tusc\package-info.java | au\com\tusc\EmploymentHistory.java | au\com\tusc\GetMemberInfoRequest.java | au\com\tusc\GetMemberInfoRequestType.java | au\com\tusc\GetMemberInfoResponse.java | au\com\tusc\GetMemberInfoResponseType.java | au\com\tusc\InsuranceServicesGetmemberinfo.java | au\com\tusc\InsuranceServicesGetmemberinfoService.java | au\com\tusc\MemberPackages.java | au\com\tusc\ObjectFactory.java | au\com\tusc\package-info.java | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077616#4077616 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077616

18 years, 8 months

1
0
0 / 0

[JBossWS] - Wsconsume generated Stubs failing with JBoss-4.2.0

by vashistvishal

I have a problem with generating Stubs from WSDL using Wsconsume, part of WS tools used in JBoss-4.2 This is the wsdl which i'm using.... <?xml version="1.0" encoding="UTF-8"?> | <wsdl:definitions name="insurance_pub" targetNamespace="http://www.myhome.com.au/insurance.doc.wsdl" | xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" | xmlns:tns="http://www.myhome.com.au/insurance.doc.wsdl" | xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" | xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"> | <wsdl:types> | <xsd:schema | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | targetNamespace="http://www.myhome.com.au/insurance.doc.wsdl" | xmlns:edm="http://www.myhome.com.au/insurance.doc.wsdl" | xmlns:tns="http://localhost/insurance/pub/getMemberInfo"> | | <xsd:import | namespace="http://localhost/insurance/pub/getMemberInfo"/> | | <xsd:element name="getMemberInfo" type="tns:GetMemberInfoRequest"/> | <xsd:element name="getMemberInfoResponse" type="tns:GetMemberInfoResponse"/> | </xsd:schema> | | <xsd:schema | xmlns:xsd="http://www.w3.org/2001/XMLSchema" | targetNamespace="http://localhost/insurance/pub/getMemberInfo" | xmlns:tns="http://localhost/insurance/pub/getMemberInfo" | xmlns:edm="http://www.myhome.com.au/insurance.doc.wsdl"> | | <xsd:import | namespace="http://www.myhome.com.au/insurance.doc.wsdl"/> | | <xsd:complexType name="EmploymentHistory"> | <xsd:sequence> | <xsd:element name="fundCode" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="employerNumber" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="tradingName" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="employerStatus" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="startDate" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="endDate" nillable="true" type="xsd:string" minOccurs="0"/> | </xsd:sequence> | </xsd:complexType> | <xsd:complexType name="MemberPackages"> | <xsd:sequence> | <xsd:element name="packageName" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="packageStartDate" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="packageEndDate" nillable="true" type="xsd:string" minOccurs="0"/> | </xsd:sequence> | </xsd:complexType> | | <xsd:complexType name="GetMemberInfoRequestType"> | <xsd:sequence> | <xsd:element ref="edm:getMemberInfo"/> | <xsd:any processContents="lax"/> | </xsd:sequence> | <xsd:anyAttribute processContents="lax"/> | </xsd:complexType> | <xsd:complexType name="GetMemberInfoRequest"> | <xsd:sequence> | <xsd:element name="fundCode" nillable="true" type="xsd:string"/> | <xsd:element name="memberNumber" nillable="true" type="xsd:string"/> | </xsd:sequence> | </xsd:complexType> | <xsd:complexType name="GetMemberInfoResponseType"> | <xsd:sequence> | <xsd:element ref="edm:getMemberInfoResponse"/> | <xsd:any processContents="lax"/> | </xsd:sequence> | <xsd:anyAttribute processContents="lax"/> | </xsd:complexType> | <xsd:complexType name="GetMemberInfoResponse"> | <xsd:sequence> | <xsd:element name="fundCode" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="clientArrangementId" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="memberNumber" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="membershipType" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="title" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="givenName" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="surname" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="gender" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="email" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="phoneNumber" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="dateOfBirth" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="deemedDate" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="activeDate" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="addressLine1" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="addressLine2" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="addressLine3" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="suburb" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="state" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="postcode" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="country" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="accountBalance" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="division" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="status" nillable="true" type="xsd:string" minOccurs="0"/> | <xsd:element name="employmentHistory" type="tns:EmploymentHistory" nillable="true" maxOccurs="unbounded" minOccurs="0"/> | <xsd:element name="mbrPackages" type="tns:MemberPackages" nillable="true" maxOccurs="unbounded" minOccurs="0"/> | </xsd:sequence> | </xsd:complexType> | </xsd:schema> | | </wsdl:types> | | <wsdl:message name="getMemberInfoIn"> | <wsdl:part name="getMemberInfo" element="tns:getMemberInfo"/> | </wsdl:message> | | <wsdl:message name="getMemberInfoOutput"> | <wsdl:part name="getMemberInfoResponse" element="tns:getMemberInfoResponse"/> | </wsdl:message> | | <wsdl:portType name="Insurance_services_getmemberinfo"> | <wsdl:operation name="getMemberInfo"> | <wsdl:input message="tns:getMemberInfoIn"/> | <wsdl:output message="tns:getMemberInfoOutput"/> | </wsdl:operation> | </wsdl:portType> | <wsdl:binding name="Insurance_services_getmemberinfoBinding" type="tns:Insurance_services_getmemberinfo"> | <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> | | <wsdl:operation name="getMemberInfo"> | <soap:operation soapAction=""/> | <wsdl:input> | <soap:body use="literal"/> | </wsdl:input> | <wsdl:output> | <soap:body use="literal"/> | </wsdl:output> | </wsdl:operation> | </wsdl:binding> | <!-- to test point web browser too | | <wsdl:service name="Insurance_services_getmemberinfoService"> | <wsdl:port name="Insurance_services_getmemberinfoPort0" binding="tns:Insurance_services_getmemberinfoBinding"> | <soap:address location="http://localhost:5565/soap/DocLiteral"/> | </wsdl:port> | </wsdl:service> | </wsdl:definitions> | | | | I have not been able to understand what the problem is. Even though the stubs are generated, I'm not sure whether these are right ones, because their was warning which is coming all the time when i run wsconsume. Any pointers or hints will be a great help. I went further assuming thet "let us not worry about the warning" and tried to rune the cleint using generated stubs and i got this error at invocation of this service Exception in thread "main" java.lang.IllegalStateException: Cannot build JAXB context | at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:879) | at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:281) | at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:274) | at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:200) | at javax.xml.ws.Service.getPort(Service.java:116) | at au.com.sydney.InsuranceServicesGetmemberinfoService.getInsuranceServicesGetmemberinfoPort0(InsuranceServicesGetmemberinfoService.java:56) | at au.com.sydney.TestService.main(TestService.java:28) | Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 32 counts of IllegalAnnotationExceptions | There's no ObjectFactory with an @XmlElementDecl for the element {http://www.myhome.com.au/insurance.doc.wsdl}fundCode. | this problem is related to the following location: | at protected javax.xml.bind.JAXBElement au.com.sydney.GetMemberInfoResponse.fundCode | at au.com.sydney.GetMemberInfoResponse | As i get this run time error... I'm not sure now whether its a stub generated by wsconsume are not right because their was a warning while running wsconsume or is it JAXB or something else. Any pointers to work on will be a geart help and save me :) from stress over the weekend. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077615#4077615 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077615

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: NullPointerException with jbossws 2.0.1

by koganty

jbossws-framework.jar is deployed under jboss/server//lib. This is how the ServerConfigFactory shows up in the log : 2007-08-23 13:34:29,019 DEBUG [main][DeploymentAspectManagerImpl]: WebAppGeneratorDeploymentAspect:Create 2007-08-23 13:34:29,191 DEBUG [main][DefaultSPIProvider]: provide SPI 'class org.jboss.wsf.spi.management.ServerConfigFactory' 2007-08-23 13:34:29,206 DEBUG [main][DefaultSPIProvider]: class org.jboss.wsf.spi.management.ServerConfigFactory Implementation: org.jboss.wsf.framework.management.ServerConfigFactoryImpl@93727d 2007-08-23 13:34:29,222 ERROR [main][MainDeployer]: Could not start deployment: file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/epicenter.ear/epicenter.jar java.lang.NullPointerException at org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect.generatWebDeployment(WebAppGeneratorDeploymentAspect.java:105) at org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect.create(WebAppGeneratorDeploymentAspect.java:84) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) But the real problem is I think is the MANIFEST.MF in the jbossws.sar/META-INF directory. I see quite a few DeploymentExceptions during startup regards to unreachable jar files 'cos the MANIFEST.MF points to the wrong location. 2007-08-23 13:33:17,948 DEBUG [main][ClassLoaderUtils]: Multiple class loaders found for pkg: 2007-08-23 13:33:17,948 DEBUG [main][MainDeployer]: resolveLibraries: jbossws-spi.jar jbossws-common.jar jbossws-framework.jar jboss-jaxrpc.jar jboss-jaxws.jar jboss-saaj.jar activation.jar commons-logging.jar concurrent.jar javassist.jar jaxb-api.jar jaxb-impl.jar mail.jar jboss-remoting.jar jboss-xml-binding.jar policy.jar stax-api.jar wsdl4j.jar 2007-08-23 13:33:17,948 DEBUG [main][MainDeployer]: new manifest entry for sdi at jbossws.sar entry is jbossws-spi.jar 2007-08-23 13:33:17,948 DEBUG [main][MainDeployer]: The manifest entry in file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws.sar/ references URL file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-spi.jar which could not be opened, entry ignored 2007-08-23 13:33:17,948 DEBUG [main][NestedThrowable]: org.jboss.util.NestedThrowable.parentTraceEnabled=true 2007-08-23 13:33:17,948 DEBUG [main][NestedThrowable]: org.jboss.util.NestedThrowable.nestedTraceEnabled=false 2007-08-23 13:33:17,948 DEBUG [main][NestedThrowable]: org.jboss.util.NestedThrowable.detectDuplicateNesting=true org.jboss.deployment.DeploymentException: url file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-spi.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214) at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884) 2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: new manifest entry for sdi at jbossws.sar entry is jbossws-common.jar 2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: The manifest entry in file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws.sar/ references URL file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-common.jar which could not be opened, entry ignored org.jboss.deployment.DeploymentException: url file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-common.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214) at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884) 2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: new manifest entry for sdi at jbossws.sar entry is jbossws-framework.jar 2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: The manifest entry in file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws.sar/ references URL file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-framework.jar which could not be opened, entry ignored org.jboss.deployment.DeploymentException: url file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-framework.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214) at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884) 2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: new manifest entry for sdi at jbossws.sar entry is jboss-jaxrpc.jar 2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: The manifest entry in file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws.sar/ references URL file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jboss-jaxrpc.jar which could not be opened, entry ignored org.jboss.deployment.DeploymentException: url file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jboss-jaxrpc.jar could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214) at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884) There is more but I think this is the problem... Thank You. -Raju View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077573#4077573 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077573

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: 2 ejb3s exposed as web services. Can't have same methods

by sursha

Both ejbs are in the same jar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077557#4077557 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077557

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: 2 ejb3s exposed as web services. Can't have same methods

by darran.lofthouse＠jboss.com

You say your endpoints are in the same ear but are they also both in the same jar or in different jars? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077504#4077504 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077504

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: 2 ejb3s exposed as web services. Can't have same methods

by sursha

Thanks for looking into it. If I have authenticate(String userName, String password) only in one endpoint/1 ejb3, it works. If I have authenticate(String userName, String password) and authenticate(String userName) in one endpoint/1 ejb3, it did not work. I thought authenticate(String userName, String password) in 1 endpoint/1 ejb3 and authenticate(String userName) in different endpoint/ejb3 should work. But it did not work. Both ejb3s were packaged into the same ear file. Since both ejb3's have different name spaces, I thought it should work, but it did not !! Am I missing something? Your help will be appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077501#4077501 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077501

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: JBossAS_4.0.5 does not clean up the temp files

by PeterJ

Why not simply add a command to delete the temp directory to the end of the run.bat or run.sh script? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077451#4077451 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077451

18 years, 8 months

1
0
0 / 0

[JBossWS] - JBossAS_4.0.5 does not clean up the temp files

by BossDenny

In my JBossAs 4.0.5, the server does clean up the temp files and I'm forced to delete it's manually......I don't now because this....Please can help me????!!! grazie.... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077447#4077447 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077447

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Why are reference types no longer nillable?

by genady_yadata

Anybody? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077431#4077431 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077431

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Type Substitution doesn't work with Schema2Java Client a

by M_schumpa

I've added a jira issue and added a test case. Here's the link: http://jira.jboss.org/jira/browse/JBWS-1795 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077426#4077426 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077426

18 years, 8 months

1
0
0 / 0

[JBossWS] - jbossws-2.0.1 released

by thomas.diesler＠jboss.com

As of this post I am happy to anounce that jbossws-2.0.1.GA is released. This is a fully certified JAXWS web services implemenation. It runs on jboss-5.0.x, jboss-4.2.x, jboss-4.0.5 JAXWS brings to web services what EJB3 brings to EJB. With its greatly simplified programming model and functional enhancements it is desigend to take the place of previous JAX-RPC web service implementations. Details of how to download and install the new stack can be found in our new wiki http://jbws.dyndns.org/mediawiki/index.php/Main_Page To get started please have a look at the Quick Start and User Guide http://jbws.dyndns.org/mediawiki/index.php/Quick_Start http://jbws.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide If you don't know it already, you'll be surprised how easy it is to do Web Services. I'd like to thank the team and the many contributors for all the hard work to make this release possible. Enjoy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077413#4077413 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077413

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: .Net parameter interoperabilty

by genady_yadata

Using @XmlRootElement + @XmlType(name="") helps? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077411#4077411 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077411

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Cannot find service endpoint target

by thomas.diesler＠jboss.com

Could you modify one of our EJB3 samples test cases to reproduce this issue. Ideally, you would create a jira issue and attach patch file against the testsuite. Does this occur with jbossws-2.0.1 as well? http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Source View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077410#4077410 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077410

18 years, 8 months

1
0
0 / 0

[JBossWS] - Cannot find service endpoint target

by hansOtto

I have deployed several Webservices as EJB endpoints successfully on the JBoss 4.2.1 with JBossWS 1.2.1. There are many SLSBs inside the Webservices, injected by the @EJB annotation and build as local deployment. Now, after upgrading from JBossWS 1.2.1 to JBossWS 2.0.0, I get the following error during the EAR deployment: 14:01:25,984 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/v1, warUrl=.../tmp/deploy/deploy.last-webservices.ear-webservices_ejb3.jar5109.war/ | 14:01:26,578 INFO [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to: file:/C:/jboss_4.2.1_WS/server/default/data/wsdl/deploy.last/webservices.ear/webservices_ejb3.jar/TestService5107.wsdl | 14:01:26,875 INFO [org.jboss.wsf.spi.management.BasicEndpointRegistry] register: jboss.ws:context=v1,endpoint=TestService | 14:03:09,734 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/C:/jboss_4.2.1_WS/server/default/tmp/deploy/tmp5106webservices.ear-contents/webservices_ejb3.jar | javax.xml.ws.WebServiceException: Cannot find service endpoint target: jboss.j2ee:name=TestService,service=EJB3,jar=webservices_ejb3.jar,ear=webservices.ear | at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.start(InvocationHandlerEJB3.java:78) | at org.jboss.wsf.spi.deployment.BasicLifecycleHandler.start(BasicLifecycleHandler.java:57) | at org.jboss.wsf.stack.jbws.LifecycleHandlerImpl.start(LifecycleHandlerImpl.java:40) | at org.jboss.wsf.spi.deployment.EndpointLifecycleDeployer.start(EndpointLifecycleDeployer.java:49) | at org.jboss.wsf.spi.deployment.BasicDeployerManager.deploy(BasicDeployerManager.java:81) | at org.jboss.wsf.container.jboss42.MainDeployerHook.deploy(MainDeployerHook.java:46) | at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) | 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 $Proxy32.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at sun.reflect.GeneratedMethodAccessor27.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 $Proxy9.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) I tried to debug the deployment process and noticed that the error occurred in line 77 of the InvocationHandlerEJB3: if (dispatcher.getRegistered(objectName.getCanonicalName()) ==null) | throw new WebServiceException("Cannot find service endpoint target: " + objectName); | The problem is, that the dispatcher wants to invoke the webservice project before it is registered. At this point, the dispatcher has all deployed projects registered except the webservice project. If I remove all SLSB with the @EJB injections from the Webservices, the deployment runs successfully. Has anybody an idea? Harry View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077405#4077405 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077405

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS-Security with JAX-RPC

by thomas.diesler＠jboss.com

That all looks good. Have a look at the logfile to see if the endpoint is really using that config (i.e. is it a secure endpoint?) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077404#4077404 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077404

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: WS-Security with JAX-RPC

by FabrizioLXXIII

jboss-web.xml <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" | "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd"> | <jboss-web> | <webservice-description> | <webservice-description-name>ws_producer</webservice-description-name> | <config-name>Standard WSSecurity Endpoint</config-name> | </webservice-description> | </jboss-web> jboss-wsse-server.xml <?xml version="1.0" encoding="UTF-8"?> | <jboss-ws-security | xmlns="http://www.jboss.com/ws-security/config" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd"> | <key-store-file>WEB-INF/wsse.keystore</key-store-file> | <key-store-password>jbossws</key-store-password> | <trust-store-file>WEB-INF/wsse.truststore</trust-store-file> | <trust-store-password>jbossws</trust-store-password> | <config> | <sign type="x509v3" alias="wsse" /> | <encrypt type="x509v3" alias="wsse" /> | <requires> | <signature /> | <encryption /> | </requires> | </config> | </jboss-ws-security> web.xml <?xml version="1.0" encoding="UTF-8"?> | <web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.4" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> | <description>JBoss Integration Test - WS-Security Test - WS Producer</description> | <display-name>JBoss Integration Test - WS-Security Test - WS Producer</display-name> | | <servlet> | <description>WS Producer Servlet</description> | <display-name>WS Producer Servlet</display-name> | <servlet-name>WsProducerServlet</servlet-name> | <servlet-class>it.auriga.jbossintegrationtest.wssecurity.producer.ServiceImpl</servlet-class> | </servlet> | | <servlet-mapping> | <servlet-name>WsProducerServlet</servlet-name> | <url-pattern>/service</url-pattern> | </servlet-mapping> | </web-app> application.xml <?xml version="1.0" encoding="UTF-8"?> | <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd"> | <application> | <display-name>JBoss Integration Test - WS-Security Test - WS Producer</display-name> | <module> | <web> | <web-uri>ws_producer.war</web-uri> | <context-root>/ws_producer</context-root> | </web> | </module> | </application> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077364#4077364 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077364

18 years, 8 months

1
0
0 / 0

[JBossWS] - Unable to create connection to jUDDI registry

by lretief

I am trying to establish a connection to the JBossWS (2.0.0) jUDDI registry from a standalone JVM client. First I tried, as per the samples, doing a: ConnectionFactory factory = ConnectionFactory.newInstance(); to get the ConnectionFactory, but it told me that it could not create an instance of null. So, reading the docs for ConnectionFactory, it said I should rather do a JNDI lookup, which I now successfully do as follows: Context ctx = new InitialContext(jndiProps); ConnectionFactory factory = (ConnectionFactory) ctx.lookup("JAXR"); I then set up all the properties as per docs and code: String queryurl = System.getProperty("jaxr.query.url", "http://localhost:8080/juddi/inquiry"); String puburl = System.getProperty("jaxr.publish.url", "http://localhost:8080/juddi/publish"); Properties props = new Properties(); props.setProperty("javax.xml.registry.queryManagerURL", queryurl); props.setProperty("javax.xml.registry.lifeCycleManagerURL", puburl); String transportClass = System.getProperty("juddi.proxy.transportClass", "org.jboss.jaxr.juddi.transport.SaajTransport"); System.setProperty("juddi.proxy.transportClass", transportClass); factory.setProperties(props); That all works. And now, the line that breaks it all: Connection connection = factory.createConnection(); My exception: [junit] java.lang.NullPointerException [junit] at org.apache.juddi.proxy.RegistryProxy.getTransport(RegistryProxy.java:459) [junit] at org.apache.juddi.proxy.RegistryProxy.init(RegistryProxy.java:189) [junit] at org.apache.juddi.proxy.RegistryProxy.(RegistryProxy.java:125) [junit] at org.apache.ws.scout.registry.ConnectionImpl.(ConnectionImpl.java:59) [junit] at org.apache.ws.scout.registry.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:86) Any help much appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077337#4077337 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077337

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: jboss4.0.5 + which version of jbossws + correct document

by thomas.diesler＠jboss.com

We don't release unless hudson says its all cool. We also pass the J2EE-1.4 and JavaEE5 CTS with every release http://jbws.dyndns.org:8280/hudson/ A good stating point is a working sample. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077316#4077316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077316

18 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Server startup hangs when injecting @WebServiceRef into

by thomas.diesler＠jboss.com

@WebServiceRef injection to MBeans is not supported. Pls use the JAXWS client API View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077314#4077314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077314

18 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users August 2007