geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: xmlbeans usage in Geronimo -- upgrading to xbeans 2.0?
Date Fri, 08 Jul 2005 18:08:02 GMT
I've been attempting to maintain a port to xmlbeans 2 for about 6 
months and have been getting very tired of objections to installing it. 
  I'm now afraid that this has resulted in xmlbeans 2 being released 
with some bugs that will make using it difficult.

Some problems have crept in in my latest update, and I haven't been 
able to figure out how to solve them.  The symptoms I see are that I 
get different binary xsb files generated depending on whether I build 
one module at a time or all at once with a multiproject build.  
Depending on which generated classes I get classes from imported 
namespaces work, or don't.

I'm not sure how to proceed.  I could post a patch to a jira issue, or 
create a geronimo branch.  However there are openejb changes as well, 
and dealing with a cvs branch seems awfully painful.

The inclusion of xmlbeans in the root classloader should be 
unnecessary.  IIRC it was needed because we didnt' have a single 
version of the QName class: now that we do it should no longer be 

The intention is that xmlbeans and xmlbeans generated classes should 
only be used in  the builders, and not needed in the runtime system.  
If this is no longer the case, we have some work to do:-)  If we can 
maintain this separation there should be no problem in using any 
version of xmlbeans in an application, since the builder classloaders 
using xmlbeans and the application classloaders using xmlbeans would be 

If you want to help sort this out, your work would be extremely welcome.

david jencks

On Jul 8, 2005, at 10:39 AM, Kenneth Tam wrote:

> Hi folks,
> I'm exploring the ability to use various versions of xmlbeans with
> Geronimo.  In particular, I'm interested in being able to deploy a
> J2EE app/module (say, a WAR) that depends on a specific version of
> xmlbeans (which it provides, say in WEB-INF/lib).  Looking at this one
> use case leads me to a number of questions..
> I see v1 of xbeans being used in what appears to me (without deeper
> knowledge) to be the system classloader of the server.  It seems the
> natural usages of xbeans in Geronimo would be for general processing
> of xml configuration files (J2EE DDs, Geronimo-specific config, etc),
> as well as for xml processing in the J2EE webservices stack.
> Has there been provision made in Geronimo's usage of xbeans for the
> concurrent usage of multiple versions?  I see
>, which suggests that
> there has been some concern about how xbeans is classloaded, but that
> particular JIRA issue is very narrow.
> Is anyone already exploring upgrading the version of xbeans used by
> Geronimo to v2?  I'm beginning to play with it, but context would be
> much appreciated.  For starters, it appears that there is some CGLIB
> munging of xbeans compiled schema classes (this is based on a stack
> trace I saw simply by replacing xbeans v1 with v2 at runtime) -- that
> seems pretty scary.  The xbeans folks I've talked to tell me that the
> compat level they were shooting for is source-level, ie they expect
> clients to recompile their schemas using the new version of xbeans..
> I'm working on that now.
> thanks,
> ken

View raw message