-
1. Re: Failed EJB3 JNDI lookup.
dwebster Nov 6, 2005 3:21 PM (in response to dwebster)Actually, it is the FIRST ProxyDeployer message that looks supicious, the one about no declared remote bindings....
-
2. Re: Failed EJB3 JNDI lookup.
dwebster Nov 6, 2005 4:39 PM (in response to dwebster)Answering my question, but I've got it working now. Things are a bit pickier now in the way one passes a method call via the Proxy now. The code I was using before to call a method taking no parameters was :
InitialContext ctx = new InitialContext();
Object obj = ctx.lookup(invokeObj.getClassName());
return(obj.getClass().getMethod("methodName",class[0]{void.class}).invoke(obj,Object[] {}));
For whatever reason that seemed to work, but the class[0]{void.class} is bad unless the method declaration in the EJB is explicitly methodName(void);?? How odd is that? So if you have methodName() remove the void.class from the getMethod call and leave it just {}. Duh.... The ProxyDeployer can now find the method.