You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by xm...@xml.apache.org on 2004/09/14 21:56:40 UTC

[jira] Created: (XMLBEANS-60) New option for namespace excludes

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XMLBEANS-60

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XMLBEANS-60
    Summary: New option for namespace excludes
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: XMLBeans
 Components: 
             Compiler
   Versions:
             unspecified

   Assignee: 
   Reporter: Sal Campana

    Created: Tue, 14 Sep 2004 12:55 PM
    Updated: Tue, 14 Sep 2004 12:55 PM

Description:
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.



---------------------------------------------------------------------
JIRA INFORMATION:
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


[jira] Updated: (XMLBEANS-60) New option for namespace excludes

Posted by "Radu Preotiuc-Pietro (JIRA)" <xm...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XMLBEANS-60?page=all ]

Radu Preotiuc-Pietro updated XMLBEANS-60:
-----------------------------------------

    Fix Version: TBD

Postponing for the next version.

> 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
>      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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, 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


[jira] Commented: (XMLBEANS-60) New option for namespace excludes

Posted by "John Meagher (JIRA)" <xm...@xml.apache.org>.
    [ 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[jira] Commented: (XMLBEANS-60) New option for namespace excludes

Posted by "Radu Preotiuc-Pietro (JIRA)" <xm...@xml.apache.org>.
     [ 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