March 2012 - jbossws-issues - Jboss List Archives

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

2
2
0 / 0

[JBoss JIRA] (JBWS-3467) Remove ws-policy support

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3467: ------------------------------------ Summary: Remove ws-policy support Key: JBWS-3467 URL: https://issues.jboss.org/browse/JBWS-3467 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.1 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3458) JBossWS testsuite fails on IPv6

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3458: ------------------------------------ Summary: JBossWS testsuite fails on IPv6 Key: JBWS-3458 URL: https://issues.jboss.org/browse/JBWS-3458 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Affects Versions: jbossws-native-4.0.2, jbossws-cxf-4.0.2 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.1, jbossws-cxf-4.1 -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] (JBWS-3460) Investigate CXF specific tests IPv6 issues

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3460: ------------------------------------ Summary: Investigate CXF specific tests IPv6 issues Key: JBWS-3460 URL: https://issues.jboss.org/browse/JBWS-3460 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.0.2 Reporter: Richard Opalka Assignee: Alessio Soldano Fix For: jbossws-cxf-4.1 There is a bunch of CXF tests that are failing when using IPv6 address: --- Tests in error: testWSDLHttpProxy(org.jboss.test.ws.jaxws.cxf.httpproxy.HTTPProxyWSDLTestCase): Unexpected end of file from server testHttpProxy(org.jboss.test.ws.jaxws.cxf.httpproxy.HTTPProxyTestCase): Could not send Message. testHttpProxyUsingHTTPClientPolicy(org.jboss.test.ws.jaxws.cxf.httpproxy.HTTPProxyTestCase): Could not send Message. testSingleDeploy(org.jboss.test.ws.jaxws.cxf.bus.EJB3ClientBusTestCase): com.sun.xml.messaging.saaj.SOAPExceptionImpl test(org.jboss.test.ws.jaxws.samples.wsse.policy.trust.WSTrustTestCase): The specified request failed Tests run: 69, Failures: 0, Errors: 5, Skipped: 0 --- Tests in error: testJMSEndpointClientSide(org.jboss.test.ws.jaxws.cxf.jms.JMSEndpointOnlyDeploymentTestCase): javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed] testMessagingClient(org.jboss.test.ws.jaxws.cxf.jms.JMSEndpointOnlyDeploymentTestCase): Failed to create remoting connection testJMSEndpointServerSide(org.jboss.test.ws.jaxws.cxf.jms_http.JMSHTTPEndpointDeploymentTestCase): Server returned HTTP response code: 500 for URL: http://[::1]:8080/jaxws-cxf-jms-http-deployment-test-servlet testJMSEndpointClientSide(org.jboss.test.ws.jaxws.cxf.jms_http.JMSHTTPEndpointDeploymentTestCase): javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed] Tests run: 36, Failures: 0, Errors: 4, Skipped: 0 -- 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, 9 months

2
6
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, 9 months

3
7
0 / 0

[JBoss JIRA] (JBWS-3466) Remove schema validation feature

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3466: ------------------------------------ Summary: Remove schema validation feature Key: JBWS-3466 URL: https://issues.jboss.org/browse/JBWS-3466 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.1 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3459) jboss-webservice.xml port-component does not work

by Tomas Gustavsson (JIRA)

Tomas Gustavsson created JBWS-3459: -------------------------------------- Summary: jboss-webservice.xml port-component does not work Key: JBWS-3459 URL: https://issues.jboss.org/browse/JBWS-3459 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss AS 7.1.0.GA Reporter: Tomas Gustavsson I am trying to make an EJB WS get the same url that it had in JBoss AS 5 and 6. Using the jboss-webservice.xml described in JBWS-3376. <?xml version="1.0" encoding="UTF-8"?> <webservices version="1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.jboss.com/xml/ns/javaee" xsi:schemalocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_webservices_1_0.xsd"> <context-root>ejbca</context-root> <port-component> <port-component-name>ejbcaws</port-component-name> <port-component-uri>ejbcaws</port-component-uri> <transport-guarantee>CONFIDENTIAL</transport-guarantee> <secure-wsdl-access>true</secure-wsdl-access> </port-component> </webservices> This is basically identical to what we used before in jboss.xml. <jboss xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" version="3.0" > <webservices> <context-root>/ejbca/ejbcaws</context-root> </webservices> <enterprise-beans> <session> <ejb-name>EjbcaWS</ejb-name> <port-component> <port-component-name>ejbcaws</port-component-name> <port-component-uri>ejbcaws</port-component-uri> <transport-guarantee>CONFIDENTIAL</transport-guarantee> <secure-wsdl-access>true</secure-wsdl-access> </port-component> </session> </enterprise-beans> </jboss> The port-component items are completely ignored in JBoss AS 7.1.0, only the name and serviceName from the @WebService annotation are used. -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] (JBWS-3465) Remove fastinfoset feature

by Richard Opalka (JIRA)

Richard Opalka created JBWS-3465: ------------------------------------ Summary: Remove fastinfoset feature Key: JBWS-3465 URL: https://issues.jboss.org/browse/JBWS-3465 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.1 -- 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2012