March 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2435) Evaluate moving jbossws documentation to http://www.jboss.org/community/docs/

by Alessio Soldano (JIRA)

Evaluate moving jbossws documentation to http://www.jboss.org/community/docs/ ----------------------------------------------------------------------------- Key: JBWS-2435 URL: https://jira.jboss.org/jira/browse/JBWS-2435 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Priority: Minor Fix For: jbossws-native-3.0.6, jbossws-metro-3.0.6, jbossws-cxf-3.0.6 -- 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

15 years

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2588) Webservice deployed within EAR fails but war file only deployment successful

by Paul Smith (JIRA)

Webservice deployed within EAR fails but war file only deployment successful ---------------------------------------------------------------------------- Key: JBWS-2588 URL: https://jira.jboss.org/jira/browse/JBWS-2588 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: Currently using JBoss AS 5.0.1GA on Windows XP JRE 1.6.11 Reporter: Paul Smith I have created a simple annotated web service and it added it to a WAR. If this is deployed from eclipse to the JBoss server it deploys correctly and is accessible. If the the same WAR is then contained within an EAR file and deployed. The deployment fails with the following: 12:41:07,967 ERROR [[TestWs]] Allocate exception for servlet TestWs javax.xml.ws.WebServiceException: Cannot obtain endpoint for: jboss.ws:context=/WebService,endpoint=TestWs at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initEndpoint(AbstractEndpointServlet.java:153) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initServiceEndpoint(AbstractEndpointServlet.java:124) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.init(AbstractEndpointServlet.java:72) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- 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

15 years

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2151) We have to distribute wsrunclient.sh(.bat) for Metro and CXF

by Richard Opalka (JIRA)

We have to distribute wsrunclient.sh(.bat) for Metro and CXF ------------------------------------------------------------ Key: JBWS-2151 URL: http://jira.jboss.com/jira/browse/JBWS-2151 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Reporter: Richard Opalka -- 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

15 years

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2405) MTOM/XOP Interoperability - cid href URLEncode/URLDecode

by Chyi Pin Lim (JIRA)

MTOM/XOP Interoperability - cid href URLEncode/URLDecode -------------------------------------------------------- Key: JBWS-2405 URL: https://jira.jboss.org/jira/browse/JBWS-2405 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Environment: 14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) 14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc. 14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun Microsystems Inc. 14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core 14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA Reporter: Chyi Pin Lim WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the attachment is not URL Encoded. As such, JBossWS is unable to find the attachment. Example: <xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750" xmlns:xop="http://www.w3.org/2004/08/xop/include"/> --uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1 Content-ID: <http://tempuri.org/1/633631227250468750> Since this is an interoperability issue, I don't know how to create a test case under the test suite to simulate this error. -- 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

15 years

4
5
0 / 0

[JBoss JIRA] Created: (JBWS-2538) FastInfoset interoperability

by Alessio Soldano (JIRA)

FastInfoset interoperability ---------------------------- Key: JBWS-2538 URL: https://jira.jboss.org/jira/browse/JBWS-2538 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.1.1 We should do some tests using fastinfoset with jbossws-cxf like we did with jbossws-native. See linked issue. -- 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

15 years

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2514) wsprovide.sh missing libraries

by Bryan Kearney (JIRA)

wsprovide.sh missing libraries ------------------------------ Key: JBWS-2514 URL: https://jira.jboss.org/jira/browse/JBWS-2514 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Environment: JBoss 5.0.0 GA, Metro 3.0.5GA, Sun jdk 1.6.11, Fedora 10 Reporter: Bryan Kearney The wsprovide.sh script fails when attempting to generate the artifacts. It failed to locate the following classes: org.jboss.ws.core.soap.SAAJMetaFactoryImpl com.sun.xml.ws.security.secext10.SecurityTokenReferenceType My solution was to edit the file with these lines: WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jbossws-native-core.jar" WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/xws-security.jar" Having copied the jar files from the default deployers directory. I believe this is related to https://jira.jboss.org/jira/browse/JBWS-2511 -- 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

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2565) Problems with security after moving from AS 4.2.x series to AS 5.0.x series

by Richard Opalka (JIRA)

Problems with security after moving from AS 4.2.x series to AS 5.0.x series --------------------------------------------------------------------------- Key: JBWS-2565 URL: https://jira.jboss.org/jira/browse/JBWS-2565 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.5, jbossws-native-3.1.0 Reporter: Richard Opalka Fix For: jbossws-native-3.1.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

15 years

3
10
0 / 0

[JBoss JIRA] Created: (JBWS-2259) Review MTOM Detection

by Darran Lofthouse (JIRA)

Review MTOM Detection --------------------- Key: JBWS-2259 URL: https://jira.jboss.org/jira/browse/JBWS-2259 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.0.3 Currently MTOM is only enabled if a type annotated with @XmlMimeType - the content-type headers from the incoming message should be sufficient to decide is MTOM is required. -- 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

15 years

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2590) 4 wsappclient_reverse failures

by Alessio Soldano (JIRA)

4 wsappclient_reverse failures ------------------------------ Key: JBWS-2590 URL: https://jira.jboss.org/jira/browse/JBWS-2590 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.1.0 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.1.1 Analyze and solve failures in the following tests: src/com/sun/ts/tests/jaxws/ee/w2j/document/literal/marshalltest/Client.java#MarshallListTypesTest_from_wsappclient_reverse src/com/sun/ts/tests/jaxws/ee/w2j/rpc/literal/parametermodetest/Client.java#InOutSimpleTypesTest_from_wsappclient_reverse src/com/sun/ts/tests/jaxws/ee/w2j/rpc/literal/parametermodetest/Client.java#InSimpleTypesTest_from_wsappclient_reverse src/com/sun/ts/tests/jaxws/ee/w2j/rpc/literal/parametermodetest/Client.java#OutSimpleTypesTest_from_wsappclient_reverse Please note all failures are with appclient and in reverse tests (deploy against RI). -- 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

15 years

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2589) Some deployment failures prevent re-deployment

by Darran Lofthouse (JIRA)

Some deployment failures prevent re-deployment ---------------------------------------------- Key: JBWS-2589 URL: https://jira.jboss.org/jira/browse/JBWS-2589 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-metro, jbossws-native Affects Versions: jbossws-cxf-3.1.0, jbossws-metro-3.1.0, jbossws-native-3.1.0 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.1.1, jbossws-metro-3.1.1, jbossws-cxf-3.1.1 Deployment failures at the wrong point can leave an endpoint registered, undeployment does not remove the registration so further deployments fail with errors similar to: - java.lang.IllegalStateException: Endpoint already registered: jboss.ws:context=x_jboss,endpoint=X_Service The underlying cause is that the deployment aspects are not used to undeploy the endpoint if the deployment fails part way through, the aspect responsible for registration then rejects the second attempt as it appears it is already deployed. -- 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

15 years

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 March 2009