Hi Radu,

I see.  That explains exactly what I encountered - we were trying to
compile a new schema using xmlbean from ant, and couldn't figure out
why it failed to see the jar and kept compiling its own version of the
imported schema.

-- Jim

On Tue, Mar 18, 2008 at 5:22 PM, Radu Preotiuc-Pietro <[EMAIL PROTECTED]> wrote:
> It does say exactly that, if you are trying to use them at "runtime"
>  say.
>
>  But if you are trying to compile a new Schema with dependencies in jars
>  with an incompatible version number, there is something about that case
>  that makes it ignore that jar rather than report an error. I am not sure
>  if it is a bug or a feature (since you can still compile and use that
>  Schema) ...
>
>  Radu
>
>
>
>  On Tue, 2008-03-18 at 06:07 -0700, Jim the Standing Bear wrote:
>  > Thank you Radu.  I tend to get a little confused on backward
>  > compatibility and forward compatibility
>  >
>  >
>  > This is certainly a good thing to know.  The internal version numbers
>  > are fine as long as the dumpxsb tool can tell the difference, just
>  > like JDK, they don't need to correspond to the release version
>  > numbers.
>  >
>  > In the future, is there possibilities to let xmlbean tool to say
>  > something similar to JRE, that a bean jar is compiled with 24,
>  > expecting 23 blah blah rather than simply not being able to find it?
>  > It would've been much more informative and helpful to naive users like
>  > me.
>  >
>  >
>  >
>  > On Mon, Mar 17, 2008 at 6:13 PM, Radu Preotiuc-Pietro <[EMAIL PROTECTED]>
>  > wrote:
>  > > Actually, since you are interested in XMLBeans 2.2.0 and 2.3.0,
>  > those
>  > >  numbers are 23 for XMLBeans 2.2.0 and 24 for XMLBeans 2.3.0.
>  > >
>  > >  Radu
>  > >
>  > >
>  > >
>  > >  On Mon, 2008-03-17 at 15:08 -0700, Radu Preotiuc-Pietro wrote:
>  > >  > They are backwards compatible, but they are not "forwards"
>  > compatible.
>  > >  > What I mean by that is that a newer version of XmlBeans (say
>  > 2.3.0) can
>  > >  > read jars compiled with an older version (say 2.2.0). But
>  > XmlBeans 2.2.0
>  > >  > can't read jars compiled with XmlBeans 2.3.0. That would be a
>  > much
>  > >  > stronger requirement and few software offers this guarantee
>  > (think Java:
>  > >  > you can use JDK 1.5 to run classes compiled with JDK 1.4 but if
>  > you try
>  > >  > to run in JDK1.4 classes compiled with JDK1.5, you get an error).
>  > >  >
>  > >  > To answer your second question, there is a script in the bin
>  > directory
>  > >  > of the distribution "dumpxsb". If you do "dumpxsb xmltypes.jar",
>  > it will
>  > >  > spew a "Major version" and a "Minor version". Now those versions
>  > are not
>  > >  > equivalent to XMLBeans release versions but if you compare the
>  > version
>  > >  > numbers in jars generated with different versions of XMLBeans,
>  > you will
>  > >  > quickly see which jars are compatible and which aren't (again,
>  > this is
>  > >  > pretty much like Java's class version number).
>  > >  >
>  > >  > Hope this helps,
>  > >  > Radu
>  > >  >
>  > >  > On Mon, 2008-03-17 at 13:59 -0400, Jim the Standing Bear wrote:
>  > >  > > Hello,
>  > >  > >
>  > >  > > For the past week I have been struggling with importing a
>  > pre-compiled
>  > >  > > schema beans where xmlbean would fail to see the schema in the
>  > jar
>  > >  > > included in the classpath and kept generating its own version.
>  > >  > >
>  > >  > > Finally we made the discovery that the pre-compiled schema
>  > beans jar
>  > >  > > that I was trying to import was compiled using xmlbeans 2.3.0,
>  > but we
>  > >  > > are using v2.2.0.  So I guess they are not backwards
>  > compatible?
>  > >  > >
>  > >  > > If someone throws me a jar and says "here, use this", is there
>  > a way
>  > >  > > for me to tell which version of xmlbeans it used to compile?
>  > Thanks.
>  > >  > >
>  > >  > > -- Jim
>  > >  > >
>  > >  > >
>  > ---------------------------------------------------------------------
>  > >  > > To unsubscribe, e-mail: [EMAIL PROTECTED]
>  > >  > > For additional commands, e-mail: [EMAIL PROTECTED]
>  > >  > >
>  > >  >
>  > >  > Notice:  This email message, together with any attachments, may
>  > contain information  of  BEA Systems,  Inc.,  its subsidiaries  and
>  > affiliated entities,  that may be confidential,  proprietary,
>  > copyrighted  and/or legally privileged, and is intended solely for the
>  > use of the individual or entity named in this message. If you are not
>  > the intended recipient, and have received this message in error,
>  > please immediately return this by email and then delete it.
>  > >  >
>  > >  >
>  > ---------------------------------------------------------------------
>  > >  > To unsubscribe, e-mail: [EMAIL PROTECTED]
>  > >  > For additional commands, e-mail: [EMAIL PROTECTED]
>  > >  >
>  > >
>  > >  Notice:  This email message, together with any attachments, may
>  > contain information  of  BEA Systems,  Inc.,  its subsidiaries  and
>  > affiliated entities,  that may be confidential,  proprietary,
>  > copyrighted  and/or legally privileged, and is intended solely for the
>  > use of the individual or entity named in this message. If you are not
>  > the intended recipient, and have received this message in error,
>  > please immediately return this by email and then delete it.
>  > >
>  > >
>  > ---------------------------------------------------------------------
>  > >  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  > >  For additional commands, e-mail: [EMAIL PROTECTED]
>  > >
>  > >
>  >
>  >
>  >
>  > --
>  > --------------------------------------
>  > Standing Bear Has Spoken
>  > --------------------------------------
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: [EMAIL PROTECTED]
>  > For additional commands, e-mail: [EMAIL PROTECTED]
>  >
>  >
>  >
>
>  Notice:  This email message, together with any attachments, may contain 
> information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated 
> entities,  that may be confidential,  proprietary,  copyrighted  and/or 
> legally privileged, and is intended solely for the use of the individual or 
> entity named in this message. If you are not the intended recipient, and have 
> received this message in error, please immediately return this by email and 
> then delete it.
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
--------------------------------------
Standing Bear Has Spoken
--------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to