[jboss-dev-forums] [Design of EJB 3.0] - Re: @RemoteBindings and clientBindUrl - JNDI binding questio

[jaikiran]

"wolfc" wrote : 
  | 
  | The goal is to give the bean developer the ability to specify a client bind url per remote business interface. Now in your example you have 2 bindings and 1 interface.
  | 

I started off with this test based on what i read here http://docs.jboss.org/ejb3/app-server/reference/build/reference/en/html/transport.html#d0e786. The example there is similar, in the sense that it has a single remote interface but with 2 RemoteBinding.  Has that behaviour changed?

Currently I don't see a way where i can associate a remote business interface (rather than a remote jndi binding) with a client bind url? To make it more clear:



  | @RemoteBindings ( 
  |       {
  |          @RemoteBinding (jndiBinding=MyStatelessBeanWithMultipleRemoteBindings.REMOTE_JNDI_NAME),
  |          @RemoteBinding (jndiBinding=MyStatelessBeanWithMultipleRemoteBindings.ANOTHER_REMOTE_JNDI_NAME, clientBindUrl=MyStatelessBeanWithMultipleRemoteBindings.CUSTOM_CLIENT_BIND_URL)
  |       }
  | 
  | public class MyStatelessBeanWithMultipleRemoteBindings implements MyStatelessRemote, AnotherRemote
  | 

Currently, I can't specify that the @RemoteBinding with a CUSTOM_CLIENT_BIND_URL is for the "AnotherRemote" business interface.

"wolfc" wrote : 
  | In my mind clientBindUrl is an attribute of the remote business interface. 
  | 

Since the intention is to allow the bean developer to specify a client bind url per remote business interface, shouldn't the @RemoteBinding have a provision where the beanInterface can be mentioned. Maybe a "beanInterface" property to the @RemoteBinding annotation?. Just a thought, maybe there's a better way to handle this. In terms of API changes, not sure how big this change would be. 


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

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