I think the @Lock should /always/ be visible on the *public* contract
(interfaces), so that API users understand that there is one.
The implementation is *private* nö? The implementation should be able to
override the contract is it sees fit to do so, which is why I chose the
order @Remote, @Local then Class.
Romain Manni-Bucau wrote
>
> i tend to think so since intrefaces are kind of parent but i didnt find
> (maybe miss) sthg clear in the spec
>
> the lock is for me linked to impl not the contract
>
> wdyt?
>
> - Romain
>
>
> 2012/7/5 AndyG <andy.gumbrecht@>
>
>> I also believe this is legal right?
>>
>> @Local
>> @Lock(LockType.READ)
>> public interface *Deployer *{
>>
>> @Remote
>> public interface DeployerRemote extends *Deployer *{
>>
>> @Singleton
>> @TransactionManagement(TransactionManagementType.BEAN)
>> @AccessTimeout(value = 60, unit = TimeUnit.SECONDS)
>> public class DeployerImpl extends AbstractDeployer implements *Deployer*,
>> DeployerRemote {
>>
>> Or does @Lock(LockType.READ) only belong on the implementation?
>>
>>
>>
>> --
>> View this message in context:
>> http://openejb.979440.n4.nabble.com/Re-svn-commit-r1357576-in-openejb-trunk-openejb-container-openejb-core-src-main-java-org-apache-opena-tp4656048p4656055.html
>> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>>
>
--
View this message in context:
http://openejb.979440.n4.nabble.com/Re-svn-commit-r1357576-in-openejb-trunk-openejb-container-openejb-core-src-main-java-org-apache-opena-tp4656048p4656060.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
