August 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2196) FastInfoset interoperability

by Thomas Diesler (JIRA)

FastInfoset interoperability ---------------------------- Key: JBWS-2196 URL: http://jira.jboss.com/jira/browse/JBWS-2196 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Thomas Diesler Alexander Philippou sais MSFT doesn't offer a Fast Infoset implementation. For WCF, Fast Infoset is provided by Noemax's WCF-Xtensions. I assume that general JBossWS<->WCF interop is given so we just need to focus on trying Fast Infoset as message encoding. This will also test content negotiation, which again is provided only by WCF-Xtensions. We have raised a test service, its wsdl is at http://www.noemax.com:8080/BenchmarkService?wsdl. It will be great if you can run a client to test it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1862) RPC DII Calls Assume child element of soap:body is called 'result' in the response message.

by Darran Lofthouse (JIRA)

RPC DII Calls Assume child element of soap:body is called 'result' in the response message. ------------------------------------------------------------------------------------------- Key: JBWS-1862 URL: http://jira.jboss.com/jira/browse/JBWS-1862 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-1.2.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.3 RPC DII Calls Assume child element of soap:body is called 'result' in the response message. For document style endpoints it will fall back to checking the type but for RPC calls if the name does not match the following error will be reported. java.rmi.RemoteException: Call invocation failed; nested exception is: org.jboss.ws.WSException: Cannot find child element: result at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:526) at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:276) ... Caused by: org.jboss.ws.WSException: Cannot find child element: result at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:866) at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:586) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:356) at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:507) ... 2 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-2165) Fix xop tests with maven build

by Thomas Diesler (JIRA)

Fix xop tests with maven build ------------------------------ Key: JBWS-2165 URL: http://jira.jboss.com/jira/browse/JBWS-2165 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Thomas Diesler Fix For: jbossws-metro-3.0.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
10
0 / 0

[JBoss JIRA] Created: (JBWS-2266) Schema Validation Feature Fails for Special Characters

by Richard Opalka (JIRA)

Schema Validation Feature Fails for Special Characters ------------------------------------------------------ Key: JBWS-2266 URL: https://jira.jboss.org/jira/browse/JBWS-2266 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.2 Reporter: Richard Opalka -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2206) WSDL imports are not replaced with absolute path

by Heiko Braun (JIRA)

WSDL imports are not replaced with absolute path ------------------------------------------------- Key: JBWS-2206 URL: http://jira.jboss.com/jira/browse/JBWS-2206 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-metro-3.0.2 SunRI does not support wsdlLocation on EJB endpoints -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-2252) Using swaref.xsd receive connection time out during deployment

by Gianni Mazza (JIRA)

Using swaref.xsd receive connection time out during deployment -------------------------------------------------------------- Key: JBWS-2252 URL: http://jira.jboss.com/jira/browse/JBWS-2252 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Environment: Windows. JBoss 4.0.5.GA Ejb3 enabled, Jbossws-native 2.0.3.GA Reporter: Gianni Mazza Hi, we have developed an application using JBoss 4.0.5.GA Ejb3 enabled with JBossws-native-2.0.3.GA. We use swaref to manage attachment for a web services. During the deploy of our application we see that we receive an error of "connetion time out" probably because the application try to reach the address http://ws-i.org/profiles/basic/1.1/swaref.xsd. ===================================================================================================== 2008-07-02 10:46:10,460 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.management.ServerConfigFactory' 2008-07-02 10:46:10,460 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] class org.jboss.wsf.spi.management.ServerConfigFactory Implementation: org.jboss.wsf.framework.management.ServerConfigFactoryImpl@383efa 2008-07-02 10:46:10,491 DEBUG [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory] parse: file:/D:/jboss-4.0.5.GA_RFI/jboss-4.0.5.GA/server/rfiws/tmp/jbossws/WrappedEndpointService50520.wsdl 2008-07-02 10:46:10,491 DEBUG [org.jboss.ws.core.utils.JBossWSEntityResolver] resolveEntity: [pub=http://ws-i.org/profiles/basic/1.1/swaref.xsd,sysid=http://ws-i.org/p...] 2008-07-02 10:46:10,507 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.management.ServerConfigFactory' 2008-07-02 10:46:10,507 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] class org.jboss.wsf.spi.management.ServerConfigFactory Implementation: org.jboss.wsf.framework.management.ServerConfigFactoryImpl@d41115 2008-07-02 10:46:43,367 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/D:/jboss-4.0.5.GA_RFI/jboss-4.0.5.GA/server/rfiws/tmp/deploy/tmp50486RFIPlatform.ear-contents/RFIPlatform-ejb.jar org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection timed out: connect at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:154) at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:321) at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:171) at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:52) at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.java:78) at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:71) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) at org.jboss.wsf.container.jboss40.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) at org.jboss.wsf.container.jboss40.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 $Proxy29.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.GeneratedMethodAccessor21.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java: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:490) at java.lang.Thread.run(Thread.java:595) Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectException: Connection timed out: connect at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:394) at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:178) at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:128) ... 83 more Caused by: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.Socket.connect(Socket.java:520) at java.net.Socket.connect(Socket.java:470) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:388) at sun.net.www.http.HttpClient.openServer(HttpClient.java:523) at sun.net.www.http.HttpClient.<init>(HttpClient.java:231) at sun.net.www.http.HttpClient.New(HttpClient.java:304) at sun.net.www.http.HttpClient.New(HttpClient.java:321) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934) at java.net.URL.openStream(URL.java:1007) at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader.java:588) at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reader.java:560) at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:385) ... 85 more ===================================================================================================== Actually the server is not connected to internet and we must take it disconnected. If we try on a server with internet connection enabled deployment seems to work well. We have seen that a similar bug was fixed with version 2.0.0 of jbossws, but we still have the problem with our version 2.0.3. Someone can help me? Are we doing something wrong? Thank you very much. Bye Gianni -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2244) EntityResolver is not used when schema imports are handled.

by Franz Willer (JIRA)

EntityResolver is not used when schema imports are handled. ----------------------------------------------------------- Key: JBWS-2244 URL: http://jira.jboss.com/jira/browse/JBWS-2244 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.2 Environment: System (*nix, windows,..) without internet access. Reporter: Franz Willer Priority: Minor Web service deployment fails when a schema file use an import ( e.g. http://www.w3.org/2001/xml.xsd). The reason therefore is that WSDL11Reader.handleSchemaImports does not use EntityResolver. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBWS-2207) Allow to fully initialize the WS stack

by Vladimir Ralev (JIRA)

Allow to fully initialize the WS stack -------------------------------------- Key: JBWS-2207 URL: http://jira.jboss.com/jira/browse/JBWS-2207 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Vladimir Ralev The first webmethod call either inbound or outbound is always very slow (for each method). Subsequent calls are fine. My guess is that some lazy initialization occurs at this time. We have an application that requires the first calls to be as fast as the subsequent calls. We need some API or a propery of the stack to allow to fully pre-initialize the stack. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2011) Signature is invalid error when the message contains \r

by Richard Opalka (JIRA)

Signature is invalid error when the message contains \r ------------------------------------------------------- Key: JBWS-2011 URL: http://jira.jboss.com/jira/browse/JBWS-2011 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Reporter: Richard Opalka Assigned To: Alessio Soldano Fix For: jbossws-native-2.0.4 Description of the problem is on the forum -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
12
0 / 0

[JBoss JIRA] Created: (JBWS-2129) Wrapper class is not found

by Thomas Diesler (JIRA)

Wrapper class is not found -------------------------- Key: JBWS-2129 URL: http://jira.jboss.com/jira/browse/JBWS-2129 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-1.0.1 Reporter: Thomas Diesler [tdiesler@tdvaio trunk]$ ant -Dtest=jaxws/handlerscope test Caused by: com.sun.xml.ws.model.RuntimeModelerException: runtime modeler error: Wrapper class org.jboss.test.ws.jaxws.handlerscope.jaxws.Echo is not found. Have you run APT to generate them? at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:287) at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:596) at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:543) at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:371) at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:258) at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322) at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188) at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467) at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parseAdapters(DeploymentDescriptorParserExt.java:291) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2008