Comments on: Fixing Wicket Property Models Using Salve

By: ivaynberg

ivaynberg — Sun, 26 Jun 2011 06:49:59 +0000

@Marcue, metagen is not yet available in the maven central repo. that means you have to install it locally. check out the source and run
mvn install
this will deploy the necessary artifacts into your local maven repo, after which your project should find them.

By: Marcue

Marcue — Sun, 26 Jun 2011 06:13:35 +0000

Oh my taggings did not show propertly in my comment.
But I did it exactly as shown at
https://github.com/42Lines/metagen

By: Marcue

Marcue — Sun, 26 Jun 2011 06:12:15 +0000

Hello ivaynberg,

I read you’re commment and I have a lot of interest.
I tried install metagen by adding this on my pom.xml:

1.0-SNAPSHOT

and…

net.ftlines.metagen
metagen-core
${metagen.version}

net.ftlines.metagen
metagen-processor
${metagen.version}

net.ftlines.metagen
metagen-wicket
${metagen.version}

but Maven says: Missing artifacts for all of them.

Is not working?
Or is it wrong?

By: ivaynberg

ivaynberg — Wed, 22 Jun 2011 04:11:44 +0000

currently i would recommend using this: https://github.com/42Lines/metagen
We are using it in production with good results.

By: Carlos

Carlos — Wed, 22 Jun 2011 02:45:23 +0000

So, is this something you recommend using?

By: ivaynberg

ivaynberg — Wed, 11 May 2011 15:20:43 +0000

@bert: this is my latest attempt at fixing this: https://github.com/42Lines/metagen

its being used in production and works very well

By: bert bruynooghe

bert bruynooghe — Wed, 11 May 2011 07:49:10 +0000

Based on this idea, I developped my own VerifiablePropertyModel. You can find some explanation on https://github.com/bertBruynooghe/wicket-verifiable/wiki

By: ivaynberg

ivaynberg — Sat, 21 Feb 2009 18:32:38 +0000

@Anotine:

The names are a bit cryptic, but the reason is that I want to keep them as short as possible, I got tired of typing out PropertyModel all the time :)

There is no need to do this in development mode; when your application is running, in any mode, you will already get a runtime exception. The entire point of this is to shift the error from runtime into a lower phase such as compile or test because runtime is the hardest to test.

By: Antoine

Antoine — Sat, 21 Feb 2009 05:11:06 +0000

Igor,

I like your idea. I would definitely prefer to use such a PeModel over a PropertyModel (although I find the names Pe and PeModel too cryptic). Could it be taken a step further such that this new model would be integrated into the Wicket core, and that testing is happening automatically when running in development mode?

–Antoine

By: ivaynberg

ivaynberg — Tue, 27 Jan 2009 15:49:36 +0000

@Daniele: doing so will push the check back into runtime which is highly undesirable. All the analyzer sees is “new Pe(…)” and it checks just that part of the bytecode.