[jbossws-issues] [JBoss JIRA] Commented: (JBWS-3058) Create errata report for JBossWS-CXF 3.3.1.GA

Alessio Soldano (JIRA) jira-events at lists.jboss.org
Tue Jun 8 03:18:38 EDT 2010


    [ https://jira.jboss.org/browse/JBWS-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12534376#action_12534376 ] 

Alessio Soldano commented on JBWS-3058:
---------------------------------------

# [CXF-1252] Provider PAYLOAD endpoint expects SOAP Envelope
# [CXF-1517] HTTP bindings for Provider
# [CXF-1519] Explicitly set the namespace of a WebFault
# [CXF-1521] Exception handling with @WebFault annotation
# [CXF-2006] RespectBinding feature and not understood required extensibility elements
# [EJBTHREE-1152] service-ref in ejb-jar.xml is ignored
# [JBWS-2596] Resource injection in jaxws endpoints and handlers
# [JBWS-2561] XOP request not properly inlined
# [JBWS-2480] Soap attachments are dropped on server response
# [JBWS-2397] Fix jbws1797 testcase
# [JBWS-2917] We're using buggy xalan version causing namespaces issues
# [JBWS-2895] JAX-RPC available from AS 6.0.0.M3
# [JBWS-2945] JAX-WS 2.2 implementation not yet available for CXF stack
# [JBWS-2987] Review JMS integration
# [JBWS-3002] Verify POJO endpoints are shared
FIXME: [CXF-1310] Generated WSDL for an WS-RM endpoint does not contain RM policies
FIXME: [CXF-1507] CXF client handler cannot set mime header
FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding

AS 5.1.0:

# [CXF-1252] Provider PAYLOAD endpoint expects SOAP Envelope
# [CXF-1517] HTTP bindings for Provider
# [CXF-1519] Explicitly set the namespace of a WebFault
# [CXF-1521] Exception handling with @WebFault annotation
# [CXF-2006] RespectBinding feature and not understood required extensibility elements
# [EJBTHREE-1152] service-ref in ejb-jar.xml is ignored
# [JBWS-2596] Resource injection in jaxws endpoints and handlers
# [JBWS-2561] XOP request not properly inlined
# [JBWS-2480] Soap attachments are dropped on server response
# [JBWS-2397] Fix jbws1797 testcase
# [JBWS-2917] We're using buggy xalan version causing namespaces issues
# [JBWS-2895] JAX-RPC available from AS 6.0.0.M3
# [JBWS-2945] JAX-WS 2.2 implementation not yet available for CXF stack
# [JBWS-2987] Review JMS integration
# [JBWS-3002] Verify POJO endpoints are shared
FIXME: [CXF-1310] Generated WSDL for an WS-RM endpoint does not contain RM policies
FIXME: [CXF-1507] CXF client handler cannot set mime header
FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding

AS 6.0.0.M3:

# [CXF-1252] Provider PAYLOAD endpoint expects SOAP Envelope
# [CXF-1517] HTTP bindings for Provider
# [CXF-1519] Explicitly set the namespace of a WebFault
# [CXF-1521] Exception handling with @WebFault annotation
# [CXF-2006] RespectBinding feature and not understood required extensibility elements
# [EJBTHREE-1152] service-ref in ejb-jar.xml is ignored
# [JBWS-2596] Resource injection in jaxws endpoints and handlers
# [JBWS-2561] XOP request not properly inlined
# [JBWS-2480] Soap attachments are dropped on server response
# [JBWS-2397] Fix jbws1797 testcase
# [JBWS-2945] JAX-WS 2.2 implementation not yet available for CXF stack
# [JBWS-2987] Review JMS integration
# [JBWS-3002] Verify POJO endpoints are shared
# [JBWS-3039] Spring 3 classpath scanning fails on AS 6
FIXME: [CXF-1310] Generated WSDL for an WS-RM endpoint does not contain RM policies
FIXME: [CXF-1507] CXF client handler cannot set mime header
FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding 

> Create errata report for JBossWS-CXF 3.3.1.GA
> ---------------------------------------------
>
>                 Key: JBWS-3058
>                 URL: https://jira.jboss.org/browse/JBWS-3058
>             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.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

        


More information about the jbossws-issues mailing list