Re: New App - Best Practices

2010-10-04 Thread Erdinc
My suggestion : Wicket / Spring / Cayenne ORM


From: Josh Kamau
Sent: Mon, October 4, 2010 1:37:45 PM
Subject: Re: New App - Best Practices

I use Wicket/Guice/JPA-Hibernate.

I think you will have to do alot of evaluation of the technologies yourself.
You have wicket for the presentation, now find a DI container and an ORM
solution and you are sorted. Normally the Presentation layer is the hard
part to decide when you are a java developer but you seem to have that taken
care off.


On Mon, Oct 4, 2010 at 1:15 PM, Sam Stainsby

 On Mon, 04 Oct 2010 17:49:07 +1000, Chris Colman wrote:

 You are also missing out on advantages like automatic schema updates,
 DB4O's own unique ID system, and other very useful parts of the DB4O
  The way I use JDO I get all of those features but in a datastore
  agnostic way.

 This is really interesting, albeit your solution uses non-open source
 tools that I could not specify as a dependency in our open source
 framework. We also didn't discuss DB4O's native queries, which are
 optimised on the fly, but we are wandering further off-topic, so I will
 send an email.

 To unsubscribe, e-mail:
 For additional commands, e-mail:


Re: Convention for classes name

2010-06-05 Thread Erdinc
I add PG prefix to page classes, e.g PGCustomerEditor, and RC to custom 
components, e.g RCDateTimeEditor.

From: Gustavo Henrique
Sent: Sat, June 5, 2010 10:46:17 PM
Subject: Convention for classes name

Is there any name convention for classes using wicket?
I'm using that model: CustomerPage, OrderPanel, ProductAddForm. What you
think about?



Re: Type Inference for Wicket 1.4

2010-04-16 Thread Erdinc
Or use wicket as I explained on this page :)

From: James Carman
Sent: Fri, April 16, 2010 2:05:12 PM
Subject: Re: Type Inference for Wicket 1.4

And, nothing is stopping you from doing something like this in your
own code.  I have a class called ComponentUtils where I put stuff like
this.  I have two methods:

public static T extends Serializable IModelT modelOf(T bean);
public static T extends Serializable IModelT modelFor(ClassT
beanClass); // This will instantiate the object for you.

I also have:

public static void detachAllModelFields(Component c);

With static imports, you can just use these methods like they're in
your classes.

On Fri, Apr 16, 2010 at 1:21 AM, Jeremy Thomerson wrote:
 This is the key - and it has been discussed before (in the many grueling 1.4
 conversations).  The short of it is that with private constructors there's a
 huge change and an inability to extend.  And without the private
 constructors, the static methods are dumb and extraneous because you would
 need hundreds of them, and you would need even more of them on your extended
 model and component classes.

 Jeremy Thomerson

 On Thu, Apr 15, 2010 at 8:51 AM, Thomas Kappler

 On 04/15/10 13:06, James Perry wrote:

 I can sympathise with that. However I don't think it would be a
 maintenance nightmare if the constructors are set to private; but that
 would mean a dramatic API change for such convenience and I'm guessing
 you're not willing to do this.

 Apart from the huge change for questionable benefit, that would also remove
 inheritance, which is essential to the Wicket way, because you can't extend
 a class with private constructors only. If you can, get a hold of Bloch,
 Effective Java, and read the insightful chapter on the constructor vs.
 static factory method trade-off.

 -- Thomas


 On 14 April 2010 17:01, Igor  wrote:

 you are going to have one factory method for each constructor, its
 going to be a pita to maintain. not something we will want in core.


 On Wed, Apr 14, 2010 at 8:51 AM, James Perry  wrote:

 I am looking to migrate from Wicket 1.3 and Wicket 1.4 and I really
 like the type-safe goodies but I do not like its verbosity. I was
 thinking of writing a patch that provides factories to improve the
 brevity by type inference of the generic invariant.

 This is an example of my idea:

 ModelMySuperLongNameForASimpleFooObject  model = Model.newModel();

 public staticT  ModelT  newModel() {
return new ModelT();

 Feedback welcomed. :-)


 To unsubscribe, e-mail:
 For additional commands, e-mail:

 To unsubscribe, e-mail:
 For additional commands, e-mail:

 To unsubscribe, e-mail:
 For additional commands, e-mail:

  Swiss Institute of Bioinformatics Tel: +41 22 379 51 89
  CMU, rue Michel Servet 1
  1211 Geneve 4


 To unsubscribe, e-mail:
 For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:


Re: A web site developed with Wicket

2010-03-31 Thread Erdinc
I don't think to release the source code of the application for now,  but I am 
trying to collect the techniques I applied in my wicket projects by maintaining 
an open source project - EasyWicket -

From: Gustavo Henrique
Sent: Wed, March 31, 2010 2:55:20 PM
Subject: Re: A web site developed with Wicket

could you release the wicket code for us?
that would be a great help for the community.