OK, time to learn the JCA pools!
Scott M Stark wrote:
> The JCA architecture provides a standard mechanism for managing connections.
> It uses a callback mechanism to notify the connection user of changes in its
> state:
>
> public interface javax.resource.spi.ConnectionEventListener {
>
> public void connectionClosed(ConnectionEvent event);
>
> public void connectionErrorOccurred(ConnectionEvent event);
>
> // Local Transaction Management related events
>
> public void localTransactionStarted(ConnectionEvent event);
>
> public void localTransactionCommitted(ConnectionEvent event);
>
> public void localTransactionRolledback(ConnectionEvent event);
>
> }
>
> ----- Original Message -----
> From: "Guy Rouillier" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, July 02, 2001 11:10 PM
> Subject: Re: [JBoss-user] Strange Behavior When DataSource goes down.
>
>
>
>>I see one problem here and one issue.
>>
>>Problem: There is no standard, cross-vendor approach that I'm aware of to
>>test to see if a database connection is still alive.
>>
>>Issue: My opinion is that we should try to standardize a solution whose
>>semantics work for any connection oriented resource, not just databases.
>>Something like a standardized "boolean isConnected()" method that would
>>
> work
>
>>equally well for connections to an email server or to a database server
>>
> (for
>
>>example.)
>>
>>
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
