These are only preconditions if they prevent Proxy generation or lead to non-deterministic results upon lookup/invocation. For example, if @Remote specifies a class that is not an interface, Proxy component should throw the error.
Adding a validation component to aspectize deployment rules based on available metadata can cover all cases and provide a pluggable mechanism looking forward. Less code in the Containers (EJB3 Core), less code in the Proxy stuff (where some of it doesn't belong).
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150175#4150175
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150175
ok, so it turns out that even tho the initial connection to jndi was happening the exported stub that was being returned still had an endpoint of localhost. This is because if the property java.rmi.server.hostname is not set it defaults to localhost, when the App Server starts up, setting this property is one of the first things it does.
Ive changed the jbm-standalone-beans.xml to inject the host property from the configuration object so that we only need to configure it in one place. The configuration property also sets the java.rmi.server.hostname property when the host is set.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4150133#4150133
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4150133