You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "tli (JIRA)" <ji...@apache.org> on 2006/12/07 07:46:21 UTC

[jira] Created: (CXF-297) Checking in-bound message format should based on content-type, not by mtom-setting, content-id should be decoded by URLDecoder first

Checking in-bound message format should based on content-type, not by mtom-setting, content-id should be decoded by URLDecoder first
------------------------------------------------------------------------------------------------------------------------------------

                 Key: CXF-297
                 URL: http://issues.apache.org/jira/browse/CXF-297
             Project: CXF
          Issue Type: Bug
    Affects Versions: 2.0-RC
            Reporter: tli
         Assigned To: tli
             Fix For: 2.0-RC




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (CXF-297) Checking in-bound message format should based on content-type, not by mtom-setting, content-id should be decoded by URLDecoder first

Posted by "tli (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/CXF-297?page=all ]

tli resolved CXF-297.
---------------------

    Resolution: Fixed

> Checking in-bound message format should based on content-type, not by mtom-setting, content-id should be decoded by URLDecoder first
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-297
>                 URL: http://issues.apache.org/jira/browse/CXF-297
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.0-RC
>            Reporter: tli
>         Assigned To: tli
>             Fix For: 2.0-RC
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira