Hello Charles, if you need help in testing the archetypes please send me a message.
Regards, Heinz On Wed, Dec 2, 2009 at 09:39, Charles Moulliard <[email protected]> wrote: > Are you interested by my suggestion ? If this is the case, where can I put > these archetypes under servicemix svn ? > > I propose in a first step to create the following archetypes for SMX4: > > - osgi-features = maven project + xml features file > - osgi-camel-spring > - osgi-camel-blueprint (when camel-blueprint will be ready) > - osgi-pojo-spring > - osgi-servicemix-project = parent pom containing list of modules to be > installed in maven repo + dependencies definition + maven-bundle-plugin > definition > - osgi-config-spring = maven project + src/main/resources/META-INF/spring > (could be used to place spring activemq.xml config file, ....) > > For JBI, clarification is requested as normally a JBI project is packaged as > a collection of jar/zip in sa zip file + jbi/config.xml > > Regards, > > Charles Moulliard > Senior Enterprise Architect > Apache Camel Committer > > ***************************** > blog : http://cmoulliard.blogspot.com > twitter : http://twitter.com/cmoulliard > Linkedlin : http://www.linkedin.com/in/charlesmoulliard > > Apache Camel Group : > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm > > > On Tue, Dec 1, 2009 at 2:33 PM, Charles Moulliard <[email protected]>wrote: > >> >> >> On Tue, Dec 1, 2009 at 1:39 PM, Gert Vanthienen <[email protected] >> > wrote: >> >>> Charles, >>> >>> For a JBI application, we have two ways of deploying that. >>> >>> The first way is using JBI packaging. You can just take your SU/SA >>> that's being created with the existing archetypes and put that in the >>> deploy folder. There's no special configuration required for >>> ServiceMix 4, our deployer understands JBI packaging and will create a >>> pseudo-bundle for the SA and set up JBI compliant classloaders for the >>> SU. So for the JBI packaging, we can just reuse the existing >>> archetypes and there's no additional work required. >>> >>> The second way is using OSGi packaging. In this scenario, the entire >>> JBI configuration is put in a single XML file and that requires the >>> EndpointExporter bean to be configured in the XML file to register the >>> beans as endpoints in the NMR. The XML file can be either deployed >>> directly or be embedded in a bundle (using Spring-DM). I don't think >>> there's an archetype around for creating this type of bundle yet. >>> >>> We don't have an archetype for the plain-pojo(-with-blueprint?) bundle >>> either. For the Camel OSGi archetype, I think we can safely reuse >>> Camel's archetype there. Does this answer the question? >>> >> >> >> Yes >> >>> >>> For the plain XML style of deployment, it doesn't really make a lot of >>> sense to look at creating an archetype for that. Actually, I'm >>> starting to wonder if we shouldn't consider building a dev: shell >>> inside Karaf, where we can implement some help for these kind of >>> simple deployments (e.g. similar to what happens when you do an >>> activemq:create-broker -- just create a sample XML file to start >>> from)? >>> >> >> What you propose is a must for administrator in charge to deploy the >> project. At the beginning, we start from a java project or a java project >> using maven as build tool. In this case, it makes sense to have an archetype >> to create bundles that we will deploy on Apache Felix Karaf pr Apache >> ServiceMix 4 / Fuse next. >> >> The archetype with options like specification type (jbi, camel) and Service >> container type (spring, blueprint, ..) could generate by example the maven >> project structure like this : >> >> pom.xml (dependencies adapted according to option selected, will contain >> maven-bundle-plugin, ...) >> src/main/java >> src/main/resources/META-INF/MANIFEST file (generated by >> maven-bundle-plugin, ...) >> src/main/resources/META-INF/spring/camel-context.xml (for camel and spring) >> src/main/resources/META-INF/OSGI-INF/blueprint/camel-context.xml (for camel >> and blueprint) >> src/main/resources/META-INF/jbi/jbi.xml (for JBI SA assembly) >> >> Question : Can we deploy a JBI project where the SU=individual bundles and >> SA=bundle containing the full XML config file ? >> >> Regards, >> >> Charles >> >> >> >> >>> Regards, >>> >>> Gert Vanthienen >>> ------------------------ >>> Open Source SOA: http://fusesource.com >>> Blog: http://gertvanthienen.blogspot.com/ >>> >>> >>> >>> 2009/12/1 Charles Moulliard <[email protected]>: >>> > Hi Gert, >>> > >>> > I will work on that today. Concerning JBI spec, I have questions that I >>> > would like to discuss before to start something about maven >>> plugin/smx-arch. >>> > >>> > >>> > To create bundles top of OSGI platform, we can start from a maven >>> project >>> > where we use the felix/bnd maven plugin (maven-bundle-plugin), use ops4j >>> > plugin to create a project structure, use Spring Dynamic Modules Maven >>> > Archetype, ... >>> > All these plugins are based on the assumption that we will deploy a >>> project >>> > as a collection of bundles. Regarding to JBI where we have a collection >>> of >>> > Service Units embedded in a Service Assembly, this assumption is >>> truncated >>> > as we need to build a SA. >>> > >>> > Remark : I have had a look to the example (generated using >>> jbi-maven-plugin) >>> > bridge provided in the distro SMX 4.1 where I see that : >>> > - MANIFEST file of each SU is not OSGI fied >>> > - SA = zip file containing each SU zip >>> > >>> > Question : What will be the strategy of JBI project deployment top of a >>> OSGI >>> > server ? >>> > >>> > 1) Like now = example of bridge >>> > 2) Each SU becomes an individual OSGI bundle . This means that the >>> > JBI-maven-plugin will be modified to generate the MANIFEST file required >>> by >>> > OSGI (using maven-bundle-plugin) including classes exported / imported. >>> The >>> > SA will be an empty jar file containing a MANIFEST file with the list of >>> > packages to be imported/exported (???) and the jbi.xml file. How this >>> file >>> > will be loaded ??? >>> > >>> > Regards, >>> > >>> > Charles Moulliard >>> > Senior Enterprise Architect >>> > Apache Camel Committer >>> > >>> > ***************************** >>> > blog : http://cmoulliard.blogspot.com >>> > twitter : http://twitter.com/cmoulliard >>> > Linkedlin : http://www.linkedin.com/in/charlesmoulliard >>> > >>> > Apache Camel Group : >>> > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm >>> > >>> > >>> > On Mon, Nov 30, 2009 at 7:44 PM, Gert Vanthienen >>> > <[email protected]>wrote: >>> > >>> >> Heinz, Charles, >>> >> >>> >> This script doesn't yet exist for ServiceMix 4. Are you interested in >>> >> having such a script in ServiceMix 4 as well or do you have >>> >> another/better suggestion to making working with the archetypes a bit >>> >> easier? We'd welcome any kind of user feedback on this topic... >>> >> >>> >> Regards, >>> >> >>> >> Gert Vanthienen >>> >> ------------------------ >>> >> Open Source SOA: http://fusesource.com >>> >> Blog: http://gertvanthienen.blogspot.com/ >>> >> >>> >> >>> >> >>> >> 2009/11/30 Heinz Drews <[email protected]>: >>> >> > That was my assumption also, the sample pom.xml in the document >>> refers >>> >> > to a Servicemix 3.3 version. >>> >> > >>> >> > The use of Maven is the weak spot in the documentation, not even the >>> >> > examples help. >>> >> > >>> >> > Regards, >>> >> > Heinz >>> >> > >>> >> > On Mon, Nov 30, 2009 at 17:30, Charles Moulliard < >>> [email protected]> >>> >> wrote: >>> >> >> For me, this is an error in the fuse documentation. This .bat, .sh >>> >> script is >>> >> >> present in SMX3 and not in SM4. >>> >> >> >>> >> >> Charles Moulliard >>> >> >> Senior Enterprise Architect >>> >> >> Apache Camel Committer >>> >> >> >>> >> >> ***************************** >>> >> >> blog : http://cmoulliard.blogspot.com >>> >> >> twitter : http://twitter.com/cmoulliard >>> >> >> Linkedlin : http://www.linkedin.com/in/charlesmoulliard >>> >> >> >>> >> >> Apache Camel Group : >>> >> >> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm >>> >> >> >>> >> >> >>> >> >> On Mon, Nov 30, 2009 at 5:28 PM, Heinz Drews <[email protected] >>> > >>> >> wrote: >>> >> >> >>> >> >>> Hello, >>> >> >>> >>> >> >>> I also have seen the reference to smx-arch in the documentation but >>> I >>> >> >>> cannot find it in the Fuse-Distribution. >>> >> >>> >>> >> >>> >>> >> >>> Regards, >>> >> >>> Heinz >>> >> >>> >>> >> >>> On Mon, Nov 30, 2009 at 17:07, Charles Moulliard < >>> [email protected] >>> >> > >>> >> >>> wrote: >>> >> >>> > The fuse documentation speaks about a smx-arch command for SMX4 >>> ( >>> >> >>> > http://fusesource.com/docs/esb/4.1/jbi/index.html) >>> >> >>> > >>> >> >>> > Seeding a project using a Maven artifact >>> >> >>> > >>> >> >>> > FUSE ESB provides Maven artifacts for a number of service unit >>> types. >>> >> You >>> >> >>> > can use them to seed a project with the *smx-arch* command. As >>> shown >>> >> in >>> >> >>> > Example 7.3< >>> >> >>> >>> >> >>> http://fusesource.com/docs/esb/4.1/jbi/ESBMavenSU.html#ESBMavenSUArchCmd >>> >, >>> >> >>> > the *smx-arch* command takes three arguments. The groupId value >>> and >>> >> the >>> >> >>> > artifactId values correspond to the project's group ID and >>> artifact >>> >> ID. >>> >> >>> > >>> >> >>> > >>> >> >>> > What's that ? >>> >> >>> > >>> >> >>> > >>> >> >>> > Regards, >>> >> >>> > >>> >> >>> > Charles Moulliard >>> >> >>> > Senior Enterprise Architect >>> >> >>> > Apache Camel Committer >>> >> >>> > >>> >> >>> > ***************************** >>> >> >>> > blog : http://cmoulliard.blogspot.com >>> >> >>> > twitter : http://twitter.com/cmoulliard >>> >> >>> > Linkedlin : http://www.linkedin.com/in/charlesmoulliard >>> >> >>> > >>> >> >>> > Apache Camel Group : >>> >> >>> > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm >>> >> >>> > >>> >> >>> > >>> >> >>> > On Mon, Nov 30, 2009 at 5:01 PM, Jean-Baptiste Onofré < >>> >> [email protected] >>> >> >>> >wrote: >>> >> >>> > >>> >> >>> >> Hi Charles, >>> >> >>> >> >>> >> >>> >> AFAIK, there is not archetype for this. However, I think it can >>> be a >>> >> >>> good >>> >> >>> >> idea. >>> >> >>> >> >>> >> >>> >> Regards >>> >> >>> >> JB >>> >> >>> >> -----Original Message----- >>> >> >>> >> From: Charles Moulliard <[email protected]> >>> >> >>> >> Date: Mon, 30 Nov 2009 16:56:57 >>> >> >>> >> To: <[email protected]> >>> >> >>> >> Subject: maven archetype Service Unit for SMX4 >>> >> >>> >> >>> >> >>> >> Hi, >>> >> >>> >> >>> >> >>> >> Is there a maven archetype that we can use to create a JBI maven >>> >> project >>> >> >>> >> for >>> >> >>> >> SMX4 like we have for SMX3 and described here ( >>> >> >>> >> >>> >> >>> >>> >> >>> http://servicemix.apache.org/22-beginner-creating-our-first-su-module.html >>> >> >>> >> ) >>> >> >>> >> ? >>> >> >>> >> >>> >> >>> >> Regards, >>> >> >>> >> >>> >> >>> >> Charles Moulliard >>> >> >>> >> Senior Enterprise Architect >>> >> >>> >> Apache Camel Committer >>> >> >>> >> >>> >> >>> >> ***************************** >>> >> >>> >> blog : http://cmoulliard.blogspot.com >>> >> >>> >> twitter : http://twitter.com/cmoulliard >>> >> >>> >> Linkedlin : http://www.linkedin.com/in/charlesmoulliard >>> >> >>> >> >>> >> >>> >> Apache Camel Group : >>> >> >>> >> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> > >>> >> >>> >>> >> >> >>> >> > >>> >> >>> > >>> >> >> >
