Wicket RAD and Domdrides...

[jwcarman]

I have been working on a library called Domdrides (for DOMain-DRIven DESign) and I have been thinking about developing a wicket-based library that leverages Domdrides to enabled rapid development.  I haven't had a chance to dive in to Wicket RAD yet.  Is it based solely on JPA?  Domdrides has a "core" library that has been implemented using JPA, Hibernate, and iBATIS.  So, hopefully, something like Wicket RAD could be written against the Domdrides core and you would just need to drop in the proper implementation classes.  

I'm going to play around with Wicket RAD.  Would you guys like to work together?  I've got some ideas about setting up nice maven archetype templates that would allow you to generate entity/repository classes and have them woven into your application automatically.  All you would have to do is add your own custom stuff (like properties and custom finder methods to the repositories).  The domdrides library can be found at (as well as the main maven repository):

http://domdrides.sourceforge.net

[wfaler]

Hi,
Wicket RAD is not based on JPA, in fact the JPA stuff is only in an optional extension module to the core of Wicket RAD.

I haven't heard of your framework, but I think if there are common areas and synergies to be found that fits, working together is definitely a good idea - a community is stronger than lone warriors.

Have a look at Wicket RAD, play around with it and let me know what you think and if you see any areas where your framework might add value.

jwcarman wrote:

I have been working on a library called Domdrides (for DOMain-DRIven DESign) and I have been thinking about developing a wicket-based library that leverages Domdrides to enabled rapid development.  I haven't had a chance to dive in to Wicket RAD yet.  Is it based solely on JPA?  Domdrides has a "core" library that has been implemented using JPA, Hibernate, and iBATIS.  So, hopefully, something like Wicket RAD could be written against the Domdrides core and you would just need to drop in the proper implementation classes.  

I'm going to play around with Wicket RAD.  Would you guys like to work together?  I've got some ideas about setting up nice maven archetype templates that would allow you to generate entity/repository classes and have them woven into your application automatically.  All you would have to do is add your own custom stuff (like properties and custom finder methods to the repositories).  The domdrides library can be found at (as well as the main maven repository):

http://domdrides.sourceforge.net

[jwcarman]

Well, I took a look at Wicket-RAD, but I had some concerns.  When I tried to use the form generation stuff (from the example), I had to add the JPA-specific jar to my classpath to get the component class.  I didn't like that.  In my mind, the components should be in the "core" and they should be written against some "core" api that abstracts away the persistence technology.  I've started a project called "Wicketopia" that sits on top of domdrides and does some of what I'm looking for.  I haven't implemented the automatic form generation piece yet, because I want to see if we can work together (or if I can provide my own extension to Wicket-RAD).  If you've got time, take a look:

http://wicketopia.sourceforge.net

In particular, take a look at my CreateEntityForm, UpdateEntityForm, and RemoveEntityLink (they're in the "wicketopia" module).  I think you'll find that they're somewhat similar to what you guys have, but they're also somewhat simpler (no complex class hierarchy to deal with for one).  Let me know what you think and if you think we might be able to join forces.  Wicket really needs a library like we're talking about and I really want it to be slick!  Thanks for taking the time to discuss ideas with me.

James

[wfaler]

Hi,
You don't have to add JPA specific jars to your classpath at all, that is ONLY if you use the wicket-rad-jpa package.

All the form generation resides in wicket-rad-core under the org.wicketrad.propertyeditor package (PropertyEditPanel and sub-classes thereof).
What is in the JPA specific extension module only uses that and adds the JPA aspect to it, but it is by no means required or included by wicket-rad-core.

jwcarman wrote:

Well, I took a look at Wicket-RAD, but I had some concerns.  When I tried to use the form generation stuff (from the example), I had to add the JPA-specific jar to my classpath to get the component class.  I didn't like that.  In my mind, the components should be in the "core" and they should be written against some "core" api that abstracts away the persistence technology.  I've started a project called "Wicketopia" that sits on top of domdrides and does some of what I'm looking for.  I haven't implemented the automatic form generation piece yet, because I want to see if we can work together (or if I can provide my own extension to Wicket-RAD).  If you've got time, take a look:

http://wicketopia.sourceforge.net

In particular, take a look at my CreateEntityForm, UpdateEntityForm, and RemoveEntityLink (they're in the "wicketopia" module).  I think you'll find that they're somewhat similar to what you guys have, but they're also somewhat simpler (no complex class hierarchy to deal with for one).  Let me know what you think and if you think we might be able to join forces.  Wicket really needs a library like we're talking about and I really want it to be slick!  Thanks for taking the time to discuss ideas with me.

James

[jwcarman]

Did you get a chance to check out wicketopia?  

One other gripe I had was the Identifiable interface.  It seems wrong to me to put a view-specific interface on a domain class.  Then again, if you're adding all those annotations, why not? :)  

[wfaler]

Identifiable is not view-centric, nor is it required by any means (only interface required by the view-centric bits is Serializable, which is more of a Wicket requirement really).

Identifiable is ONLY used if you decided to implement the BeanService type stuff, OR use the JPA extension module.

Haven't checked out Wicketopia yet, I'm a bit swamped at the moment - winding down one project, getting ready to get onto two(!) new ones next week, one which will be using large parts of Wicket RAD.
Like the name though, wish I would have thought of it. :D

jwcarman wrote:

Did you get a chance to check out wicketopia?  

One other gripe I had was the Identifiable interface.  It seems wrong to me to put a view-specific interface on a domain class.  Then again, if you're adding all those annotations, why not? :)