Hi, from my point of view (SA developer), it's ok to have lesser archetypes to maintain (1: no consumer/provider sub-archetypes) at the cost of having to uncomment the consumer/provider elements in the xbean.xml before calling mvn.
That's because I use a script to generate a SA skeleton and then do the edits anyway on the xbean.xml. Maybe those who'd like more automation (a mvn or eclipse plugin) would prefer to have the sub-archetipes. Regards, Corrado Campisano 2010/8/13 Jean-Baptiste Onofré <j...@nanthrax.net> > Hi all, > > After a first archetype release vote, some discussions have involved on > IRC. > > There is two points that have to be clarified: > > 1/ Archetypes and components > > Currently, we have one archetype per endpoint type. For example, we have > one archetype to create a HTTP Consumer endpoint, one archetype to create a > HTTP Provider endpoint, etc. > I have homogenized all archetype in this way, splitting some like > servicemix-mail-service-unit in servicemix-mail-poller-service-unit and > servicemix-mail-sender-service-unit. > Using this solution: > - we have important number of archetypes (it's maybe not simple for user to > pick up the right one) > - each archetype provides a simple xbean corresponding exactly of the > expected behavior (for example, the user will have a HTTP consumer endpoint > and only this using servicemix-http-consumer-service-unit). > > We have another way to see archetypes: one archetype per component. > In that case, we have only servicemix-http-service-unit. > The xbean.xml contains all possible endpoints configuration. > > 2/ XBean content and documentation > > The archetypes provide a sample xbean with the endpoint configuration. > > A comment should be present just before the endpoint snippet: > > <!-- Endpoint description --> > <component:endpoint ... /> > > This comment could contain: > - the URL of the component wiki page > - a brief documentation on the endpoint: what the endpoint does, what the > endpoint attributes. > > Another question is: should we have an endpoint sample or endpoints > commented to let the user uncomment what he wants. > > For example, we can have: > > <http:consumer .../> > <http:provider .../> > > or > > <!-- > <http:consumer .../> > --> > <!-- > <http:provider .../> > --> > > and let the user uncomment and change the endpoint matching what he needs. > > Any comment is welcome. > > FYI, I will want some feedback to this discussion before resuming my work > on archetypes. > > Regards > JB >
