Thank you Darran,

proxy.ejb3:

  | 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,
Mike

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

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


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to