RE: [sca-assembly] ISSUE 40: Autowire at the domain-level

["Patil, Sanjay" <sanjay.patil@sap.com>]

+1 to the concern that the autowiring at the domain level would be
dangerous in enterprise production environments. 

I think the use of autowire feature (if it stays) should be limited to
simplifying assembly development environment (e.g. the target of a wire
is obvious to the composite developer, or there are just too many
obvious wires cluttering the visual representation and the composite
SCDL file), and we should require that the autowires be resolved
before/while a composite is deployed.

-- Sanjay

> -----Original Message-----
> From: David Booz [mailto:booz@us.ibm.com] 
> Sent: Thursday, Jan 24, 2008 21:50 PM
> To: sca-assembly@lists.oasis-open.org
> Subject: Re: [sca-assembly] ISSUE 40: Autowire at the domain-level
> 
> Or we could choose to disallow autowire at the Domain level 
> for everyone.
> At the very least, I think it should be an optional feature 
> if it stays.
> If it stays, then I'd like the default to be off for the Domain.
> 
> My main concern with autowire in the domain is that it is 
> potentially very
> dangerous in a large enterprise production environment.  It has the
> possibility for un-intentional side effects. Those 
> environments generally
> like to put very tight control over the relationships between 
> the different
> parts of the system (domain).  I suspect that since you raised the
> question, there may be other environments where less rigor is 
> tolerable and
> surprises can be dealt with easily, e.g. turning your phone 
> off and then on
> again. In those cases it seems that the introduction of a new autowire
> target into the domain is one of the drivers of the re-injection
> capability.  I think this is your second bullet below.
> 
> 
> 
> Dave Booz
> STSM, SCA and WebSphere Architecture
> Co-Chair OASIS SCA-Policy TC
> "Distributed objects first, then world hunger"
> Poughkeepsie, NY (845)-435-6093  or  8-295-6093
> e-mail:booz@us.ibm.com
> http://washome.austin.ibm.com/xwiki/bin/view/SCA2Team/WebHome
> 
> 
>                                                               
>              
>              Scott Vorthmann                                  
>              
>              <scottv@tibco.com                                
>              
>              >                                                
>           To 
>                                        Michael Rowley 
> <mrowley@bea.com>    
>              01/22/2008 07:11                                 
>           cc 
>              PM                        "OASIS Assembly"       
>              
>                                        
> <sca-assembly@lists.oasis-open.org> 
>                                                               
>      Subject 
>                                        [sca-assembly] ISSUE 
> 40: Autowire   
>                                        at the domain-level    
>              
>                                                               
>              
>                                                               
>              
>                                                               
>              
>                                                               
>              
>                                                               
>              
>                                                               
>              
> 
> 
> 
> 
> 
> http://www.osoa.org/jira/browse/ASSEMBLY-40
> 
> On Jan 22, 2008, at 3:54 PM, Michael Rowley wrote:
> 
> >
> > RAISER: Michael Rowley
> >
> > TARGET: SCA Assembly Specification section 6.4.2 Autowire
> >
> > DESCRIPTION:
> >
> > Assume that a component is deployed at the domain level has a
> > reference that has been marked to be resolved by autowire.  If a new
> > component is deployed later that qualifies as a target for the
> > autowire, will the existing component now target the new component?
> > The specification could:
> > - Require that the runtime handle such dynamic changes and effect
> > such changes onto existing component references.
> > - Allow that some runtimes may freeze the results of autowire at the
> > time the client component is deployed, while others will treat the
> > autowiring as dynamic.
> > - Allow some runtimes to completely disallow autowiring for domain-
> > level components.
> >
> > PROPOSAL:
> >
> > None.
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all 
> your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr
> oups.php 
> 
>