org.jboss.naming.ExternalContext MBean

[pstephen]

Can the org.jboss.naming.ExternalContext MBean be used to aggregate the name spaces of multiple JBoss instances? Or is there a better way to do this?

[adrian.brock]

Sounds like clustering?

Regards,
Adrian

[pstephen]

Depends on your definition of clustering. I want to be able to deploy a system that has three subsystems across three seperate machines. I thought creating a single namespace for that environment would make things easier to maintain.

[adrian.brock]

Sorry clustering is too general a term.
A farm is more accurate. You deploy a bean on one machine
and it gets copied to others in the cluster.
That way you have the advantage that the bean is always
available locally.

An aggregated jndi namespace doesn't give you this.
The bean is available in the local jndi namespace,
but any invokes have to go over the wire to where the
bean is really deployed.
Of course, this might be exactly what you want?

Regards,
Adrian

[pstephen]

Aggrevated name space is what I'm looking to implement.

1. Can org.jboss.naming.ExternalContext be used to implement this?

2. If it can what would the MBean's properties file entry for java.naming.provider.url look like: jnp://host.host.com:1099?

[adrian.brock]

I don't see any reason why they cannot be aggregated.

Have you seen this link?
http://www.jboss.org/online-manual/HTML/ch13s126.html

The properties should be same as connecting from
a client. So yes you need to specify the provider.url

Regards,
Adrian