May 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2844) The deploy script does not endorse the cxf and metro jaxws implementation

by Jim Ma (JIRA)

The deploy script does not endorse the cxf and metro jaxws implementation -------------------------------------------------------------------------- Key: JBWS-2844 URL: https://jira.jboss.org/jira/browse/JBWS-2844 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-metro-3.2.2, jbossws-cxf-3.2.2 There is no endorsed jars for metro and native stack under $JBOSS_HOME/lib/endorsed, this will cause ServiceObjectFactory uses sun's RI class in JDK. -- 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

13 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-3040) Default WSSecurity configurations should support both SOAP protocol versions

by Richard Opalka (JIRA)

Default WSSecurity configurations should support both SOAP protocol versions ---------------------------------------------------------------------------- Key: JBWS-3040 URL: https://jira.jboss.org/browse/JBWS-3040 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.3.0 Hi, I'm using JBossWS 3.1.1.GA, and I've discovered a possible problem when mixing the support for WS-Policy, WS-Security and a web service with SOAP1.2 binding. The problem is that by default, if no specific client configuration is provided, the client wsdl parser will parse the provided policy, detect that WS-Security is required and load the "Standard WSSecurity Client" configuration from the embedded standard-jaxws-client-confix.xml, which correcly adds the WS-Security handler, but only for the SOAP11 binding. As the web services requires SOAP12, the client will send the message using this protocol, the handler will not be activated, and of course the message will be rejected. There a two fixes: first provide a custom client configuration that adds the WS-Security handler for both protocols bindings (which is what I've done), second modify the standard configuration provided with the bundled library to activate the handler for both protocols. I not sure if later versions have already fixed this problems but, if not, would it possible to include this change in the standard config? All the best, Riccardo. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3039) Spring 3 classpath scanning fails on AS 6

by Alessio Soldano (JIRA)

Spring 3 classpath scanning fails on AS 6 ----------------------------------------- Key: JBWS-3039 URL: https://jira.jboss.org/browse/JBWS-3039 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-4.0 ... because of http://jira.springframework.org/browse/SPR-7197 -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3038) Provide new BusFactory impl allowing for integration customizations of default Bus

by Alessio Soldano (JIRA)

Provide new BusFactory impl allowing for integration customizations of default Bus ---------------------------------------------------------------------------------- Key: JBWS-3038 URL: https://jira.jboss.org/browse/JBWS-3038 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.3.0 We should provide a new version of BusFactory allowing us to customize default beans loaded in default Bus (Manager, Configurer, ...). That would also allow us to avoid shipping all the cxf-extension-*.xml files in jbossws-cxf-client.jar as well as provide the cxf.xml we also ship in that jar with no way of touching it (as the same is in cxf-rt-core.jar and different versions make the CXF behavior unpredictable / dependent on users' classpath configuration). -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3037) TODO - better description

by Richard Opalka (JIRA)

TODO - better description ------------------------- Key: JBWS-3037 URL: https://jira.jboss.org/browse/JBWS-3037 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.3.0 -- 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

13 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3036) Clean up thirdparty libs dependency

by Alessio Soldano (JIRA)

Clean up thirdparty libs dependency ----------------------------------- Key: JBWS-3036 URL: https://jira.jboss.org/browse/JBWS-3036 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.3.0 We have refences to geronimo-* api libs that can be replaced by standard groupId/artifactId ones, as well as minor clean up to do wrt 3rd party dependencies -- 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

13 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3020) Investigate why HandlerScopeTestCase fails

by Richard Opalka (JIRA)

Investigate why HandlerScopeTestCase fails ------------------------------------------ Key: JBWS-3020 URL: https://jira.jboss.org/jira/browse/JBWS-3020 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Fix For: jbossws-cxf-3.3.0 ------------------------------------------------------------------------------- Test set: org.jboss.test.ws.jaxws.handlerscope.HandlerScopeTestCase ------------------------------------------------------------------------------- Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.412 sec <<< FAILURE! testClientAccess(org.jboss.test.ws.jaxws.handlerscope.HandlerScopeTestCase) Time elapsed: 5.271 sec <<< FAILURE! junit.framework.ComparisonFailure: expected: <...SOAP12ClientHandler:SOAPClientHandler:ServiceClientHandler:ServiceWildcardClientHandler:PortClientHandler:PortWildcardClientHandler:GeneralClientHandler:GeneralServerHandler:PortWildcardServerHandler:PortServerHandler:ServiceWildcardServerHandler:ServiceServerHandler:SOAPServerHandler:SOAP12ServerHandler:endpoint:SOAP12ServerHandler:SOAPServerHandler:ServiceServerHandler:ServiceWildcardServerHandler:PortServerHandler:PortWildcardServerHandler:GeneralServerHandler:GeneralClientHandler:PortWildcardClientHandler:PortClientHandler:ServiceWildcardClientHandler:ServiceClientHandler:SOAPClientHandler:SOAP12ClientHandler> but was: <...null:null:null:null:null:null:null:GeneralServerHandler:PortWildcardServerHandler:PortServerHandler:ServiceWildcardServerHandler:ServiceServerHandler:SOAPServerHandler:SOAP12ServerHandler:endpoint:SOAP12ServerHandler:SOAPServerHandler:ServiceServerHandler:ServiceWildcardServerHandler:PortServerHandler:PortWildcardServerHandler:GeneralServerHandler:null:null:null:null:null:null:null> at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at org.jboss.test.ws.jaxws.handlerscope.HandlerScopeTestCase.assertResponse(HandlerScopeTestCase.java:91) at org.jboss.test.ws.jaxws.handlerscope.HandlerScopeTestCase.testClientAccess(HandlerScopeTestCase.java:56) -- 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

13 years, 12 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-3035) Generate correct transportId "http://www.w3.org/2003/05/soap/bindings/HTTP/" for SOAP12Binding

by Jim Ma (JIRA)

Generate correct transportId "http://www.w3.org/2003/05/soap/bindings/HTTP/" for SOAP12Binding ---------------------------------------------------------------------------------------------- Key: JBWS-3035 URL: https://jira.jboss.org/browse/JBWS-3035 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.CR2 Reporter: Jim Ma Fix For: jbossws-native-4.0 When the service class uses SOAP12HTTP_BINDING : @BindingType(value = SOAPBinding.SOAP12HTTP_BINDING) public interface SOAPEndpoint { @WebMethod public String echo(String msg); } As per soap12 spec , the transportId in generated wsdl should be : "http://www.w3.org/2003/05/soap/bindings/HTTP", not http://schemas.xmlsoap.org/soap/http" <binding name="SOAPEndpoint" type="tns:SOAPEndpoint"> <soap12:binding transport="http://www.w3.org/2003/05/soap/bindings/HTTP/" style="document"/> -- 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

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3030) Refactor *-deploy.conf for supporting un-install of CXF stack

by Alessio Soldano (JIRA)

Refactor *-deploy.conf for supporting un-install of CXF stack ------------------------------------------------------------- Key: JBWS-3030 URL: https://jira.jboss.org/browse/JBWS-3030 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-metro, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.3.0, jbossws-cxf-3.3.0, jbossws-metro-3.3.0 Currently the *-deploy.conf scripts allow for default uninstall of jbossws-native stack from vanilla JBoss AS (where not previuos jbws installation left the deploy.conf uninstall file). This need to support CXF stack too, as that can come by default too on AS in future. Also, the *-deploy.conf files could be refactored and simplified into just two of them (one for the common stuff and one for a given server profile/configuration stuff). -- 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

14 years

1
2
0 / 0

[JBoss JIRA] Updated: (JBWS-3029) Quote mismatch in JBossWS console index.html

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/browse/JBWS-3029?page=com.atlassian.jira.plugin.sy... ] Alessio Soldano updated JBWS-3029: ---------------------------------- Security: Public (was: JBoss Internal) > Quote mismatch in JBossWS console index.html > -------------------------------------------- > > Key: JBWS-3029 > URL: https://jira.jboss.org/browse/JBWS-3029 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-native-3.1.2 > Environment: SOA 5.0.0 and EAP 5.0.1 > Reporter: Julian Coleman > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-native-3.3.0, jbossws-cxf-3.3.0, jbossws-metro-3.3.0 > > > The file: > modules/management/src/main/webapp/index.html > contains mismatched quotes: > <meta http-equiv='Content-Type content='text/html; charset=iso-8859-1'> > It should be corrected to: > <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> -- 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

14 years

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 May 2010