RE: JCA adapter question

2004-12-15 Thread John Gilbert
I got that far plus I added code to do container managed authentication.
Then I got pulled away before I could thoroughly test it. I can send out
the code and deployment descriptors.

The problem I was having was with transactions. After bouncing weblogic
everything disappeared.



-Original Message-
From: Brian DeHaven [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 15, 2004 4:44 PM
To: [EMAIL PROTECTED]
Subject: JCA adapter question

I have the JCA adapter mostly working in weblogic, but this isn't really
a 
weblogic specific question. If no one has converted it yet, only a few 
changes were needed so far.. such as using interfaces so you can cast
the 
connection proxy to something useful by the client.

I'm running into a problem with the 
WebDAVManagedConnectionFactory.matchManagedConnections call, however.
Once 
one connection is created, this method always matches with the first 
created connection and never returns null.. thus no new connections are 
ever created beyond the first one. I'm unsure if the Set of connections 
passed in represents all connections (active or inactive) or should only

include inactive connections. In other words, who should be determining 
that a new connection needs to be created? This matchManagedConnections 
method or the creator of the Set of connections being considered for a 
match?

I want to be sure this functionality (adding new connections at runtime 
beyond the first one) is working in JBoss, so I know if this is a
weblogic 
issue or a coding issue of the JCA adapter. Thanks for any help.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: JCA adapter question

2004-12-16 Thread Ryan Rhodes
Hi Brian,
I believe the set of connections that is passed to matchManagedConnections 
is only the inactive connections.  It's the containers responsibility to 
take care of that.

The reason this method always returns the first connection in the inactive 
set, is because we are not keeping any connection configuration state on the 
managedconnection.  We just setup the connection every time it is opened 
with WebDAVManagedConnection.open(), and we throw it away every time the 
connection is closed with WebDAVManagedConnection.cleanup().

The latest version allows for container managed authentication where the 
connection is created using a JAAS Subject, but I did not rewrite the 
matching to try to keep around the authentication information and reuse it 
by matching.

-Ryan Rhodes
From: Brian DeHaven <[EMAIL PROTECTED]>
Reply-To: "Slide Users Mailing List" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: JCA adapter question
Date: Wed, 15 Dec 2004 16:44:06 -0500
I have the JCA adapter mostly working in weblogic, but this isn't really a
weblogic specific question. If no one has converted it yet, only a few
changes were needed so far.. such as using interfaces so you can cast the
connection proxy to something useful by the client.
I'm running into a problem with the
WebDAVManagedConnectionFactory.matchManagedConnections call, however. Once
one connection is created, this method always matches with the first
created connection and never returns null.. thus no new connections are
ever created beyond the first one. I'm unsure if the Set of connections
passed in represents all connections (active or inactive) or should only
include inactive connections. In other words, who should be determining
that a new connection needs to be created? This matchManagedConnections
method or the creator of the Set of connections being considered for a
match?
I want to be sure this functionality (adding new connections at runtime
beyond the first one) is working in JBoss, so I know if this is a weblogic
issue or a coding issue of the JCA adapter. Thanks for any help.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]