Using databases and container events?

Question

I'm having trouble finding documents show how one should use databases and listen for container events? I'm using Berkley Java DB. I'll need all my remote object to have access to the database. How do I pass that in? Custom adapters? Also, when Tomcat shuts down I need to close the database, how would this be down? Custom adapters? So I may be answering my own question, but I'm asking cause I really don't see anything in the documentation that points this out. It really looks like I'd be using singletons and factories for this. I could register a Servlet or Servlet Context to listen for Tomcat events, but I figured it couldn't hurt to ask others using Blaze, as I'm very new to it. Thanks.

Answer 1

So how would you tell Blaze to use this? Is there something you put into the config file? My thoughts on all this is to use PicoContainer to manage all services then create an adapter to inject all resources when creating remote objects. But this seems a little heavy if Blaze can do all this for me. The adapter seems like the injection point to me. Is that not what it's used for? Or is using it like that bad practice under Blaze? I've read all I can find on Blaze, so either it's missing docs, or I'm not finding them all. If I'm missing them, by all means let me know where to go. I don't want to ask questions that are already answered in documents else where.
On Tue, May 20, 2008 at 10:51 AM, Mete Atamel <
[email protected]> wrote:
A new message was posted by Mete Atamel in
General Discussion --
  Using databases and container events?
I think it's mainly in JavaDocs but here's a sample I have where I check to make sure the HSQLDB is running as the BlazeDS starts up:
import java.sql.Connection;
import java.sql.SQLException;
import flex.messaging.config.ConfigMap;
import flex.messaging.services.AbstractBootstrapService;
public class DatabaseCheckService extends AbstractBootstrapService
    // This is called right before server starts up.
    public void initialize(String id, ConfigMap properties)
        Connection c = null;
        try
            // Check that the database is running...
            c = ConnectionHelper.getConnection();
            // ... if yes return
            return;
        catch (SQLException e)
            System.out.println("DB is not running!");
        finally
            ConnectionHelper.close(c);
// This is called as server is starting.
    public void start()
        // No-op
// This is called as server is stopping.
    public void stop()
        // No-op
View/reply at
Using databases and container events?
Replies by email are OK.
Use the
unsubscribe form to cancel your email subscription.
"All that is necessary for the triumph of evil is that good men do nothing." - Edmund Burke