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
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
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 creating
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
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 this
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
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 loading).
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 change.
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 unsubscribe,
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-annotation.
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.
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, just
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.
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
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
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
. 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-annotation 1.0
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-annotations doesn't really tell you anything about what
features it provides (as was pointed
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
future
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 called
Yes, that is what I ment. I should have said wicketstuff-annotation
and wicketstuff-automount.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of James Carman
Sent: Tuesday, May 06, 2008 5:45 PM
To: users@wicket.apache.org
Subject: Re: [announce] wicketstuff
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:
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.
23 matches
Mail list logo
