-
1. Re: org/jboss/system/ServiceMBeanSupport
juha Oct 8, 2003 6:37 PM (in response to zuurbier)You should use JBoss 3.2.1 instead.
-- Juha -
2. Re: org/jboss/system/ServiceMBeanSupport
zuurbier Oct 9, 2003 12:30 PM (in response to zuurbier)Thanks, indeed with jboss-3.2.1 I get a correct result.
-
3. Re: org/jboss/system/ServiceMBeanSupport
noleme Feb 26, 2004 6:17 PM (in response to zuurbier)Does this mean that one cannot write standalone client applications for 4.0DR2 ???????
-
4. Re: org/jboss/system/ServiceMBeanSupport
noleme Feb 26, 2004 6:37 PM (in response to zuurbier)OK, here is the deal... One doesn't have to downgrade to 3.x to make the standalone applications running under JBoss 4.0DR2.
This is the list of libraries needed:
log4j.jar
jboss-all-client.jar
jboss-system.jar
jboss-jmx.jar
jboss-remoting.jar
dom4j.jar
Also, looks like you DO NOT need to pass this in your environemnt:
env.put("java.naming.factory.url.pkgs", "org.jboss.naming.client");
And the final key is:
Add a file called jndi.properties to your client class path with the follwing content:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://localhost:1099
java.naming.factory.url.pkgs=org.jboss.naming.client
(change the host and the port if needed)
Anyone could argue about the restrictions of this approach, but it will help at least to unit test your beans :)