Thanks again,
By including all of the Tuscany jars do you mean the runtime jars or the
component jars (i.e. the web app and components need to be packaged
together)
Chris
Hi Chris
Some more thoughts and some comments in line..
A service is defined by a contract/interface and collects together a set of
related operations. A service may provide an endpoint through which remote
clients can access it over the network
A component provides the implementation for one or
Hi,
Thanks again for the reply. I think we are nearly reaching a point of
agreement on this; however I am still unsure of how some of the
intricacies will work.
I can see how the samples are working, as Tuscany has automatic access
to the files required as they are included within the same
Simon,
Thanks for the response again.
I understand a little better now; however some parts of it still leave
me a little stumped. How these physical units would be packaged and
moved around.
If I have a webapp with JSP, Servlets and the other usual bits and bobs.
This would be packaged in it's
On Fri, Jun 6, 2008 at 3:51 PM, Simon Laws [EMAIL PROTECTED]
wrote:
On Fri, Jun 6, 2008 at 3:15 PM, Miles, Chris
[EMAIL PROTECTED]
wrote:
Hi, thanks very much for a response. I will try explain this better.
In a traditional J2EE application like many I have worked on in the past
the