[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlbeans-dev
Subject:    [jira] Commented: (XMLBEANS-60) New option for namespace excludes
From:       "Radu Preotiuc-Pietro (JIRA)" <xmlbeans-dev () xml ! apache ! org>
Date:       2005-01-21 1:22:17
Message-ID: 857828302.1106270537606.JavaMail.jira () ajax ! apache ! org
[Download RAW message or body]

     [ http://issues.apache.org/jira/browse/XMLBEANS-60?page=comments#action_57867 ]
     
Radu Preotiuc-Pietro commented on XMLBEANS-60:
----------------------------------------------

Sal, can you provide an example that you've run into? I see code in StscImporter:357 \
that skips downloading a file whose namespace is already "known" even if the location \
is different, so I'd like to understand your problem in more detail. Thanks.


> New option for namespace excludes
> ---------------------------------
> 
> Key: XMLBEANS-60
> URL: http://issues.apache.org/jira/browse/XMLBEANS-60
> Project: XMLBeans
> Type: New Feature
> Components: Compiler
> Versions: unspecified
> Reporter: Sal Campana
> Assignee: Radu Preotiuc-Pietro

> 
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]