anonymous wrote :
| Your doing it all wrong. Read my previous comments.
|
Lovely. I actually won a bet. I bet someone at JBoss that you wouldn't post a response
without saying something like this. Of course, given your nature I probably should have
given him odds.
anonymous wrote :
| When JBossTS asks you to recover, you iterate over this repository and retrieve
| all the XAResources.
|
Ok, let's take a simple scenario:
JDBC based deployment using a security domain with a login config of
CallerIdentityLoginModule. Just because the TxManager is deployed, doesn't mean the
XAResource gets created. This comes off the underlying Connection which is only created
when the pool is first used. So, what goes in the repository in this case? What do I
iterate over during recovery?
How about a JDBC deployment that only support application-managed security? What if this
is required information and can only be done via
getConnection(username,password)?
anonymous wrote :
| We discussed this nearly two years.
|
Well, unless you think my name is something other than Weston (which you actually seem
completely incapable of remembering) we haven't. I have been here one year, and let me
tell you I have loved every day!
The example you posted as a sample security configuration basically just offloads what
would be in the external config file to the *-ds.xml, fine. I am not sure why you are
listing a local-tx-datasource as these won't be supporting recovery, but no matter.
So, I am assuming that your
| <recovery-security-domain>Recovery</recovery-security-domain>
|
is defined in login-config, so we have yet another piece of external information to
'kludge' this together it just happens to be in a 'comfortable' place that
you are familiar with.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009420#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...