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