[JBoss JIRA] Created: (JBWS-3327) Populate MessageContext.WSDL_* props before POST handler execution
by Alessio Soldano (JIRA)
Populate MessageContext.WSDL_* props before POST handler execution
------------------------------------------------------------------
Key: JBWS-3327
URL: https://issues.jboss.org/browse/JBWS-3327
Project: JBoss Web Services
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Alessio Soldano
Fix For: jbossws-native-4.0
Currently POST handlers do not have access to WSDL_* props in the MessageContext as those are populated in MessageContextJAXWS::setOperationMetaData(..) which is run between POST and ENDPOINT handler execution for incoming server side messages.
We should evaluate computing and setting the operationMetaData before POST handlers execution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (JBWS-2157) Child nodes truncated when using jaxb to marshall data into a SOAP header
by Andrew Dinn (JIRA)
Child nodes truncated when using jaxb to marshall data into a SOAP header
--------------------------------------------------------------------------
Key: JBWS-2157
URL: http://jira.jboss.com/jira/browse/JBWS-2157
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.1
Reporter: Andrew Dinn
I wish to serialise a CoordinationContext type (a complex type defined in the OASIS WS-COOR 1.1 spec) into a SOAP message header as follows:
<code>
final JAXBContext jaxbCtx = getJaxbContext();
final SOAPMessage soapMessage = context.getMessage();
final SOAPEnvelope soapEnvelope = soapMessage.getSOAPPart().getEnvelope();
SOAPHeader soapHeader = soapEnvelope.getHeader() ;
if (soapHeader == null)
{
soapHeader = soapEnvelope.addHeader() ;
}
Marshaller marshaller = jaxbCtx.createMarshaller();
marshaller.marshal(coordinationContext, soapHeader);
</code>
The problem is that the header gets inserted without any children.
What happens is that the marshaller creates a SOAP tree top down consisting of SOAPElementImpl instances. It inserts these nodes into the tree below the SOAPHeader as it creates them. So, when the first node is created a call to SOAPHeader.addchild() is made. This call deteccts that the supplied node is of the wrong type so it substitutes a SOAPHeaderElementImpl. It attempts to copy the supplied node's substructure but the marshaller has not created the children at this point.
--
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
[JBoss JIRA] Created: (JBWS-2338) Review our SPI abstractsions and interfaces
by Richard Opalka (JIRA)
Review our SPI abstractsions and interfaces
-------------------------------------------
Key: JBWS-2338
URL: https://jira.jboss.org/jira/browse/JBWS-2338
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: jbossws-cxf, jbossws-metro, jbossws-native
Affects Versions: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5
Terminology:
DA = Deployment Aspect
Issues:
* WSFRuntime isn't good abstraction and should be removed from our SPI because it doesn't integrate with JBossAS deployers architecture very well
(it's issue is it depends on web container runtime which can be unavailable at AS start time (e.g. there can be multiple webservice archives in deploy directory that are started before web container is available)
* We moved some servlet dependent DAs to servlet lifecycle init()/destroy() methods. The problem of it is it executes DAs for whole deployment, not just particular deployed endpoint.
(IOW we execute the same DAs multiple times if there are more than one webservice endpoints in deployment. This need SPI review and repair)
--
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
[JBoss JIRA] Created: (JBWS-3235) org.jboss.ws.core.soap.SOAPFaultImpl should be Serializable
by david.boeren (JIRA)
org.jboss.ws.core.soap.SOAPFaultImpl should be Serializable
-----------------------------------------------------------
Key: JBWS-3235
URL: https://issues.jboss.org/browse/JBWS-3235
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.4.1
Reporter: david.boeren
Priority: Trivial
Fix For: jbossws-native-4.0
org.jboss.ws.core.soap.SOAPFaultImpl is currently not Serializable at runtime, which is counterintuitive since descendants of Throwable generally are, and all descendants of Throwable are marked as implementing the Serializable interface.
There is a workaround to extract the message and place it in a different Exception class but this is an extra step that should not be necessary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month