I think it's always neccesary to know where the HAJNDI ports and nodes are. You can configure clients to connect with a list of HAJNDI services. If one fails, the client try to continue with the next.
i.e. | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=localhost:1100,localhost:1200 | For your code, access to the cluster is now transparent. If you are going to change the cluster, just you'll need to change the configuration of the client View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865204#3865204 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865204 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
