[EMAIL PROTECTED] wrote:
I don't think you are disagreeing because I agree with both of you.
There's something in the Java water that just leads to overly abstracted
software... I fall for it from time to time even though I'm getting
better at seeing it.
Back on topic a bit, Jonathan, I looked at your database package and I
like what you have there. I was wondering how you see EJB3 and Hibernate
fitting together in your wicket-contrib-data package. Are you working
with pre-3.0 Hibernate? My understanding is that the ejb3 version would
have an EntityManager injected into the code by the container instead of
the session object. Are you planning on creating a new
wicket.contrib.database.ejb3 package or would this still be considered
Hibernate?
i'm using hib3 but not entity manager. i don't know yet how that would
work.
I guess in a nutshell, what I'm asking is, "If I want to make an
annotated Hibernate 3/Ejb3 version of your database package, should I
write a new package in the same structure as the one you wrote or is
yours going to encompass that?"
good q. don't have time to learn ejb3 right now. maybe you will have
opinions on that soon...
feel free to contribute!
jon
I just realized this is another thread that should probably be on the
dev mailing list.
-paul
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jonathan
Locke
Sent: Saturday, July 30, 2005 4:43 PM
To: [email protected]
Subject: Re: [Wicket-user] Hibernate/EJB3.0
nothing's perfect. i'm not talking about perfect. that's religion.
i'm just talking about
things where people bothered to work problems until the solution was not
only workable
but just reasonably good and simple. there are so very few things like
this given the
billions and billions and billions of dollars that have been pumped into
software.
Eelco Hillenius wrote:
I agree on the interface issue, but I also think you put it too strong
when you say it is just the fads that say this. Software engineering
is still an immature industry, so we have to look for right principles
and best practices to get us to the next step. The Abstract Class vs
Interface is pretty controversial (though again, I'm all on your
side), but having 'interface based design', can save you from designs
that aren't as good. I guess just as AOP can save you from less than
perfect designs. And lets be honest, a perfect design is really hard
to get, and Wicket surely is not perfect yet either. And OO as put in
Java is not nescesarily the end of the road either.
Eelco
Jonathan Locke wrote:
thanks. it might not be complete yet, but i hope it's a good start
at something simple.
<rant scope="general">
this rant isn't in response to you or anyone on this list... i'm just
venting....
one of the many reasons i'm so sick of software lately is that nobody
ever takes the
time to think things through. that's why we've got all these stupid
industry fads
and buzzwords and people naming classes "EntityBaseImplDelegate".
there is a time and a place for abstraction and flexibility.
everything should not
be malleable. everything should not be named abstractly. EVERYTHING
SHOULD
NOT BE AN INTERFACE! is anyone out there listening to me!? and the
latest
buzzword should not be in every project. trying to blindly apply
design patterns,
interfaces and fancy abstractions is not always a sign of mature
design. in fact,
it's often quite the opposite! i'm reminded of this quote:
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&opÌk
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
