January 2012 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3072) The wsdl part generated for fault message is not valid

by Jim Ma (JIRA)

The wsdl part generated for fault message is not valid ------------------------------------------------------ Key: JBWS-3072 URL: https://jira.jboss.org/browse/JBWS-3072 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Jim Ma Assignee: Jim Ma -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (JBWS-3407) Client aggregation module for Native stack

by Alessio Soldano (Created) (JIRA)

Client aggregation module for Native stack ------------------------------------------ Key: JBWS-3407 URL: https://issues.jboss.org/browse/JBWS-3407 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-4.0.1 We either need a module similar to org.jboss.ws.cxf.jbossws-cxf-client:main but for native stack or clear directions in the doc for what to use with native stack installed on AS7. The xts module dependency also probably needs to be fixed to be able to work with native stack too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[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, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-3311) Make SwapableMemoryDataSource.maxMemorySize Configurable

by Kyle Lape (JIRA)

Make SwapableMemoryDataSource.maxMemorySize Configurable -------------------------------------------------------- Key: JBWS-3311 URL: https://issues.jboss.org/browse/JBWS-3311 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Kyle Lape Assignee: Mustafa Musaji Make the maxMemorySize configurable by a system property. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (JBWS-3376) Introduce jboss-webservices.xml DD

by Richard Opalka (Created) (JIRA)

Introduce jboss-webservices.xml DD ---------------------------------- Key: JBWS-3376 URL: https://issues.jboss.org/browse/JBWS-3376 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 It's needed for customization of webservices.xml <webservices> <context-root/>? <config-name/>? <config-file/>? <webservice-description>* <webservice-description-name/> <wsdl-publish-location/> </webservice-description> </webservices> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
7
0 / 0

[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, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-2302) Verify dependencies on outstanding Metro issues

by Alessio Soldano (JIRA)

Verify dependencies on outstanding Metro issues ----------------------------------------------- Key: JBWS-2302 URL: https://jira.jboss.org/jira/browse/JBWS-2302 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Fix For: jbossws-metro-3.0.4 Before releasing we should check if some of the Metro issue we created have been solved, so that the corresponding JBossWS issue can be solved. -- 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, 9 months

3
22
0 / 0

[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, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBWS-3055) SOAPElementImpl.getElementsByTagName does not return correct results.

by Marek Baluch (JIRA)

SOAPElementImpl.getElementsByTagName does not return correct results. --------------------------------------------------------------------- Key: JBWS-3055 URL: https://jira.jboss.org/browse/JBWS-3055 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Environment: jbossws version: JBossWS-native 3.1.2.SP3_CP01 Reporter: Marek Baluch If SOAPElementImpl.getElementsByTagName(String str) method is called on an element which has a child element with a tag name <ns4:RequestedSecurityToken>...</ns4:RequestedSecurityToken> and the input parameter is only the name without namespace ("RequestedSecurityToken") then the element will not be found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2843) wsprovide tool does not check the annotation and method signature

by Jim Ma (JIRA)

wsprovide tool does not check the annotation and method signature ----------------------------------------------------------------- Key: JBWS-2843 URL: https://jira.jboss.org/jira/browse/JBWS-2843 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Jim Ma wsprovide tool will generate wrong wsdl for this wrong jaxws annotated add method (the parameter style should be wrapped: @SOAPBinding(parameterStyle = ParameterStyle.BARE) public class Test { @WebMethod public int add(int a, int b) { return(a + b); } We should validate this method and it's annotation before generate wsdl . -- 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, 9 months

3
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2012