March 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3198) EPR's address is NOT used for invocations on the endpoint when the dispatchImpl is created with EPR

by Jim Ma (JIRA)

EPR's address is NOT used for invocations on the endpoint when the dispatchImpl is created with EPR ---------------------------------------------------------------------------------------------------- Key: JBWS-3198 URL: https://issues.jboss.org/browse/JBWS-3198 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Affects Versions: jbossws-native-3.4.1, jbossws-cxf-3.4.1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-4.0, jbossws-cxf-4.0 >From the jaxws api : Creates a Dispatch instance for use with objects of the user's choosing. If there are any reference parameters in the endpointReference, then those reference parameters MUST appear as SOAP headers, indicating them to be reference parameters, on all messages sent to the endpoint. The endpointReference's address MUST be used for invocations on the endpoint. In the implementation of this method, the JAX-WS runtime system takes the responsibility of selecting a protocol binding (and a port) and configuring the dispatch accordingly from the WSDL associated with this Service instance or from the metadata from the endpointReference. If this Service instance has a WSDL and the endpointReference also has a WSDL in its metadata, then the WSDL from this instance MUST be used. If this Service instance does not have a WSDL and the endpointReference does have a WSDL, then the WSDL from the endpointReference MAY be used. An implementation MUST be able to retrieve the portName from the endpointReference metadata. This method behaves the same as calling dispatch = service.createDispatch(portName, type, mode, features); where the portName is retrieved from the WSDL or EndpointReference metadata. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-3185) WSTF Scenario 3 - Asynch 05/06/07/08 tests case failure

by Jim Ma (JIRA)

WSTF Scenario 3 - Asynch 05/06/07/08 tests case failure ------------------------------------------------------- Key: JBWS-3185 URL: https://issues.jboss.org/browse/JBWS-3185 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-3.4.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-2235) Support for multiple schemas validation

by Alessio Soldano (JIRA)

Support for multiple schemas validation --------------------------------------- Key: JBWS-2235 URL: http://jira.jboss.com/jira/browse/JBWS-2235 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.1 Reporter: Alessio Soldano The schema validation feature currently support one imported schema only. We should support multiple schemas instead. -- 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

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-3222) Test failures due to WS scripts currently available on AS7

by Alessio Soldano (JIRA)

Test failures due to WS scripts currently available on AS7 ---------------------------------------------------------- Key: JBWS-3222 URL: https://issues.jboss.org/browse/JBWS-3222 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-3229) DOMUtils issue on test classpath

by Richard Opalka (JIRA)

DOMUtils issue on test classpath -------------------------------- Key: JBWS-3229 URL: https://issues.jboss.org/browse/JBWS-3229 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 junit.framework.AssertionFailedError: NonAnonymousResponses <------>at junit.framework.Assert.fail(Assert.java:47) <------>at junit.framework.Assert.assertTrue(Assert.java:20) <------>at junit.framework.Assert.assertNotNull(Assert.java:220) <------>at org.jboss.test.ws.jaxws.jbws2960.JBWS2960TestCase.testPolicyReference(JBWS2960TestCase.java:107) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-3216) Investigate & fix test failures against AS7

by Richard Opalka (JIRA)

Investigate & fix test failures against AS7 ------------------------------------------- Key: JBWS-3216 URL: https://issues.jboss.org/browse/JBWS-3216 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3258) No class available with name 'org.jboss.mq.server.jmx.Queue'

by Richard Opalka (JIRA)

No class available with name 'org.jboss.mq.server.jmx.Queue' ------------------------------------------------------------ Key: JBWS-3258 URL: https://issues.jboss.org/browse/JBWS-3258 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-4.0 15:16:48,616 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."jaxws-samples-jmstransport.sar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-samples-jmstransport.sar".INSTALL: Failed to process phase INSTALL of deployment "jaxws-samples-jmstransport.sar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_20] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] Caused by: java.lang.IllegalStateException: No class available with name 'org.jboss.mq.server.jmx.Queue' at org.jboss.msc.value.LookupClassValue.getValue(LookupClassValue.java:70) at org.jboss.msc.value.LookupClassValue.getValue(LookupClassValue.java:32) at org.jboss.msc.value.CachedValue.getValue(CachedValue.java:54) at org.jboss.msc.value.LookupConstructorValue.getValue(LookupConstructorValue.java:66) at org.jboss.msc.value.LookupConstructorValue.getValue(LookupConstructorValue.java:37) at org.jboss.msc.value.CachedValue.getValue(CachedValue.java:54) at org.jboss.msc.value.ConstructedValue.<init>(ConstructedValue.java:51) at org.jboss.as.service.ParsedServiceDeploymentProcessor.addService(ParsedServiceDeploymentProcessor.java:127) at org.jboss.as.service.ParsedServiceDeploymentProcessor.deploy(ParsedServiceDeploymentProcessor.java:102) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102) ... 4 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2882) Give setMTOMEnabled higher priority for clients

by Darran Lofthouse (JIRA)

Give setMTOMEnabled higher priority for clients ----------------------------------------------- Key: JBWS-2882 URL: https://jira.jboss.org/jira/browse/JBWS-2882 Project: JBoss Web Services Issue Type: Task 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 Presently JBossWS clients call setMTOMEnabled to indicate if MTOM should be enabled for the call, however JBossWS then scans the known types for an @XmlMimeType annotation to decide if the call is eligible for MTOM. The MTOM optimisation however applies to all binary types and not just the ones annotated with @XmlMimeType. The call to setMTOMEnabled should be sufficient to enable MTOM without requiring the check for @XmlMimeType -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-3228) javax.xml.stream.XMLStreamException: Prefix cannot be null

by Richard Opalka (JIRA)

javax.xml.stream.XMLStreamException: Prefix cannot be null ---------------------------------------------------------- Key: JBWS-3228 URL: https://issues.jboss.org/browse/JBWS-3228 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 javax.xml.stream.XMLStreamException: Prefix cannot be null at org.apache.cxf.staxutils.StreamWriterContentHandler.startElement(StreamWriterContentHandler.java:242) [cxf-common-utilities.jar:2.3.2] at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:551) [:1.6.0_20] at com.sun.xml.bind.v2.runtime.output.SAXOutput.endStartTag(SAXOutput.java:124) [jaxb-impl-2.2.jar:2.2] at com.sun.xml.bind.v2.runtime.XMLSerializer.leafElement(XMLSerializer.java:324) [jaxb-impl-2.2.jar:2.2] at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$1.writeLeafElement(RuntimeBuiltinLeafInfoImpl.java:210) [jaxb-impl-2.2.jar:2.2] at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$1.writeLeafElement(RuntimeBuiltinLeafInfoImpl.java:209) [jaxb-impl-2.2.jar:2.2] at com.sun.xml.bind.v2.runtime.reflect.TransducedAccessor$CompositeTransducedAccessorImpl.writeLeafElement(TransducedAccessor.java:250) [jaxb-impl-2.2.jar:2.2] at com.sun.xml.bind.v2.runtime.property.SingleElementLeafProperty.serializeBody(SingleElementLeafProperty.java:98) [jaxb-impl-2.2.jar:2.2] at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:340) [jaxb-impl-2.2.jar:2.2] at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:593) [jaxb-impl-2.2.jar:2.2] at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:324) [jaxb-impl-2.2.jar:2.2] at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:494) [jaxb-impl-2.2.jar:2.2] at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:315) [jaxb-impl-2.2.jar:2.2] ... 37 more Caused by: javax.xml.stream.XMLStreamException: Prefix cannot be null at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartElement(XMLStreamWriterImpl.java:1291) [:1.6.0_20] at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartElement(XMLStreamWriterImpl.java:1269) [:1.6.0_20] at org.apache.cxf.staxutils.StreamWriterContentHandler.startElement(StreamWriterContentHandler.java:203) [cxf-common-utilities.jar:2.3.2] ... 49 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3254) Add the missed jaxws2.2 methods in DelegateEndpointImpl

by Jim Ma (JIRA)

Add the missed jaxws2.2 methods in DelegateEndpointImpl --------------------------------------------------------- Key: JBWS-3254 URL: https://issues.jboss.org/browse/JBWS-3254 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 Delegate this two methods to cxf's jaxws22 endpointimpl: public void setEndpointContext(EndpointContext ctxt) public void publish(javax.xml.ws.spi.http.HttpContext context) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2011