I was already wondering why to use JDO when someone is already using EJBs. This feature confuses me more !
Make a POJO persistant archieve the same goal as an Entity bean ? so why bother : I do not see any other advantages than the speed of developpement (no EJB overhead, just POJO).
Back to a more technical question : to make something persistent, you should define a way to store it in a secure place. To work at a field level (for the queries for example), you should store the object's fields in an independant way.
Question is : what storage layer to use and where to declare all this (fields mapping and relative stuff)?
I guess a database is the layer and a config file does the mapping (the page that is still under construction) but (database + mapping configuration files) = ejb ...
Ionel
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
