The only thing the remote client really needs are the remote and home interfaces. I'm not too sure what is meant by "stubs", but as long as you define the remote and home interfaces of each EJB you want to access remotely in the deployment descriptors (ejb-jar.xml and jboss.xml) you should be sweet. It sounds like you may have to look more in depth at a general introduction to j2ee and enterprise java beans. There are a heap of books available on this subject. Getting a remote client to connect to JBoss was non-trivial for me in the beginning, but looking at Enterprise Java Beans 3rd Edition by Richard Monson-Haefel and working through the JBoss workbook based on this book got me started. The workbook is available from this site for free. Download the workbook and code which doesn't go into much depth but does give you a lot of working examples of remote clients as well as invaluable information on how to configure JBoss and the clients to work.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822468#3822468 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822468 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
