Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1650

Need EL-replacement within @RemoteBinding.clientBindUrl so connect addresses are not hardcoded

    Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      CentOS release 5 (Final)

      Description

      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

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  alrubinger Andrew Rubinger
                  Reporter:
                  slimamar amar slimane
                • Votes:
                  5 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated: