March 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2966) Fix regressions due to HornetQ update

by Alessio Soldano (JIRA)

Fix regressions due to HornetQ update ------------------------------------- Key: JBWS-2966 URL: https://jira.jboss.org/jira/browse/JBWS-2966 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-metro, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.3.0.CR1, jbossws-metro-3.3.0.CR1, jbossws-native-3.3.0.CR1 Currently all JMS endpoint tests are failing -- 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

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2982) Native ignores user specified MessageContext.HTTP_REQUEST_HEADERS

by Richard Opalka (JIRA)

Native ignores user specified MessageContext.HTTP_REQUEST_HEADERS ----------------------------------------------------------------- Key: JBWS-2982 URL: https://jira.jboss.org/jira/browse/JBWS-2982 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 See related user forum -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2981) Add <wsa:MessageID> element in request soap message

by Jim Ma (JIRA)

Add <wsa:MessageID> element in request soap message ---------------------------------------------------- Key: JBWS-2981 URL: https://jira.jboss.org/jira/browse/JBWS-2981 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.3.0 Now the wsa request message only includes the required <wsa:Action> element , add <wsa:MessageID> to get better interoperability. -- 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

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2980) The wsa action in response message is not correct when the @Action output value is not specified

by Jim Ma (JIRA)

The wsa action in response message is not correct when the @Action output value is not specified ------------------------------------------------------------------------------------------------- Key: JBWS-2980 URL: https://jira.jboss.org/jira/browse/JBWS-2980 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.3.0 The response message wsa Action is <wsa:Action></wsa:Action> : @Action(input="http://input") public int addNumbers(int arg0, int arg1) { return arg0 + arg1; } The default wsa Action should be : [target namespace]/[port type name]/[output name] -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2970) InjectionMetaDataDeploymentAspect misuse of EJBContainer.getEnc()

by Alessio Soldano (JIRA)

InjectionMetaDataDeploymentAspect misuse of EJBContainer.getEnc() ----------------------------------------------------------------- Key: JBWS-2970 URL: https://jira.jboss.org/jira/browse/JBWS-2970 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Alessio Soldano Assignee: Richard Opalka Fix For: jbossws-native-3.3.0, jbossws-metro-3.3.0, jbossws-cxf-3.3.0 See Carlo's explanation at http://community.jboss.org/message/533419#533419 -- 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

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2978) WSA implementation does not verify soap action and wsa action mismatch

by Jim Ma (JIRA)

WSA implementation does not verify soap action and wsa action mismatch ---------------------------------------------------------------------- Key: JBWS-2978 URL: https://jira.jboss.org/jira/browse/JBWS-2978 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.3.0 Web Services Addressing SOAP Binding spec section 4.2 : "Use of the SOAPAction HTTP request header field is required when using the SOAP 1.1 HTTP binding. The field-value of the SOAPAction HTTP request header MUST either be the value of the [action] property enclosed in quotation marks, or the empty value "". The latter case supports the ability to obscure the [action] property through SOAP-level security mechanisms, without requiring otherwise unnecessary transport-level security. Any other value for SOAPAction results in an Invalid Message Addressing Property fault." -- 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

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2976) The incompatiable handler can be added in HTTPBinding

by Jim Ma (JIRA)

The incompatiable handler can be added in HTTPBinding ----------------------------------------------------- Key: JBWS-2976 URL: https://jira.jboss.org/jira/browse/JBWS-2976 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.3.0 It should throw WebServiceException when attempting to configure an incompatible handler. -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2975) JAXBSerializer does not use defaultNamespace to create JAXBContext

by Jim Ma (JIRA)

JAXBSerializer does not use defaultNamespace to create JAXBContext ------------------------------------------------------------------- Key: JBWS-2975 URL: https://jira.jboss.org/jira/browse/JBWS-2975 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.3.0 The namespace prefix of type attribute in return element is lost in the marshaled message for GetCars object: --------Car.java----------- @XmlSeeAlso({Toyota.class, Ford.class}) public abstract class Car { private String model; private String make; public String getModel() { return model; } public void setModel(String model) { this.model = model; } public String getMake() { return make; } public void setMake(String make) { this.make = make; } } ------Ford.java----------- public class Ford extends Car { private String color; private final String make="Ford"; public Ford() { setMake("Ford"); } public String getMake() { return make; } public Ford(String model, String color) { setModel(model); this.color = color; } public String getColor() { return color; } public void setColor(String color) { this.color = color; } } ---GetCars.java---------- @XmlRootElement(name = "getSedansResponse", namespace = "http://jbossws.jboss.org") @XmlAccessorType(XmlAccessType.FIELD) @XmlType(name = "getSedansResponse", namespace = "http://jbossws.jboss.org") public class GetCars { @XmlElement(name = "return", namespace = "") private List<Car> _return; /** * * @return * returns List<Car> */ public List<Car> getReturn() { return this._return; } /** * * @param _return * the value for the _return property */ public void setReturn(List<Car> _return) { this._return = _return; } } -- 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

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2973) Client side respects the @HandlerChian in service endpoint interface class

by Jim Ma (JIRA)

Client side respects the @HandlerChian in service endpoint interface class -------------------------------------------------------------------------- Key: JBWS-2973 URL: https://jira.jboss.org/jira/browse/JBWS-2973 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.CR1 Reporter: Jim Ma Fix For: jbossws-native-3.3.0 The client side just needs to respect the @HandlerChain in service class. -- 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

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-1672) SunRI does not respect @HandlerChain on client SEI

by Thomas Diesler (JIRA)

SunRI does not respect @HandlerChain on client SEI -------------------------------------------------- Key: JBWS-1672 URL: http://jira.jboss.com/jira/browse/JBWS-1672 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: integration-sunri Reporter: Thomas Diesler Fix For: jbossws-2.1.0 tests-run-internal: [junit] Running org.jboss.test.ws.jaxws.samples.handlerchain.HandlerChainTestCase [junit] FIXME: [JBWS-1671] SunRI client handler cannot set mime header [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 4.209 sec [junit] Test org.jboss.test.ws.jaxws.samples.handlerchain.HandlerChainTestCase FAILED @WebService(name="Endpoint") @SOAPBinding(style = SOAPBinding.Style.RPC) @HandlerChain(file = "jaxws-handlers-client.xml") // relative path from the class file public interface EndpointWithHandlerChain { public String echo(String input); } -- 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

14 years, 1 month

4
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2010