You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Doug Donohoe <do...@donohoe.info> on 2008/05/06 21:33:19 UTC
[announce] wicketstuff-annotation 1.0 released
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://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation
A short example is at the end of this email.
I would like to thank Mr Mean and Martijn Dashorst for their assistance in
getting this project in TeamCity. The process was fairly painless thanks to
their work.
Our pom.xml is pretty simple, is configured to generate javadoc and depends
on wicketstuff-parent. It should be a good example for other wicket-stuff
projects (if they need one).
Thanks,
-Doug Donohoe
Use wicketstuff-annotation to use Java Annotations and class path searching
to mount your Wicket pages:
========================================================
@MountPath(path = "terms")
public class Terms extends WebPage { ... }
@MountPath(path = "terms")
@MountMixedParam(parameterNames={"sport", "show"})
public class Dogs extends WebPage { ... }
========================================================
public class MyWicketApplication extends WebApplication
{
@Override
protected void init()
{
new
AnnotatedMountScanner().scanPackage("com.acme.wicket.pages").mount(this);
}
}
========================================================
--
View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17090601.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Eelco Hillenius <ee...@gmail.com>.
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 <do...@donohoe.info> 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://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation
>
> A short example is at the end of this email.
>
> I would like to thank Mr Mean and Martijn Dashorst for their assistance in
> getting this project in TeamCity. The process was fairly painless thanks to
> their work.
>
> Our pom.xml is pretty simple, is configured to generate javadoc and depends
> on wicketstuff-parent. It should be a good example for other wicket-stuff
> projects (if they need one).
>
> Thanks,
>
> -Doug Donohoe
>
> Use wicketstuff-annotation to use Java Annotations and class path searching
> to mount your Wicket pages:
>
> ========================================================
> @MountPath(path = "terms")
> public class Terms extends WebPage { ... }
>
> @MountPath(path = "terms")
> @MountMixedParam(parameterNames={"sport", "show"})
> public class Dogs extends WebPage { ... }
> ========================================================
> public class MyWicketApplication extends WebApplication
> {
> @Override
> protected void init()
> {
> new
> AnnotatedMountScanner().scanPackage("com.acme.wicket.pages").mount(this);
> }
> }
> ========================================================
> --
> View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17090601.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Eelco Hillenius <ee...@gmail.com>.
> > 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)." and also: "The class path
> scanning is very efficient by itself and limiting the search only makes it
> faster."
Deep down it does scan the class path though, in a very similar way as
we do in some parts of Wicket.
I don't know much about ASM (which is used by Spring to visit the
class definitions). Is that where you get the edge in performance?
Anyway, I'm not sure whether you actually need Spring (and) ASM to do
the trick, but it does look quite nice, both the Spring code and how
wicketstff-annotation does it.
Cheers,
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Eelco Hillenius <ee...@gmail.com>.
> 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.
Yeah, I agree it is probably asking for trouble.
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Doug Donohoe <do...@donohoe.info>.
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 incurred at startup, we
don't require an alternate solution. Also note that anything JAR-based
would not easily work in development environments where you don't JAR after
each change.
-Doug
Maarten Bosteels wrote:
>
> On Wed, May 7, 2008 at 9:20 AM, Johan Compagner <jc...@gmail.com>
> 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
> information. Instead, it uses a meta-data reader to determine this (which
> is
> faster than going through class loading)." and also: "The class path
> scanning is very efficient by itself and limiting the search only makes it
> faster."
>
> regards,
> Maarten
>
>
>>
>> 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 packages.
>> those manifest entries are then read in when the jar is in the classpath
>>
>> johan
>
>
--
View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17103504.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Maarten Bosteels <mb...@gmail.com>.
On Wed, May 7, 2008 at 9:20 AM, Johan Compagner <jc...@gmail.com>
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
information. Instead, it uses a meta-data reader to determine this (which is
faster than going through class loading)." and also: "The class path
scanning is very efficient by itself and limiting the search only makes it
faster."
regards,
Maarten
>
> 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 packages.
> those manifest entries are then read in when the jar is in the classpath
>
> johan
>
>
> On Tue, May 6, 2008 at 9:33 PM, Doug Donohoe <do...@donohoe.info> 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://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation
> >
> > A short example is at the end of this email.
> >
> > I would like to thank Mr Mean and Martijn Dashorst for their assistance
> in
> > getting this project in TeamCity. The process was fairly painless
> thanks
> > to
> > their work.
> >
> > Our pom.xml is pretty simple, is configured to generate javadoc and
> > depends
> > on wicketstuff-parent. It should be a good example for other
> wicket-stuff
> > projects (if they need one).
> >
> > Thanks,
> >
> > -Doug Donohoe
> >
> > Use wicketstuff-annotation to use Java Annotations and class path
> > searching
> > to mount your Wicket pages:
> >
> > ========================================================
> > @MountPath(path = "terms")
> > public class Terms extends WebPage { ... }
> >
> > @MountPath(path = "terms")
> > @MountMixedParam(parameterNames={"sport", "show"})
> > public class Dogs extends WebPage { ... }
> > ========================================================
> > public class MyWicketApplication extends WebApplication
> > {
> > @Override
> > protected void init()
> > {
> > new
> >
> AnnotatedMountScanner().scanPackage("com.acme.wicket.pages").mount(this);
> > }
> > }
> > ========================================================
> > --
> > View this message in context:
> >
> http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17090601.html
> > Sent from the Wicket - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Martijn Dashorst <ma...@gmail.com>.
On 5/7/08, Johan Compagner <jc...@gmail.com> 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 scanning everything and create a manifest
> entries of all the packages.
> those manifest entries are then read in when the jar is in the classpath
Hmm... interesting idea...
Martijn
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by James Carman <ja...@carmanconsulting.com>.
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 <jc...@gmail.com> 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 scanning everything and create a manifest
> entries of all the packages.
> those manifest entries are then read in when the jar is in the classpath
>
> johan
>
>
>
>
> On Tue, May 6, 2008 at 9:33 PM, Doug Donohoe <do...@donohoe.info> 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://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation
> >
> > A short example is at the end of this email.
> >
> > I would like to thank Mr Mean and Martijn Dashorst for their assistance in
> > getting this project in TeamCity. The process was fairly painless thanks
> > to
> > their work.
> >
> > Our pom.xml is pretty simple, is configured to generate javadoc and
> > depends
> > on wicketstuff-parent. It should be a good example for other wicket-stuff
> > projects (if they need one).
> >
> > Thanks,
> >
> > -Doug Donohoe
> >
> > Use wicketstuff-annotation to use Java Annotations and class path
> > searching
> > to mount your Wicket pages:
> >
> > ========================================================
> > @MountPath(path = "terms")
> > public class Terms extends WebPage { ... }
> >
> > @MountPath(path = "terms")
> > @MountMixedParam(parameterNames={"sport", "show"})
> > public class Dogs extends WebPage { ... }
> > ========================================================
> > public class MyWicketApplication extends WebApplication
> > {
> > @Override
> > protected void init()
> > {
> > new
> > AnnotatedMountScanner().scanPackage("com.acme.wicket.pages").mount(this);
> > }
> > }
> > ========================================================
> > --
> > View this message in context:
> > http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17090601.html
> > Sent from the Wicket - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Johan Compagner <jc...@gmail.com>.
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 scanner work, does
it know the jar of the class..
johan
On Wed, May 7, 2008 at 9:48 AM, Eelco Hillenius <ee...@gmail.com>
wrote:
> On Wed, May 7, 2008 at 12:20 AM, Johan Compagner <jc...@gmail.com>
> 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 scanning everything and create a manifest
> > entries of all the packages.
> > those manifest entries are then read in when the jar is in the
> classpath
>
> So it would be either you find a special entry and use that or you
> scan if such an entry is not found for a jar?
>
> Eelco
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Eelco Hillenius <ee...@gmail.com>.
On Wed, May 7, 2008 at 12:20 AM, Johan Compagner <jc...@gmail.com> 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 scanning everything and create a manifest
> entries of all the packages.
> those manifest entries are then read in when the jar is in the classpath
So it would be either you find a special entry and use that or you
scan if such an entry is not found for a jar?
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Johan Compagner <jc...@gmail.com>.
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 packages.
those manifest entries are then read in when the jar is in the classpath
johan
On Tue, May 6, 2008 at 9:33 PM, Doug Donohoe <do...@donohoe.info> 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://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation
>
> A short example is at the end of this email.
>
> I would like to thank Mr Mean and Martijn Dashorst for their assistance in
> getting this project in TeamCity. The process was fairly painless thanks
> to
> their work.
>
> Our pom.xml is pretty simple, is configured to generate javadoc and
> depends
> on wicketstuff-parent. It should be a good example for other wicket-stuff
> projects (if they need one).
>
> Thanks,
>
> -Doug Donohoe
>
> Use wicketstuff-annotation to use Java Annotations and class path
> searching
> to mount your Wicket pages:
>
> ========================================================
> @MountPath(path = "terms")
> public class Terms extends WebPage { ... }
>
> @MountPath(path = "terms")
> @MountMixedParam(parameterNames={"sport", "show"})
> public class Dogs extends WebPage { ... }
> ========================================================
> public class MyWicketApplication extends WebApplication
> {
> @Override
> protected void init()
> {
> new
> AnnotatedMountScanner().scanPackage("com.acme.wicket.pages").mount(this);
> }
> }
> ========================================================
> --
> View this message in context:
> http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17090601.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: [announce] wicketstuff-annotation 1.0 released
Posted by James Carman <ja...@carmanconsulting.com>.
wicketstuff-automount?
On Tue, May 6, 2008 at 3:51 PM, Matthijs Wensveen <m....@func.nl> 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 'something with annotations'. IMO
> 'wicketstuff-mount-annotations' or somesuch would be better.
>
> Just my 2c.
> Matthijs
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: [announce] wicketstuff-annotation 1.0 released
Posted by "Hoover, William " <wh...@nemours.org>.
Yes, that is what I ment. I should have said "wicketstuff-annotation"
and "wicketstuff-automount".
-----Original Message-----
From: jcarman@carmanconsulting.com [mailto:jcarman@carmanconsulting.com]
On Behalf Of James Carman
Sent: Tuesday, May 06, 2008 5:45 PM
To: users@wicket.apache.org
Subject: Re: [announce] wicketstuff-annotation 1.0 released
On Tue, May 6, 2008 at 5:42 PM, Eelco Hillenius
<ee...@gmail.com> wrote:
> On Tue, May 6, 2008 at 2:24 PM, Hoover, William <wh...@nemours.org>
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" projects can utilize the core capabilities
> without reinventing > the wheel. This would also accommodate those
> who want a specific > dependency for wicket-automount.
>
> The project can be split without needing to make one a core project
> though. On the long term we could consider making something like that
> a core project, but for now that simply wouldn't be practical. The
> great thing about wicket-stuff projects is that it is easy for people
> to join the effort.
I don't think they meant core project as in a subproject of Wicket,
hosted at the ASF. I think they meant a core wicket-annotations project
at wicketstuff that others could "lean on"
>
> Eelco
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by James Carman <ja...@carmanconsulting.com>.
On Tue, May 6, 2008 at 5:42 PM, Eelco Hillenius
<ee...@gmail.com> wrote:
> On Tue, May 6, 2008 at 2:24 PM, Hoover, William <wh...@nemours.org> 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" projects can utilize the core capabilities without reinventing
> > the wheel. This would also accommodate those who want a specific
> > dependency for wicket-automount.
>
> The project can be split without needing to make one a core project
> though. On the long term we could consider making something like that
> a core project, but for now that simply wouldn't be practical. The
> great thing about wicket-stuff projects is that it is easy for people
> to join the effort.
I don't think they meant core project as in a subproject of Wicket,
hosted at the ASF. I think they meant a core wicket-annotations
project at wicketstuff that others could "lean on"
>
> Eelco
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Eelco Hillenius <ee...@gmail.com>.
On Tue, May 6, 2008 at 2:24 PM, Hoover, William <wh...@nemours.org> 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" projects can utilize the core capabilities without reinventing
> the wheel. This would also accommodate those who want a specific
> dependency for wicket-automount.
The project can be split without needing to make one a core project
though. On the long term we could consider making something like that
a core project, but for now that simply wouldn't be practical. The
great thing about wicket-stuff projects is that it is easy for people
to join the effort.
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: [announce] wicketstuff-annotation 1.0 released
Posted by Doug Donohoe <do...@donohoe.info>.
That's not a bad idea. I'll put it on my TODO list. I may wait and see what
other annotation specific needs arise before acting.
-Doug
Hoover, William 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" projects can utilize the core capabilities without reinventing
> the wheel. This would also accommodate those who want a specific
> dependency for wicket-automount.
>
> -----Original Message-----
> From: jcarman@carmanconsulting.com [mailto:jcarman@carmanconsulting.com]
> 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 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 something called wicket-automount.
>
> On Tue, May 6, 2008 at 4:02 PM, Ryan Sonnek <ry...@gmail.com>
> wrote:
>> 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 lump all annotations together.
>>
>> On Tue, May 6, 2008 at 2:59 PM, James Carman
>> <ja...@carmanconsulting.com>
>> wrote:
>>
>>
>>
>> > 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 goodies, I can just download this
>> little nugget and > use it.
>> >
>> > On Tue, May 6, 2008 at 3:55 PM, Doug Donohoe <do...@donohoe.info>
> wrote:
>> > >
>> > > 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. Believe me, > I > > spent
>> an hour staring out the window trying to decide on the right > name.
>> > >
>> > > Hopefully the documentation explains clearly what it does.
>> > >
>> > > -Doug
>> > >
>> > >
>> > >
>> > >
>> > > Matthijs Wensveen-2 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 'something with
>> annotations'. IMO > > > 'wicketstuff-mount-annotations' or somesuch
>> would be better.
>> > > >
>> > > > Just my 2c.
>> > > > Matthijs
>> > > >
>> > > >
>> ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > > > For additional commands, e-mail: users-help@wicket.apache.org
>
>> > > > > > > > > > > > > > -- > > View this message in
>> context:
>> >
>> http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-t
>> p17090601p17091003.html
>> > >
>> > > Sent from the Wicket - User mailing list archive at Nabble.com.
>> > >
>> > >
>> > >
>> ---------------------------------------------------------------------
>> > >
>> > >
>> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > > For additional commands, e-mail: users-help@wicket.apache.org >
>
>> > > > > >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > For additional commands, e-mail: users-help@wicket.apache.org > >
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17092957.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: [announce] wicketstuff-annotation 1.0 released
Posted by "Hoover, William " <wh...@nemours.org>.
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" projects can utilize the core capabilities without reinventing
the wheel. This would also accommodate those who want a specific
dependency for wicket-automount.
-----Original Message-----
From: jcarman@carmanconsulting.com [mailto:jcarman@carmanconsulting.com]
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 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 something called wicket-automount.
On Tue, May 6, 2008 at 4:02 PM, Ryan Sonnek <ry...@gmail.com>
wrote:
> 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 lump all annotations together.
>
> On Tue, May 6, 2008 at 2:59 PM, James Carman
> <ja...@carmanconsulting.com>
> wrote:
>
>
>
> > 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 goodies, I can just download this
> little nugget and > use it.
> >
> > On Tue, May 6, 2008 at 3:55 PM, Doug Donohoe <do...@donohoe.info>
wrote:
> > >
> > > 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. Believe me, > I > > spent
> an hour staring out the window trying to decide on the right > name.
> > >
> > > Hopefully the documentation explains clearly what it does.
> > >
> > > -Doug
> > >
> > >
> > >
> > >
> > > Matthijs Wensveen-2 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 'something with
> annotations'. IMO > > > 'wicketstuff-mount-annotations' or somesuch
> would be better.
> > > >
> > > > Just my 2c.
> > > > Matthijs
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > > > > > > > > > > > > -- > > View this message in
> context:
> >
> http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-t
> p17090601p17091003.html
> > >
> > > Sent from the Wicket - User mailing list archive at Nabble.com.
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > >
> > >
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org >
> > > > > >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org > >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by James Carman <ja...@carmanconsulting.com>.
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 something called wicket-automount.
On Tue, May 6, 2008 at 4:02 PM, Ryan Sonnek <ry...@gmail.com> wrote:
> 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 lump all annotations together.
>
> On Tue, May 6, 2008 at 2:59 PM, James Carman <ja...@carmanconsulting.com>
> wrote:
>
>
>
> > 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 goodies, I can just download this little nugget and
> > use it.
> >
> > On Tue, May 6, 2008 at 3:55 PM, Doug Donohoe <do...@donohoe.info> wrote:
> > >
> > > 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. Believe me,
> > I
> > > spent an hour staring out the window trying to decide on the right
> > name.
> > >
> > > Hopefully the documentation explains clearly what it does.
> > >
> > > -Doug
> > >
> > >
> > >
> > >
> > > Matthijs Wensveen-2 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 'something with annotations'. IMO
> > > > 'wicketstuff-mount-annotations' or somesuch would be better.
> > > >
> > > > Just my 2c.
> > > > Matthijs
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> > > >
> > >
> > > --
> > > View this message in context:
> > http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17091003.html
> > >
> > > Sent from the Wicket - User mailing list archive at Nabble.com.
> > >
> > >
> > > ---------------------------------------------------------------------
> > >
> > >
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Ryan Sonnek <ry...@gmail.com>.
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 lump all annotations together.
On Tue, May 6, 2008 at 2:59 PM, James Carman <ja...@carmanconsulting.com>
wrote:
> 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 goodies, I can just download this little nugget and
> use it.
>
> On Tue, May 6, 2008 at 3:55 PM, Doug Donohoe <do...@donohoe.info> wrote:
> >
> > 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. Believe me,
> I
> > spent an hour staring out the window trying to decide on the right
> name.
> >
> > Hopefully the documentation explains clearly what it does.
> >
> > -Doug
> >
> >
> >
> >
> > Matthijs Wensveen-2 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 'something with annotations'. IMO
> > > 'wicketstuff-mount-annotations' or somesuch would be better.
> > >
> > > Just my 2c.
> > > Matthijs
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> > >
> >
> > --
> > View this message in context:
> http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17091003.html
> >
> > Sent from the Wicket - User mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> >
> >
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: [announce] wicketstuff-annotation 1.0 released
Posted by James Carman <ja...@carmanconsulting.com>.
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 goodies, I can just download this little nugget and
use it.
On Tue, May 6, 2008 at 3:55 PM, Doug Donohoe <do...@donohoe.info> wrote:
>
> 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. Believe me, I
> spent an hour staring out the window trying to decide on the right name.
>
> Hopefully the documentation explains clearly what it does.
>
> -Doug
>
>
>
>
> Matthijs Wensveen-2 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 'something with annotations'. IMO
> > 'wicketstuff-mount-annotations' or somesuch would be better.
> >
> > Just my 2c.
> > Matthijs
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17091003.html
>
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
>
>
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Doug Donohoe <do...@donohoe.info>.
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. Believe me, I
spent an hour staring out the window trying to decide on the right name.
Hopefully the documentation explains clearly what it does.
-Doug
Matthijs Wensveen-2 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 'something with annotations'. IMO
> 'wicketstuff-mount-annotations' or somesuch would be better.
>
> Just my 2c.
> Matthijs
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17091003.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Matthijs Wensveen <m....@func.nl>.
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.
Matthijs
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Ned Collyer <ne...@gmail.com>.
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Jonathan Locke <jo...@gmail.com>.
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
> BookmarkablePageRequestTargetUrlCodingStrategy becomes the
> MountBookmarkablePageRequestTarget. I'm not sure why that one is such a
> mouthful. In essence, I'm just following the established standard.
>
> If people want, I can change it.
>
> Fortunately, it is the default when you just use @MountPath by itself, so
> you don't currently need to use it. I added it to be complete. Also
> note, I chose it as default since that is what WebApplication.mount()
> defaults too.
>
> -Doug
>
>
> Jonathan Locke wrote:
>>
>>
>> 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://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation
>>>
>>> A short example is at the end of this email.
>>>
>>> I would like to thank Mr Mean and Martijn Dashorst for their assistance
>>> in getting this project in TeamCity. The process was fairly painless
>>> thanks to their work.
>>>
>>> Our pom.xml is pretty simple, is configured to generate javadoc and
>>> depends on wicketstuff-parent. It should be a good example for other
>>> wicket-stuff projects (if they need one).
>>>
>>> Thanks,
>>>
>>> -Doug Donohoe
>>>
>>> Use wicketstuff-annotation to use Java Annotations and class path
>>> searching to mount your Wicket pages:
>>>
>>> ========================================================
>>> @MountPath(path = "terms")
>>> public class Terms extends WebPage { ... }
>>>
>>> @MountPath(path = "terms")
>>> @MountMixedParam(parameterNames={"sport", "show"})
>>> public class Dogs extends WebPage { ... }
>>> ========================================================
>>> public class MyWicketApplication extends WebApplication
>>> {
>>> @Override
>>> protected void init()
>>> {
>>> new
>>> AnnotatedMountScanner().scanPackage("com.acme.wicket.pages").mount(this);
>>> }
>>> }
>>> ========================================================
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17093691.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Doug Donohoe <do...@donohoe.info>.
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 following the established standard.
If people want, I can change it.
Fortunately, it is the default when you just use @MountPath by itself, so
you don't currently need to use it. I added it to be complete. Also note,
I chose it as default since that is what WebApplication.mount() defaults
too.
-Doug
Jonathan Locke wrote:
>
>
> 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://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation
>>
>> A short example is at the end of this email.
>>
>> I would like to thank Mr Mean and Martijn Dashorst for their assistance
>> in getting this project in TeamCity. The process was fairly painless
>> thanks to their work.
>>
>> Our pom.xml is pretty simple, is configured to generate javadoc and
>> depends on wicketstuff-parent. It should be a good example for other
>> wicket-stuff projects (if they need one).
>>
>> Thanks,
>>
>> -Doug Donohoe
>>
>> Use wicketstuff-annotation to use Java Annotations and class path
>> searching to mount your Wicket pages:
>>
>> ========================================================
>> @MountPath(path = "terms")
>> public class Terms extends WebPage { ... }
>>
>> @MountPath(path = "terms")
>> @MountMixedParam(parameterNames={"sport", "show"})
>> public class Dogs extends WebPage { ... }
>> ========================================================
>> public class MyWicketApplication extends WebApplication
>> {
>> @Override
>> protected void init()
>> {
>> new
>> AnnotatedMountScanner().scanPackage("com.acme.wicket.pages").mount(this);
>> }
>> }
>> ========================================================
>>
>
>
--
View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17093688.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Jonathan Locke <jo...@gmail.com>.
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://wicketstuff.org/confluence/display/STUFFWIKI/wicketstuff-annotation
>
> A short example is at the end of this email.
>
> I would like to thank Mr Mean and Martijn Dashorst for their assistance in
> getting this project in TeamCity. The process was fairly painless thanks
> to their work.
>
> Our pom.xml is pretty simple, is configured to generate javadoc and
> depends on wicketstuff-parent. It should be a good example for other
> wicket-stuff projects (if they need one).
>
> Thanks,
>
> -Doug Donohoe
>
> Use wicketstuff-annotation to use Java Annotations and class path
> searching to mount your Wicket pages:
>
> ========================================================
> @MountPath(path = "terms")
> public class Terms extends WebPage { ... }
>
> @MountPath(path = "terms")
> @MountMixedParam(parameterNames={"sport", "show"})
> public class Dogs extends WebPage { ... }
> ========================================================
> public class MyWicketApplication extends WebApplication
> {
> @Override
> protected void init()
> {
> new
> AnnotatedMountScanner().scanPackage("com.acme.wicket.pages").mount(this);
> }
> }
> ========================================================
>
--
View this message in context: http://www.nabble.com/-announce--wicketstuff-annotation-1.0-released-tp17090601p17093680.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Ryan Sonnek <ry...@gmail.com>.
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 <lu...@gmail.com>
wrote:
> 2008/5/6 Doug Donohoe <do...@donohoe.info>:
> >
> > 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, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: [announce] wicketstuff-annotation 1.0 released
Posted by Luca Marrocco <lu...@gmail.com>.
2008/5/6 Doug Donohoe <do...@donohoe.info>:
>
> 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, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org