[Jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: org.jboss.remoting.CannotConnectException (ejb3)

[bendis <nu...@jb...>]

Hi!

@RemoteBinding annotation solves this problem, but IMHO very badly. IP addresses, ports etc. should *not* be directly in the Java code of beans! What if I move some beans to JBoss behind firewall? What if I change the port number? I must edit and recompile *every* EJB.

Specifying the adrress using this annotation is like hard-coding JDBC URLs directly into Java code!

This information should be stored somewhere in the JBoss configuration... And it is - the clientConnectAddress and clientConnectPort attributes in ejb3.deployer/META-INF/jboss-service.xml (see the post above). But EJB3.0 silently ignores this information and uses hard-coded default socket://0.0.0.0:3873 - unless specified by @RemoteBinding. My opinion is that @RemoteBinding annotation should have no clientBindUrl attribute. Instead, there should be some attribute which would refer to some specific org.jboss.remoting.transport.Connector MBean configuration.

What is your opinion? I consider @RemoteBinding.clientBindUrl as a serious design flaw - should I file a bug?

Regards,
Bendis

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882887#3882887

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882887