October 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1802) org.jboss.ws.core.client.RemotingConnectionImpl.addURLParameter() doesn't guarantee a URL as expected by the JBossRemoting InvokerLocator

by Tom Fennelly (JIRA)

org.jboss.ws.core.client.RemotingConnectionImpl.addURLParameter() doesn't guarantee a URL as expected by the JBossRemoting InvokerLocator ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBWS-1802 URL: http://jira.jboss.com/jira/browse/JBWS-1802 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.1 Reporter: Tom Fennelly According to the JBossRemoting docs, if you're adding the InvokerLocator.DATATYPE URL param for marshaling, it will expect the URL to have a path (or at least a single "/" character) between the port number and the query string e.g. It's fine with... http://x:8080/myservice?datatype=blah But it's not fine with... http://x:8080?datatype=blah It has to be... http://x:8080/?datatype=blah That seems daft to me, but I trid it out (by changing RemotingConnectionImpl), and making sure the "/" is there fixes the issue. If it's not there, the InvokerLocator constructor balks while trying to parse the URL. -- 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

17 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1856) Attachment part not cleanup correctly

by Heiko Braun (JIRA)

Attachment part not cleanup correctly ------------------------------------- Key: JBWS-1856 URL: http://jira.jboss.com/jira/browse/JBWS-1856 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc, jbossws-jaxws Affects Versions: jbossws-1.2.1 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-2.0.2 The SwapableMemoryData source prevent OOME by writing large attachment to disk. These files are removed when JBoss is shutdown, but not during run-time. This causes a SLA issue. -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1853) Update ClientLaucher to new metadata model

by Thomas Diesler (JIRA)

Update ClientLaucher to new metadata model ------------------------------------------ Key: JBWS-1853 URL: http://jira.jboss.com/jira/browse/JBWS-1853 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Carlo de Wolf Fix For: jbossws-2.0.2 The webserviceref tests do not compile because of the broken dependency on ClientLauncher -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1851) Remove container integration jar from jbossws.sar

by Thomas Diesler (JIRA)

Remove container integration jar from jbossws.sar ------------------------------------------------- Key: JBWS-1851 URL: http://jira.jboss.com/jira/browse/JBWS-1851 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.1.SP2 The container integration jbossws-jboss42.jar and jbossws-jboss50.jar should not be part of the delivery, since they are now part of the AS code base. Building AS installs these jars in ${server.lib.dir} -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1823) Implement and document JAXB introductions

by Thomas Diesler (JIRA)

Implement and document JAXB introductions ----------------------------------------- Key: JBWS-1823 URL: http://jira.jboss.com/jira/browse/JBWS-1823 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-2.0.2 Heiko, could you please post the test case here and document this if not done already. -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1815) Cannot add fault detail

by Thomas Diesler (JIRA)

Cannot add fault detail ----------------------- Key: JBWS-1815 URL: http://jira.jboss.com/jira/browse/JBWS-1815 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.2 Hello! I can't get the detail element of the SOAPFault. Is there a magic way to do this. I have a Provider< SOAPMessage > implementation. When I do the following ... Code: @Local @Stateless @WebServiceProvider( serviceName = "MyService", portName = "MyServiceSoap11Port", targetNamespace = "http://my.service.com/something", wsdlLocation = "META-INF/wsdl/my-service.wsdl") @ServiceMode(value = Service.Mode.MESSAGE) public class MyServiceEndpointProvider implements Provider<SOAPMessage> { public SOAPMessage invoke(SOAPMessage requestSoapMessage) { ... SOAPFault theSOAPFault = SOAPFactory.newInstance().createFault(); Detail soapFaultDetail = soapFault.addDetail(); SOAPElement myFaultElement = soapFaultDetail.addChildElement(new QName("http://my.service.com/common-ws/types", "myFault")); SOAPElement myCodeElement = myFaultElement.addChildElement(new QName("http://my.service.com/common-ws/types", "code")); myCodeElement.setNodeValue("SC_BAD_REQUEST"); SOAPElement myMessageElement = myFaultElement.addChildElement(new QName("http://my.service.com/common-ws/types", "message")); myMessageElement.setNodeValue("This is a faked error"); throw new SOAPFaultException(theSOAPFault) ... } } ... the detail part of the fault is missing, i.e. the serialized response does not contain my detail information, just the top fault element. Am I missing something obvious here or is it a bug. I'm using JBoss 4.2.1.GA with JBossWS 2.0.1.GA. And yes, my wsdl points out a fault element specifying the detail above. -- 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

17 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-1761) WSProvide ignore SOAPBinding declaration

by Heiko Braun (JIRA)

WSProvide ignore SOAPBinding declaration ---------------------------------------- Key: JBWS-1761 URL: http://jira.jboss.com/jira/browse/JBWS-1761 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Heiko Braun -- 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

17 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-1810) In wstools use String.replace(CharSequence,char,char) instead of String.replace(CharSequence,CharSequence,CharSequence)

by Darran Lofthouse (JIRA)

In wstools use String.replace(CharSequence,char,char) instead of String.replace(CharSequence,CharSequence,CharSequence) ----------------------------------------------------------------------------------------------------------------------- Key: JBWS-1810 URL: http://jira.jboss.com/jira/browse/JBWS-1810 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxrpc Affects Versions: jbossws-2.0.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.2 In wstools use String.replace(CharSequence,char,char) instead of String.replace(CharSequence,CharSequence,CharSequence), this is due to a limitation in the version of JBoss Retro included in some JBoss AS releases returning an empty String when you call the second replace method. -- 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

17 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1846) Release jbossws-2.0.2.GA binary

by Thomas Diesler (JIRA)

Release jbossws-2.0.2.GA binary ------------------------------- Key: JBWS-1846 URL: http://jira.jboss.com/jira/browse/JBWS-1846 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.1 The release criteria for jbossws are: * pass all internal jbossws tests * pass all portable j2ee-1.4 tests from the jboss testsuite -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1644) Process wsdl extensibility elements

by Alessio Soldano (JIRA)

Process wsdl extensibility elements ----------------------------------- Key: JBWS-1644 URL: http://jira.jboss.com/jira/browse/JBWS-1644 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assigned To: Alessio Soldano Fix For: jbossws-2.0.1 Wsdl extensibility elements/attributes have to be dealt in both marshalling and unmarshalling of wsdl to the unified wsdl structure. This is required to collect eventual policy attachment in wsdl or wsdl fragments. -- 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

17 years, 3 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2007