Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates
 66.249.82.193 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=IguZm0Dt0ocb798MByK/fN4h4FdVQBJcey+MAlP3ZFVGoYLcFkrhNrWXVXkqx2nFFJxSE2S1LwZXO+hL2+zbYA1McvRDzQvs8d5f5N17ia4qG0MWtMweJbfwcR8ZWcCu1CuOvrHe7bdWM5SutmLxlEBYVqHe3tSn9N4DVD271r4=
Message-ID: <19e0530f0602100736k270331d8w5e090088dce97505@mail.gmail.com>
Date: Fri, 10 Feb 2006 10:36:52 -0500
From: Davanum Srinivas <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-dev@ws.apache.org, rickmcg@gmail.com
Subject: Re: Axis 1.X HEAD broken
Cc: David Blevins <david.blevins@visi.com>
In-Reply-To: <43ECB012.9000206@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <19e0530f0601290504u60d3dc32v5c660bcd0f0ff1b@mail.gmail.com>
	 <83881183-FAB3-4082-AD18-CAD5DF82117F@visi.com>
	 <19e0530f0602071530t447ee419ie47dfed4672fa496@mail.gmail.com>
	 <13E65B97-2189-477F-AB11-FB073A0B5590@visi.com>
	 <86ecc290602071726l1b78135ahc58d7fdacaf3e682@mail.gmail.com>
	 <824D4FC2-ADD1-4CF4-B591-9FA30F2E4BE0@gmail.com>
	 <E68159C2-CB16-47D9-A5F3-F46E5935B498@visi.com>
	 <43E9F5AE.8010902@gmail.com>
	 <E0B78B5E-FC13-4364-BF2A-376E03277815@visi.com>
	 <43ECB012.9000206@gmail.com>

Thanks a ton Rick.

On 2/10/06, Rick McGuire <rickmcg@gmail.com> wrote:
> David Blevins wrote:
> > Hey Rick, see below.  Smushing some of your replies into this email
> > (man, you work fast :)
> >
> > David Blevins wrote:
> >
> >> Hey Rick, I know you are working on the javamail code.  Is this
> >> something you can help with?  See below....
> >>
> >>
> >>> On Feb 7, 2006, at 6:03 PM, Changshin Lee wrote:
> >>>
> >>>
> >>>> Currently ant clean all-tests fails at test.saaj package test:
> >>>>
> >>>> TestAttachment
> >>>>
> >>>> - java.io.IOException:
> >>>> javax.activation.UnsupportedDataTypeException: multipart/related;
> >>>> type=3D"text/xml";
> >>>> start=3D"<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=3D----=3D_Par=
t_0.1139364018621
> >>>>
> >>>>     at javax.activation.DataHandler.writeTo(DataHandler.java:76)
> >>>>     at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:513)
> >>>>     at
> >>>> org.apache.axis.attachments.MimeUtils.writeToMultiPartStream(MimeUti=
ls.java:202)
> >>>>
> >>>>     at
> >>>> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream(Att=
achmentsImpl.java:493)
> >>>>
> >>>>     at org.apache.axis.Message.writeTo(Message.java:545)
> >>>>     at
> >>>> test.saaj.TestAttachment.testStringAttachment(TestAttachment.java:55=
)
> >>>>
> >>> [...]
> >>>
> >
> > http://svn.apache.org/repos/asf/webservices/axis/trunk/java/test/saaj/T=
estAttachment.java
> >
> >
> >
> >>>> TestAttachmentSerialization
> >>>>
> >>>> - java.io.IOException:
> >>>> javax.activation.UnsupportedDataTypeException: multipart/related;
> >>>> type=3D"text/xml";
> >>>> start=3D"<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=3D----=3D_Par=
t_0.1139364114325
> >>>>
> >>>>     at javax.activation.DataHandler.writeTo(DataHandler.java:76)
> >>>>     at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:513)
> >>>>     at
> >>>> org.apache.axis.attachments.MimeUtils.writeToMultiPartStream(MimeUti=
ls.java:202)
> >>>>
> >>>>     at
> >>>> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream(Att=
achmentsImpl.java:493)
> >>>>
> >>>>     at org.apache.axis.Message.writeTo(Message.java:545)
> >>>>     at
> >>>> test.saaj.TestAttachmentSerialization.saveMsgWithAttachments(TestAtt=
achmentSerialization.java:113)
> >>>>
> >>>>
> >>> [...]
> >>>
> >
> > http://svn.apache.org/repos/asf/webservices/axis/trunk/java/test/saaj/T=
estAttachmentSerialization.java
> >
> >
> >
> >>>> Note that activation.jar and mail.jar from Sun solves these problems=
.
> >>>>
> >>>
> >>>
> >>> So I added the javamail and activation jars from geronimo specs
> >>> assuming they would work as well (or as bad) as the sun ones for
> >>> Axis' purpose, but it looks like we were lucky enough to uncover a
> >>> really great test case :)
> >>>
> >>> You know what's going on here?
> >>>
> >
> > On Feb 8, 2006, at 2:36 AM, Rick McGuire wrote:
> >
> >> I'm a little confused at the situation here.  Does this work, or fail
> >> using the Sun javamail version?  The stack traces above are clearly
> >> from the Geronimo one.  Without a little debugging, I'm not sure I
> >> understand why it's failing.  The Geronimo javamail version only has
> >> JAF handlers for two MIME types, text and XML...but this IS XML, so I
> >> don't understand why it's not locating the handler.
> >> If you can get me a test case to reproduce this, I'll move chasing
> >> this down to the top of my javamail priority list.
> >>
> >
> > Right, it works for the Sun javamail, but not for the Geronimo
> > javamail version.  The failures above are caused by the Geronimo versio=
n.
> >
> > On Feb 8, 2006, at 3:16 AM, Rick McGuire wrote:
> >
> >> I think I have an idea on what's going on here.  Comparing the
> >> handlers registered in the Sun mailcap file vs. the ones registered
> >> in the Geronimo file, it appears the problem is not with locating a
> >> handler for the "text/xml" datatype, but rather with
> >> "multipart/related".  The Sun version registers a handler for
> >> "multipart/*", while the G. version only has handlers for
> >> "text/plain" and "text/xml" (it's missing other types registered by
> >> the Sun version too, but this problem, I believe, is caused by the
> >> missing multipart bit).
> >> I just started working on filling on some of the gaps in the
> >> MimeMessage class, and this appears related.  I'll see if I can whip
> >> up a MimeMessage handler.  It may take a day or too, as I need to do
> >> a little research to figure out what's required.  I'd appreciate the
> >> test case, since that will help me figure out if I've got it right or
> >> not.
> >>
> >
> > Ok, so we're a little short on handlers for multipart/*, specifically
> > multipart/related.  Got it.
> >
> > On Feb 8, 2006, at 5:44 AM, Rick McGuire wrote:
> >
> >> Writing handlers looks easier than I originally suspected it would
> >> be.  I think I have a handler now that will do the job, but I still
> >> need a test case to verify this fixes the problem (and also debug my
> >> code).
> >>
> >
> > Excellent -- that was a quick "day or two" :)
> >
> > How much coffee have you been drinking this morning?  This one is a
> > record, i've clocked you at going from confused to having a solution
> > in three emails and 3hrs and 8min.
> >
> > I've linked the test cases by name above.  This is the source you'll
> > need to grab to run them:
> >
> > http://svn.apache.org/repos/asf/webservices/axis/trunk/java
> >
> > It's basically 'ant all-tests' to run them.  You can of course dig
> > through and run just the saaj tests too.
> >
> > You the man!
> I've just opened Jira GERONIMO-1619 with the fix (fixes, actually, as it
> required a chain of at least 6 things to be fixed to clear up the
> problem).  There's also another Jira (1618) I opened to fix a build
> problem that will require resolution for this to be completely operationa=
l.
>
> I'm able to cleanly run the tests up to some of the wsdl/interop tests,
> which fail because of compile errors.  The specific identified tests
> appear to be working now.
>
> Rick
>
> >
> > -David
> >
> >
> >
>
>


--
Davanum Srinivas : http://wso2.com/blogs/