Hi,
As decided in the discussion with Carbon Team, I have implemented two
archetypes.
1. carbon-bundle-archetype
This is an archetype for a generic OSGi bundle which does not include
anything Carbon specific.
2. carbon-component-archetype
This is an archetype for a carbon component with a
On Mon, Nov 16, 2015 at 9:22 PM, Harsha Thirimanna wrote:
> We can add a sample service holder class also as a template in archetype
> to hold OSGi services that is consumed by this component. We may need to
> give a commented out code to show that usage and then anyone can
We can add a sample service holder class also as a template in
archetype to hold
OSGi services that is consumed by this component. We may need to give a
commented out code to show that usage and then anyone can follow that
pattern. WDYT ?
*Harsha Thirimanna*
Senior Software Engineer; WSO2,
@Maninda This is basically a template, as you said which can be used to
create a carbon component easily.
@Harsha At the moment it has been decided to implement
1. a bundle archetype which is for generating a generic OSGi bundle
and
2. a Carbon Component archetype which includes a service
Can you explain how does this help us on development. Is it useful for
creating a new carbon compoment easily? Or is this a new standard way of
generating carbon 5 components.
Thanks.
*Maninda Edirisooriya*
Senior Software Engineer
*WSO2, Inc.*lean.enterprise.middleware.
*Blog* :