nrkonjeti

 Profile Answers by nrkonjeti Questions by nrkonjeti

• Aug 3rd, 2006

Generally, we write 1)Home Interface,2)Remote Interface,3)EJB Bean class.explaction of 1: Home interface contains the create method, which is used to access EJB Bean Object at client side.2: remo...

Answer Question  Select Best Answer

krishnaprasad

• Jun 21st, 2006

using pool tag in xml file it is possible..ok

Answer Question  Select Best Answer

Amrita Mathur

• Jul 13th, 2006

Hi,All the applications are deployed in teh same way on WLs 9.1.Please see the instructions on the following link and deploy the EJB application:http://e-docs.bea.com/wls/docs92/ConsoleHelp/taskhelp/applications/DeployEnterpriseApplications.htmlRegardsAmrita

Answer Question  Select Best Answer

srikanth-wipro

• Nov 3rd, 2006

 BMP- in bmp u should write jdbc code explicitly for accessing the database. ADV- Container Independent DisAdv-Database dependentCMP- in cmp cantainer will write all jdbc logic u just m...

Answer Question  Select Best Answer

madhu

• Oct 14th, 2006

its just like a unique identity.every entity bean has a primarykey class .in that we have to write code for finding the entity bean.in that class we have to implement hashcode() and equals().

Answer Question  Select Best Answer

Raj

• Nov 6th, 2006

When ejbFind/ejbSelect(select query) fails entity bean will throw FinderExceptionWhen ejbCreate(insert query) fails entity bean will throw CreateException

Answer Question  Select Best Answer

anindita

• Oct 10th, 2006

It is usually thrown from ejbLoad() and ejbStore() methods. This occurs when the row the entity bean tries to update doesnot exist.

Answer Question  Select Best Answer

Raj

• Nov 6th, 2006

Interfaces are used in client to call the implementation class running in server.

Answer Question  Select Best Answer

anil

• Sep 28th, 2006

Generally,these two interfaces are implemented by the EJB Container.

Answer Question  Select Best Answer

chirag desai

• Sep 27th, 2006

hi,well, in case of stateless session bean you have at least one ejb create method with out any arguments while in case of stateful session bean you can have one opr more than one ejbcreate method wit...

Answer Question  Select Best Answer

If your method in the session bean is already running under a transaction the calls to any other bean which have been deployed with trans-attribute 'Required' will be executed within the same transaction context. So if your session bean is using container-managed transactions and your method is deployed with 'Required', 'RequiresNew' or 'Mandatory', you can safely assume that the calls to your entity...