Garrett,

How do I close the bug? username: eliast

-Elias

Rajkumar Kothapa (JIRA) wrote:
>     [ 
> http://issues.apache.org/jira/browse/ABDERA-1?page=comments#action_12419701 ] 
> 
> Rajkumar Kothapa commented on ABDERA-1:
> ---------------------------------------
> 
> Sorry. You can go ahead and close the bug.
> 
>> Attachment deserialization doesnt work with multiref's
>> ------------------------------------------------------
>>
>>          Key: ABDERA-1
>>          URL: http://issues.apache.org/jira/browse/ABDERA-1
>>      Project: Abdera
>>         Type: Bug
> 
>>  Environment: java version "1.4.2_07"
>> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07-b05)
>> Java HotSpot(TM) Client VM (build 1.4.2_07-b05, mixed mode)
>>     Reporter: Rajkumar Kothapa
> 
>> Attachment deserialization with multirefs in the request/response soap body 
>> doesnt work. It fails with a ClassCastException inside populateDataHandler 
>> method of org.apache.axis.encoding.ser.JAFDataHandlerDeserializer. It fails 
>> in this line : 
>> ref = AttachmentUtils.getActivationDataHandler((org.apache.axis.Part)ref);
>> Looks like the ClassCastException occurs because the ref object returned 
>> from the previous line is a SOAPBodyElement but is being cast to a Part. And 
>> this occurs only when  the "href" of a soap element  refers to a multiref 
>> element whose href in turn points to the required attachment. The tests work 
>> fine when multiref support is disabled both on the client and the server 
>> side. And according to the comments in org.apache.axis.client.Call(line 
>> number 1541) this seems like a known issue.
>>             // If there are any MIME types, turn off multirefs.
>>             // I don't know enough about the guts to know why
>>             // attachments don't work with multirefs, but they don't.
>> Is this issue going to be fixed?
>> rajkumar
> 

Reply via email to