> Ok, so at end last, I find out that a connection pool is not visible to
> the outside world. The reason I figured that is that Weblogic does allow
it
We see connection pools as strictly local things since they use VM-local
resources (i.e. connections). WebLogic may get around this by wrapping it in
a remote version, which is ok. If you make such a wrapper you are free to
add it to JBoss.
> Regarding the ...tcx.bind(..., saying it must come in my
> code is a real eye opener, I'll carry that bit of advice to my death bed.
Well, what did you expect? Since this is a binding that you want to perform,
for whatever reason, it must be done somehow in your code. Where and how you
do that is entirely up to you. I'd recommend a custom MBean that you add to
the server.
regards,
Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
