October 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2784) MetaDataBuilder chokes on multiple imports

by Heiko Braun (JIRA)

MetaDataBuilder chokes on multiple imports ------------------------------------------ Key: JBWS-2784 URL: https://jira.jboss.org/jira/browse/JBWS-2784 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Heiko Braun See MetaDataBuilder#replaceWSDL11PortAddress(...) and dependend issue. This piece of code, always sets a successfully matched port ('wsdlOneOnePort') to null when a subsequent import is parsed. It's basically missing the break statement: Iterator importsByNS = l.iterator(); while (importsByNS.hasNext()) { Import anImport = (Import)importsByNS.next(); wsdlOneOnePort = modifyPortAddress(anImport.getNamespaceURI(), portQName, serviceEndpointURL, anImport.getDefinition().getServices()); } -- 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

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2752) Add 'nocompile' option to wsconsume (command line)

by Alessio Soldano (JIRA)

Add 'nocompile' option to wsconsume (command line) -------------------------------------------------- Key: JBWS-2752 URL: https://jira.jboss.org/jira/browse/JBWS-2752 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: tools-jaxws Reporter: Alessio Soldano Fix For: jbossws-native-3.2.1 This option is only available in the Ant task version of the tool, while it's not there in the command line one. -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2783) Malformed URL exception when deploying wsdl with jms address

by Alessio Soldano (JIRA)

Malformed URL exception when deploying wsdl with jms address ------------------------------------------------------------ Key: JBWS-2783 URL: https://jira.jboss.org/jira/browse/JBWS-2783 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.2.1 When providing a custom wsdl contract for a jms endpoint (thus having a jms address), we get a MalformedURL exception due to the native stack trying to rewrite the address. <sjain> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/home/somil/Platforms/EAP/jboss-eap-5.0/jboss-as/server/default/deploy/myApp.jar/ <sjain> at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) <sjain> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177) <sjain> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1440) <sjain> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1158) <sjain> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1099) <sjain> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) <sjain> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1632) <sjain> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935) <sjain> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083) <sjain> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985) <sjain> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823) <sjain> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) <sjain> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:782) <sjain> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) <sjain> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) <sjain> at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) <sjain> at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) <sjain> at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) <sjain> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) <sjain> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1632) <sjain> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935) <sjain> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083) <sjain> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985) <sjain> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:775) <sjain> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540) <sjain> at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) <sjain> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256) <sjain> at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) <sjain> at org.jboss.Main.boot(Main.java:221) <sjain> at org.jboss.Main$1.run(Main.java:556) <sjain> at java.lang.Thread.run(Thread.java:636) <sjain> Caused by: org.jboss.ws.WSException: Malformed URL: jms://localhost:8080/jaxws-samples-jmstransport/OrganizationJMSEndpoint <sjain> at org.jboss.ws.metadata.builder.MetaDataBuilder.getServiceEndpointAddress(MetaDataBuilder.java:252) <sjain> at org.jboss.ws.metadata.builder.MetaDataBuilder.replaceAddressLocation(MetaDataBuilder.java:317) <sjain> at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:193) <sjain> at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50) <sjain> at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.java:76) <sjain> at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:69) <sjain> at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:129) <sjain> at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:76) <sjain> at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60) <sjain> at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:113) <sjain> at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) <sjain> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) <sjain> ... 29 more -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-2753) Leverage keep-alive connections to improve client side perfomances

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2753?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2753: ---------------------------------- Issue Type: Bug (was: Feature Request) Changed to bug fix, as in 3.2.0 (already using Netty) keep-alive was not available. > Leverage keep-alive connections to improve client side perfomances > ------------------------------------------------------------------ > > Key: JBWS-2753 > URL: https://jira.jboss.org/jira/browse/JBWS-2753 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-native-3.2.0 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-native-3.2.1 > > > The current NettyClient in jbossws-native core does not cache keep alive connections. Doing that instead would mean performance increase when performing sequences of invocations to the same url. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2777) Schema imports and includes not correctly processed by WSDL11Reader if same xsd previously processed.

by Darran Lofthouse (JIRA)

Schema imports and includes not correctly processed by WSDL11Reader if same xsd previously processed. ----------------------------------------------------------------------------------------------------- Key: JBWS-2777 URL: https://jira.jboss.org/jira/browse/JBWS-2777 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.0 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.1 This is a continuation of JBWS-2411 where an optimisation was put in place to prevent an OutOfMemoryError caused by circular schema includes. The change introduced a side effect and if subsequent imports or includes are found for the same schema as the processing is skipped because it has been performed once before the update of the schema location is also skipped. At the same time schemas with no target namespace are also silently dropped so if these are required by the referenced schemas further parsing will result in numerous errors being reported. -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBWS-2753) Leverage keep-alive connections to improve client side perfomances

by Darran Lofthouse (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2753?page=com.atlassian.jira.plug... ] Darran Lofthouse commented on JBWS-2753: ---------------------------------------- I would class this as a regression, I did think keep-alive was working with Remoting. > Leverage keep-alive connections to improve client side perfomances > ------------------------------------------------------------------ > > Key: JBWS-2753 > URL: https://jira.jboss.org/jira/browse/JBWS-2753 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-native-3.2.0 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-native-3.2.1 > > > The current NettyClient in jbossws-native core does not cache keep alive connections. Doing that instead would mean performance increase when performing sequences of invocations to the same url. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2736) jbossws-cxf-3.2.0 errata

by Richard Opalka (JIRA)

jbossws-cxf-3.2.0 errata ------------------------ Key: JBWS-2736 URL: https://jira.jboss.org/jira/browse/JBWS-2736 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Fix For: jbossws-cxf-3.2.0 -- 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

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2781) Allow use of custom ClientSocketChannelFactory

by Alessio Soldano (JIRA)

Allow use of custom ClientSocketChannelFactory ---------------------------------------------- Key: JBWS-2781 URL: https://jira.jboss.org/jira/browse/JBWS-2781 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.0 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.2.1 This basically cover the needs of https://jira.jboss.org/jira/browse/JBWS-2672 after the Remoting -> Netty refactoring of the native stack transport layer. We need to give users means of providing their own custom factory of sockets/channels. -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1822) Cannot find service endpoint target

by Harro Harten (JIRA)

Cannot find service endpoint target ----------------------------------- Key: JBWS-1822 URL: http://jira.jboss.com/jira/browse/JBWS-1822 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-2.0.1 Reporter: Harro Harten Hello, I´ve taken the TestSample called 'webservice' of the JbossWS-native-2.0.1GA package and modified it by adding a simple TestBean with the @EJB annotation inside of the 'EJB3Bean01.java'. This works very well, only if all classes are in the same package, if you move the TestBean in another package, the following Error occur: ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/C:/jboss_4.2.1_WS_2.0.1/server/default/tmp/deploy/tmp39184test.ear-contents/jaxws-samples-webservice01-ejb3.jar javax.xml.ws.WebServiceException: Cannot find service endpoint target: jboss.j2ee:name=EJB3Bean01,service=EJB3,jar=jaxws-samples-webservice01-ejb3.jar,ear=test.ear at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.init(InvocationHandlerEJB3.java:83) at org.jboss.wsf.framework.deployment.DefaultLifecycleHandler.create(DefaultLifecycleHandler.java:51) at org.jboss.wsf.framework.deployment.EndpointLifecycleDeploymentAspect.create(EndpointLifecycleDeploymentAspect.java:42) 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 $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.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor29.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´ve added the whole eclipse project as an attachment. Thanks, Harry -- 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

14 years, 6 months

6
8
0 / 0

[JBoss JIRA] Created: (JBWS-2714) JAXBIntroductions support

by Alessio Soldano (JIRA)

JAXBIntroductions support ------------------------- Key: JBWS-2714 URL: https://jira.jboss.org/jira/browse/JBWS-2714 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano JAXBIntros are currrently supported on Native stack only. We should investigate whether adding support for that in JBossWS-CXF / CXF is useful and how to do that. -- 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

14 years, 6 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2009