April 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2479) @XmlJavaTypeAdapter on SEI causes exception

by Alessio Soldano (JIRA)

@XmlJavaTypeAdapter on SEI causes exception ------------------------------------------- Key: JBWS-2479 URL: https://jira.jboss.org/jira/browse/JBWS-2479 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano When annotation a method/parameter in the SEI with @XmlJavaTypeAdapter, we get an exception from APT. See: https://jax-ws.dev.java.net/issues/show_bug.cgi?id=557 -- 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, 7 months

6
8
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-2262) WSDL is not correctly modified to use the configured https port

by Richard Nagy (JIRA)

WSDL is not correctly modified to use the configured https port --------------------------------------------------------------- Key: JBWS-2262 URL: https://jira.jboss.org/jira/browse/JBWS-2262 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBOSS version JBOSS-4.2.2.GA Linux 2.6.9-55.0 ELsmp Reporter: Richard Nagy When an ear file is deployed and used with the https protocol, the WSDL is not correctly modified to use the configured port numbers. The endpoint url in the wsdl is expected to be dynamically rebuilt during deployment. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2457) Update WS-Addressing tutorials to use JAXWS 2.1 AddressingFeature

by Alessio Soldano (JIRA)

Update WS-Addressing tutorials to use JAXWS 2.1 AddressingFeature ----------------------------------------------------------------- Key: JBWS-2457 URL: https://jira.jboss.org/jira/browse/JBWS-2457 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productivity Reporter: Alessio Soldano 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

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2320) Check JBossWS Maven Support on Windows OS

by Richard Opalka (JIRA)

Check JBossWS Maven Support on Windows OS ----------------------------------------- Key: JBWS-2320 URL: https://jira.jboss.org/jira/browse/JBWS-2320 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 Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4 It will make our community happy -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2587) Investigate why jaxws.samples.wssecurity.* tests are failing when running whole test suite

by Richard Opalka (JIRA)

Investigate why jaxws.samples.wssecurity.* tests are failing when running whole test suite ------------------------------------------------------------------------------------------ Key: JBWS-2587 URL: https://jira.jboss.org/jira/browse/JBWS-2587 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.0 Reporter: Richard Opalka Assignee: Alessio Soldano Priority: Optional Fix For: jbossws-native-3.1.1 Results : Failed tests: testUsernameTokenNegative(org.jboss.test.ws.jaxws.samples.wssecurity.SimpleUsernameTestCase) testUsernameTokenNegative(org.jboss.test.ws.jaxws.samples.wssecurity.SimpleDispatchTestCase) Tests run: 1438, Failures: 2, Errors: 0, Skipped: 0 I'd like to see that fixed. Feel free to reschedule to next release Alessio (since code freeze is away already) but if you have some time could you have a look now? The strange thing for me is we can't reproduce it on hudson. -- 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, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2630) Invalid "Endpoint Address" in http://localhost:8080/jbossws/services, when a .war is embedded in a jar.

by Daniel Bevenius (JIRA)

Invalid "Endpoint Address" in http://localhost:8080/jbossws/services, when a .war is embedded in a jar. --------------------------------------------------------------------------------------------------------- Key: JBWS-2630 URL: https://jira.jboss.org/jira/browse/JBWS-2630 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Priority: Minor I noticed this when working on getting examples for JBossESB running on JBoss AS 5. We have .esb archives (jar archives) that can contain a .war inside of them. For example, we have a quickstart that is named Quickstart_webservice_consumer1.esb which contains a Quickstart_webservice_consumer1.war. Deploying this on AS 5 will produce the following "Endpoint Address" in http://localhost:8080/jbossws/services: http://127.0.0.1:8080/Quickstart_webservice_consumer1-Quickstart_webservi... But if I try to access that the resource is not found. I was not sure about the component for this. The ContextServlet exists in the jbossws-framework project but I don't know if that maps to one of the components in the dropdown. -- 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, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2402) Upgrade jUDDI to 2.0rc5

by Alessio Soldano (JIRA)

Upgrade jUDDI to 2.0rc5 ----------------------- Key: JBWS-2402 URL: https://jira.jboss.org/jira/browse/JBWS-2402 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.0.5 We should upgrade jUDDI dependency to 2.0rc5 to satisfy the SOA-P requirements. See the forum thread for more details. -- 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, 8 months

2
17
0 / 0

[JBoss JIRA] Created: (JBWS-2247) Write test for JBWS-1190 from scratch using MessageContext properties

by Alessio Soldano (JIRA)

Write test for JBWS-1190 from scratch using MessageContext properties --------------------------------------------------------------------- Key: JBWS-2247 URL: http://jira.jboss.com/jira/browse/JBWS-2247 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Reporter: Alessio Soldano The JBWS-1190 test currently should be re-written using the message context properties (looking at the data dir is not a valid solution for metro and cxf). Also please note that the information coming from the jbossws/services console might be misleading. -- 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, 9 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2009