On Nov 9, 2006, at 2:59 PM, Rick wrote:
I'm not convinced that DAS really requires it but I'll let them be
the judge of that. Just from what I remembered I didn't see the
need so I questioned it. I just think when possible it best to
integrate at the highest level of the stack that suits
I'm not convinced that DAS really requires it but I'll let them be the judge of
that. Just from what I remembered I didn't see the need so I questioned it. I
just think when possible it best to integrate at the highest level of the stack
that suits your needs.
Jim, you lost me and peeked my int
On Nov 9, 2006, at 11:34 AM, cr22rc wrote:
My understanding is you would need to implement classes from
tuscany-spi to implement your container. This is surely specific
to Tuscany. The work that was started by Luciano was as I
understood it a Pojo that was an SCA component. That should b
My understanding is you would need to implement classes from tuscany-spi to
implement your container. This is surely specific to Tuscany. The work that
was started by Luciano was as I understood it a Pojo that was an SCA component.
That should be able to work in any other SCA implementation.
T
On 11/9/06, Luciano Resende <[EMAIL PROTECTED]> wrote:
Hi Guys
Amita have started work to expose DAS as an SCA container, and we are
looking what would be the best way to get collaboration on continuing the
task. One of the ways we were thinking was to clean-up what is available
today and ge
I think the best possible solution would be what we have discussed as
"Declarative DAS", where we would extend the programming model to expose
services that interact with a persistent layer in a declarative fashion
hiding the implementation details from the service developer, you can see
some disc
I absolutely want the best possible solution to integration and this
discussion is helping quit a bit. I may misunderstand but, if we
develop implementation.das and an associated container, wont this be
usable in another SCA implementation?
--
Kevin
Rick wrote:
I quickly skimmed the threads
I quickly skimmed the threads on this and I didn't pick up what the advantage
was it making this a "container". The only thing I seen was a tighter
integration between DAS and SCA. But as I understand it me this is really a
tighter integration between DAS and Tuscany implementation of SCA. In
Hi Luciano,
Is the DAS container a component or binding? If it is in the former,
I would think it should go under container/container.das, otherwise
binding/binding/das/
Also, the dependency in the module should be against a version of DAS
and not the DAS project directly so that it is tr
Hi Guys
Amita have started work to expose DAS as an SCA container, and we are
looking what would be the best way to get collaboration on continuing the
task. One of the ways we were thinking was to clean-up what is available
today and get it into the trunk, so we could share and continue contri
10 matches
Mail list logo
