Hi, In my ejb examples i am able to create the home object..but while creating the remote object it throws an exception. I am able to see the jndi object on the jndi tree.i am using wls 6.1 please let me know the possible reasons.. thanks, trupti
hate to be blunt, but you're going to have to be more specific if you want anyone to provide any meaningful insight. perhaps posting the exception stack trace would help.
in your home interface, - do you have a create(...) method that matches an ejbCreate(...) method in the bean class? - is the create(...) method public? - and does it return an object implementing your remote reference? cheers, -miftah
hi, I have done all the things that you have mentioned earlier.. my create() method in the home interface matches with the ejbCreate() of the bean. create() method is public. The create() method returns the remote object. but still i am getting that error. I hope the problem is not with the wls6.1 as i am using the evaluation copy.. what i have observered is ..when i deploy the Bean on the wls console i see the check box checked meaning it is deployed. but when i view the jndi tree..suppose the name of the jndi tree is "helloWorld.hello"..i am able to see only the naming context & the Bound object is not visible..but when i shut down the server & restart it..& again build the example..it's getting deplyoed & i can see the naming context & the bound object too.. This is something wiered i have observed .i don't know the error which i am getting has some relation to this problem.. please let me know the reason if any body knows it.. thanks, trupti
as you are using the wls6.1 evaluation, its better to deploy your EJB manually(without using the console gui). For this, run the server in Development mode (for this set STARTMODE=false in your startWebLogic.cmd file). Once you are running in Development mode, you create your .jar file with all related files and copy this file to the 'applications' folder of your Server. Check the running default server's output buffer for any error messages/exceptions. If it is throwing some exceptions, the problem mostly lies within the deployment descriptors. Viewing the logs/wl-domain.log file will give you a better picture. ------------------ Take care r@njith