Jean-Sebastien Delfino wrote:

Simon Nash wrote:
[snip]

a) runtimes of various kinds (SCA standalone, embedded within Tomcat,

etc)

[snip]

b) applications, containing only the code and other artifacts required for the application itself

[snip]

     Drop contribution jars into a directory which are then picked up
automatically and all contained composites are run

[snip]

 Webapp
      Construct a webapp
      Add dependencies (using maven?) for tuscany jars
      Configure web.xml to include the Tuscany filters

[snip]

I've been thinking about how to provide useful input here but I'm still a little puzzled as it mixes different topics in one thread. I've left a few snippets above to try to illustrate that, and there's more (about distro packaging for example) in other responses to the thread.

Here are the topics I think I've seen:

- Does the app developer need to know what Tuscany and dependency JARs are required by his SCA contributions?

- Under which circumstances does the app packager want to package the Tuscany and dependency JARs with the application artifacts.

- Which containers are we supporting and what kind of integration with them? Tomcat is just one example, Geronimo, JMS providers, embedded Jetty are others.

- Does the app developer need to know ahead of time which container integration his app is going to be deployed to. For example can I use the EJB, WS and JMS bindings together in one app, and which container integration is going to support that?

- What distro Zips are we building and what do they contain? just the runtime? samples or not? dependencies or not? are we building specialized distros for different use cases?

Would it make sense to spawn separate threads for these different topics?
>
With a big topic like this, dividing it into separate threads makes it
easier for people to follow and participate in the discussions.  The
split you are suggesting looks good to me.

  Simon



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to