RE: [JBoss-user] Beans calling beans

2001-05-08 Thread Marko Štrukelj
Title: RE: [JBoss-user] Beans calling beans Hmm... OutOfMemoryError in situations when no large memory objects are allocated tipically means you have done a recursive method call and the method just keeps calling itself indefinately - or something equivalent is happening like one method

RE: [JBoss-user] Beans calling beans

2001-05-08 Thread Michael Lennon
it won't work carefully read this link: >http://www.jboss.org/documentation/HTML/ch06s05.html > >> try{ >> Object ref = jndiContext.lookup("SecurityManagerEJB"); >> }catch(Exception e){ >> e.printStackTrace(); &g

RE: [JBoss-user] Beans calling beans

2001-05-08 Thread Schouten, Andreas
If the beans are in the same jar, You don't need the reference tag. (Maybe than the server looks for the classes in the classpath and not in the jar file.) Happens the exception on runtime or deploy time? I think You already checked the path information in the jar for the classes

RE: [JBoss-user] Beans calling beans

2001-05-08 Thread Marko Štrukelj
Title: RE: [JBoss-user] Beans calling beans Leave everything as it is but try a lookup like this: Object ref = jndiContext.lookup("java:comp/env/SecurityManagerEJB"); And if it won't work carefully read this link: http://www.jboss.org/documentation/HTML/ch06s05.html

RE: [JBoss-user] Beans calling Beans

2001-04-20 Thread Swarr, Bob
I would suggest applying the model-view-controller design pattern to this function.   The model or data model would be an MBean loaded when the server starts.   The session bean could be a view-controller that provides data from the model to worker beans via method calls.  Any EJBs that us