Re: [announce] wicketstuff-annotation 1.0 released

2008-05-07 Thread Eelco Hillenius
> In my project, I have 60+ jar files in the classpath and the scan only took > 255 milliseconds (on a 1.66 ghz core duo mac). Yeah, that sounds perfectly acceptable. > Also note that anything JAR-based > would not easily work in development environments where you don't JAR after > each chan

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-07 Thread Eelco Hillenius
> > if the scanning of the classpath is expensive (i guess all classes are > > loaded that are scanned..) > > It says: "Note that Spring does not load the class to determine this > information. Instead, it uses a meta-data reader to determine this (which is > faster than going through class lo

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-07 Thread Doug Donohoe
Thank you Maarten for pointing out the documentation I wrote on this. In my project, I have 60+ jar files in the classpath and the scan only took 255 milliseconds (on a 1.66 ghz core duo mac). Initializing hibernate takes much longer. I think this is pretty decent, and since it is only incurr

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-07 Thread Maarten Bosteels
On Wed, May 7, 2008 at 9:20 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > if the scanning of the classpath is expensive (i guess all classes are > loaded that are scanned..) Hi, I guess you haven't read the docs completely :-) It says: "Note that Spring does not load the class to determine

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-07 Thread James Carman
I did something like this for Hibernate back in the day. I wrote an APT processor that checked for all classes annotated with @Entity and added those to a hibernate.cfg.xml file. On Wed, May 7, 2008 at 3:20 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > if the scanning of the classpath is expen

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-07 Thread Johan Compagner
that would then be the best impl yes. But I dont know if you know what jars you are scanning... So do you know that you dont have to do this because this jar is described in the manifest and another doesnt have it and you have to scan That could be difficult. But i dont know how the current sc

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-07 Thread Eelco Hillenius
On Wed, May 7, 2008 at 12:20 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > if the scanning of the classpath is expensive (i guess all classes are > loaded that are scanned..) > cant there be an option that the scanning is only done once? > When you create the jar so with maven/ant? > When cr

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-07 Thread Martijn Dashorst
On 5/7/08, Johan Compagner <[EMAIL PROTECTED]> wrote: > if the scanning of the classpath is expensive (i guess all classes are > loaded that are scanned..) > cant there be an option that the scanning is only done once? > When you create the jar so with maven/ant? > When creating the jar you are

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-07 Thread Johan Compagner
if the scanning of the classpath is expensive (i guess all classes are loaded that are scanned..) cant there be an option that the scanning is only done once? When you create the jar so with maven/ant? When creating the jar you are scanning everything and create a manifest entries of all the packag

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Ned Collyer
Had a look at the wiki. Well done, well thought out, simple to implement. And a sensible license :) -- View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17093692.html Sent from the Wicket - User mailing list archive at Nabble.com. -

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Jonathan Locke
oh okay, that's fine. i see your point. i suppose i'd prefer it was BookmarkablePageUrlCodingStrategy. Doug Donohoe wrote: > > To get my name and to be consistent, I simply lopped of the > "UrlCodingStrategy" at the end of the strategy names. Thus the unwieldy > BookmarkablePageRequestTarge

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Doug Donohoe
To get my name and to be consistent, I simply lopped of the "UrlCodingStrategy" at the end of the strategy names. Thus the unwieldy BookmarkablePageRequestTargetUrlCodingStrategy becomes the MountBookmarkablePageRequestTarget. I'm not sure why that one is such a mouthful. In essence, I'm just f

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Jonathan Locke
neato. but don't you think MountBookmarkablePageRequestTarget could be just MountBookmarkable? Doug Donohoe wrote: > > I am pleased to announce the 1.0 release of wicketstuff-annotation. > > Full documentation and explanation (e.g., what, why, how) is at the > wicket-stuff wiki: > > http://

RE: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Hoover, William
bject: Re: [announce] wicketstuff-annotation 1.0 released On Tue, May 6, 2008 at 5:42 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > On Tue, May 6, 2008 at 2:24 PM, Hoover, William <[EMAIL PROTECTED]> wrote: > > Would it be better if there were a core wicket-annotation project &g

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread James Carman
On Tue, May 6, 2008 at 5:42 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > On Tue, May 6, 2008 at 2:24 PM, Hoover, William <[EMAIL PROTECTED]> wrote: > > Would it be better if there were a core wicket-annotation project that > > provides the basics (such as the scanner) and another project cal

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Eelco Hillenius
On Tue, May 6, 2008 at 2:24 PM, Hoover, William <[EMAIL PROTECTED]> wrote: > Would it be better if there were a core wicket-annotation project that > provides the basics (such as the scanner) and another project called > wicket-automount (with wicket-annotation dependency)? That way other > "fut

RE: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Doug Donohoe
t. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of James Carman > Sent: Tuesday, May 06, 2008 4:37 PM > To: users@wicket.apache.org > Subject: Re: [announce] wicketstuff-annotation 1.0 released > > The name wicket-a

RE: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Hoover, William
heel. This would also accommodate those who want a specific dependency for wicket-automount. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Carman Sent: Tuesday, May 06, 2008 4:37 PM To: users@wicket.apache.org Subject: Re: [announce] wicketstuff-anno

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread James Carman
The name wicket-annotations doesn't really tell you anything about what features it provides (as was pointed out earlier). If I were a person wanting to find an easier way to mount pages, it wouldn't necessarily be obvious to check wicket-annotations. However, it would be more obvious if I saw so

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Eelco Hillenius
Nice job! Great that you added a WIKI page and a proper build config etc. Cheers, Eelco On Tue, May 6, 2008 at 12:33 PM, Doug Donohoe <[EMAIL PROTECTED]> wrote: > > I am pleased to announce the 1.0 release of wicketstuff-annotation. > > Full documentation and explanation (e.g., what, why, how)

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Ryan Sonnek
the only reason to break annotations out into separate distributions is if new dependencies are introduced with a subset of annotations. if a new annotation comes along that requires hibernate jars to be on the classpath, that definitely should be it's own project. otherwise, it makes sense to lu

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread James Carman
Yes, but should we globalize the "annotations" namespace to mean that anyone who wants to do anything with annotations should put it inside this project? Perhaps keeping things smaller is a better idea. That way, if I want to use automount, but I don't want all of the other annotation-based goodi

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Doug Donohoe
Matthijs, That is a good point and I did consider that, but I thought if anyone else wants to do things with annotations and wicket in the future, this would be a perfect place to put that code (especially given the underlying scanning support). Thus, I was being optimistic about the future. Be

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread James Carman
wicketstuff-automount? On Tue, May 6, 2008 at 3:51 PM, Matthijs Wensveen <[EMAIL PROTECTED]> wrote: > Doug Donohoe wrote: > > > I am pleased to announce the 1.0 release of wicketstuff-annotation. > > > > > > Nice. But the name 'wicketstuff-annotation' does not say anything about > what it does,

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Matthijs Wensveen
Doug Donohoe wrote: I am pleased to announce the 1.0 release of wicketstuff-annotation. Nice. But the name 'wicketstuff-annotation' does not say anything about what it does, just 'something with annotations'. IMO 'wicketstuff-mount-annotations' or somesuch would be better. Just my 2c. Ma

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Ryan Sonnek
nice work! i really like how you don't have to touch the web application class every time add a new page! On Tue, May 6, 2008 at 2:42 PM, Luca Marrocco <[EMAIL PROTECTED]> wrote: > 2008/5/6 Doug Donohoe <[EMAIL PROTECTED]>: > > > > I am pleased to announce the 1.0 release of wicketstuff-annotat

Re: [announce] wicketstuff-annotation 1.0 released

2008-05-06 Thread Luca Marrocco
2008/5/6 Doug Donohoe <[EMAIL PROTECTED]>: > > I am pleased to announce the 1.0 release of wicketstuff-annotation. [cut] > http://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation cool :D Luca - To unsubscri