October 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2372) Protocol not considered when re-writing address in WSDL based on request address.

by Darran Lofthouse (JIRA)

Protocol not considered when re-writing address in WSDL based on request address. --------------------------------------------------------------------------------- Key: JBWS-2372 URL: https://jira.jboss.org/jira/browse/JBWS-2372 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.0.5 When the address in the WSDL is dynamically re-written the request host and port are used in the re-write but the protocol is not used. If the WSDL is requested with: - https://localhost:9443/PhoneBook?wsdl The resulting address in the WSDL is: - http://localhost:9443/PhoneBook So still the secure port but no 'https' -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2299) Run TCK5 jws test suite and detect issues

by Richard Opalka (JIRA)

Run TCK5 jws test suite and detect issues ----------------------------------------- Key: JBWS-2299 URL: https://jira.jboss.org/jira/browse/JBWS-2299 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: 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, 3 months

2
3
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, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2371) Fix maven build to include right woodstox artifact

by Alessio Soldano (JIRA)

Fix maven build to include right woodstox artifact -------------------------------------------------- Key: JBWS-2371 URL: https://jira.jboss.org/jira/browse/JBWS-2371 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5 woodstox 3.2.6 should be included from the jboss maven repo, where it lives under a different groupId: org.codehaus.woodstox -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2315) URL.openStream fails in Vista with Connect exception due to IPv6

by Alessio Soldano (JIRA)

URL.openStream fails in Vista with Connect exception due to IPv6 ---------------------------------------------------------------- Key: JBWS-2315 URL: https://jira.jboss.org/jira/browse/JBWS-2315 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-3.0.5 Magesh says: "should we set jvm arg in ant build file by default?" <jvmarg value="-Djava.net.preferIPv4Stack=true"/> -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-2339) There are ugly hacks regarding endpoint state that needs to be fixed

by Richard Opalka (JIRA)

There are ugly hacks regarding endpoint state that needs to be fixed -------------------------------------------------------------------- Key: JBWS-2339 URL: https://jira.jboss.org/jira/browse/JBWS-2339 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5 Take a look e.g. to AbstractAspectizedEndpointServlet + AbstractEndpointServlet how they're leveraging endpoint state. AbstractEndpointServlet is calling endpoint start()/stop() template methods to simulate endpoint start/stop events. These ugly hacks needs to be removed and proper LifecycleDeploymentAspect or something like that needs to be introduced. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2366) Restore missing images on wiki

by Alessio Soldano (JIRA)

Restore missing images on wiki ------------------------------ Key: JBWS-2366 URL: https://jira.jboss.org/jira/browse/JBWS-2366 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5 The missing images need to be restored on the wiki and put in SVN so that they don't get lost again (this was caused by the hardware failure and following change of the jbws wiki box which should not happen anymore... however it's better having them in SVN). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2365) Fix JBossWS-3.0.4.GA-testsuite-AS5.0.x job on hudson

by Alessio Soldano (JIRA)

Fix JBossWS-3.0.4.GA-testsuite-AS5.0.x job on hudson ---------------------------------------------------- Key: JBWS-2365 URL: https://jira.jboss.org/jira/browse/JBWS-2365 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.0.4 See http://hudson.qa.jboss.com/hudson/job/JBossWS-3.0.4.GA-testsuite-AS5.0.x -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2359) jbossws-cxf-3.0.4 errata

by Alessio Soldano (JIRA)

jbossws-cxf-3.0.4 errata ------------------------ Key: JBWS-2359 URL: https://jira.jboss.org/jira/browse/JBWS-2359 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.0.4 -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2357) jbossws-metro-3.0.4 errata

by Alessio Soldano (JIRA)

jbossws-metro-3.0.4 errata -------------------------- Key: JBWS-2357 URL: https://jira.jboss.org/jira/browse/JBWS-2357 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Fix For: jbossws-metro-3.0.4 -- 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, 3 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2008