[JBoss JIRA] (JBWS-3584) Cannot configure timeout when reading WSDL creating javax.xml.ws.Service
by Rafael Sisto (JIRA)
Rafael Sisto created JBWS-3584:
----------------------------------
Summary: Cannot configure timeout when reading WSDL creating javax.xml.ws.Service
Key: JBWS-3584
URL: https://issues.jboss.org/browse/JBWS-3584
Project: JBoss Web Services
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Reporter: Rafael Sisto
When creating a new WS client using:
new javax.xml.ws.Service(URL wsdlLocation, QName serviceName)
If the URL successfully connects to the server holding the WSDL resource, when trying to read the file the WS client may hang waiting for the resource.
The only way to avoid this is configuring the system property: sun.net.client.defaultReadTimeout (-1 by default, no timeout), which may affect other functionalities.
This can be avoided storing the WSDL locally.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBWS-3582) JBossWS-CXF 4.1.1.Final Errata
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3582?page=com.atlassian.jira.plugin.... ]
Richard Opalka commented on JBWS-3582:
--------------------------------------
---
JBossAS 7.1.3.Final
---
[CXF-1519] Explicitly set the namespace of a WebFault
[CXF-2006] RespectBinding feature and not understood required extensibility elements
[JBWS-2561] XOP request not properly inlined
[JBWS-2480] Soap attachments are dropped on server response
[JBWS-3493] WS-Trust tests w/ PicketLink STS require PL 2.1.2.Final or greater
[JBWS-3441] Support CDI interceptors for POJO JAX-WS services
FIXME: [CXF-1519] Explicitely set the namespace of a WebFault
FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding
FIXME: [JBWS-3079] Add support for https protocol
FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader
FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol
> JBossWS-CXF 4.1.1.Final Errata
> ------------------------------
>
> Key: JBWS-3582
> URL: https://issues.jboss.org/browse/JBWS-3582
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: Richard Opalka
> Assignee: Richard Opalka
> Fix For: jbossws-cxf-4.1.1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBWS-3582) JBossWS-CXF 4.1.1.Final Errata
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3582?page=com.atlassian.jira.plugin.... ]
Richard Opalka commented on JBWS-3582:
--------------------------------------
---
JBossAS 7.1.2.Final
---
[CXF-1519] Explicitly set the namespace of a WebFault
[CXF-2006] RespectBinding feature and not understood required extensibility elements
[JBWS-2561] XOP request not properly inlined
[JBWS-2480] Soap attachments are dropped on server response
[JBWS-3493] WS-Trust tests w/ PicketLink STS require PL 2.1.2.Final or greater
[JBWS-3441] Support CDI interceptors for POJO JAX-WS services
FIXME: [CXF-1519] Explicitely set the namespace of a WebFault
FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding
FIXME: [JBWS-3079] Add support for https protocol
FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader
FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol
> JBossWS-CXF 4.1.1.Final Errata
> ------------------------------
>
> Key: JBWS-3582
> URL: https://issues.jboss.org/browse/JBWS-3582
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: Richard Opalka
> Assignee: Richard Opalka
> Fix For: jbossws-cxf-4.1.1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBWS-3582) JBossWS-CXF 4.1.1.Final Errata
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3582?page=com.atlassian.jira.plugin.... ]
Richard Opalka edited comment on JBWS-3582 at 12/21/12 3:47 AM:
----------------------------------------------------------------
---
JBossAS 7.1.1.Final
---
[CXF-1519] Explicitly set the namespace of a WebFault
[CXF-2006] RespectBinding feature and not understood required extensibility elements
[JBWS-2561] XOP request not properly inlined
[JBWS-2480] Soap attachments are dropped on server response
[JBWS-3493] WS-Trust tests w/ PicketLink STS require PL 2.1.2.Final or greater
[JBWS-3441] Support CDI interceptors for POJO JAX-WS services
FIXME: [CXF-1519] Explicitely set the namespace of a WebFault
FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding
FIXME: [JBWS-3079] Add support for https protocol
FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader
FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol
was (Author: ropalka):
---
JBossAS 7.1.1.Final
---
[CXF-1519] Explicitly set the namespace of a WebFault
[CXF-2006] RespectBinding feature and not understood required extensibility elements
[JBWS-2561] XOP request not properly inlined
[JBWS-2480] Soap attachments are dropped on server response
[JBWS-3493] WS-Trust tests w/ PicketLink STS require PL 2.1.2.Final or greater
[JBWS-3441] Support CDI interceptors for POJO JAX-WS services
FIXME: [CXF-1519] Explicitely set the namespace of a WebFault
FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding
FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader
FIXME: [JBWS-3079] Add support for https protocol
FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol
FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader
> JBossWS-CXF 4.1.1.Final Errata
> ------------------------------
>
> Key: JBWS-3582
> URL: https://issues.jboss.org/browse/JBWS-3582
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: Richard Opalka
> Assignee: Richard Opalka
> Fix For: jbossws-cxf-4.1.1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBWS-3582) JBossWS-CXF 4.1.1.Final Errata
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3582?page=com.atlassian.jira.plugin.... ]
Richard Opalka commented on JBWS-3582:
--------------------------------------
---
JBossAS 7.1.1.Final
---
[CXF-1519] Explicitly set the namespace of a WebFault
[CXF-2006] RespectBinding feature and not understood required extensibility elements
[JBWS-2561] XOP request not properly inlined
[JBWS-2480] Soap attachments are dropped on server response
[JBWS-3493] WS-Trust tests w/ PicketLink STS require PL 2.1.2.Final or greater
[JBWS-3441] Support CDI interceptors for POJO JAX-WS services
FIXME: [CXF-1519] Explicitely set the namespace of a WebFault
FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding
FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader
FIXME: [JBWS-3079] Add support for https protocol
FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol
FIXME: [JBWS-3330] RMI class loader disabled / CNFE with remote classloader
> JBossWS-CXF 4.1.1.Final Errata
> ------------------------------
>
> Key: JBWS-3582
> URL: https://issues.jboss.org/browse/JBWS-3582
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: Richard Opalka
> Assignee: Richard Opalka
> Fix For: jbossws-cxf-4.1.1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBWS-3568) Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
by Magesh Bojan (JIRA)
[ https://issues.jboss.org/browse/JBWS-3568?page=com.atlassian.jira.plugin.... ]
Magesh Bojan commented on JBWS-3568:
------------------------------------
Thanks Richard!
> Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
> ----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3568
> URL: https://issues.jboss.org/browse/JBWS-3568
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-integration
> Environment: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes"
> Reporter: Magesh Bojan
> Assignee: Richard Opalka
> Fix For: jbossws-cxf-4.1.1
>
> Attachments: hello.zip, HelloWorldServlet.java, HelloWorldServlet.java-fix
>
>
> Deploying attached sample creates the following error:
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sample]] (ServerService Thread Pool -- 55) JBWEB000289: Servlet Hello threw load() exception: org.jboss.msc.service.DuplicateServiceException: Service jboss.ws.endpoint."ws.deployment"."org.jboss.servlet.hello.BaseWebService" is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
> at org.jboss.as.webservices.service.EndpointService.install(EndpointService.java:193)
> at org.jboss.as.webservices.deployers.EndpointServiceDeploymentAspect.start(EndpointServiceDeploymentAspect.java:50)
> at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:131)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:123)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:102)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95)
> at org.jboss.servlet.hello.HelloWorldServlet.init(HelloWorldServlet.java:78) [classes:]
> at javax.servlet.GenericServlet.init(GenericServlet.java:242) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBWS-3568) Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3568?page=com.atlassian.jira.plugin.... ]
Richard Opalka commented on JBWS-3568:
--------------------------------------
The following code shows how it should be right - note it requires JBossWS release in AS7 trunk.
{code}
public void init() throws ServletException {
try {
Map<String,String> urlPatternToClassNameMap = new HashMap<String, String>();
WebservicesMetaData metadata = new WebservicesMetaData();
WebserviceDescriptionMetaData webserviceDescription = new WebserviceDescriptionMetaData(metadata);
metadata.addWebserviceDescription(webserviceDescription);
PortComponentMetaData portComponent = new PortComponentMetaData(webserviceDescription);
portComponent.setPortComponentName("HelloWebService"); //unique ID
portComponent.setServiceEndpointInterface(BaseWebService.class.getName());
portComponent.setWsdlPort(new QName("http://test", "HelloWebServicePort"));
portComponent.setWsdlService(new QName("http://test", "HelloWebService"));
portComponent.setServletLink("HelloWebService"); // automagically generated from URL pattern
webserviceDescription.addPortComponent(portComponent);
urlPatternToClassNameMap.put("/HelloWebService", BaseWebService.class.getName());
portComponent = new PortComponentMetaData(webserviceDescription);
portComponent.setPortComponentName("HeyWebService"); //unique ID
portComponent.setServiceEndpointInterface(BaseWebService.class.getName());
portComponent.setWsdlPort(new QName("http://test", "HeyWebServicePort"));
portComponent.setWsdlService(new QName("http://test", "HeyWebService"));
portComponent.setServletLink("HeyWebService"); // automagically generated from URL pattern
webserviceDescription.addPortComponent(portComponent);
urlPatternToClassNameMap.put("/HeyWebService", BaseWebService.class.getName());
context = PUBLISHER.publish("ws", Thread.currentThread().getContextClassLoader(), urlPatternToClassNameMap, metadata);
} catch (Exception e) {
throw new ServletException(e);
}
}
{code}
> Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
> ----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3568
> URL: https://issues.jboss.org/browse/JBWS-3568
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-integration
> Environment: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes"
> Reporter: Magesh Bojan
> Assignee: Richard Opalka
> Fix For: jbossws-cxf-4.1.1
>
> Attachments: hello.zip, HelloWorldServlet.java, HelloWorldServlet.java-fix
>
>
> Deploying attached sample creates the following error:
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sample]] (ServerService Thread Pool -- 55) JBWEB000289: Servlet Hello threw load() exception: org.jboss.msc.service.DuplicateServiceException: Service jboss.ws.endpoint."ws.deployment"."org.jboss.servlet.hello.BaseWebService" is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
> at org.jboss.as.webservices.service.EndpointService.install(EndpointService.java:193)
> at org.jboss.as.webservices.deployers.EndpointServiceDeploymentAspect.start(EndpointServiceDeploymentAspect.java:50)
> at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:131)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:123)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:102)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95)
> at org.jboss.servlet.hello.HelloWorldServlet.init(HelloWorldServlet.java:78) [classes:]
> at javax.servlet.GenericServlet.init(GenericServlet.java:242) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months