I'm working on an application that heavily uses XMLBeans to provide for a modular information repository system. I'm also considering how best to move into using OSGi.
Does anybody have any suggestions on how to make using XMLBeans with OSGi less painful? The thing I like most about XMLBeans is the built in type system, and how it can find schema types off the class path. However, once you use OSGi, this becomes problematic because the general best practice nowadays is to import specific packages that you know you'll need. This ends up conflicting with the auto-discovery nature of XMLBeans. You basically have to end up exporting the entire set of packages under schemaorg_apache_xmlbeans, and then using Require-Bundle to make sure that all possible schema elements can be discovered. Part of the problem is that I have a "common" bundle that has the base schema, from which I want to detect schema components (which describes elements which are extensions off the base schema) in other bundles. I'm really keen on keeping this sort of model because it prevents me from having to maintain a monolithic schema package (which works well for my particular application), but for the trouble mentioned above. Wesley --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org For additional commands, e-mail: dev-h...@xmlbeans.apache.org
