The local use of the mbean will not use this as you say its a bound property of the mbean the service requesting portmapping is talking to. This information needs to be part of the ServiceBinding object for use in remote access to a central authority as well as debugging.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Mike Finn" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 24, 2002 6:18 AM Subject: RE: [JBoss-dev] Re: [JBoss-user] JBoss in a multi developers environment Scott, Does the 'server name' (server identity) need to be part of the "getPort" request, if it is spec'd in the svc bind mbean config? if the server name was set on the mbean, then the port maps could be keyed off that (in addition to service name). So, the request for getport could assume the 'curent' server name for the port lookup. Or am I missing something? (been known to happen) #mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Scott M Stark Sent: Monday, May 20, 2002 4:52 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Re: [JBoss-user] JBoss in a multi developers environment > > > // The service JMX name > > String jmxName; > > // The virtualHost the service wants to bind to which may be null > > String virtualHost; > > // The name of the JBoss service instance to support always giving an > > // instance the same values > > String serverName; > > > I'm lost. What is this? Can you give an example? > Its what I have been referring to as the starksm and dsundstrom config instances. Say we setup two JBoss instances of main.jboss.org. As Dan is saying, I don't want to have to change my configuration to connect to my instance each time the server is restarted. So when Jason configures my instance he adds: <mbean code="...ServiceBindingMgr" name="...,service=ServiceBindingMgr"> ... <ServerName>starksm</ServerName> </mbean> while for your instance he adds: <mbean code="...ServiceBindingMgr" name="...,service=ServiceBindingMgr"> ... <ServerName>dsundstrom</ServerName> </mbean> Now there can be a static configuration for our instances for which the client ports, address in use is invariant across instance restarts. > > > // The default port > > int port; > > // The default interface > > InetAddress bindAddr; > > > Of these values, would the ServiceBindingManager only be allowed to > change virtualHost, port, and bindAddr? > Yes. > BTW, do you actually like this idea Scott? > Yes, its a definite improvement over what we have. In the future I would like to see this integrated with a client side naming service but as I said that is another layer. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
