Re: Getting service manually through servlet

2007-07-16 Thread Jean-Sebastien Delfino
ant elder wrote: I think right now you have to use a META-INF/sca-contribution.xml file to point to your .composite files, you can see an example in one of the Tuscany samples, eg: https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/calculator-webapp/src/main/webapp/META-INF/.

Re: Getting service manually through servlet

2007-07-16 Thread ant elder
On 7/17/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: ant elder wrote: I think right now you have to use a META-INF/sca-contribution.xml file to point to your .composite files, you can see an example in one of the Tuscany samples, eg:

Re: Getting service manually through servlet

2007-07-13 Thread Robert Young
Ah yes, I hadn't spotted the sca-contributions.xml file in the sample. It working now, just my other trouble of how to get hold of the servlet context in the service now. Cheers Rob On 7/12/07, Luciano Resende [EMAIL PROTECTED] wrote: I remember having similar discussions when we discussed

Re: Getting service manually through servlet

2007-07-12 Thread Luciano Resende
So, two questions : 1- Are you registering the tuscany servlet context listener to your web.xml file ? 2 - How are you contributing your contributions ? You might be having problems finding the root of the contribution or the deployables, please take a look at this [1] as a reference. [1] -

Re: Getting service manually through servlet

2007-07-12 Thread ant elder
I think right now you have to use a META-INF/sca-contribution.xml file to point to your .composite files, you can see an example in one of the Tuscany samples, eg: https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/calculator-webapp/src/main/webapp/META-INF/. An alternative may

Re: Getting service manually through servlet

2007-07-12 Thread Luciano Resende
I remember having similar discussions when we discussed web-app story. One issue I see here, when adding all composites as deployable, is that, in some phases of the development life-cycle you might have bad composites, and that would not cause any issues to your app, as these bad composites are