> may be, just may, thats because of Maturity of JPA and hibernate
> hibernate has made great advances from version 2 to 3, after
adopting JPA
> standard,
> which was really merging the hibernate, toplink, kodo, castor, and other
> ORMs
>
> speaking of my self, currently I don't have any serious design
problem with
> Hibernate,

Hibernate is a mature product for sure, but from time  to time you get
stuck on various design or implementation flaws it has, which takes
80% of your time. There are still a lot of bugs in various places (the
famous criteria/sub criteria bug, problems with criteria and
components, ... ), the crap CGLIB library used in proxying is a pool
of bugs, and there are a lot of places for improvement which are left
out. Look in hibernate JIRA to see how many issues are open, and
remember these are only part of user issues which manage to make it to
the open issues list. Other issues normally get ignored or closed by
the ever so arrogant hibernate team. What redhat/jboss have done is
leave out a framework with 90% popularity, to work  on a framework with
hardly 5% usage in java world.

> but from the time you have introduced me Wickets,
> I can't keep thinking about how could I have Inheritance in web UI
> technologies I use.

I dont get what you mean here. Can you clarify a bit ?