axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Sosnoski (JIRA)" <>
Subject [jira] Commented: (AXIS2-209) mtom cid with encoded url
Date Wed, 07 Sep 2005 07:43:30 GMT
    [ ] 

Dennis Sosnoski commented on AXIS2-209:

I'd think that we'd need to make sure we handle the unescaping for any framework URIs (including
those in WSDL, and in schemas, as well as in SOAP headers for WS-Addressing and such). If
the URIs are in user data that's a different story - if they're accessing the data through
OM I'd think it'd be up to them to process the text, while if they're accessing it via a data
binding framework the framework should handle the unescaping (another thing to add to my JiBX
todo list, that).

> mtom cid with encoded url
> -------------------------
>          Key: AXIS2-209
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>     Reporter: Davanum Srinivas
>     Assignee: Saminda Wishwajith Abeyruwan

> Indigo is sending a xop include like this
> <xop:Include href="" xmlns:xop=""/>
> with a content-id like this
> --uuid:f83d35ae-9bf5-470a-8fb4-7b624abd6921+id=1
> Content-ID: <>
> Content-Transfer-Encoding: binary
> Content-Type: application/octet-stream
> This "seems" to be legal. can someone please dig into this?
> thanks,
> dims

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message