wicket-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Donohoe <d...@donohoe.info>
Subject Re: how to contribute / wicket 1.4 plans
Date Sat, 03 May 2008 20:02:20 GMT

I actually have it working w/out class path scanning.  I'll be posting
details soon.

-Doug


John Ray-2 wrote:
> 
> I'm curious to know how much extra time is added to the application 
> startup by doing the class path scanning. Particularly for larger 
> projects. I just find that when doing development the faster an 
> application starts the better.
> 
> John
> 
> 
> Doug Donohoe wrote:
>> Thanks.  I'm not sure if class path scanning is needed.  To be honest,
>> I haven't looked at the internals of 'mount' yet...
>>
>> -Doug
>>
>>
>> jwcarman wrote:
>>   
>>> On Sat, May 3, 2008 at 9:20 AM, Doug Donohoe <doug@donohoe.info> wrote:
>>>     
>>>>  3) Use Annotations to handle mounting.  Instead of putting all mount
>>>> logic
>>>>  in the Application class, you could annotate your pages with something
>>>> like
>>>>  @Mount( strategy=foo.class, params=x,y,z ).  Then upon initialization,
>>>>  Wicket could scan the class path and auto-mount these annotated pages.
>>>>  Scanning the classpath is pretty easy using some spring-core
>>>> functionality.
>>>>  I don't know if the Spring license is compatible with Apache, so this
>>>> might
>>>>  need to be a contrib feature.
>>>>       
>>> Spring uses the Apache License, v2
>>>
>>>
>>>     
>>
>>   
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/how-to-contribute---wicket-1.4-plans-tp17034501p17037980.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.


Mime
View raw message