Generated schema-component: differentiate naming of generated schema from component artifactId

*Description*
Using values hd.lab.soitk:schema1 for groupId:artifactId the generated 
component has a pom.xml with:

  <groupId>hd.lab.soitk</groupId>
  <artifactId>schema1-schemas</artifactId>

and schemas in:

  resources\schemas\hd\lab\soitk\schema1\schema1.xsd
  resources\schemas\hd\lab\soitk\schema1\schema1Service.wsdl

with schema-namespaces and java-package-mappings as:

  urn:hd.lab.soitk.schema1.schema1.wsdl:v1
     =hd.lab.soitk.schema1.schema1.wsdl.v1
  urn:hd.lab.soitk.schema1.schema1.schema:v1
     =hd.lab.soitk.schema1.schema1.schema.v1

*Suggested changes*
1. Name the generated schema different from artifactId.
For example: if artifactId is _schema1_ the schema could be named 
_schema1DefaultSchema_ and then have namespace to java-mappings like:

  urn:hd.lab.soitk.schema1.schema1defaultschema.wsdl:v1
     =hd.lab.soitk.schema1.schema1defaultschema.wsdl.v1
  urn:hd.lab.soitk.schema1.schema1defaultschema.schema:v1
     =hd.lab.soitk.schema1.schema1defaultschema.schema.v1

Even better: allow explicit naming of schema in generation-wizard.

2. Use a filepath for schemas where both schema name AND artifactId is parts of 
the path (this seems to be missing now?).
For example:

the current paths:

  resources\schemas\hd\lab\soitk\schema1\schema1.xsd
  resources\schemas\hd\lab\soitk\schema1\schema1Service.wsdl

would then be:

  resources\schemas\hd\lab\soitk\schema1\schema1defaultschema\schema1defaultschema.xsd
  resources\schemas\hd\lab\soitk\schema1\schema1defaultschema\schema1defaultschemaService.wsdl

Original issue reported on code.google.com by hakan.d...@gmail.com on 22 Oct 2010 at 7:45

cloudtrends / soi-toolkit

Generated schema-component: differentiate naming of generated schema from component artifactId #25