Sunit,

please see inline ...

Werner

PS Btw, apologies for using your surname to address you ... :-(,

On Tue, 20 Jul 2004 07:10:48 -0700, Kavathekar, Sunit wrote:

>Sorry about the html. It was  not intentional. The "module logon" I mentioned is just 
>a stored procedure call that identifies the session to the db owner 
(who may be monitoring usage). 
>
>For example :
>
> private void logon(int db) throws SQLException {
>        String appName              = System.getProperty("appName", "UnknownApp");
>        String programName          = DB_MODULE_PREFIX + appName;
>        String programParentName    = "";
>        String programArguments     = "";
>
>        CallableStatement logon = connections[db].prepareCall("begin module_logon(? , 
> ? , ? , ? , ? , ?); end;");
>
>        logon.setString(1, programName);
>        logon.setString(2, programParentName);
>        logon.setString(3, programArguments);
>        logon.registerOutParameter(4, java.sql.Types.INTEGER);
>        logon.registerOutParameter(5, java.sql.Types.INTEGER);
>        logon.registerOutParameter(6, java.sql.Types.INTEGER);
>
>        logon.execute();
>
>         etc........... 
>
>
>The point is that this is part of the connection initialization. I have, in effect, 
>bypassed the problem by simply providing a DataSource implementation of 
my own which maintains a connection pool and calls the procedure for each connection - 
I was wondering if there was a way to do this while still using 
the Castor connection mechanism.
If you happen to have your own DataSource implementation, why not use it with Castor 
in the standard way. Just specify your DataSource 
implementation in the JDO config file (formerly database.xml), and you should be fine.

>
>Thanks for the info.
>
>Sunit
>
>
>-----Original Message-----
>From: Werner Guttmann [mailto:[EMAIL PROTECTED] 
>Sent: Monday, July 19, 2004 1:09 PM
>To: [EMAIL PROTECTED]
>Subject: Re: [castor-user] Castor connections
>
>
>Kavathekar,
>
>please see below ...
>
>Werner
>
>PS Please refrain from sending HTML formatted emails to this mailing list in the 
>future (as per our mailing list guidelines).
>PSS It would be nice if you could use a [JDO] on the subject line to indicate that 
>your question is JDO specific (again as per mailing list guidelines).
>
>--Original Message Text---
>From: Kavathekar, Sunit
>Date: Fri, 16 Jul 2004 10:51:22 -0700
>
>Castor connections 
>
>Questions about Castor jdo connections.  
>
>1. I need to have the connection do a "module logon" to the database before it 
>executes any statement. Is there a way to do this without conducting 
surgery on the Castor code base? . Follow up question : If surgery must be conducted 
(and code introduced to have Castor do a module logon right 
after it opens a connection) what classes should I look into?  
>
>werner> Can you please expand on what needs to be done ? E.g a small code fragemnt 
>using JDBC that explained what you are trying to achieve.
>
>2. Where can I find examples of poolman setup for Oracle connection pools used within 
>Castor?  
>werner --> In the documentation (e.g. http://castor.exolab.org). Iow, there is a full 
>sampelk of how to use PoolMan.
>
>3. Where can I find examples of OQL queries  with all the different features?  
>werner --> src/examples/jdo ....
>
>Thanks,
>Sunit  
>
>
>
>-----------------------------------------------------------
>If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a 
>subject of:
>        unsubscribe castor-user
>
>



----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-user

Reply via email to