tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fernando Padilla <f...@alum.mit.edu>
Subject Re: [jira] Closed: (TAP5-316) Add service overriding capabilities to tapestry-ioc, similar to what tapestry-core has (the Alias service)
Date Mon, 05 Jan 2009 18:45:58 GMT
I was wondering..

decorateServiceA() is much like an override..


would it be a clean idea to simply support:

overrideBuildServiceA()



instead of:

buildServiceB()

contributeAlias() {
   alias( "serviceB", "serviceA" );
}






Howard M. Lewis Ship (JIRA) wrote:
>      [ https://issues.apache.org/jira/browse/TAP5-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
> 
> Howard M. Lewis Ship closed TAP5-316.
> -------------------------------------
> 
>        Resolution: Fixed
>     Fix Version/s: 5.1.0.0
> 
>> Add service overriding capabilities to tapestry-ioc, similar to what tapestry-core
has (the Alias service)
>> ----------------------------------------------------------------------------------------------------------
>>
>>                 Key: TAP5-316
>>                 URL: https://issues.apache.org/jira/browse/TAP5-316
>>             Project: Tapestry 5
>>          Issue Type: New Feature
>>          Components: tapestry-ioc
>>    Affects Versions: 5.1.0.0, 5.0.15
>>            Reporter: Thiago H. de Paula Figueiredo
>>            Assignee: Howard M. Lewis Ship
>>             Fix For: 5.1.0.0
>>
>>
>> Alias and AliasContribution are part of tapestry-core, not tapestry-ioc. Why don't
we move them to tapestry-ioc?
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message