For your revised item #1, there is a cmd line tool called sfactor that
might get you what you want.
Here's the usage:
xmlbeans/trunk/bin>sfactor
Refactors a directory of XSD files to remove name conflicts.
Usage: sfactor [-import common.xsd] [-out outputdir] inputdir
-import common.xsd - The XSD file to contain redundant
definitions for importing.
-out outputdir - The directory into which to place XSD
files resulting from refactoring,
plus a commonly imported common.xsd.
inputdir - The directory containing the XSD files with
redundant definitions.
-license - Print license information.
Best of luck,
-Jacob Danner
On 5/17/07, Radu Preotiuc-Pietro <[EMAIL PROTECTED]> wrote:
1) No. There is no algorithm defined for doing a semantic diff between two
Schemas, so we didn't spend the time to implement anything in this area. (as
you have seen yourself, you don't even need a diff after all, but something
different) But using the SchemaType API you have all you need to implement
some custom logic appropriate to your use-case.
2) Yes, XmlBeans fully supports loading and manipulating invalid Schema
documents.
Radu
________________________________
From: Ajay Aggarwal [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 17, 2007 8:12 AM
To: [email protected]
Subject: RE: questions on XMLBeans
Let me further qualify point number 1 below. What I really need to do is
compare the two schemas and come up with a 3rd one which contains only the
common definitions.
________________________________
From: Ajay Aggarwal [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 17, 2007 11:05 AM
To: [email protected]
Subject: questions on XMLBeans
I am evaluating XMLBeans for one of the projects. I have a few questions:
1) Does XML Beans provide any utility/hooks to compare two different
schema files?
2) If my XML document deviates slightly from the underlying schema,
can I still load it using XMLBeans… some sort of best effort XML to Java
mapping?
Thanks.
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]
