am geting bit diff error..I read all the links.. which you gave ..but still am not geting it..cleared.
As I told you before am using weblogic8.1, first of all I would like to know do we need to give a name("Advisor") in JNDI in weblogic, as its mentioned in HFEJB page52 for RI Server. if you say that we have give the JNDI name in weblogic, where do we ned to give?
Hello. First of all you have to run ejbgen and obtain the remote component interface (advice) and remote Home interface (advice home) and also the ejb-jar.xml. Second you need to archive all these files in a jar according to EJB requirements with META-INF/ejb-jar.xml and advice classes. Third if it is not generated you need to create weblogic-ejb-jar.xml - the Bea weblogic deployment descriptor - and this is where you put your JNDI name. I have done a ejb-jar on Bea WLI without ejb gen so I am not fully aware about it's features kind of an ejb-doclet. Good luck! [ October 02, 2006: Message edited by: Mihai Lihatchi ]
Better, faster, lighter Java ... you mean Ruby right ?
SCEA5,SCBCD1.3,SCWCD5,SCJP1.4 - memories from my youth.
posted 13 years ago
I really thankful to man. I was worndering for the past 2 days.. you helped me a lot.
You told me 3 points.Actually I wrote only the bean, rest of the process done by WLS.
I already done the first point and I got Advice, Advicehome, ejb-jar.xml, weblogic-ejb-jar.xml
actally 1rst and 2nd point done by WLS.. it seems doclet is set like that..
I got the headfirst/AdviceApp.jar in that jar I got all the xml'es under META-INF/***.xml
Context ic = new InitialContext(); Object o = ic.lookup("Advisor"); // replace with YOUR JNDI name for the bean AdviceHome home = (AdviceHome) PortableRemoteObject.narrow(o, AdviceHome.class); Advice advisor = home.create(); System.out.println(advisor.getMessage());
can you please tel me where & how give JNDI name "Advisor".
I badly need your help Mihai. sorry to bother you.
Hello. You shoud focus on weblogic-ejb-jar.xml now. First of all the <jndi-name> should be
Remember that this is Bea specific and for other app server you need to use other deployment descriptors .. it has nothing to do with the certification objectives. When you do the lookup in the client you should do lookup for advisor.. something like