On Mon, Jan 26, 2009 at 12:20 PM, ant elder <[email protected]> wrote:

> The current Tuscany Webapp support that we have in 1.x is described on the
> wiki page at [1], I'd like to start bringing this up in the 2.x code base so
> we need to decide what we want to support. Right now i'm focusing on similar
> support as we have in 1.x where the webapp is a container for a Tuscany
> runtime and not so much on the webapp as an SCA contribution which requires
> deep integration into the servlet container (which we're working on
> separately with the Tuscany-Geronimo plugin work).
>
> So in 1.x we support three ways of defining the composites included in the
> webapp:
>
> - using a META-INF/sca-contributions.xml
> - by including deployable composite files within a folder named
> META-INF/sca-deployables
> - by using an WEB-INF/web.composite application composite
>
> How about dropping those first two and only supporting web.composite in
> 2.x?
>
>    ...ant
>
> [1]
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Web+Applications
>

I'd be happy to let 2 go, i.e META-INF/sca-deployables, as this is a Tuscany
extension. Why would we get rid of support for
META-INF/sca-contributions.xml?

Simon

Reply via email to