Comments in line... On 5/13/07, Simon Nash <[EMAIL PROTECTED]> wrote:
My preference would be not to couple SCA and DAS together by including these samples in the SCA release.
I'd agree with you if this was the sample introducing dependency on DAS/SDO, but bigbank already have these dependencies...
Of course if these were to be delivered as part of DAS then this would make DAS dependent on SCA. I'm not sure how the DAS folks would feel about that.
These samples were originally introduced as DAS samples, but introducing SCA dependencies in DAS was causing circular dependencies, then it was moved to sampleapps/das-pojo-service and now became sca/samples/das-service and das-service-web.
Maybe we need some other release/packaging vehicle for Tuscany samples that use a combination of SCA, SDO and DAS.
Well, we used to have sampleapps, but that is gone as of now.
Simon Luciano Resende wrote: > So, BigBank, das-service and das-service-web would have dependencies > on DAS and SDO. > If these samples go to the distribution, we would probably want SDO > beta1 dependency and DAS xx, but I'm not sure what the xx should be, > DAS beta1 is not release yet, although the release process had already > started, let me also double check with the DAS Comunity where we are > with the release process. > > On 5/11/07, Simon Laws <[EMAIL PROTECTED]> wrote: > >> I'm probably stating the obvious and I'm guess this is the motivation >> behind >> Ant's question but I don't see the DAS itself in the bindary distro. >> Is the >> proposition to ship the DAS jar(s) as part of the SCA distiribution? >> I'm not >> expressing an opinion here just working out what the question is;-) >> >> Simon >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Luciano Resende http://people.apache.org/~lresende --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
