Re: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossJCADatabaseFailover
I'd like to slightly refactor the ha-local-rar stuff so that it can support more than just "sticky round-robin"; the use case being to share the load across multiple read-only databases.
The obvious way to extend HA would be to add an additional configuration key that either indicates a Java class to use (implementing, say, URLSelectorStrategy) or some sort of general configuration value set, e.g. "SRR", "RR".
One complication I see is both XA and non-XA have their own URLSelector implementations. (This I think can be easily fixed.)
If I could solicit your opinion on what the configuration names and class layout should be, I can take a stab at it.
I also don't see any unit tests for this functionality in HEAD -- are there any?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994030#3994030
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994030
It currently does not support a j2ee datasource, that is planned for post-GA. There are known issues with the connection pooling (3cpo) and hooking it up to use a datasource. The direction taken when writing the message store was to work as a totally standalone message persistence mechanism. Now that we have started packaging SARs I need to revisit this so that we can in fact hook into a datasource. It is possible, but I know it has problems. Since we can't introduce any code changes that would potentially break anything, I have held off on this till after the G.A.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994003#3994003
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994003
Adrian
I presume this integration is a requirement for the implementation of the management interface to the ProfileService? i.e. this is the MetaData which the management related portions of the ProfileService is going to need to override.
What are the next steps to generating a replacement for the current ManagementView/ManagedObject api?
When do you see the work to define a mapping from the ManagedObject view to the deployment MetaData view fitting in? Can it be done after an initial cut of the ManagementView/ManagedObject api has been committed?
Thanks
Charles
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993999#3993999
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993999
I did a simple inner complex type naming modifications of spring-beans.xsd, trying to match it as best as possible to our bean-deployer.xsd.
But now I'm stuck with wrong interceptor being used while trying to handle my xml - so I get a CCE.
| Caused by: java.lang.ClassCastException: org.jboss.beans.metadata.plugins.AbstractListMetaData
| at org.jboss.kernel.plugins.deployment.xml.EntryValueInterceptor.add(EntryValueInterceptor.java:41)
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:1034)
|
Trying to figure out what can cause this did make me find some other problems and new features, but I simply cannot get my first test (DescribeSpringTestCase) working.
Ant [test] build support for spring-int module is commited, but DescribeSpringTestCase currently surpresses the exception.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993972#3993972
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993972