On Apr 21, 2009, at 9:36 AM, Mieleton wrote:
>
>
> Craig McClanahan wrote:
>>
>> I can't think of anything off the top of my head that would change
>> this
>> between 1.0.2 and 1.0.3, but I do know that this would be the
>> exception
>> you'd get if you didn't have jersey-multipart-xxx.jar in your
>> application's classpath. Can you double check that this is still
>> being
>> included in a 1.0.3 environment?
>>
>>
>
> It should be included correctly.
>
Are you using Maven?
Do you also have a dependency on MIMEPull ?
<dependency>
<groupId>org.jvnet</groupId>
<artifactId>mimepull</artifactId>
<version>1.3</version>
</dependency>
1.0.3 changed the underlying implementation from JavaMail to MIMEPull
so as to support very large message body parts without running out of
memory.
Paul.
>
>
>> It also appears from your log below that a "--" is missing from the
>> boundary header for the first body part, but is present on the
>> second.
>> Is this a real client issue, or is it an artifact of cut-n-paste?
>> Also,
>> what does the Content-Type header on the second body part actually
>> say?
>>
>>
>
> The log is a direct result from using
> com.sun.jersey.api.container.filter.LoggingFilter and i have not
> changed it
> in any way.
>
> I have 2 objects in the multipart message, first is normal java object
> transferred as XML, other is InputStream containing what ever file
> that we
> are transferring from our client to server.
>
> --
> View this message in context: http://n2.nabble.com/Multipart-1.0.3-not-finding-message-body-reader-tp2668407p2668459.html
> Sent from the Jersey mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>