[
https://issues.apache.org/jira/browse/XMLBEANS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493094
]
John Meagher commented on XMLBEANS-60:
--------------------------------------
This is useful when using schema extension. Some users only need to know about
the base types (if they're basically just pass throughs). The end consumers
and producers of the xml need to know about the specific types. It makes sense
to generate the code for the base type schemas only once then have a separate
code generation task for each specific derived type.
> New option for namespace excludes
> ---------------------------------
>
> Key: XMLBEANS-60
> URL: https://issues.apache.org/jira/browse/XMLBEANS-60
> Project: XMLBeans
> Issue Type: New Feature
> Components: Compiler
> Affects Versions: unspecified
> Reporter: Sal Campana
> Assigned To: Radu Preotiuc-Pietro
> Fix For: TBD
>
>
> SchemaCompiler should provide a way for certain namespaces to be excluded
> from compilation.
> As it stands today, regeneration of schemas is dependant on a combination of
> namespace and location.
> A typical scenario is that the same schema file is located in 2 different
> locations. The schema from the first location has been precompiled and
> included in the classpath. When compiling the schema from the second
> location SchemaCompile should be able to determine that these are the same
> file and not regenerate. Since the combination of namespace and location is
> being used to determine if a schema has been generated, and since the
> locations are different, the schema is generated twice and may cause
> classloader problems at runtime.
> We have 2 different suggestions on how this issue may be addressed:
> 1. Provide the ability to specify 1 or more schemaExclude namespace options.
> This is similar to how Axis' Wsdl2Java addresses this issue.
> and/or
> 2. Provide an option to always ignore the schema location (Global) when
> determining if the schema has already been generated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
