[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2088) Relax matching requirements in decodeMultipartRelatedMessage()

[Franz Willer (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBWS-2088?page=comments#action_12419570 ] 
            
Franz Willer commented on JBWS-2088:
------------------------------------

I just wanted to patch MultipartRelatedDecoder to solve the issue from Axis but recognized that there is already my workaround included but commented out!

         if ( start != null && part.getContentId().startsWith("<")) {
            if ( !(start.charAt(0)=='<')) {
               start = "<"+start+">";
            }
         }

I'm wondering now if it was possible to activate this workaround for the next release?
 (I know that this issue has to be solved in Axis but for myself i always have to patch  new JBossWS releases for this to support axis based clients (;( )

Kind regards


> Relax matching requirements in decodeMultipartRelatedMessage()
> --------------------------------------------------------------
>
>                 Key: JBWS-2088
>                 URL: http://jira.jboss.com/jira/browse/JBWS-2088
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions: jbossws-native-3.0.1
>            Reporter: David Boeren
>         Assigned To: Heiko Braun
>
> Apache Axis sends a slightly non-standard value in the Content-Type which many WS implementations accept but JBossWS does not, and this is interfering with multipart related service calls.
> The "start" tag in the Content-Type has an incorrect format.  It is this:
> start="0.urn:uuid:278C3ADFCFF3AF170A1206560191992 at apache.org";
> but it should be this:
> start="<0.urn:uuid:278C3ADFCFF3AF170A1206560191992 at apache.org>";
> To work around that problem, change this method: org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage
> Change this:
>   public void decodeMultipartRelatedMessage(InputStream stream) throws IOException, MessagingException
>   {
>      String boundaryParameter = contentType.getParameter("boundary");
>      String start = contentType.getParameter("start");
> to this:
>   public void decodeMultipartRelatedMessage(InputStream stream) throws IOException, MessagingException
>   {
>      String boundaryParameter = contentType.getParameter("boundary");
>      String start = null

-- 
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