November 2012 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3546) Support -a WSProvide option

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3546: ------------------------------------- Summary: Support -a WSProvide option Key: JBWS-3546 URL: https://issues.jboss.org/browse/JBWS-3546 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxws-tools-maven-plugin Reporter: Alessio Soldano Fix For: jbossws-jaxws-tools-maven-plugin-1.1.1.GA ... while moving to JBossWS 4.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

12 years

2
5
0 / 0

[JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration

by Chris Laprun (JIRA)

Chris Laprun created JBWS-3569: ---------------------------------- Summary: WSDL produced for a multi-port service contains invalid port addresses in clustered configuration Key: JBWS-3569 URL: https://issues.jboss.org/browse/JBWS-3569 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Chris Laprun Priority: Critical Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in ports containing the node URLs instead of the loadbalancer's. I've tried using the dynamic WSDL rewriting as described in https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster node port) that haven't been used to access the WSDL, the port used to access the WSDL has the proper address though. -- 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

12 years

3
4
0 / 0

[JBoss JIRA] (JBWS-3568) Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException

by Magesh Bojan (JIRA)

Magesh Bojan created JBWS-3568: ---------------------------------- Summary: 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 Priority: Critical 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

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] (JBWS-3567) Upgrade to Apache WSS4J 1.6.8

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3567: ------------------------------------- Summary: Upgrade to Apache WSS4J 1.6.8 Key: JBWS-3567 URL: https://issues.jboss.org/browse/JBWS-3567 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3566) Upgrade to Apache CXF 2.7

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3566: ------------------------------------- Summary: Upgrade to Apache CXF 2.7 Key: JBWS-3566 URL: https://issues.jboss.org/browse/JBWS-3566 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.2 -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3561) Allow enabling CXF MBean management in jboss-webservices.xml

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3561: ------------------------------------- Summary: Allow enabling CXF MBean management in jboss-webservices.xml Key: JBWS-3561 URL: https://issues.jboss.org/browse/JBWS-3561 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-4.2 Users can currently set the enable.cxf.management context-param prop to true in the web.xml for turning on the cxf management into the JBoss MBean server. This is not possible atm for EJB3 WS deployment. The configuration option should be exposed in jboss-webservices.xml -- 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

12 years, 1 month

2
2
0 / 0

[JBoss JIRA] (JBWS-3552) @XmlJavaTypeAdapter ignored on exception classes

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3552: ------------------------------------ Summary: @XmlJavaTypeAdapter ignored on exception classes Key: JBWS-3552 URL: https://issues.jboss.org/browse/JBWS-3552 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-4.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

12 years, 1 month

3
14
0 / 0

[JBoss JIRA] (JBWS-3426) Factor out EndpointService logic and update EndpointServiceDA

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3426: ------------------------------------- Summary: Factor out EndpointService logic and update EndpointServiceDA Key: JBWS-3426 URL: https://issues.jboss.org/browse/JBWS-3426 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Affects Versions: jbossws-cxf-4.0.1, jbossws-native-4.0.1 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.2, jbossws-native-4.0.2 As a consequence of having moved the registration of endpoints into EndpointRegistry in the AS7 EndpointService, the JBossWS Shared Testsuite test for the EndpointPublisher fails due to the published endpoint not being registered. That's because the ServiceTarget is not available in that case, hence the EndpointService is not installed. This needs to be solved by having the logic of the EndpointService being invoked differently by the EndpointServiceDA when there's not ServiceTarget available (the endpoint registration is still possible, as well as looking up the current mbeanserver, etc.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
7
0 / 0

[JBoss JIRA] (JBWS-3565) Simplify WS Ref creation process

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3565: ------------------------------------ Summary: Simplify WS Ref creation process Key: JBWS-3565 URL: https://issues.jboss.org/browse/JBWS-3565 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka -- 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

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (JBWS-3551) Extend UnifiedVirtualFile API with no-check findChild methods

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3551: ------------------------------------- Summary: Extend UnifiedVirtualFile API with no-check findChild methods Key: JBWS-3551 URL: https://issues.jboss.org/browse/JBWS-3551 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-4.1 The UnifiedVirtualFile abstraction in quite used for accessing file/resources in deployments. Most of the time, thought, the lookup of unified virtual file children leads to nothing (the required resource is simply missing) and a localized IOException is thrown. In most scenarios, that's not an actual "error", the procedure just implies trying multiple locations, and the exception is trapped and in most cases not even logged. We need new flavors of findChild(String child) and getChildren() methods also accepting a boolean flag to suppress exception, log a message (if the log level is enabled) and return null / empty collection if nothing is found. The new methods are to then to be used for instance to speed-up the jbossws-common ResourceResolverImpl, which currently badly affects performances in the jbossws-cxf stack, being is used whenever the Apache CXF resource resolver manager is also used. -- 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

12 years, 1 month

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2012