Hey
[EMAIL PROTECTED] wrote:
> Trying to inderstand the new JDBC 2.0 standard extensions.
>
> 1. the Connection Poolng section (6) pg 17 para 2 says
> "a middle tier server who wishes to implement connection pooling should provide a
>data source class"
>
> If the middle tier does not wish to support "DataSource" class who implements the
>"DataSource" and who registers it in the JNDI?
Then the middle tier does not wish to support JDBC 2.0 Connection
Pooling...
> 2. The document only says that app server need to implement "DataSource" and JDBC
>vendor "DataSource_intf", and does not explain as to why the app > server need to
>implement this?
> Can't the app server make use of DataSources registered in the JNDI by the Database?
Where did you read this? I don't see any reason as to why the server
should implement DataSource. The database does not bind the DataSource
into JNDI. The system administrator typically names the DataSource
implementation in his server configuration tool and since DataSource's
must follow the JavaBean API guidelines when it comes to configuration
(see JDBC2.0, section 5.3) it can be easily deployed in a server without
the DataSource being implemented by the server vendor.
> 3. Can't we bypass the app server once we connect to the database via JDBC,
>especially to handle distributed transactions?
How do you intend to do this?
> 4. If we have an DataSource (with XA support) registered in JNDI and a TM which can
>manage distributed transactions.
> What exactly does the EJB framework need to handle to support application level
>transaction demaracation?
> WHY?
The tx demarcation mgmt tells the TM (roughly) when to start new tx's,
and when to commit or rollback them. How should the TM otherwise get
these calls do you suggest?
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
