January 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1672) SunRI does not respect @HandlerChain on client SEI

by Thomas Diesler (JIRA)

SunRI does not respect @HandlerChain on client SEI -------------------------------------------------- Key: JBWS-1672 URL: http://jira.jboss.com/jira/browse/JBWS-1672 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 tests-run-internal: [junit] Running org.jboss.test.ws.jaxws.samples.handlerchain.HandlerChainTestCase [junit] FIXME: [JBWS-1671] SunRI client handler cannot set mime header [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 4.209 sec [junit] Test org.jboss.test.ws.jaxws.samples.handlerchain.HandlerChainTestCase FAILED @WebService(name="Endpoint") @SOAPBinding(style = SOAPBinding.Style.RPC) @HandlerChain(file = "jaxws-handlers-client.xml") // relative path from the class file public interface EndpointWithHandlerChain { public String echo(String input); } -- 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

16 years

4
12
0 / 0

[JBoss JIRA] Created: (JBWS-2774) Cleaned up dependency in cxf client module

by Jim Ma (JIRA)

Cleaned up dependency in cxf client module ------------------------------------------ Key: JBWS-2774 URL: https://jira.jboss.org/jira/browse/JBWS-2774 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-3.2.1 There is no aegis related jar files in client library, look at if we need to add other jar files to enable ws-*, aegis etc. Look at if we also can remove the geronimo-*.jar shipped in cxf and use Sun equivalent. -- 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

16 years

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...

by Chris Laprun (JIRA)

JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine... --------------------------------------------------------------------------------------------------------- Key: JBWS-2884 URL: https://jira.jboss.org/jira/browse/JBWS-2884 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Chris Laprun Priority: Blocker I get: Caused by: org.jboss.ws.WSException: Invalid HTTP server response [503] - Service Unavailable at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75) at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:570) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:369) at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:231) when attempting to connect to a remote webservice with JBoss WS but I can access it just fine using SOAPUI. The remote service is defined by: http://portalstandards.oracle.com/portletapp/portlets?WSDL I'm trying to access the getServiceDescription method. SOAP body as generated by JBoss WS is: <getServiceDescription xmlns="urn:oasis:names:tc:wsrp:v1:types"><registrationContext xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/><desiredLocales>en-US</desiredLocales><desiredLocales>en</desiredLocales></getServiceDescription> Requesting: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:oasis:names:tc:wsrp:v1:types"> <soapenv:Header/> <soapenv:Body> <getServiceDescription xmlns="urn:oasis:names:tc:wsrp:v1:types"><registrationContext xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/><desiredLocales>en-US</desiredLocales><desiredLocales>en</desiredLocales></getServiceDescription> </soapenv:Body> </soapenv:Envelope> in SOAP UI results in the expected result: <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="urn:oasis:names:tc:wsrp:v1:types"> <env:Body> <ns0:getServiceDescriptionResponse> <ns0:requiresRegistration>true</ns0:requiresRegistration> <ns0:customModeDescriptions itemName="urn:javax:portlet:mode:custom:edit_defaults"> <ns0:description xml:lang="en" resourceName="urn:javax:portlet:mode:custom:edit_defaults"> <ns0:value>This mode signifies that the portlet should render a screen to set the default values for the modifiable preferences that are typically changed in the EDIT screen. Calling this mode requires that the user must have administrator rights.</ns0:value> </ns0:description> </ns0:customModeDescriptions> <ns0:customModeDescriptions itemName="urn:javax:portlet:mode:custom:about"> <ns0:description xml:lang="en" resourceName="urn:javax:portlet:mode:custom:about"> <ns0:value>This mode should be used by the portlet to display information on the portlet's purpose, origin, version, etc.</ns0:value> </ns0:description> </ns0:customModeDescriptions> </ns0:getServiceDescriptionResponse> </env:Body> </env:Envelope> JBoss WS fails on with the above 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

16 years, 1 month

5
17
0 / 0

[JBoss JIRA] Created: (JBWS-2887) Update to Apache CXF 2.2.6

by Alessio Soldano (JIRA)

Update to Apache CXF 2.2.6 -------------------------- Key: JBWS-2887 URL: https://jira.jboss.org/jira/browse/JBWS-2887 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.3.0 Apache CXF 2.2.6 should be available soon -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2890) wsprovide tool sets returning object's name to the "return" in the java file when no name is provided in the endpoint

by Stelios Koussouris (JIRA)

wsprovide tool sets returning object's name to the "return" in the java file when no name is provided in the endpoint --------------------------------------------------------------------------------------------------------------------- Key: JBWS-2890 URL: https://jira.jboss.org/jira/browse/JBWS-2890 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.1.SP2 Reporter: Stelios Koussouris I use JBDS to create a "web service" based on a POJO. It generates some artifacts included some java source files. In the file named XXXResponse.java, there's some error code like: @XmlElement(namespace = "", name = "return") private String return; public String getReturn() { return this.return; } public void setReturn(String return1) { this.return = return; } "return" is a java key word, and can not be used as variable. This has been verified by a) JBDS generation of the webservice (Bottom-Up) b) wsprovide.sh (myself) -k c) wsprovide.bat (customer) by running JBDS on Windows The class itself when decompiled seems to have correctly the name to "_return" Hence, there seems to be an error in wsprovide tool creating the .java files (perhaps the wsdl as well) -- 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

16 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2021) app-client with client and server not sharing the same filesystem

by Alessio Soldano (JIRA)

app-client with client and server not sharing the same filesystem ----------------------------------------------------------------- Key: JBWS-2021 URL: http://jira.jboss.com/jira/browse/JBWS-2021 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assigned To: Alessio Soldano Fix For: jbossws-native-2.0.5 Some jax-rpc tests using app-client were failing due to JBVFS-17. This however pointed out that our current implementation for app-client is supposed to work only when server and client share the same filesystem (see the referenced forum thread). We should think about something like a buffering virtual file implementation that eagerly reads the referenced resources from the file system before the metadata it is contained in is bound to the JNDI. -- 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

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2903) MTOM/XOP root MIME part does not contain charset parameter

by David Boeren (JIRA)

MTOM/XOP root MIME part does not contain charset parameter ---------------------------------------------------------- Key: JBWS-2903 URL: https://jira.jboss.org/jira/browse/JBWS-2903 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Reporter: David Boeren Web service responses sent from JBoss that are MTOM/XOP encoded cannot be parsed by some clients because the root MIME part does not contain charset parameter. RFC2616 Sections 14.17 and 3.7.1 state that the charset is not required unless it differs from the implicit default of "ISO-8859-1". JBossWS is encoding the root MIME part in UTF8, so the charset must be provided. As such, this is a bug in JBossWS. -- 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

16 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2656) no soap 1.2 inline multireferences support

by Wojciech Oczkowski (JIRA)

no soap 1.2 inline multireferences support ------------------------------------------ Key: JBWS-2656 URL: https://jira.jboss.org/jira/browse/JBWS-2656 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.2 Environment: debian, jboss-4.2, sun-java-6 Reporter: Wojciech Oczkowski jbossws doesn't seem to support inline multireferences from soap 1.2 while consuming webservices from other enviroments (php for example) result like: <item> <name>item1</name> <product enc:id="ref1"> <name>product1</name> </product> </item> <item> <name>item2</name> <product enc:ref="#ref1"/> </item> is unmarshaled with item2 object with product object filled with null's -- 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

16 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2650) Evaluate providing a maven plugin for wsconsume/wsprovide

by Alessio Soldano (JIRA)

Evaluate providing a maven plugin for wsconsume/wsprovide --------------------------------------------------------- Key: JBWS-2650 URL: https://jira.jboss.org/jira/browse/JBWS-2650 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: tools-jaxws Reporter: Alessio Soldano -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2572) Marshalling JAXB element over SOAPHeader produces an empty element

by Jose Antonio (JIRA)

Marshalling JAXB element over SOAPHeader produces an empty element ------------------------------------------------------------------ Key: JBWS-2572 URL: https://jira.jboss.org/jira/browse/JBWS-2572 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.5 Environment: JDK 1.6, JBoss 4.2.3, Ubuntu Linux 8.10 Reporter: Jose Antonio Hello, I'm trying to set some ws security headers manually in a handler for a Web service client and server. I have generated JAXB bindings from WS Security schema and in the client, I generate a Security element with a UserNameToken inside. Then, I try to put it in the headers in my handler like this: public boolean handleMessage(SOAPMessageContext context) { ............................................ ObjectFactory fact = new ObjectFactory(); JAXBElement<SecurityHeaderType> secHead = fact.createSecurity(sec); Marshaller marshaller = ctx.createMarshaller(); SOAPEnvelope envelope = context.getMessage().getSOAPPart().getEnvelope(); SOAPHeader header = (envelope.getHeader() == null) ? envelope.addHeader() : envelope.getHeader(); marshaller.marshal(secHead,header); sec is a JAXB element with the Security element content and is not null and not empty. If I execute my client with this handler in local, using JAX-WS RI 2.1, I get the expected behavior and I get a header with a Security element and a UserNameToken inside. But when I deploy my client in JBoss and try to execute it, I get an empty Security element. There is no UserNameToken inside. I tried the following workaround and it works for JBoss: DocumentBuilder builder = DocumentBuilderFactory.newInstance().newDocumentBuilder(); Document doc = builder.newDocument(); marshaller.marshal(secHead, doc); SOAPFactory sFact = SOAPFactory.newInstance(); header.appendChild(sFact.createElement(doc.getDocumentElement())); However, it's not the optimum way of doing it, since I need to create two factories and an intermediary document only to append a child to a header, while it could be done only with one sencence. -- 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

16 years, 1 month

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2010