September 2009 - jbossws-issues - Jboss List Archives

[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, 7 months

1
5
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, 7 months

1
2
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, 7 months

4
18
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, 7 months

4
17
0 / 0

[JBoss JIRA] Created: (JBWS-2131) WebServiceException: Failed to build METRO runtime model

by Thomas Diesler (JIRA)

WebServiceException: Failed to build METRO runtime model -------------------------------------------------------- Key: JBWS-2131 URL: http://jira.jboss.com/jira/browse/JBWS-2131 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/jbws1702 test 19:24:24,883 ERROR [MainDeployer] Could not start deployment: file:/home/tdiesler/svn/jbossws/stack/metro/trunk/output/tests/libs/jaxws-jbws1702.war javax.xml.ws.WebServiceException: Failed to build METRO runtime model at org.jboss.wsf.stack.metro.metadata.RuntimeModelDeploymentAspect.create(RuntimeModelDeploymentAspect.java:136) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) 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) -- 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, 7 months

3
9
0 / 0

[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, 7 months

3
13
0 / 0

[JBoss JIRA] Created: (JBWS-2596) Resource injection in jaxws endpoints and handlers

by Richard Opalka (JIRA)

Resource injection in jaxws endpoints and handlers -------------------------------------------------- Key: JBWS-2596 URL: https://jira.jboss.org/jira/browse/JBWS-2596 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Reporter: Richard Opalka Fix For: jbossws-cxf-3.2.0, jbossws-metro-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

13 years, 8 months

3
14
0 / 0

[JBoss JIRA] Created: (JBWS-2637) incorrect namespace for fault messages

by Bart Vanhaute (JIRA)

incorrect namespace for fault messages -------------------------------------- Key: JBWS-2637 URL: https://jira.jboss.org/jira/browse/JBWS-2637 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.1 Environment: JBossAS-4.2.3.GA Reporter: Bart Vanhaute There is a problem with the namespace for web faults when this namespace is not the same as the namespace of the service. The type definition of the web faults has the correct namespace, but the reference to the type from the message part elements uses the name space qualifier (tns) of the service instead. See the jboss forum for an example. Note: I now tested this again with the 3.1.1 version, and the problem is still the same. -- 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
2
0 / 0

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

by Alessio Soldano (JIRA)

JAXBIntroductions support ------------------------- Key: JBWS-2715 URL: https://jira.jboss.org/jira/browse/JBWS-2715 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Fix For: community contributions JAXBIntros are currrently supported on Native stack only. We should investigate whether adding support for that in JBossWS-Metro 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

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-1716) Erroneous UTF-8 character encoding when marshalling on machines with non-UTF-8 default encoding

by floe fliep (JIRA)

Erroneous UTF-8 character encoding when marshalling on machines with non-UTF-8 default encoding ----------------------------------------------------------------------------------------------- Key: JBWS-1716 URL: http://jira.jboss.com/jira/browse/JBWS-1716 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Reporter: floe fliep When sending a client request which includes a non-ASCII UTF-8 character such as the "ç" in "Français" on a machine which has the default character encoding set to something different than UTF-8, the encoding is erroneous. For example, the "ç" in the example above is marshalled on the network stream as 0xC3 0x83 0xC2 0xA7 instead of the legal UTF-8 sequence being 0xC3 0xA7, when the machine's default character set is set to MS1252 in this case (Windows). A fix for this is setting the system property file.encoding=utf-8, but this causes as many problems elsewhere as it fixes (especially in the case of legacy platform-specific file reading) ... . A forum post is highly likely to expose the same phenomenon: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030510#4030510 After some good hours of stepping through the JBossWS code, I discovered what I guess must be the culprit in the method XMLFragment.writeSourceInternal(Writer writer): .... if (reader == null) reader = new InputStreamReader(streamSource.getInputStream()); Here streamSource.getInputStream() is an already UTF-8 encoded stream. However, when a new instance of InputStreamReader is created around it, it will be set to the machine's default character encoding, thus effectively interpreting bytes from the UTF-8 stream in a different encoding scheme, resulting in corrupted data. Each time data passes through the marschalling corruption is added, effectively worsening wrong character count when data is passed back and forth. I would suggest attaching a reader to the StreamSource source instance var so that it keeps track of its encoding, but that might break things elsewhere ... -- 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, 9 months

4
8
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