Now, just a couple implementation notes on this.

First, I don't think writing this data/jnp-service.url file is a proper function of the NamingService, so I'll write a separate service to do it and inject the NamingService as a source of information.

Second, the proper ultimate source of this URL(s) is org.jnp.server.Main, since that's who opens the socket. That will require a new release of jnp-server.jar. I'll ping Jason as to whether that's feasible for 5.1.0.GA. If not, for 5.1.x I'll just put the logic in the NamingService class, which is part of the AS codebase itself. Not ideal, but OK.

I'm trying to track down someone to answer my question about 0.0.0.0. I wrote a simple method to create a List that I can move into org.jnp.server.Main in about 5 mins if that's what they want.

Just chatted with Ian and he says JON already has logic that recognizes a plugin config property with a value like "jnp://0.0.0.0:1099" and understands that the agent should connect via 127.0.0.1. So I think just writing that is fine. I'll add this in right now.

That's where I'm doing it yeah, unless you say not. I'd put it in trunk as well.

I'm about to commit it to the branch, but NamingMCUnitTestCase.testMainBean fails. Is that a known issue? I think I've commented out my change and the test for it, and I still see that failure.

Thanks; that was it. I'm an idiot and forgotten I'd started an AS instance earlier.

This is checked in on Branch_5_0.

Thanks; it's done in trunk as well. I added a List property there as Main accepts multiple bind addresses.

Both trunk and Branch_5_x are updated. Thanks again, Scott.