It's definitely being ignored. The logs are producing:
09:02:49,646 INFO [ProxyDeployer] no declared remote bindings
09:02:49,646 INFO [ProxyDeployer] there is remote interfaces
09:02:49,646 INFO [ProxyDeployer] default remote binding has jndiName of com.mycompany.util.Proxy
So I'm left with the question: is this a bug or user error?
Thank you Darran,
META-INF/ META-INF/MANIFEST.MF com/ com/mycompany/ com/mycompany/proxy/ META-INF/jboss.xml com/mycompany/proxy/DefaultProxy.class
The actual proxy interface is in a jar next to proxy.ejb3, called util.jar:
META-INF/ META-INF/MANIFEST.MF com/ com/mycompany/ com/mycompany/util/ com/mycompany/util/Proxy.class
where Proxy is a simple interface with the @Remote annotation.
I've been through the tutorial, which is where I got the jboss.xml from. The only other thing I see that would possibly apply is the "JNDI Bindings" section which would unfortunately tie the code itself to JBoss (not that I have anything against JBoss). If possible, I would like to keep anything container-specific in the configuration files.
Thanks again for your response,