[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:…
[View More]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
[View Less]
13 years, 11 months
[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: …
[View More]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
[View Less]
14 years
[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.…
[View More]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
[View Less]
14 years
[JBoss JIRA] Created: (JBWS-3231) policy alternatives can not be satisfied
by Richard Opalka (JIRA)
policy alternatives can not be satisfied
----------------------------------------
Key: JBWS-3231
URL: https://issues.jboss.org/browse/JBWS-3231
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Richard Opalka
Fix For: jbossws-cxf-4.0
testMtomWithProxy(org.jboss.test.ws.jaxws.samples.mtom.MtomTestCase) Time elapsed: 0.132 sec <<< ERROR!
javax.…
[View More]xml.ws.soap.SOAPFaultException: These policy alternatives can not be satisfied:.
{http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization}OptimizedMimeSerialization
<------>at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
<------>at $Proxy45.sayHello(Unknown Source)
<------>at org.jboss.test.ws.jaxws.samples.mtom.MtomTestCase.testMtomWithProxy(MtomTestCase.java:61)
Caused by: org.apache.cxf.binding.soap.SoapFault: These policy alternatives can not be satisfied:.
{http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization}OptimizedMimeSerialization
<------>at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:75)
<------>at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:46)
<------>at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:35)
<------>at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
<------>at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:99)
<------>at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69)
<------>at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34)
<------>at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
<------>at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:755)
<------>at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2335)
<------>at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2193)
<------>at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2037)
<------>at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
<------>at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:697)
<------>at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
<------>at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
<------>at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
<------>at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
<------>at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
<------>at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
<------>at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
<------>... 32 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
14 years, 1 month
[JBoss JIRA] Created: (JBWS-3236) Ensure JBossWSBusFactory is built properly on AS7
by Alessio Soldano (JIRA)
Ensure JBossWSBusFactory is built properly on AS7
-------------------------------------------------
Key: JBWS-3236
URL: https://issues.jboss.org/browse/JBWS-3236
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-4.0
The BusFactory build process is …
[View More]heavily influenced by the TCCL setup. We need to ensure that at least when the JBossWS flavour of the bus is being built, the whole dependency set is used. This means making sure all the cxf components are visible in the used classloader, as well as the jbossws customizations.
- set services="export" on jbossws-cxf-factories dependency in jaxws-client module?
- overwrite TCCL in JBossWSBusFactory when building?
- try BusFactory.newInstance() in basic servlet (see the cxf testsuite endorse testcase) having Dependencies: org.jboss.ws.jaxws-client services in MANIFEST.MF
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
14 years, 1 month