May 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1671) SunRI client handler cannot set mime header

by Thomas Diesler (JIRA)

SunRI client handler cannot set mime header ------------------------------------------- Key: JBWS-1671 URL: http://jira.jboss.com/jira/browse/JBWS-1671 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-sunri Reporter: Thomas Diesler Fix For: jbossws-2.1.0 [tdiesler@tddell sunri]$ ant -Dtest=jaxws/samples/handlerchain test tests-run-internal: [junit] Running org.jboss.test.ws.jaxws.samples.handlerchain.HandlerChainTestCase [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 4.162 sec [junit] Test org.jboss.test.ws.jaxws.samples.handlerchain.HandlerChainTestCase FAILED Caused by: java.lang.IllegalStateException: Unexpected cookie list: null at org.jboss.test.ws.jaxws.samples.handlerchain.ClientMimeHandler.handleInbound(ClientMimeHandler.java:64) at org.jboss.wsf.spi.handler.GenericHandler.handleMessage(GenericHandler.java:55) at com.sun.xml.ws.handler.HandlerProcessor.callHandleMessageReverse(HandlerProcessor.java:313) at com.sun.xml.ws.handler.HandlerProcessor.callHandlersResponse(HandlerProcessor.java:195) at com.sun.xml.ws.handler.ClientSOAPHandlerTube.callHandlersOnResponse(ClientSOAPHandlerTube.java:181) -- 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

13 years, 8 months

3
13
0 / 0

[JBoss JIRA] Created: (JBWS-2329) Failed to deploy service with multiple bindings

by Alessio Soldano (JIRA)

Failed to deploy service with multiple bindings ----------------------------------------------- Key: JBWS-2329 URL: https://jira.jboss.org/jira/browse/JBWS-2329 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-3.0.3 Reporter: Alessio Soldano When deploying an archive containing two endpoint corresponding to two wsdl binding of the same wsdl service, we get this exception: javax.xml.ws.WebServiceException: Not a primary WSDL=file:/home/alessio/dati/jboss-4.2-src/build/output/jboss-4.2.4.GA/server/default/tmp/deploy/tmp50323jaxws-jbws2278-exp.war/WEB-INF/wsdl/Test.wsdl since it doesn't have Service {http://org.jboss.test.ws/jbws2278}TestEndpointImplSoap12Service at com.sun.xml.ws.server.EndpointFactory.verifyPrimaryWSDL(EndpointFactory.java:455) at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:155) at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467) at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parseAdapters(DeploymentDescriptorParserExt.java:301) at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parse(DeploymentDescriptorParserExt.java:178) at org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect.start(RuntimeModelDeploymentAspect.java:110) ... 66 more See the testcase for JBWS-2278. This could be related to a missing configuration in the generate sun-jaxws.xml. -- 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

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-1949) MEtro MTOM ignores content-type on attachment part

by Heiko Braun (JIRA)

MEtro MTOM ignores content-type on attachment part -------------------------------------------------- Key: JBWS-1949 URL: http://jira.jboss.com/jira/browse/JBWS-1949 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-metro Affects Versions: jbossws-2.0.3 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.1.0 It turns everything into application/octet-stream on a DataHandler instance, even though the attachment part contains an explicit content-type. -- 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

13 years, 8 months

4
17
0 / 0

[JBoss JIRA] Created: (JBWS-1777) WSProvide output is not correctly redirected

by Heiko Braun (JIRA)

WSProvide output is not correctly redirected -------------------------------------------- Key: JBWS-1777 URL: http://jira.jboss.com/jira/browse/JBWS-1777 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Heiko Braun See WSProvideTestCase -- 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

13 years, 8 months

4
18
0 / 0

[JBoss JIRA] Created: (JBWS-2127) Cannot generate WSDL for binding "http://www.w3.org/2003/05/soap/bindings/HTTP/"

by Thomas Diesler (JIRA)

Cannot generate WSDL for binding "http://www.w3.org/2003/05/soap/bindings/HTTP/" -------------------------------------------------------------------------------- Key: JBWS-2127 URL: http://jira.jboss.com/jira/browse/JBWS-2127 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-1.0.1 Reporter: Thomas Diesler [tdiesler@tdvaio trunk]$ ant -Dtest=jaxws/binding test Caused by: com.sun.xml.ws.server.ServerRtException: Cannot generate WSDL for binding "http://www.w3.org/2003/05/soap/bindings/HTTP/" at com.sun.xml.ws.server.EndpointFactory.generateWSDL(EndpointFactory.java:415) at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:196) at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467) at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parseAdapters(DeploymentDescriptorParserExt.java:291) at org.jboss.wsf.stack.metro.DeploymentDescriptorParserExt.parse(DeploymentDescriptorParserExt.java:167) at org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect.create(RuntimeModelDeploymentAspect.java:111) -- 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

13 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-2390) Cannot get wsit-rt and wsit-tools artifact from Metro 1.4 sources

by Alessio Soldano (JIRA)

Cannot get wsit-rt and wsit-tools artifact from Metro 1.4 sources ----------------------------------------------------------------- Key: JBWS-2390 URL: https://jira.jboss.org/jira/browse/JBWS-2390 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Fix For: jbossws-metro-3.0.6 We currently get the wsit-rt and wsit-tools artifacts from the Metro/WSIT sources. * cvs -d :pserver:username@cvs.dev.java.net:/cvs checkout -r metro1_4-release wsit/wsit * ant jar * ant create-wsit-rt-jar * ant create-wsit-tools-jar Starting from Metro 1.4 the create-wsit-rt-jar and create-wsit-tools-jar targets are not available anymore. It's quite trivial to restore them, but we should get in touch with Sun about this. -- 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

13 years, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-2915) WSDL metadata is missing in EPR

by Richard Opalka (JIRA)

WSDL metadata is missing in EPR ------------------------------- Key: JBWS-2915 URL: https://jira.jboss.org/jira/browse/JBWS-2915 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Richard Opalka The following test org.jboss.test.ws.jaxws.endpointReference.EndpointReferenceTestCase fail with the following exception: javax.xml.ws.WebServiceException: WSDL metadata is missing in EPR at com.sun.xml.ws.spi.ProviderImpl.getPort(ProviderImpl.java:147) at javax.xml.ws.EndpointReference.getPort(EndpointReference.java:158) at org.jboss.test.ws.jaxws.endpointReference.EndpointReferenceTestCase.innerTestDispatch(EndpointReferenceTestCase.java:135) at org.jboss.test.ws.jaxws.endpointReference.EndpointReferenceTestCase.testDispatchWithFeatures(EndpointReferenceTestCase.java:148) -- 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

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2946) Review deploy scripts for installing jbws to every profile meant for having ws

by Alessio Soldano (JIRA)

Review deploy scripts for installing jbws to every profile meant for having ws ------------------------------------------------------------------------------ Key: JBWS-2946 URL: https://jira.jboss.org/jira/browse/JBWS-2946 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-metro, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.3.0.Beta2, jbossws-metro-3.3.0.Beta2, jbossws-native-3.3.0.Beta5 See http://community.jboss.org/thread/148499?tstart=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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2957) TODO - better description

by Richard Opalka (JIRA)

TODO - better description ------------------------- Key: JBWS-2957 URL: https://jira.jboss.org/jira/browse/JBWS-2957 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.3.0.Beta5 -- 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

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2928) Use JBoss provided EE APIs

by Richard Opalka (JIRA)

Use JBoss provided EE APIs -------------------------- Key: JBWS-2928 URL: https://jira.jboss.org/jira/browse/JBWS-2928 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.3.1, jbossws-metro-3.3.1, jbossws-cxf-3.3.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

13 years, 8 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2010