axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Venkat Reddy <vred...@gmail.com>
Subject Re: [Axis2] Subtle yet serious issue
Date Tue, 13 Sep 2005 06:20:19 GMT
Actually the original issue reported by Jaya seems slightly different.
The xbean-2.0.0-beta1.jar has classes like SOAPMessageFactory and
other javax.xml.soap classes. SOAPMessageFactory has hard-coded
reference to Axis 1.x implementation for SOAPMessageFactoryImpl, and
thus, clashing with Axis2 SAAJ implementation. I'm not sure if these
classes are really required for XML beans functionality. Could someone
tell us if there is an already existing bug report related to this, or
is this as designed?

- venkat


On 9/12/05, Steve Loughran <stevel@apache.org> wrote:
> Steve Loughran wrote:
> > David Jencks wrote:
> >
> >> I'm not entirely sure what the problem you are running into is, but I
> >> recall some discussion on the xmlbeans list about something that
> >> sounds related to me.  I think that in xbean-2.0.0.jar the classes
> >> involved have been moved into an xmlbeans package from the
> >> javax.xml.soap package.  There are several other bug fixes in 2.0.0
> >> that made it usable in geronimo, so you may want to upgrade anyway.
> >>
> >> thanks
> >> david jencks
> >>
> >
> >
> >  I've just had a look and in xmlbeans-2.0.0 there are
> >
> > org.apache.xmlbeans
> > javax.xml.namespace.QName      (the java1.5 thingy?)
> > org.w3c.dom. DomConfiguration/DomStringList/TypeInfo/UserDataHandler
> >
> > repackage.*
> > schemaorg_apache_xmlbeans.*
> >
> > Now, jsr173_api.jar also includes javax.xml.namespace.QName, as does
> > xmlpublic.jar. I dont know why it is everywhere, but it is harmless, *as
> > long as nobody seals any of their JAR files*. The moment you try and
> > seal any of those jars, everything breaks. Which is why mixing in other
> > people's .class files is a bad thing, at least from the perspective of
> > those of us who do sign and seal our jars before deployment. I will have
> > to purge them all out.
> >
> 
> looks like this is a known defect:
> http://issues.apache.org/jira/browse/XMLBEANS-193
> 
> as an aside, this is why signing jars during dev is good practise. It
> verifies that your code can be signed, and so used in things like java
> web start.
>

Mime
View raw message