axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Scheuerle (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-4481) JAX-WS Marshaling is not optimized if xsi:type is requested
Date Mon, 31 Aug 2009 13:04:32 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rich Scheuerle resolved AXIS2-4481.
-----------------------------------

    Resolution: Fixed

> JAX-WS Marshaling is not optimized if xsi:type is requested
> -----------------------------------------------------------
>
>                 Key: AXIS2-4481
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4481
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>            Priority: Minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The JAX-WS engine uses the marshal methods provided by JAX-B.
> The JAX-B supports marshaling to an XMLStreamWriter or an OutputStream.
> In most cases, the JAX-WS runtime uses the latter (marshaling to OutputStream).  This
is accomplished by getting the target OutputStream from the XMLStreamWriter.
> However, there is one path where this optimization is not being used.  This JIRA corrects
this path

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message