+1
If your interfaces are in place you can pretty much change the persistence layer to whatever you like very quickly.
I'll check ibatis 2 out if it does mean editing lots of xml files :o)
On 28 Jun 2004, at 10:54, <[EMAIL PROTECTED]> wrote:
On 04/06/28 8:55, "Mark Lowe" <[EMAIL PROTECTED]> wrote:
The only thing thats stopped me using ibatis is that there's no xdoclet template thus the need to edit and maintain a bunch of mapping files, "YAWN".
iBatis has the DAO framework so you could switch from persistence layer with relative ease. You can use Hibernate and ibatis... no mapping needed (check ibatis 2.0)
More, if you start developing and realize that you made the wrong choice for persistence (slow performance, change of requirements) then you can still move with a reduced cost (only the DAO implementation is affected).
Pedro Salgado
Mark
On 28 Jun 2004, at 02:11, Vic Cekvenich wrote:
EJB is heavy, therefore slow and less scaleable. So in order to support a heavy transaction load, you would avoid it.
(and I think the reason somone mentioned iBatis is that it's popular and scaleable, more so that Hibrenate becuase it's lower to the metal (SQL))
.V
Irfandhy Franciscus wrote: . I am justscared that it would not be able to handle heavy concurrent transaction without EJB.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
