avalon-phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <Paul_Hamm...@yahoo.com>
Subject Re: Extending DefaultApplication
Date Sat, 07 Sep 2002 08:13:38 GMT

In your own fork, of course you can do what you like.  If after some 
weeks/months you are still convinced that the reason for forking is good 
donate the changes back (against the then head revision) with a report 
on its rationale and usage and if it is good, we'd commit it.  My 
observation is that you should try to make it a configurable choice via 


- Paul

> Hi,
> I need to extend DefaultApplication in order to setup "default" 
> security context for blocks. I am planning to introduce a factory of 
> Application instances, so one can configure non-default implementation 
> of Application interface (JaasApplication in my case). However, I have 
> noticed that DefaultApplication is final and all its supporting 
> classes (BlockEntry, BlockInvocationHandler and alike) are package 
> protected and final. Would  it be a problem if I relax these 
> restructions, i.e. make DefaultApplication non-final and make its 
> supporting classes public non-final as needed?

To unsubscribe, e-mail:   <mailto:avalon-phoenix-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-phoenix-dev-help@jakarta.apache.org>

View raw message