Hi Luca, In other terms, that piece of documentation is a warning. Since XMLBeans keeps all of the xml infoset information about the schema type system in the .xsb files, this is simply a warning to let you know there may be conflicts as multiple similar instance of the xsb file might exist on the classpath. You deal with the same thing when you have two classes with the same package and name on the classpath. The default way java handles this is to use the first matching class it finds. This behavior can be manipulated using classloaders. Hope this helps, -jacobd
On Dec 10, 2007 9:08 AM, Luca Santaniello <[EMAIL PROTECTED]> wrote: > Perfect, now run. > > Can I generate 2 jar from 2 xsd with targetNamespace = > http://www.opengis.org/wfs > > I have read on documentation this alert: > > Note: XMLBeans doesn't support using two or more sets of java classes (in > different packages) mapped to schema types/elements that have the same > names > and target namespaces, using all in the same class loader. Depending on > the > direction you are using for the java classes to schema types mapping, some > features might not work correctly. This is because even though the package > names for the java classes are different, the schema location for the > schema > metadata (.xsb files) is the same and contains the corresponding > implementing java class, so the JVM will always pick up the first on the > classpath. This can be avoided if multiple class loaders are used. > > I don't understand > > > > -- > Email.it, the professional e-mail, gratis per te: http://www.email.it/f > > Sponsor: > Dimagrire in 30 giorni: Garanzia soddisfatti o rimborsati > * > * > Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=7108&d=10-12 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
