[JBoss JIRA] Created: (JBWS-2744) Dispatch and Config Provider via System Properties and/or a Properties file
by Anil Saldhana (JIRA)
Dispatch and Config Provider via System Properties and/or a Properties file
---------------------------------------------------------------------------
Key: JBWS-2744
URL: https://jira.jboss.org/jira/browse/JBWS-2744
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Anil Saldhana
The Dispatch seems to be an important JAXWS client construct. It does not provide everything that any JBossWS user needs. Hence there are chances where he may have to cast the dispatch to ConfigProvider and provide the additional settings as outlined in the forum thread.
For this reason, I suggest adding a properties file on the classpath and one setting that can be done via system property. The DispatchImpl implementation needs to handle this one system prop and use the associated properties file to get the settings.
--
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
12 years, 6 months
[JBoss JIRA] Created: (JBWS-3019) Moving to jbossws-native-3.2.2.GA Stopped honering my java http proxy settings
by David Waters (JIRA)
Moving to jbossws-native-3.2.2.GA Stopped honering my java http proxy settings
------------------------------------------------------------------------------
Key: JBWS-3019
URL: https://jira.jboss.org/jira/browse/JBWS-3019
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.2.2
Environment: jboss-5.1.0.GA, Sun java 1.6.0_14, Window XP 64bit, Intel Core2
Reporter: David Waters
In order to talk to a NTLM secured webservice I go through a NTLM Http proxy (ntlmaps).
I configure this proxy through a java.net.ProxySelector (ProxySelector.setDefault(aCustomProxySelector)).
This was working (with issues) with the version of jbossws that ships with jboss 5.1.0GA (jbossws version 3.1.2.GA). I was required to turn off chunking so I updated to jbossws 3.2.2GA and used ChunkedEncodingFeature to disable chunking.
The installation of jbossws 3.2.2 stopped the webservice calls calling my proxy selector and did not use my configured proxy. I have tried to find any way to reinstate the proxy but have been unsuccessful.
--
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
12 years, 7 months
[JBoss JIRA] Created: (JBWS-2930) IllegalArgumentException: Illegal null argument:ns - Raised initialising Service referencing a WSDL which imports a xsd with no namespace
by Darran Lofthouse (JIRA)
IllegalArgumentException: Illegal null argument:ns - Raised initialising Service referencing a WSDL which imports a xsd with no namespace
-----------------------------------------------------------------------------------------------------------------------------------------
Key: JBWS-2930
URL: https://jira.jboss.org/jira/browse/JBWS-2930
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.2.2
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.3.0
The following exception is thrown when a Service is initialised using a WSDL that imports a schema with no namespace: -
java.lang.IllegalArgumentException: Illegal null argument:ns
at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSModel.createNamespaceItemIfNotExistent(JBossXSModel.java:511)
at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSModel.addXSElementDeclaration(JBossXSModel.java:351)
at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.copyXSModel(WSSchemaUtils.java:707)
at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:202)
--
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
12 years, 7 months