Hi,
I realized that we have an established pattern for the code of
implementation and binding extensions. We also use "copy/paste" to create
new modules for implementation/binding extensions. I think it would be
useful to develop two maven archetypes that can be used to generate the
skeleton modules for implementation/binding extensions. Developers can just
provide the name of the implementation/binding. The java and resource files
will be generated in a maven module. For example, the
sample-implementation-pojo will contain the following files:
*
META-INF/services/org.apache.tuscany.sca.contribution.processor.StAXArtifactProcessor
*
META-INF/services/org.apache.tuscany.sca.contribution.processor.ValidationSchema
*
META-INF/services/org.apache.tuscany.sca.provider.ImplementationProviderFactory
* META-INF/services/pojo.POJOImplementationFactory
# sample-implementation-pojo.xsd
# pojo/POJOImplementation.java
* pojo/POJOImplementationFactory.java
* pojo/impl/POJOImplementationFactoryImpl.java
# pojo/impl/POJOImplementationImpl.java
# pojo/impl/POJOImplementationProcessor.java
# pojo/provider/POJOImplementationProvider.java
# pojo/provider/POJOImplementationInvoker.java
# pojo/provider/POJOImplementationProviderFactory.java
The files marked with * will be completely generated while those with # will
have skeleton code produced.
Thoughts? Want to help?
Thanks,
Raymond
