Haven't looked at it in a little while now, but from what I recall, here are 
some thoughts on issues we encountered:
- there was a problem exposing multiple beans as services from one Spring 
context.
- cannot use AOP across multiple implementation.spring components (each 
component has a different Spring context)
- in general unable to share beans across multiple components (probably as 
designed)
- some interoperability between sca properties and beans (using one to inject 
into the other)
- maybe policy could tie into/leverage AOP and Spring transaction management?
- to solve some of the above, perhaps a parent Spring context could be defined 
at the composite level?

Sunny Ip


----- Original Message ----
From: Feng Wang <[EMAIL PROTECTED]>
To: "[email protected]" <[email protected]>
Sent: Wednesday, July 16, 2008 2:41:23 AM
Subject: Re: Tuscany users, we want your input on SCA/Spring integration

Hi,all

    My answers below.
    
Thanks,
Feng Wang

On 2008-07-16 04:25:15,Luciano Resende <[EMAIL PROTECTED]> wrote:

>I'd like to start collecting user scenarios and necessary enhancements
>to the current SCA/Spring integration.
>
>Please help us by answering the questions below, and also providing
>any extra feedback you think can help.
>
>
>What Spring release are you using ?
spring 2.0
>What Spring features do you use? Spring Framework, Spring Web
>Services, Spring Dynamic Modules for OSGi?
Spring Framework(transaction,proxy,rmi,jndi,jmx)
>
>
>What benefits from SCA/Spring integration are you looking for?
>
>  * Support for remote communication between components?
>
>  * Co-existence of Spring and SCA?
>
>  * Support coarse-grained assembly beyond the POJOs?
My scenario is that the old application based on Spring and the new application 
based on sca and the new will reuse the Spring bean.
So the fundamental function is the assembly between Spring bean and 
sca component and deploying the Spring bean as a sca service.

>
>
>What use cases do you have beyond the SCA/Spring spec 1.0?
>
>What are the main issues or wish-to-have features in our current
>SCA/Spring integration ?
>
Some functions of sca and Spring is intersect such as transaction security etc,
so the coordination will be important.
>
>-- 
>Luciano Resende
>Apache Tuscany Committer
>http://people.apache.org/~lresende
>http://lresende.blogspot.com/

Reply via email to