This update removes the need for any extra configuration when using the
default configuration of JBoss.  Extra config will be needed only if the
naming service is changed, or the handle requires extra environment
properties to construct the context.

It looks like the follow-up I added to the change note about the addition of
this feature did not make it to this list, so I am including it here:

<snip>

This behavior has been augmented slightly to prevent any
configuration complications for a default install.  By
default no properties need to be set to make use of this
feature.

The method in which InitialContextHandles are created has
been moved to a plugable InitialContextHandleFactory.  To
override the default behavior, set the system property:

org.jboss.ejb.plugins.jrmp.interfaces.InitialContextHandle.factory

to be the name of the class which implements
InitialContextHandleFactory.  If this value is not a valid
class or does not implement this interface then an exception
will be thrown (rather than assuming the default behavior).

There are two implementations of InitialContextHandle:

DefaultInitialContextHandle - inspects the local
configuration (used by default, hence the name).

PropertiesInitialContextHandle - reads the environment
properties used to construct the initial context from a
properties file (this is the previous behavior).

To make use of the properties based configuration, change
the factory to:

org.jboss.ejb.plugins.jrmp.interfaces.PropertiesInitialContextHandle$Factory

and set a system property defining the url of the properties
file to read:

org.jboss.ejb.plugins.jrmp.interfaces.PropertiesInitialContextHandle.environment=<some_url>

</snip>

I updated the testsuite with the new jboss-client.jar, does anyone know why
the ./dist/bin/* scripts use checked in versions of these libraries, but
./src/build/run_tests.xml uses the built files from the jboss module?

I checked that if the JBoss server was using a different port number for the
naming server that the handles still work correctly.

--jason


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to