On Nov 29, 2007 5:39 PM, Simon Laws <[EMAIL PROTECTED]> wrote: > > > On Nov 28, 2007 11:25 PM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> > wrote: > > > Simon Laws wrote: > > > On Nov 28, 2007 4:11 PM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> > > > wrote: > > > > > >> Simon Laws wrote: > > >> [snip] > > >>> If I understand this correctly it looks like a reasonable way to > > extend > > >> the > > >>> Fruit&Veg scenario. In the current scenario I believe that the > > catalog > > >>> services, when run from the "cloud" module are running as part of > > the > > >>> distributed domain but rely on the embedded Jetty support . > > >> Correct > > >> > > >> So let me > > >>> confirm that you are suggesting three new things > > >>> > > >>> 1. creating implementation.ejb to support the Vegetable catalog > > >>> 2. choosing a different hosting option in order to deploy SCA > > >> applications > > >>> to a Geronimo server such that they take part in the SCA domain > > >>> 3. choosing a different hosting option in order to deploy SCA > > >> applications > > >>> to a Tomcat server such that they take part in the SCA domain > > >> Yes to 1 and 3. > > >> > > >> With (2), the vegetable catalog is an existing JEE application. So > > we're > > >> not going to deploy it to Geronimo as a new SCA > > contribution/application > > >> etc, it is already there running on Geronimo, and the point of the > > >> merger is to not have to rewrite it in SCA form, but instead model > > its > > >> presence in the domain with an SCA composite, then wire to it. > > > > > > > > > Ah. I see. Ok I like that. > > > > > > > Cool, since you're still busy with the service discovery thing, I > > thought I could help by putting together the model and XML support for > > implementation.ejb. It's available under sca/modules in > > implementation-ejb and implementation-ejb-xml. > > > > This will allow us to describe the existing catalog EJB like that: > > > > <composite name="veggie-catalog"> > > <component name="VeggieCatalog"> > > <implementation.ejb ejb-link="catalog-ejb.jar#CatalogEJB"/> > > </component> > > </composite> > > > > Some day in the future we'll probably want to have more code to > > introspect the EJB module and derive its services and bindings, but for > > now we should be able to build an interesting scenario with just the > > model and no more code than what I just checked in. The idea is to be > > able to develop the scenario and explore how to work with existing JEE > > apps and different containers in an SCA domain without piling more > > runtime code into Tuscany. > > > > For now, we just need to write the description of the service and > > binding by hand, something like that: > > > > <componentType> > > <service name="Catalog"> > > <interface.java interface="catalog.Catalog"/> > > </service> > > </componentType> > > > > and back to the composite: > > <composite name="veggie-catalog"> > > <component name="VeggieCatalog"> > > <implementation.ejb ejb-link="catalog-ejb.jar#CatalogEJB"/> > > <service name="Catalog"> > > <binding.ejb uri="CatalogEJB"/> > > </service> > > </component> > > </composite> > > > > I'll start to add a module to the store tutorial to host the composite > > and componentType. > > > > Let me know when you're done with the service discovery thing and want > > to jump in, there's a lot to do, including developing the EJB session > > bean itself, getting Geronimo in the picture etc. > > > > Hope this helps. > > -- > > Jean-Sebastien > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > Ok, sounds interesting. I'm going to start looking now. I still have > some domain things ongoing but they will be illuminated by the scenario > anyhow. The first thing I'm going to do is get the tutorial up and running > on my PC. It's at this point I admit that I haven't done that yet:-) The I'd > like to run up the scenario using the technology we have already, i.e. not > trying to do Geronimo integration in the first instance. I want to see what > the scenario looks like before working on any new features that may be > required. > > Regards > > Simon >
To get me going on this I've experimented with moving the FruitsCatalog out of the cloud and into a webapp. The web app relies on the evolving deep tomcat integration so starting the scenario requires the following steps.... Unzip the distribution/tomcat zip over your tomcat installation Set the tomcat/sca-contributions/tuscany.properties file to include node and domain URLs that are to your liking. Copy tutorial-catalog-jse.war to tomcat/webapps Run LaunchCloud Run LaunchStoreDistributed And you are set. It's all a bit fragile at the moment so lots of things to do, for example, the domain is a pain as it doesn't track when things go away so it can get confusing. However lets try and get the majority of the scenario working and we can then look back and see where the holes are. I haven't done anything with the EJB code you made yet other than look at it. I could start building the EJB for the vegetable catalog if you like. I'm assuming from what you say that we will deploy the EJB app to Geronimo standalone as if it had existed before we came along with SCA. Where will the composite that references this EJB be deployed to? I'm struggling with how to satisfy "The idea is to be able to develop the scenario and explore how to work with existing JEE apps and different containers in an SCA domain without piling more runtime code into Tuscany." as it seems that we will need to deploy the composite that references the EJB to Geronimo which, in turn, means bringing up the Geronimo/Tuscany integration code again. Simon
