Thanks Radu, that clears things up.

Regards,
Vance

> -------- Original Message --------
> Subject: RE: Generic form of setCompileMdefNamespaces?
> From: Radu Preotiuc-Pietro <[EMAIL PROTECTED]>
> Date: Tue, June 03, 2008 5:22 pm
> To: user@xmlbeans.apache.org
> 
> You should take it to mean "It will be possible in the upcoming 2.4
> release" :-)
> 
> The reason we have been reluctant to add this feature until now is that
> it's very easy to use it indiscriminately and run into very
> hard-to-figure-out bugs. By forcing people to set the namespace, it's
> forcing them to look at the Schema and make sure that all conflicts are
> "acceptable"; XMLBeans doesn't attempt to make any check that the
> conflicting types are somehow "equivalent". That's the caveat...
> 
> Radu
> 
> On Tue, 2008-06-03 at 13:40 -0700, Vance Vagell wrote:
> > Should I take the silence since I asked this to mean "no, there is no way 
> > to do that without knowing all the namespaces beforehand"?  We'd like to 
> > shut off this schema policy enforcement altogether.
> > 
> > Thanks,
> > Vance
> > 
> > > -------- Original Message --------
> > > Subject: Generic form of setCompileMdefNamespaces?
> > > From: Vance Vagell <[EMAIL PROTECTED]>
> > > Date: Thu, May 29, 2008 4:13 pm
> > > To: user@xmlbeans.apache.org
> > > 
> > > Hi folks,
> > > 
> > > Is there a way to disable duplicate global type checking, akin to 
> > > XmlOptions.setCompileMdefNamespaces(), that DOES NOT require you to 
> > > specify a list of namespaces up-front?  
> > > 
> > > We can't easily identify that namespace list before compilation, so this 
> > > particular method signature is difficult (if not impossible) for us to 
> > > use.
> > > 
> > > Regards,
> > > Vance
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > ---------------------------------------------------------------------
> > 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]

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

Reply via email to