When a java programme is executed by using the command 'java classname' a process called the JVM or Java Virtual Machine is started to execute the bytecode in the specified class.
By starting JBoss and your application separately they are both running in their own JVMs and will both have their own java process running. Local insterfaces can only be used by components running within the JBoss JVM, this is why your servlet is able to access them. Generally access to entity beans should be wrapped by session beans and your remote application can then call the remote interface of the session bean that will then use the local interface of the entity beans. Switching to using remote interfaces for your entity beans will stop you from making use of CMR if you require it later. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852179#3852179 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852179 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
