Hi,
i also spent a lot of time to configure and work this thing (as Marc mentioned
before) out. The Client should get the originalUrl (InvokerLocator) and not the
ip-adress from server. So i think a good solution would be to set the hostname
initially (at startup with --host=) which then will be used inside of
jboss-service.xml from ejb3.deployer as an part of the attribute InvokerLocator
(via ${jboss.bind.address}). Instead of ip adress resolving, this hostname
should be used for the mbean and the default entry for clientBindUrl when
registering (deploying) EJB3-Beans.
In addition to this default behaviour a developer should also have the chance
to override this by using Annotation @RemoteBinding(...clientBindUrl...) or the
much better way, as bdecoste and Marc mentioned before, via an entry in
jboss.xml.
Should this be possible or are we running into problems when using Jboss
Clustering?
Kind regards
Heiko
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944629#3944629
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944629
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
