Hi, Don't worry too much.
Apache Derby is IBM (ex Sybase) Cloudscape donated to the open source community and rebadged. If you use stand alone processes, only one process can access Cloudscape/Derby databases - as you know. But IBM also provided a server that would allow multiple connections, and provided the same functionality within connection pools in an application server. So you should write your entity layer to persist to the database through pooled connections to the Derby/Cloudscape database. Assume that the connection pool and underlying software will handle multiple connections. This still leaves you with the normal problems. You may need, or want, to use Bean Managed Persistence because your objects don't look like rows in a relational database (mine never do). And you need to make sure that, when dealing with updates on multiple tables, you always update tables in the same order to avoid deadlocks. But at least you don't need a special pattern. James View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862156#3862156 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862156 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
