You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by David Blevins <da...@visi.com> on 2006/02/08 00:06:27 UTC
Re: Axis 1.X HEAD broken
On Jan 30, 2006, at 8:00 PM, David Blevins wrote:
> On Jan 29, 2006, at 5:04 AM, Davanum Srinivas wrote:
>
>> Dug,
>> Can u please fix the build break? I just got the latest HEAD and
>> there
>> are failures even in the funtional tests :( We can't reallly
>> afford to
>> do that. we need to get "ant clean all-tests" working again. I can
>> confirm that all tests were passing before your changes got in.
>>
>> David,
>> Can u please help?
>>
>
> I'd be happy to help Doug with his changes if I can. Doug, what do
> you need?
>
Dims, could you forward me the commit message pertaining to Doug's
changes?
-David
Re: Axis 1.X HEAD broken
Posted by Davanum Srinivas <da...@gmail.com>.
Thanks a ton Rick.
On 2/10/06, Rick McGuire <ri...@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="text/xml";
> >>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----=_Part_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(MimeUtils.java:202)
> >>>>
> >>>> at
> >>>> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream(AttachmentsImpl.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/TestAttachment.java
> >
> >
> >
> >>>> TestAttachmentSerialization
> >>>>
> >>>> - java.io.IOException:
> >>>> javax.activation.UnsupportedDataTypeException: multipart/related;
> >>>> type="text/xml";
> >>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----=_Part_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(MimeUtils.java:202)
> >>>>
> >>>> at
> >>>> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream(AttachmentsImpl.java:493)
> >>>>
> >>>> at org.apache.axis.Message.writeTo(Message.java:545)
> >>>> at
> >>>> test.saaj.TestAttachmentSerialization.saveMsgWithAttachments(TestAttachmentSerialization.java:113)
> >>>>
> >>>>
> >>> [...]
> >>>
> >
> > http://svn.apache.org/repos/asf/webservices/axis/trunk/java/test/saaj/TestAttachmentSerialization.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 version.
> >
> > 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 operational.
>
> 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/
Re: Axis 1.X HEAD broken
Posted by Rick McGuire <ri...@gmail.com>.
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="text/xml";
>>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----=_Part_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(MimeUtils.java:202)
>>>>
>>>> at
>>>> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream(AttachmentsImpl.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/TestAttachment.java
>
>
>
>>>> TestAttachmentSerialization
>>>>
>>>> - java.io.IOException:
>>>> javax.activation.UnsupportedDataTypeException: multipart/related;
>>>> type="text/xml";
>>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----=_Part_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(MimeUtils.java:202)
>>>>
>>>> at
>>>> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream(AttachmentsImpl.java:493)
>>>>
>>>> at org.apache.axis.Message.writeTo(Message.java:545)
>>>> at
>>>> test.saaj.TestAttachmentSerialization.saveMsgWithAttachments(TestAttachmentSerialization.java:113)
>>>>
>>>>
>>> [...]
>>>
>
> http://svn.apache.org/repos/asf/webservices/axis/trunk/java/test/saaj/TestAttachmentSerialization.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 version.
>
> 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.
It might be a little slower this afternoon....the caffeine jolt tends to
wear off in the early afternoon :-)
>
> 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!
>
> -David
>
>
>
Re: Axis 1.X HEAD broken
Posted by Davanum Srinivas <da...@gmail.com>.
Please replace that with the whitemesa wsdl
(http://www.whitemesa.net/wsdl/r3/import1.wsdl) and see if that fixes
the problem.
thanks,
dims
On 2/14/06, David Blevins <da...@visi.com> wrote:
> On Feb 12, 2006, at 3:41 PM, Changshin Lee wrote:
>
> > I'd appreciate your great (and fast :-) work on that.
>
> Thanks to Rick for fixing and Alan Cabrera for building/publishing
> the new spec jars!
>
> > Meanwhile, currently build fails due to unavailability of http://
> > soapinterop.java.sun.com/round3/groupd/import1?WSDL .
>
> I admit I'm way more familiar with the core code than the tests....
>
> Dims, do you know what this all about?
>
> -David
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: old specs (was: Re: Axis 1.X HEAD broken)
Posted by Jason Dillon <ja...@planet57.com>.
> I'm in favor of keeping the 1.0 and 1.1 spec jars all separate until
> this can all be sorted out. Too many people are having trouble
> building the HEAD because of the deps on the 1.1 spec jars.
I'm not sure what you man... I changed the depends on console-
framework just now to use 2 depends instead of one, but they are
still the latest versions built from specs/trunk.
--jason
Re: old specs (was: Re: Axis 1.X HEAD broken)
Posted by Bruce Snyder <br...@gmail.com>.
On 2/12/06, Jason Dillon <ja...@planet57.com> wrote:
> I ran into this yesterday too :-(
>
> Does not look like the new spec build using m2 creates a jar for
> maven 1 with all of the dependencies. The geronimo-spec-j2ee module
> only builds a pom.
>
> Maybe, until we can move to m2, we should just depend on each of the
> spec jars and not the all-in-one j2ee version.
I'm in favor of keeping the 1.0 and 1.1 spec jars all separate until
this can all be sorted out. Too many people are having trouble
building the HEAD because of the deps on the 1.1 spec jars.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo (http://geronimo.apache.org/)
Castor (http://castor.org/)
Re: old specs (was: Re: Axis 1.X HEAD broken)
Posted by Jason Dillon <ja...@planet57.com>.
I ran into this yesterday too :-(
Does not look like the new spec build using m2 creates a jar for
maven 1 with all of the dependencies. The geronimo-spec-j2ee module
only builds a pom.
Maybe, until we can move to m2, we should just depend on each of the
spec jars and not the all-in-one j2ee version.
--jason
On Feb 12, 2006, at 2:44 AM, Jacek Laskowski wrote:
> 2006/2/12, David Blevins <da...@visi.com>:
>
>> As well, I deleted the old 1.1-SNAPSHOT jars that never should
> ...snip...
>> geronimo-j2ee_1.4_spec-1.1-SNAPSHOT.jar
>
> ...and (incidentally) broke [continuum] BUILD FAILURE: Geronimo::
> Applications:
>
> BUILD FAILED
> File...... /home/continuum/.maven/cache/maven-multiproject-
> plugin-1.4.1/plugin.jelly
> Element... maven:reactor
> Line...... 218
> Column.... -1
> The build cannot continue because of the following unsatisfied
> dependency:
>
> geronimo-j2ee_1.4_spec-1.1-SNAPSHOT.jar
>
> ;)
>
>> -David
>
> --
> Jacek Laskowski
> http://www.laskowski.org.pl
Re: old specs (was: Re: Axis 1.X HEAD broken)
Posted by Jacek Laskowski <el...@gmail.com>.
2006/2/12, David Blevins <da...@visi.com>:
> As well, I deleted the old 1.1-SNAPSHOT jars that never should
...snip...
> geronimo-j2ee_1.4_spec-1.1-SNAPSHOT.jar
...and (incidentally) broke [continuum] BUILD FAILURE: Geronimo:: Applications:
BUILD FAILED
File...... /home/continuum/.maven/cache/maven-multiproject-plugin-1.4.1/plugin.jelly
Element... maven:reactor
Line...... 218
Column.... -1
The build cannot continue because of the following unsatisfied dependency:
geronimo-j2ee_1.4_spec-1.1-SNAPSHOT.jar
;)
> -David
--
Jacek Laskowski
http://www.laskowski.org.pl
old specs (was: Re: Axis 1.X HEAD broken)
Posted by David Blevins <da...@visi.com>.
On Feb 10, 2006, at 5:36 PM, David Blevins wrote:
> One note, we are publishing the 1.0 jars with the snapshot jars
> which we probably should not do. It means there is one jar here,
> for example:
>
> http://cvs.apache.org/repository/org.apache.geronimo.specs/jars/
> geronimo-jms_1.1_spec-1.0.jar
>
> ...which is different than these jars...
>
> http://www.apache.org/dist/java-repository/
> org.apache.geronimo.specs/jars/geronimo-jms_1.1_spec-1.0.jar
> http://www.ibiblio.org/maven/org.apache.geronimo.specs/jars/
> geronimo-jms_1.1_spec-1.0.jar
> http://www.tux.org/pub/net/apache/dist/java-repository/
> org.apache.geronimo.specs/jars/geronimo-jms_1.1_spec-1.0.jar
> http://apache.mirror99.com/java-repository/
> org.apache.geronimo.specs/jars/geronimo-jms_1.1_spec-1.0.jar
>
> You might want to kill those quick before someone grabs them.
> Maybe just copy all the *1.0.jar files from /www/www.apache.org/...
> into /www/cvs.apache.org/...
>
So, I rsync'ed the correct spec 1.0 jars into cvs.apache.org
rsync -rt -v /www/www.apache.org/dist/java-repository/
org.apache.geronimo.specs /www/cvs.apache.org/repository/
As well, I deleted the old 1.1-SNAPSHOT jars that never should have been
geronimo-ejb_2.1_spec-1.1-SNAPSHOT.jar
geronimo-ejb_2.1_spec-1.1-SNAPSHOT.jar.md5
geronimo-ejb_2.1_spec-1.1-SNAPSHOT.jar.sha1
geronimo-j2ee-connector_1.5_spec-1.1-SNAPSHOT.jar
geronimo-j2ee-connector_1.5_spec-1.1-SNAPSHOT.jar.md5
geronimo-j2ee-connector_1.5_spec-1.1-SNAPSHOT.jar.sha1
geronimo-j2ee-deployment_1.1_spec-1.1-SNAPSHOT.jar
geronimo-j2ee-deployment_1.1_spec-1.1-SNAPSHOT.jar.md5
geronimo-j2ee-deployment_1.1_spec-1.1-SNAPSHOT.jar.sha1
geronimo-j2ee-jacc_1.0_spec-1.1-SNAPSHOT.jar
geronimo-j2ee-jacc_1.0_spec-1.1-SNAPSHOT.jar.md5
geronimo-j2ee-jacc_1.0_spec-1.1-SNAPSHOT.jar.sha1
geronimo-j2ee-management_1.0_spec-1.1-SNAPSHOT.jar
geronimo-j2ee-management_1.0_spec-1.1-SNAPSHOT.jar.md5
geronimo-j2ee-management_1.0_spec-1.1-SNAPSHOT.jar.sha1
geronimo-j2ee_1.4_spec-1.1-SNAPSHOT.jar
geronimo-j2ee_1.4_spec-1.1-SNAPSHOT.jar.md5
geronimo-j2ee_1.4_spec-1.1-SNAPSHOT.jar.sha1
geronimo-jaxr_1.0_spec-1.1-SNAPSHOT.jar
geronimo-jaxr_1.0_spec-1.1-SNAPSHOT.jar.md5
geronimo-jaxr_1.0_spec-1.1-SNAPSHOT.jar.sha1
geronimo-jaxrpc_1.1_spec-1.1-SNAPSHOT.jar
geronimo-jaxrpc_1.1_spec-1.1-SNAPSHOT.jar.md5
geronimo-jaxrpc_1.1_spec-1.1-SNAPSHOT.jar.sha1
geronimo-jms_1.1_spec-1.1-SNAPSHOT.jar
geronimo-jms_1.1_spec-1.1-SNAPSHOT.jar.md5
geronimo-jms_1.1_spec-1.1-SNAPSHOT.jar.sha1
geronimo-jsp_2.0_spec-1.1-SNAPSHOT.jar
geronimo-jsp_2.0_spec-1.1-SNAPSHOT.jar.md5
geronimo-jsp_2.0_spec-1.1-SNAPSHOT.jar.sha1
geronimo-jta_1.0.1B_spec-1.1-SNAPSHOT.jar
geronimo-jta_1.0.1B_spec-1.1-SNAPSHOT.jar.md5
geronimo-jta_1.0.1B_spec-1.1-SNAPSHOT.jar.sha1
geronimo-qname_1.1_spec-1.1-SNAPSHOT.jar
geronimo-qname_1.1_spec-1.1-SNAPSHOT.jar.md5
geronimo-qname_1.1_spec-1.1-SNAPSHOT.jar.sha1
geronimo-saaj_1.1_spec-1.1-SNAPSHOT.jar
geronimo-saaj_1.1_spec-1.1-SNAPSHOT.jar.md5
geronimo-saaj_1.1_spec-1.1-SNAPSHOT.jar.sha1
geronimo-servlet_2.4_spec-1.1-SNAPSHOT.jar
geronimo-servlet_2.4_spec-1.1-SNAPSHOT.jar.md5
geronimo-servlet_2.4_spec-1.1-SNAPSHOT.jar.sha1
-David
Re: Axis 1.X HEAD broken
Posted by David Blevins <da...@visi.com>.
Excellent.
One note, we are publishing the 1.0 jars with the snapshot jars which
we probably should not do. It means there is one jar here, for example:
http://cvs.apache.org/repository/org.apache.geronimo.specs/jars/
geronimo-jms_1.1_spec-1.0.jar
...which is different than these jars...
http://www.apache.org/dist/java-repository/
org.apache.geronimo.specs/jars/geronimo-jms_1.1_spec-1.0.jar
http://www.ibiblio.org/maven/org.apache.geronimo.specs/jars/
geronimo-jms_1.1_spec-1.0.jar
http://www.tux.org/pub/net/apache/dist/java-repository/
org.apache.geronimo.specs/jars/geronimo-jms_1.1_spec-1.0.jar
http://apache.mirror99.com/java-repository/
org.apache.geronimo.specs/jars/geronimo-jms_1.1_spec-1.0.jar
You might want to kill those quick before someone grabs them. Maybe
just copy all the *1.0.jar files from /www/www.apache.org/... into /
www/cvs.apache.org/...
-David
On Feb 10, 2006, at 4:57 PM, Alan D. Cabrera wrote:
> Uploaded
>
>
> Regards,
> Alan
>
> On 2/10/2006 12:12 PM, David Blevins wrote:
>
>> Yes Sir, Thank You Sir!
>>
>> Let me know when they're up and I'll check those puppies into Axis
>> scm.
>>
>> -David
>>
>> On Feb 10, 2006, at 11:48 AM, Alan D. Cabrera wrote:
>>
>>> Applied and commited. You need me to deploy these puppies?
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>> On 2/10/2006 10:48 AM, David Blevins wrote:
>>>
>>>> Hey Alan,
>>>>
>>>> I broke part of the axis build by checking in the javamail and
>>>> activation jars from geronimo. Rick has fixed it in
>>>> GERONIMO-1619 and GERONIMO-1618. You've got GERONIMO-1618
>>>> already.
>>>>
>>>> Can you take these both and can you get them in asap so I can
>>>> get new javamail jars into Axis and their build working again?
>>>>
>>>> -David
>>>>
>>>> Begin forwarded message:
>>>>
>>>>> From: David Blevins <da...@visi.com>
>>>>> Date: February 10, 2006 10:10:34 AM PST
>>>>> To: axis-dev@ws.apache.org
>>>>> Cc: Rick McGuire <ri...@gmail.com>
>>>>> Subject: Re: Axis 1.X HEAD broken
>>>>> Reply-To: axis-dev@ws.apache.org
>>>>>
>>>>>
>>>>> On Feb 10, 2006, at 7:24 AM, Rick McGuire wrote:
>>>>>
>>>>>> David Blevins wrote:
>>>>>>
>>>>>>>>>> Currently ant clean all-tests fails at test.saaj package
>>>>>>>>>> test:
>>>>>>>>>>
>>>>>>>>>> TestAttachment
>>>>>>>>>>
>>>>>>>>>> - java.io.IOException:
>>>>>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>>>>>> related; type="text/xml";
>>>>>>>>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----
>>>>>>>>>> =_Part_0.1139364018621
>>>>>>>>>
>>>>>>>>>
>>>>> [...]
>>>>>
>>>>>>>>>> TestAttachmentSerialization
>>>>>>>>>>
>>>>>>>>>> - java.io.IOException:
>>>>>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>>>>>> related; type="text/xml";
>>>>>>>>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----
>>>>>>>>>> =_Part_0.1139364114325
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>
>>>>>> 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 operational.
>>>>>>
>>>>>> 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.
>>>>>
>>>>>
>>>>>
>>>>> Excellent! I'll get right on GERONIMO-1619 and GERONIMO-1618
>>>>> and get new jars into Axis asap.
>>>>>
>>>>> -David
>>>>>
>>>
>>>
>
>
Re: Axis 1.X HEAD broken
Posted by "Alan D. Cabrera" <ad...@toolazydogs.com>.
Uploaded
Regards,
Alan
On 2/10/2006 12:12 PM, David Blevins wrote:
> Yes Sir, Thank You Sir!
>
> Let me know when they're up and I'll check those puppies into Axis scm.
>
> -David
>
> On Feb 10, 2006, at 11:48 AM, Alan D. Cabrera wrote:
>
>> Applied and commited. You need me to deploy these puppies?
>>
>>
>> Regards,
>> Alan
>>
>> On 2/10/2006 10:48 AM, David Blevins wrote:
>>
>>> Hey Alan,
>>>
>>> I broke part of the axis build by checking in the javamail and
>>> activation jars from geronimo. Rick has fixed it in GERONIMO-1619
>>> and GERONIMO-1618. You've got GERONIMO-1618 already.
>>>
>>> Can you take these both and can you get them in asap so I can get
>>> new javamail jars into Axis and their build working again?
>>>
>>> -David
>>>
>>> Begin forwarded message:
>>>
>>>> From: David Blevins <da...@visi.com>
>>>> Date: February 10, 2006 10:10:34 AM PST
>>>> To: axis-dev@ws.apache.org
>>>> Cc: Rick McGuire <ri...@gmail.com>
>>>> Subject: Re: Axis 1.X HEAD broken
>>>> Reply-To: axis-dev@ws.apache.org
>>>>
>>>>
>>>> On Feb 10, 2006, at 7:24 AM, Rick McGuire wrote:
>>>>
>>>>> David Blevins wrote:
>>>>>
>>>>>>>>> Currently ant clean all-tests fails at test.saaj package test:
>>>>>>>>>
>>>>>>>>> TestAttachment
>>>>>>>>>
>>>>>>>>> - java.io.IOException:
>>>>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>>>>> related; type="text/xml";
>>>>>>>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----
>>>>>>>>> =_Part_0.1139364018621
>>>>>>>>
>>>>>>>>
>>>> [...]
>>>>
>>>>>>>>> TestAttachmentSerialization
>>>>>>>>>
>>>>>>>>> - java.io.IOException:
>>>>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>>>>> related; type="text/xml";
>>>>>>>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----
>>>>>>>>> =_Part_0.1139364114325
>>>>>>>>
>>>>>>>>
>>>>>
>>>>
>>>>> 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 operational.
>>>>>
>>>>> 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.
>>>>
>>>>
>>>>
>>>> Excellent! I'll get right on GERONIMO-1619 and GERONIMO-1618 and
>>>> get new jars into Axis asap.
>>>>
>>>> -David
>>>>
>>
>>
Re: Axis 1.X HEAD broken
Posted by David Blevins <da...@visi.com>.
Yes Sir, Thank You Sir!
Let me know when they're up and I'll check those puppies into Axis scm.
-David
On Feb 10, 2006, at 11:48 AM, Alan D. Cabrera wrote:
> Applied and commited. You need me to deploy these puppies?
>
>
> Regards,
> Alan
>
> On 2/10/2006 10:48 AM, David Blevins wrote:
>
>> Hey Alan,
>>
>> I broke part of the axis build by checking in the javamail and
>> activation jars from geronimo. Rick has fixed it in
>> GERONIMO-1619 and GERONIMO-1618. You've got GERONIMO-1618 already.
>>
>> Can you take these both and can you get them in asap so I can get
>> new javamail jars into Axis and their build working again?
>>
>> -David
>>
>> Begin forwarded message:
>>
>>> From: David Blevins <da...@visi.com>
>>> Date: February 10, 2006 10:10:34 AM PST
>>> To: axis-dev@ws.apache.org
>>> Cc: Rick McGuire <ri...@gmail.com>
>>> Subject: Re: Axis 1.X HEAD broken
>>> Reply-To: axis-dev@ws.apache.org
>>>
>>>
>>> On Feb 10, 2006, at 7:24 AM, Rick McGuire wrote:
>>>
>>>> David Blevins wrote:
>>>>
>>>>>>>> Currently ant clean all-tests fails at test.saaj package test:
>>>>>>>>
>>>>>>>> TestAttachment
>>>>>>>>
>>>>>>>> - java.io.IOException:
>>>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>>>> related; type="text/xml";
>>>>>>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----
>>>>>>>> =_Part_0.1139364018621
>>>>>>>
>>> [...]
>>>
>>>>>>>> TestAttachmentSerialization
>>>>>>>>
>>>>>>>> - java.io.IOException:
>>>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>>>> related; type="text/xml";
>>>>>>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----
>>>>>>>> =_Part_0.1139364114325
>>>>>>>
>>>>
>>>
>>>> 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 operational.
>>>>
>>>> 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.
>>>
>>>
>>> Excellent! I'll get right on GERONIMO-1619 and GERONIMO-1618
>>> and get new jars into Axis asap.
>>>
>>> -David
>>>
>
>
Re: Fwd: Axis 1.X HEAD broken
Posted by "Alan D. Cabrera" <ad...@toolazydogs.com>.
Applied and commited. You need me to deploy these puppies?
Regards,
Alan
On 2/10/2006 10:48 AM, David Blevins wrote:
> Hey Alan,
>
> I broke part of the axis build by checking in the javamail and
> activation jars from geronimo. Rick has fixed it in GERONIMO-1619
> and GERONIMO-1618. You've got GERONIMO-1618 already.
>
> Can you take these both and can you get them in asap so I can get new
> javamail jars into Axis and their build working again?
>
> -David
>
> Begin forwarded message:
>
>> From: David Blevins <da...@visi.com>
>> Date: February 10, 2006 10:10:34 AM PST
>> To: axis-dev@ws.apache.org
>> Cc: Rick McGuire <ri...@gmail.com>
>> Subject: Re: Axis 1.X HEAD broken
>> Reply-To: axis-dev@ws.apache.org
>>
>>
>> On Feb 10, 2006, at 7:24 AM, Rick McGuire wrote:
>>
>>> David Blevins wrote:
>>>
>>>>>>> Currently ant clean all-tests fails at test.saaj package test:
>>>>>>>
>>>>>>> TestAttachment
>>>>>>>
>>>>>>> - java.io.IOException:
>>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>>> related; type="text/xml";
>>>>>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----
>>>>>>> =_Part_0.1139364018621
>>>>>>
>> [...]
>>
>>>>>>> TestAttachmentSerialization
>>>>>>>
>>>>>>> - java.io.IOException:
>>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>>> related; type="text/xml";
>>>>>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----
>>>>>>> =_Part_0.1139364114325
>>>>>>
>>>
>>
>>> 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 operational.
>>>
>>> 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.
>>
>>
>> Excellent! I'll get right on GERONIMO-1619 and GERONIMO-1618 and
>> get new jars into Axis asap.
>>
>> -David
>>
Fwd: Axis 1.X HEAD broken
Posted by David Blevins <da...@visi.com>.
Hey Alan,
I broke part of the axis build by checking in the javamail and
activation jars from geronimo. Rick has fixed it in GERONIMO-1619
and GERONIMO-1618. You've got GERONIMO-1618 already.
Can you take these both and can you get them in asap so I can get new
javamail jars into Axis and their build working again?
-David
Begin forwarded message:
> From: David Blevins <da...@visi.com>
> Date: February 10, 2006 10:10:34 AM PST
> To: axis-dev@ws.apache.org
> Cc: Rick McGuire <ri...@gmail.com>
> Subject: Re: Axis 1.X HEAD broken
> Reply-To: axis-dev@ws.apache.org
>
>
> On Feb 10, 2006, at 7:24 AM, Rick McGuire wrote:
>
>> David Blevins wrote:
>>>>>> Currently ant clean all-tests fails at test.saaj package test:
>>>>>>
>>>>>> TestAttachment
>>>>>>
>>>>>> - java.io.IOException:
>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>> related; type="text/xml";
>>>>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----
>>>>>> =_Part_0.1139364018621
> [...]
>>>>>> TestAttachmentSerialization
>>>>>>
>>>>>> - java.io.IOException:
>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>> related; type="text/xml";
>>>>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----
>>>>>> =_Part_0.1139364114325
>>
>
>> 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 operational.
>>
>> 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.
>
> Excellent! I'll get right on GERONIMO-1619 and GERONIMO-1618 and
> get new jars into Axis asap.
>
> -David
>
Re: Axis 1.X HEAD broken
Posted by David Blevins <da...@visi.com>.
On Feb 12, 2006, at 3:41 PM, Changshin Lee wrote:
> I'd appreciate your great (and fast :-) work on that.
Thanks to Rick for fixing and Alan Cabrera for building/publishing
the new spec jars!
> Meanwhile, currently build fails due to unavailability of http://
> soapinterop.java.sun.com/round3/groupd/import1?WSDL .
I admit I'm way more familiar with the core code than the tests....
Dims, do you know what this all about?
-David
Re: Axis 1.X HEAD broken
Posted by Changshin Lee <ia...@gmail.com>.
I'd appreciate your great (and fast :-) work on that.
Meanwhile, currently build fails due to unavailability of http://
soapinterop.java.sun.com/round3/groupd/import1?WSDL .
Cheers,
Ias
2006. 02. 11, 오전 3:10, David Blevins 작성:
>
> On Feb 10, 2006, at 7:24 AM, Rick McGuire wrote:
>
>> David Blevins wrote:
>>>>>> Currently ant clean all-tests fails at test.saaj package test:
>>>>>>
>>>>>> TestAttachment
>>>>>>
>>>>>> - java.io.IOException:
>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>> related; type="text/xml";
>>>>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----
>>>>>> =_Part_0.1139364018621
> [...]
>>>>>> TestAttachmentSerialization
>>>>>>
>>>>>> - java.io.IOException:
>>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>>> related; type="text/xml";
>>>>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----
>>>>>> =_Part_0.1139364114325
>>
>
>> 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 operational.
>>
>> 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.
>
> Excellent! I'll get right on GERONIMO-1619 and GERONIMO-1618 and
> get new jars into Axis asap.
>
> -David
>
Re: Axis 1.X HEAD broken
Posted by David Blevins <da...@visi.com>.
On Feb 10, 2006, at 7:24 AM, Rick McGuire wrote:
> David Blevins wrote:
>>>>> Currently ant clean all-tests fails at test.saaj package test:
>>>>>
>>>>> TestAttachment
>>>>>
>>>>> - java.io.IOException:
>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>> related; type="text/xml";
>>>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----
>>>>> =_Part_0.1139364018621
[...]
>>>>> TestAttachmentSerialization
>>>>>
>>>>> - java.io.IOException:
>>>>> javax.activation.UnsupportedDataTypeException: multipart/
>>>>> related; type="text/xml";
>>>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----
>>>>> =_Part_0.1139364114325
>
> 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 operational.
>
> 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.
Excellent! I'll get right on GERONIMO-1619 and GERONIMO-1618 and get
new jars into Axis asap.
-David
Re: Axis 1.X HEAD broken
Posted by Rick McGuire <ri...@gmail.com>.
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="text/xml";
>>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----=_Part_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(MimeUtils.java:202)
>>>>
>>>> at
>>>> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream(AttachmentsImpl.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/TestAttachment.java
>
>
>
>>>> TestAttachmentSerialization
>>>>
>>>> - java.io.IOException:
>>>> javax.activation.UnsupportedDataTypeException: multipart/related;
>>>> type="text/xml";
>>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----=_Part_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(MimeUtils.java:202)
>>>>
>>>> at
>>>> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream(AttachmentsImpl.java:493)
>>>>
>>>> at org.apache.axis.Message.writeTo(Message.java:545)
>>>> at
>>>> test.saaj.TestAttachmentSerialization.saveMsgWithAttachments(TestAttachmentSerialization.java:113)
>>>>
>>>>
>>> [...]
>>>
>
> http://svn.apache.org/repos/asf/webservices/axis/trunk/java/test/saaj/TestAttachmentSerialization.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 version.
>
> 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 operational.
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
>
>
>
Re: Axis 1.X HEAD broken
Posted by David Blevins <da...@visi.com>.
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="text/xml";
>>> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----
>>> =_Part_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
>>> (MimeUtils.java:202)
>>> at
>>> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream
>>> (AttachmentsImpl.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/
TestAttachment.java
>>> TestAttachmentSerialization
>>>
>>> - java.io.IOException:
>>> javax.activation.UnsupportedDataTypeException: multipart/related;
>>> type="text/xml";
>>> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----
>>> =_Part_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
>>> (MimeUtils.java:202)
>>> at
>>> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream
>>> (AttachmentsImpl.java:493)
>>> at org.apache.axis.Message.writeTo(Message.java:545)
>>> at
>>> test.saaj.TestAttachmentSerialization.saveMsgWithAttachments
>>> (TestAttachmentSerialization.java:113)
>>>
>> [...]
>>
http://svn.apache.org/repos/asf/webservices/axis/trunk/java/test/saaj/
TestAttachmentSerialization.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
version.
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!
-David
Re: Axis 1.X HEAD broken
Posted by David Blevins <da...@visi.com>.
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="text/xml";
> start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----
> =_Part_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
> (MimeUtils.java:202)
> at org.apache.axis.attachments.AttachmentsImpl.writeContentToStream
> (AttachmentsImpl.java:493)
> at org.apache.axis.Message.writeTo(Message.java:545)
> at test.saaj.TestAttachment.testStringAttachment
> (TestAttachment.java:55)
[...]
> TestAttachmentSerialization
>
> - java.io.IOException:
> javax.activation.UnsupportedDataTypeException: multipart/related;
> type="text/xml";
> start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----
> =_Part_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
> (MimeUtils.java:202)
> at org.apache.axis.attachments.AttachmentsImpl.writeContentToStream
> (AttachmentsImpl.java:493)
> at org.apache.axis.Message.writeTo(Message.java:545)
> at test.saaj.TestAttachmentSerialization.saveMsgWithAttachments
> (TestAttachmentSerialization.java:113)
[...]
> 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?
-David
Re: Axis 1.X HEAD broken
Posted by Changshin Lee <ia...@gmail.com>.
Currently ant clean all-tests fails at test.saaj package test:
TestAttachment
- java.io.IOException:
javax.activation.UnsupportedDataTypeException: multipart/related;
type="text/xml";
start="<DCD809ADF0929061EEBD95D393FAA38E>";;boundary=----
=_Part_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
(MimeUtils.java:202)
at org.apache.axis.attachments.AttachmentsImpl.writeContentToStream
(AttachmentsImpl.java:493)
at org.apache.axis.Message.writeTo(Message.java:545)
at test.saaj.TestAttachment.testStringAttachment(TestAttachment.java:
55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:478)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:344)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:196)
TestAttachmentSerialization
- java.io.IOException:
javax.activation.UnsupportedDataTypeException: multipart/related;
type="text/xml";
start="<BB649A1F2EB5FA531EA2D7CDC8E1063F>";;boundary=----
=_Part_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
(MimeUtils.java:202)
at org.apache.axis.attachments.AttachmentsImpl.writeContentToStream
(AttachmentsImpl.java:493)
at org.apache.axis.Message.writeTo(Message.java:545)
at test.saaj.TestAttachmentSerialization.saveMsgWithAttachments
(TestAttachmentSerialization.java:113)
at test.saaj.TestAttachmentSerialization.testAttachments
(TestAttachmentSerialization.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:478)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:344)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:196)
- InvocationTargetException:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance
(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance
(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at org.apache.axis.Message.setup(Message.java:354)
at org.apache.axis.Message.<init>(Message.java:194)
at org.apache.axis.soap.MessageFactoryImpl.createMessage
(MessageFactoryImpl.java:77)
at test.saaj.TestAttachmentSerialization.loadMsgWithAttachments
(TestAttachmentSerialization.java:122)
at test.saaj.TestAttachmentSerialization.testAttachments
(TestAttachmentSerialization.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:478)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:344)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:196)
Caused by: Error reading data stream: Error in MIME data stream,
start boundary not found, expected: --
at org.apache.axis.attachments.MultiPartRelatedInputStream.<init>
(MultiPartRelatedInputStream.java:339)
at org.apache.axis.attachments.AttachmentsImpl.<init>
(AttachmentsImpl.java:120)
... 24 more
java.lang.RuntimeException
at org.apache.axis.Message.setup(Message.java:361)
at org.apache.axis.Message.<init>(Message.java:194)
at org.apache.axis.soap.MessageFactoryImpl.createMessage
(MessageFactoryImpl.java:77)
at test.saaj.TestAttachmentSerialization.loadMsgWithAttachments
(TestAttachmentSerialization.java:122)
at test.saaj.TestAttachmentSerialization.testAttachments
(TestAttachmentSerialization.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
(RemoteTestRunner.java:478)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
(RemoteTestRunner.java:344)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
(RemoteTestRunner.java:196)
Note that activation.jar and mail.jar from Sun solves these problems.
Cheers,
Ias
2006. 02. 08, 오전 10:26, Jongjin Choi 작성:
> David.
>
> It can help you more to run ant with verbose option like this :
>
> ant -v clean all-tests
>
> I put xbean.jar and jsr173_1.0_api.jar from xmlbeans 2.0 dist into
> lib directory
> to resolve this.
>
> /Jongjin
>
> On 2/8/06, David Blevins <da...@visi.com> wrote:
>>
>> On Feb 7, 2006, at 3:30 PM, Davanum Srinivas wrote:
>>>
>>>> On Jan 30, 2006, at 8:00 PM, David Blevins wrote:
>>>>
>>>>> On Jan 29, 2006, at 5:04 AM, Davanum Srinivas wrote:
>>>>>> there are failures even in the funtional tests :(
>>>>
>>>> Dims, could you forward me the commit message pertaining to Doug's
>>>> changes?
>>>
>>>
>>> Actually i am not sure anymore what broke it...anyway here they are:
>>> http://marc.theaimsgroup.com/?l=axis-dev&w=2&r=1&s=svn+commit
>>> +dug&q=b
>>
>> Thanks.
>>
>> So the strange thing is that even the 1.4 branch fails for me
>> complaining com.superflaco.xbeans.Character doesn't exist.
>>
>> I know i've gotten those tests to run before in the 1.3 timeframe.
>>
>> I do get different failures from trunk (aka HEAD).
>>
>> On a slightly related note, do you mind if hook Axis 1.x up to the
>> continuum install in gbuild and optinally sync the jars in to
>> cvs.apache.org? I know there was some tech here when Axis was on cvs
>> but it doesn't seem to run anymore
>>
>>
>> -David
>>
>>
Re: Axis 1.X HEAD broken
Posted by Jongjin Choi <jo...@gmail.com>.
David.
It can help you more to run ant with verbose option like this :
ant -v clean all-tests
I put xbean.jar and jsr173_1.0_api.jar from xmlbeans 2.0 dist into lib directory
to resolve this.
/Jongjin
On 2/8/06, David Blevins <da...@visi.com> wrote:
>
> On Feb 7, 2006, at 3:30 PM, Davanum Srinivas wrote:
> >
> >> On Jan 30, 2006, at 8:00 PM, David Blevins wrote:
> >>
> >>> On Jan 29, 2006, at 5:04 AM, Davanum Srinivas wrote:
> >>>> there are failures even in the funtional tests :(
> >>
> >> Dims, could you forward me the commit message pertaining to Doug's
> >> changes?
> >
> > Actually i am not sure anymore what broke it...anyway here they are:
> > http://marc.theaimsgroup.com/?l=axis-dev&w=2&r=1&s=svn+commit+dug&q=b
>
> Thanks.
>
> So the strange thing is that even the 1.4 branch fails for me
> complaining com.superflaco.xbeans.Character doesn't exist.
>
> I know i've gotten those tests to run before in the 1.3 timeframe.
>
> I do get different failures from trunk (aka HEAD).
>
> On a slightly related note, do you mind if hook Axis 1.x up to the
> continuum install in gbuild and optinally sync the jars in to
> cvs.apache.org? I know there was some tech here when Axis was on cvs
> but it doesn't seem to run anymore
>
>
> -David
>
>
Re: Axis 1.X HEAD broken
Posted by David Blevins <da...@visi.com>.
On Feb 7, 2006, at 3:30 PM, Davanum Srinivas wrote:
>
>> On Jan 30, 2006, at 8:00 PM, David Blevins wrote:
>>
>>> On Jan 29, 2006, at 5:04 AM, Davanum Srinivas wrote:
>>>> there are failures even in the funtional tests :(
>>
>> Dims, could you forward me the commit message pertaining to Doug's
>> changes?
>
> Actually i am not sure anymore what broke it...anyway here they are:
> http://marc.theaimsgroup.com/?l=axis-dev&w=2&r=1&s=svn+commit+dug&q=b
Thanks.
So the strange thing is that even the 1.4 branch fails for me
complaining com.superflaco.xbeans.Character doesn't exist.
I know i've gotten those tests to run before in the 1.3 timeframe.
I do get different failures from trunk (aka HEAD).
On a slightly related note, do you mind if hook Axis 1.x up to the
continuum install in gbuild and optinally sync the jars in to
cvs.apache.org? I know there was some tech here when Axis was on cvs
but it doesn't seem to run anymore
-David
Re: Axis 1.X HEAD broken
Posted by Davanum Srinivas <da...@gmail.com>.
Actually i am not sure anymore what broke it...anyway here they are:
http://marc.theaimsgroup.com/?l=axis-dev&w=2&r=1&s=svn+commit+dug&q=b
On 2/7/06, David Blevins <da...@visi.com> wrote:
> On Jan 30, 2006, at 8:00 PM, David Blevins wrote:
>
> > On Jan 29, 2006, at 5:04 AM, Davanum Srinivas wrote:
> >
> >> Dug,
> >> Can u please fix the build break? I just got the latest HEAD and
> >> there
> >> are failures even in the funtional tests :( We can't reallly
> >> afford to
> >> do that. we need to get "ant clean all-tests" working again. I can
> >> confirm that all tests were passing before your changes got in.
> >>
> >> David,
> >> Can u please help?
> >>
> >
> > I'd be happy to help Doug with his changes if I can. Doug, what do
> > you need?
> >
>
> Dims, could you forward me the commit message pertaining to Doug's
> changes?
>
> -David
>
>
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/