Title: [JBoss-user] calling EJB by using reflexion in a generic way
There has been some discussion about similar problems ( I think... ) on this list.
There is one I started. Follow the thread Blind Lookup. I'm still trying to solve my problem.
----- Original Message -----
Sent: Wednesday, May 16, 2001 7:15 PM
Subject: [JBoss-user] calling EJB by using reflexion in a generic way

Hi all,

I'm use JBoss 2.0 Final, and I want to do somethink that I think is not conform to the EJB 1.1 spec but can be usefull

So there is my problem:

I have a Junit test that call an EJB  A and call a method on it that call within JBoss an other EJB B.
To do that I use refexion and it work fine when I call A from outside JBoss ( I think it get the code base of proxies from the localhost:8083 setted by the WebService JMX component embedded in JBoss).

But when the call is within JBoss (ie A call B) I get the following  weird exception:

[A] [A.setSessionContext]
[A] properties setted
[A] [A.ejbCreate]
[A] try to call B ...
javax.naming.CommunicationException.  Root exception is [A] java.lang.ClassNotFo
undException: com.eonworx.impl.appl.common.ejb.BHome


the code that I use to call EJB is basicaly the following for the test code and the EJB A that call the EJB B :

try
                        {
                        EJBHome home;
                        EJBObject myBean=null;
                        System.out.println("try to call B ...");
                        home=(EJBHome)getHome("B",EJBHome.class);

                        //home = (EJBHome)m_jndiContext.lookup("B");

                        Method m=home.getClass().getDeclaredMethod("create",null);
                        myBean=(EJBObject)m.invoke(home,null);
                        ((call)myBean).callMe();
                        }
                catch(Exception e)
                        {
                        e.printStackTrace();
                        }


Why the EJB A cant retrieve the proxies using JNDI in a common way without ENC. Is there any constraint necessary at the container level?

Is there any way to bypass the specification and finding the proxies in the codebase.
One think I want not to do is to put the proxies of Beans that I want genericaly call in to the classpath to be able to change their

home interface and redeploy the beans without breaking the server.
I have some test code to run and to see the problem.

Regard,
david


david arnone
developer
the eon company
www.eoncompany.com

o 212.401.5028
m none
e [EMAIL PROTECTED]


Reply via email to