cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Smyth (JIRA)" <j...@apache.org>
Subject [jira] Closed: (CXF-673) Use common prefix in all namespaces
Date Wed, 13 Jun 2007 21:23:26 GMT

     [ https://issues.apache.org/jira/browse/CXF-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrea Smyth closed CXF-673.
----------------------------

    Resolution: Invalid

> Use common prefix  in all namespaces
> ------------------------------------
>
>                 Key: CXF-673
>                 URL: https://issues.apache.org/jira/browse/CXF-673
>             Project: CXF
>          Issue Type: Task
>          Components: Configuration
>            Reporter: Andrea Smyth
>
> A prefix should be used in all namespaces defined in schema and wsdl files. 
> The type of prefix has yet to be agreed. At the minimum it should include a version independent
part like "schema" or "schemas" but ideally it version number or data should be included as
well, i.e. "schemas/2.0" or "schemas/200706" (assuming we'll get 2.0 Final out in June).
> To clarify: Whether or not code generated from types declared in these schemas should
use the prefix or a part thereof in the packagename.
> The impact of introducing a schema prefix in all schemas is significant, even when confined
to CXF:
> * Cfg files for tests and demos are affected.
> * pom files may need to pass additional arguments depending on how we proceed with the
prefix w.r.t package names.
> * If prefix is not dropped from the package name of generated classes, a lot of code
needs to be modified. At least in this case compilers/IDEs will quickly reveal what needs
to be changed. This is not the case for config files.
> Note: The main purpose of this task is to address problems of a) versioning and b) publication
(of the schemas/wsdl at their pubpic URIs).
> It has nothing or very little to do with CXF-613 and CXF-275.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message