September 2009 - jbossws-issues - Jboss List Archives

[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

[JBoss JIRA] Created: (JBWS-2776) WSDL unavailable for deployed web service in AS5.1

by Gary Brown (JIRA)

WSDL unavailable for deployed web service in AS5.1 -------------------------------------------------- Key: JBWS-2776 URL: https://jira.jboss.org/jira/browse/JBWS-2776 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Gary Brown Found an issue with an example for RiftSaw (BPEL engine) when used with ESB. The example uses JAX-WS services. The issue is recorded at: https://jira.jboss.org/jira/browse/RIFTSAW-55 The issue was that the endpoint address listed in the localhost:8080/jbossws/services console in AS5.1 was different to the one in AS4.2.3, and it navigated to an unavailable page, whereas the AS4.2.3 version displayed the correct WSDL. In AS5.1, it appears that if the war containing the JAX-WS service is embedded within another deployment (whether esb or ear), it includes the name of the parent deployment in the endpoint address. This extended endpoint address goes to an 'unavailable resource' error page, whereas the original shorter address results in a stack trace (shown in RiftSaw-55). I have attached an example ear containing the war, to demonstrate the issue. Install this in AS5.1, go to the jbossws/services console, and select the endpoint address link for either service. -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2772) Remove JBoss kernel dependencies from SPI, COMMON and all STACKS

by Richard Opalka (JIRA)

Remove JBoss kernel dependencies from SPI, COMMON and all STACKS ---------------------------------------------------------------- Key: JBWS-2772 URL: https://jira.jboss.org/jira/browse/JBWS-2772 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Priority: Critical Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 There are dependencies on JBoss kernel and its dependency management libraries in our code. This have to be located in AS IL to ensure correct JBossWS components abstractions. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2773) Remove AS IL from tests classpath

by Richard Opalka (JIRA)

Remove AS IL from tests classpath --------------------------------- Key: JBWS-2773 URL: https://jira.jboss.org/jira/browse/JBWS-2773 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 AS IL must not be visible to client side. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2740) Add Class-Path attribute to jbossws-cxf-client manifest file

by Alessio Soldano (JIRA)

Add Class-Path attribute to jbossws-cxf-client manifest file ------------------------------------------------------------ Key: JBWS-2740 URL: https://jira.jboss.org/jira/browse/JBWS-2740 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.1 The jbossws-cxf-client.jar we produce has a manifest file without the Class-Path attribute (see jbossws-native-client.jar instead). That is required for easy client classpath configuration when not using maven. Perhaps there's even a test for this (in native testsuite, as that would fail in cxf if it's in framework) -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2741) Evaluate removal of JAXWS API interfaces from jbossws-native-jaxws

by Alessio Soldano (JIRA)

Evaluate removal of JAXWS API interfaces from jbossws-native-jaxws ------------------------------------------------------------------ Key: JBWS-2741 URL: https://jira.jboss.org/jira/browse/JBWS-2741 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-3.2.1 At the current state there's probably no more reason for shipping the jaxws api inside the jbossws-native-jaxws instead of using the "official" jaxws api artifact. We might keep the jbossws-native-jaxws just for the service loads (the javax.xml.ws.spi.Provider for instance). This would simplify the m2 dependencies of projects referring to jaxws stuff (for instance jboss ejb3 client requires the jaxws api, but it's not good having that reference the jbossws-native-jaxws when using native and the jaxws-api when using metro/cxf stack). This need to be evaluated (both with jdk1.5 and jdk1.6), then changes to code, poms, manifests etc. can be done. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2764) Wrong SOAP stack version in JBoss webservices console

by Richard Opalka (JIRA)

Wrong SOAP stack version in JBoss webservices console ----------------------------------------------------- Key: JBWS-2764 URL: https://jira.jboss.org/jira/browse/JBWS-2764 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Affects Versions: jbossws-metro-3.2.0, jbossws-cxf-3.2.0 Reporter: Richard Opalka Assignee: Jim Ma Priority: Trivial Fix For: jbossws-cxf-3.2.1, jbossws-metro-3.2.1 -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2613) Ensure correct line ends in windows shell scripts (CRNL)

by Richard Opalka (JIRA)

Ensure correct line ends in windows shell scripts (CRNL) -------------------------------------------------------- Key: JBWS-2613 URL: https://jira.jboss.org/jira/browse/JBWS-2613 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0 It will be more comfortable for our users to modify these scripts. Now before touching them they need to convert them to correct windows format. -- 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, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2767) WSDL_DESCRIPTION population in MessageContext badly affects performances

by Alessio Soldano (JIRA)

WSDL_DESCRIPTION population in MessageContext badly affects performances ------------------------------------------------------------------------ Key: JBWS-2767 URL: https://jira.jboss.org/jira/browse/JBWS-2767 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.2.1 We read and transfer the wsdl to set the value for the javax.xml.ws.wsdl.description key in the MessageContext. On real world scenarios, this can cause bad performances due to the network latency. Despite the javadoc of MessageContext suggesting an InputSource for that value type, the JAXWS 2.1 spec says that has to be a URI and the Metro impl also use a URI. Using a URI would save a lot of time. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues September 2009