February 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

14 years, 1 month

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

14 years, 1 month

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

14 years, 1 month

5
17
0 / 0

[JBoss JIRA] Created: (JBWS-2940) Wrong namespace on SOAP operation when a method with header parameter having a new namespace is invoked, "second" after a method that does not have this namespace'd parameter

by Magesh Kumar B (JIRA)

Wrong namespace on SOAP operation when a method with header parameter having a new namespace is invoked, "second" after a method that does not have this namespace'd parameter ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBWS-2940 URL: https://jira.jboss.org/jira/browse/JBWS-2940 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Magesh Kumar B Assignee: Alessio Soldano Fix for JBPAPP-3785 -- 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, 1 month

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

14 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

14 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

14 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2947) WSException on client side when server sends a 100-continue HTTP response code

by Silvano Maffeis (JIRA)

WSException on client side when server sends a 100-continue HTTP response code ------------------------------------------------------------------------------ Key: JBWS-2947 URL: https://jira.jboss.org/jira/browse/JBWS-2947 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.1 Environment: Windows 2003 with IIS 6 Reporter: Silvano Maffeis JBossWS native 3.2.1 clients give an exception when they receive a HTTP "100-continue" response from the server. This is often the case when using a JBossWS client to call a .NET web service running on IIS version 6. This cannot be seen as an IIS bug since HTTP/1.1 clients should be able to deal with 100-continue response codes. Also see the following article: http://blogs.msdn.com/david.wang/archive/2006/04/05/HTTP-SYS-IIS-and-the-... The exception I'm getting on the client side: Caused by: org.jboss.ws.WSException: Invalid HTTP server response [100] - Continue at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75) at org.jboss.ws.core.client.transport.NettyClient.invokeInternal(NettyClient.java:189) ... 79 more -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2943) Inconsistent / Incomplete handling of CONFIDENTIAL transport-guarantee defined in jboss.xml compared to @WebContext annotation

by Darran Lofthouse (JIRA)

Inconsistent / Incomplete handling of CONFIDENTIAL transport-guarantee defined in jboss.xml compared to @WebContext annotation ------------------------------------------------------------------------------------------------------------------------------ Key: JBWS-2943 URL: https://jira.jboss.org/jira/browse/JBWS-2943 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.Beta4 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3 If the transport-guarantee is set to CONFIDENTIAL using the @WebContext annotation then the following happens: - 1 - The services page https://localhost:8443/jbossws/services lists access to the WSDL using a https address. 2 - The address in the WSDL is a https address. (Regardless of if WSDL is accessed over http or https) 3 - The endpoint called over http results in a 302 status being returned. If the transport-guarantee is defined in the jboss.xml then only the following happens: - 3 - The endpoint called over http results in a 302 status being returned. The first two report only http addresses. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2917) We're using buggy xalan version causing namespaces issues

by Richard Opalka (JIRA)

We're using buggy xalan version causing namespaces issues --------------------------------------------------------- Key: JBWS-2917 URL: https://jira.jboss.org/jira/browse/JBWS-2917 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-integration, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Priority: Blocker Fix For: jbossws-cxf-3.3.0, jbossws-metro-3.3.0, jbossws-native-3.3.0 JAXB internally uses XALAN. When I pass the following XML <?xml version='1.0' encoding='UTF-8'?> <EndpointReference xmlns='http://www.w3.org/2005/08/addressing'> <Address>http://localhost:8080/jaxws-endpointReference</Address> <Metadata wsdli:wsdlLocation='http://org.jboss.ws/endpointReference http://localhost:8080/jaxws-endpointReference?wsdl' xmlns:wsdli='http://www.w3.org/ns/wsdl-instance'> <wsam:InterfaceName xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata' xmlns:wsns='http://org.jboss.ws/endpointReference'>wsns:Endpoint</wsam:InterfaceName> <wsam:ServiceName EndpointName='HelloPort' xmlns='' xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata' xmlns:wsns='http://org.jboss.ws/endpointReference'>wsns:EndpointService</wsam:ServiceName> </Metadata> </EndpointReference> and process it with the following code: StreamSource source = new StreamSource(new StringReader(XML_SOURCE)); EndpointReference epRef = EndpointReference.readFrom(source); printXml(epRef.toString()); the output will be (should be identical) <?xml version='1.0' encoding='UTF-8'?> <EndpointReference xmlns='http://www.w3.org/2005/08/addressing'> <Address>http://localhost:8080/jaxws-endpointReference</Address> <Metadata wsdli:wsdlLocation='http://org.jboss.ws/endpointReference http://localhost:8080/jaxws-endpointReference?wsdl' xmlns:wsdli='http://www.w3.org/ns/wsdl-instance'> <wsam:InterfaceName xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'>wsns:Endpoint</wsam:InterfaceName> <wsam:ServiceName EndpointName='HelloPort' xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'>wsns:EndpointService</wsam:ServiceName> </Metadata> </EndpointReference> As you can see xmlns:wsns namespace declaration is lost during the identity process :( -- 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, 2 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2010