[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1650) Need EL-replacement within @RemoteBinding.clientBindUrl so connect addresses are not hardcoded

Need EL-replacement within @RemoteBinding.clientBindUrl so connect addresses are not hardcoded ---------------------------------------------------------------------------------------------- Key: EJBTHREE-1650 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1650 Project: EJB 3.0 Issue Type: Feature Request Environment: CentOS release 5 (Final) Reporter: amar slimane Assignee: Andrew Lee Rubinger With JBoss5.0.0.Beta4, it's possible to specify 'jboss.bind.address' as a remoting binding with setting 'clientBindUrl' to 0.0.0.0 : @RemoteBindings({ @RemoteBinding( clientBindUrl="socket://3873:", jndiBinding = "jndiBind1") , @RemoteBinding( clientBindUrl="sslsocket://3843:", jndiBinding = "jndiBind2") , @RemoteBinding( clientBindUrl="https://0.0.0.0:8443/servlet-invoker/SSLServerInvokerServlet", jndiBinding = "jndiBind3") , }) This don't work with JBoss5.0.0.GA and it's impossible to have multiple remoting binds for an EJB. It's critical for our application and we don't know if there is a workaround. This issue is probably relative to https://jira.jboss.org/jira/browse/EJBTHREE-1610