PROGRAMMING : EJB done right?
I've just read an extremely exciting (!) article about the new EJB 3.0 Spec. It sounds great.
It's main aim is to get rid of all the guff that EJB suffers from - and it seems to succeed. It looks like a really 'usable' framework.
Little examples... All classes are now annotated POJOs so they can be tested easily, but this is especially useful with Entity Beans which you can now send across the network instead of Value Objects - so it looks like you are just accessing the entity bean directly! Also, the EQL which was very broken now seems to implement most of the decent SQL stuff, and also has a great feature where you can create objects within the EQL so you get a list of objects back instead of resultset rows.
I have to say I want to have a good look at this, I think it is potentially great (mind you, the .Net guys are probably laughing at me)
It's main aim is to get rid of all the guff that EJB suffers from - and it seems to succeed. It looks like a really 'usable' framework.
Little examples... All classes are now annotated POJOs so they can be tested easily, but this is especially useful with Entity Beans which you can now send across the network instead of Value Objects - so it looks like you are just accessing the entity bean directly! Also, the EQL which was very broken now seems to implement most of the decent SQL stuff, and also has a great feature where you can create objects within the EQL so you get a list of objects back instead of resultset rows.
I have to say I want to have a good look at this, I think it is potentially great (mind you, the .Net guys are probably laughing at me)
0 Comments:
Post a Comment
<< Home