Don't want to hard code the dynamic IP for @RemoteBindings->

[slimamar]

Hello,

I have a problem with :
@RemoteBinding(clientBindUrl = "socket://0.0.0.0:3873")

It works fine with JBoss 5.0.0Beta4 but not with JBoss 5.0.0.GA.
The property "jboss.bind.address" is set and the hostname '0.0.0.0' is not replaced
from the client.

For more information see : http://www.jboss.com/index.html?module=bb&op=viewtopic&t=102662

[jaikiran]

Looks related to this http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146770

[alrubinger]

Please create a JIRA for this as a feature request under EJBTHREE.

S,
ALR

[slimamar]

A JIRA has been created :
https://jira.jboss.org/jira/browse/EJBTHREE-1650

It's not a feature request but a bug because with this restriction in JBoss5.0.0GA
it's impossible to have multiple remoting binds for an EJB.

[alrubinger]

"slimamar" wrote:
https://jira.jboss.org/jira/browse/EJBTHREE-1650

Thank you for opening this. I've deprioritized it from critical, changed from "bug" to "feature request", and renamed "Need EL-replacement within @RemoteBinding.clientBindUrl so connect addresses are not hardcoded".

"slimamar" wrote:
it's impossible to have multiple remoting binds for an EJB.

Nope, you can have as many @RemoteBindings as you want. However you must currently denote an explicit address within clientBindUrl (if it's specified). @see my comments in the JIRA for workarounds.

S,
ALR