[adrian.brock]

What's the issue with adding Derby to thirdparty?
Or even writing a mock XADataSource?

[aloubyansky]

You need to identify which of the xadatasource properties identifies the server,
e.g. for mssql it is "ServerName"

<url-property>ServerName</url-property>
<url-delimiter>|</url-delimiter>

Done.

[aloubyansky]

The XADataSource should just be a factory, it should be the connections that are the
heavy weight objects.
I'd guess this is the usual "You don't pay for what you don't use"
philosophy that JBoss normally does.

I could also instantiate them lazily. But then I would have to keep initialization data per datasource. As you said, datasources themselves don't look heavy weight. That's the reason for my question whether it's a big deal. It doesn't look to me as it is.

It looks like the only change you made to the existing stuff was to make
the xa props a protected field, so I don't see why it would be problem backporting
to JBoss4 (assuming you didn't break the stylesheet :-).

Not a problem at all. I just want to port less times if there are issues.

Do you have it documentated somewhere on the WIKI (as experimental)?
http://www.jboss.org/wiki/Wiki.jsp?page=JBossJCA

Will write something today or tomorrow.

and add a subtask here:
http://jira.jboss.com/jira/browse/JBAS-1597

Yes, will do. The DTD already has ha-local elements.

[aloubyansky]

What's the issue with adding Derby to thirdparty?

The issue is actually to take care of it :)

Or even writing a mock XADataSource?

That's what I'll do probably.

[aloubyansky]

Do you have it documentated somewhere on the WIKI (as experimental)?
http://www.jboss.org/wiki/Wiki.jsp?page=JBossJCA

Yes, http://www.jboss.org/wiki/Wiki.jsp?page=JBossJCADatabaseFailover. It's linked from the main JCA page under 'Database failover' in the Features section.

What about distribution and deployment of the HA connection factories? Currently, it's manually from the source.

[adrian.brock]

Just copy the rars to docs/examples/jca

[aloubyansky]

It seems like all is done. Should the issue be closed?

[adrian.brock]

Go ahead.

Raise some new tasks in JIRA for any improvements you think should be made
in future versions (including integrating the HA behaviour with the main RARs).

[norman.richards]

I see ha-xa-datasource on the wiki but not in the jboss_ds DTD. Is it valid? If it is, the DTD should be updated so I can generate the schema diagrams for the book.

[adrian.brock]

??? I think you are looking at the wrong dtd?
http://cvs.sourceforge.net/viewcvs.py/jboss/jbosscx/src/resources/dtd/jboss-ds_1_5.dtd?r1=1.1.2.4&r2=1.1.2.5

[norman.richards]

Woops. My CVS was a couple days out of date. I should have updated before posting just to be sure. My mistake - sorry for the confusion.

[kanth_seenu]

The documentation @
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossJCADatabaseFailover

says it is in experimental state. Is that in experimental still (4.2)? Please explain

If I have to do some specific actions on a URL switchover, what should I do

[adrian.brock]

No, this service is no longer experimental.

In fact, in jboss-head (JBoss5) the failover config is part of the main
*-datasource configurations making the ha-*-datasource configs redundant.

To my knowledge there has only ever been two bugs reported in the usage of this
feature.

1) An NPE when you misconfigured it (instead of it telling you what you did wrong)
2) A spelling mistake in the configuration option name

[kanth_seenu]

Hi Adrian,

Sorry to post this user question here.

Hope you answered my first question. But not the second one about listening to datasource failover.

I have even posted in users forum with no response yet
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054190#4054190

Can I get any help in this regard.