EJB Specification

can anybody help me where can i get ejb specification? not documentation...

u can follow the link:
http://java.sun.com/products/ejb/docs.html
http://www.comptechdoc.org/docs/kanti/ejb/ejbroles.html

Similar Messages

J2ee Ejb specification 2.0

Hi,
The latest Specifications for EJB 2.0 available on Sun's site talks about Entity Bean - bean managed persistance in Chapter 12 (page 257 - 258), where it states that
Bean Method bean method can
perform operations
-------------------------------------------------------ejbLoad/ejbStore Entity Context method :
getEJBHome, getEJBObject,
getcallerPrinciplal, getPrimaryKey,
getRollBackOnly, setRollBackOnly...
Business Method Entity Context method :
getEJBHome, getEJBObject,
getcallerPrinciplal,
getPrimaryKey, getRollBackOnly,
setRollBackOnly...
As per the above table, getRollBackOnly and setRollBackOnly methods can be used in different bean methods and container callback methods in Entity bean - Bean-Managed Persistence.
But as per our knowledge, the above methods can ONLY be used with Container Managed persistance beans.
Could you help me out in clearing the above confusion?
Thanks,
Gauri Tendulkar
Patni Computer Systems Ltd.
Sr. Software Engineer.

Hi!
getRollBackOnly and setRollBackOnly affects transactions of this bean, and transactios are handled by the container in any case (although you may begin and end usertransactions in the bean yourself). In the deployment-descriptor you specify how transacions should be handled for this bean (TX_REQUIRED, TX_SUPPORTED, ...)
I think even if you perform no transaction at all in the bean, you may use setRollBackOnly to mark the transaction currently open for rollback.
Hope this helps, ciao
Martin
Hi,
The latest Specifications for EJB 2.0 available on
on Sun's site talks about Entity Bean - bean managed
persistance in Chapter 12 (page 257 - 258), where it
states that
Bean Method bean method can
perform operations
jbLoad/ejbStore Entity Context method :
getEJBHome,
getEJBHome, getEJBObject,
getcallerPrinciplal,
getcallerPrinciplal, getPrimaryKey,
getRollBackOnly,
getRollBackOnly, setRollBackOnly...
Business Method Entity Context method :
getEJBHome,
getEJBHome, getEJBObject,
getcallerPrinciplal,
getcallerPrinciplal,
getPrimaryKey,
getPrimaryKey, getRollBackOnly,
setRollBackOnly...
As per the above table, getRollBackOnly and
setRollBackOnly methods can be used in different bean
methods and container callback methods in Entity bean
- Bean-Managed Persistence.
But as per our knowledge, the above methods can ONLY
be used with Container Managed persistance beans.
Could you help me out in clearing the above
confusion?
Thanks,
Gauri Tendulkar
Patni Computer Systems Ltd.
Sr. Software Engineer.

Does 8.1 sp3 support EJB Specification 2.1?

More specifically does it support the Enterprise Bean Timer interface?

John,
To have timed callbacks in 8.1sp3 you could use JMS and send messages with birth time set, which can be consumed by a MDB, which inturn on reception of message invokes the callback method.
WLS 8.1, JMS supports message birth times.
This may not be the best way, but the simplest way to get it done.
vasanthi ramesh

EJB Specification question

In the EJB Specs that I have been working with (1.1), whenever you make an entity bean, you have to specify the PK ID for the bean you wish to create. This ID goes into the database for the Server to be able to persist / find your bean. My question is:
Why do I have to specify the PK ID when I create a bean? Why can't I just call ejbCreate() and have it return an ID to me? So the Server and the Database could handle making sure that it is not a duplicate key. I find it creates more work than necessary that I have to figure out what PK ID is not taken yet and create that one, when if I used an IDENTITY field in a database, that could easily do it for me.
Anyone know why they chose to FORCE developers / (and Server admins not) to choose the PK ID? Why not give us the option of either having the server do it and return the ID, or us choosing it?
Anyone have thoughts on this?
Robert

Hi,
Although it would have been a lot easier, they
propably didn't define this in the EJB specs this way
to stay compatible with all databases. Not all
databases support the IDENTITY field. I remember there
were some interesting discussions about other ways to
define a PK on www.theserverside.com.Yeah, but that's why they could give you a choice, so that if you didn't want to do it, or your db didn't support it, you wouldn't have to do that.

Error in deploying a simple EJB 3.0

Hi ,
I am getting the following error while deploying my simple ejb of version 3.0 in Weblogic 9.2.
Exception preparing module: EJBModule(build) [EJB:011023]An error occurred while reading the deployment descriptor. The error was: Error processing annotations: java.lang.NullPointerException.
During my evaluation of Weblogic 9.2 for EJB 3.0 , I have got the following questions.
EJB Specification states that EJB's in EJB 3.0 can be developed and deployed without the need of deployment descriptors. I have created a simple EJB with two file Env.java and EnvBean.java and the source code is given below.
a) I just complied these class files and when I was trying to deploy without ejb-jar.xml and weblogic-ejb-jar.xml, the console was not at all allowing me to deploy.Why is this so?
b) After I created a META-INF file under root of classes directory by placing ejb-jar.xml with empty <enterprise-beans> element, console was allowing me to deploy with errors in parsing ejb-jar.xml. The error was either session/entity/mdb is a required under <enterprise-beans> element. Why is this required when there are several examples stating <enterprise-beans> element can be empty.
c) Later I updated ejb-jar.xml with <session> element under <enterprise-beans> with the following values. I got the above error when deployed with this change.
I had been struggling to deploy this simple bean for almost a day.Pleas point me if there is any documentation that solves my stated problem or if there is a solution.Thanks in advance.
regards
Karim
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" version="3.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
<enterprise-beans>
<session>
<description>This is the stateless ejb</description>
<display-name>Env Bean</display-name>
<ejb-name>EnvBean</ejb-name>
</session>
</enterprise-beans>
</ejb-jar>
Env.java
package examples ;
public interface Env {
public void display();
EnvBean.java
package examples;
import javax.ejb.Remote;
import javax.ejb.Stateless;
@Stateless
@Remote(Env.class)
public class EnvBean implements Env {
public void display() {
System.out.println("Welcome to EJB 3.0");
}

Presumably you're using the EJB3 tech preview, and not a vanilla WebLogic 9.2 install, right?
Can you post the full stack trace?
-Patrick

Ejb error while migrating from wl5.1 to wl8.1

Hello All,
I am trying to resolve this error that i am getting. Before i jump into the problem i would like to mention that i am in the process of converting our application from weblogic 5.1 to weblogic 8.1. For now i am using the same ejb(1.1 spec) and deploying it on WL8.1, the ejbs do get deployed, however when i try to run the application i get the following error. Am i missing something here (in descriptor files or somewhere else). Appreciate any input on this problem.
com.xxx.yyy.jsp.data.ScreenData: findByPrimaryKey(com.xxx.yyy.ejb.testUser.TestUserPK(10002))
com.xxx.yyy.jsp.data.ScreenData: Find AppUser Home for (com.xxx.yyy.ejb.testUser.TestUserPK(10002))
com.xxx.yyy.jsp.data.ScreenData: Find AppUser Bean for (com.xxx.yyy.ejb.testUser.TestUserPK(10002))
com.xxx.yyy.jsp.data.ScreenData Application user id com.xxx.yyy.ejb.testUser.TestUserPK(10002) remote server error.
Error during setXXXContext: ; nested exception is:
java.lang.IllegalStateException: [EJB:010193]Illegal call to EJBContext method. The bean is in "context setting" state. It cannot perform 'getting EJB object for Entity bean' OR 'getting the primary key' action(s). Refer to the EJB specification for more details.
java.rmi.RemoteException: Error during setXXXContext: ; nested exception is:
java.lang.IllegalStateException: [EJB:010193]Illegal call to EJBContext method. The bean is in "context setting" state. It cannot perform 'getting EJB object for Entity bean' OR 'getting the primary key' action(s). Refer to the EJB specification for more details.
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:186)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
at com.xxx.yyy.ejb.testUser.TestUserBean_19p26e_HomeImpl_812_WLStub.findByPrimaryKey(Unknown Source)
at com.xxx.yyy.jsp.data.ScreenData.findByPrimaryKey(ScreenData.java:104)
at jsp_servlet._jsp.__router._jspService(__router.java:219)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Thanks
vivi

seems like you are calling EntityContext.getEJBObject() or EntityContext.getPrimaryKey() before the context has been set on the bean. an IllegalStateException is thrown in such cases.
cheers,
mihir

EJB 3.0 PostConstruct and SessionContext -Oracle EJB 3.0 spec violatiation?

I am writing a stateless session bean using EJB 3.0 and the PostConstruct annotation. Within the PostConstruct annotated method my bean accesses the SessionContext to get the Timer Service. WebLogic 10.3.3 is throwing the following error:
com.oracle.pitchfork.interfaces.LifecycleCallbackException: Failure to invoke public void org.stola.services.MyJobRunnerBean.setupTimer() on bean class class org.stola.services.JobRunner_oa6dng_Impl with args: []
at com.bea.core.repackaged.springframework.jee.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:335)
Caused By: java.lang.IllegalStateException: [EJB:010193]Illegal call to EJBContext method. The bean is in "null" state. It cannot perform 'getting the Timer Service' action(s). Refer to the EJB specification for more details.
at weblogic.ejb.container.internal.BaseEJBContext.checkAllowedMethod(BaseEJBContext.java:141)
However, reading the EJB 3.0 specification, in section 4.5.2, table 2, it states that you can call SessionContext.getTimeService in the PostConstruct method. Is this a bug in the EJB 3.0 implementation by Oracle WebLogic?
Edited by: user4805298 on Sep 10, 2010 10:01 AM

The solution was to NOT have glabal transaction checked in the configuration of the data-source and "Failover Transaction State Upon Managed Release" uncked in the configuration of the Business component configuration.

EJB question: How to use abstract class in writing a session bean?

I had written an abstract class which implements the session bean as follow:
public abstract class LoggingSessionBean implements SessionBean {
protected SessionContext ctx;
protected abstract Object editRecord(Object obj) throws Exception;
public LoggingSessionBean()
super();
private final String getBeforeUpdateImage(Object obj) throws Exception {
// implement the details of extracting the backup image ...
public void setSessionContext(SessionContext ctx)
this.ctx = ctx;
private final void writeThisImageToDatabase(String aStr) {
// connect to database to write the record ...
public final Object update(final Object obj) {
try {
final String aStr = getBeforeUpdateImage(obj);
writeThisImageToDatabase(aStr);
editRecord(obj);
} catch (Exception e) {
ctx.setRollbackOnly();
This abstract class is to write the backup image to the database so that other session beans extending it only need to implement the details in editRecord(Object Obj) and they do not need to take care of the operation of making the backup image.
However, some several questions for me are:
1. If I write a class ScheduleSessionBean extending the above abstract class and the according 2 interfaces ScheduleSession and ScheduleSessionHome for this session bean (void update(Object obj); defined in ScheduleSession), do I still need to write the interfaces for LoggingSession and LoggingSessionHome?
2. If I wrote the interface LoggingSession extending EJBObject where it defined the abstract methods "void update(Object obj);" and "void setSessionContext(SessionContext ctx);", that this meant I needed to write the ScheduleSession to implement the Logging Session?
3. I used OC4J 9.0.4. How can I define the ejb-jar.xml in this case?

Hi Maggie,
1. do I still need to write
the interfaces for LoggingSession and
LoggingSessionHome?"LoggingSessionBean" can't be a session bean, because it's an abstract class. Therefore there's no point in thinking about the 'home' and 'remote' interfaces.
2. this
meant I needed to write the ScheduleSession to
implement the Logging Session?Again, not really a question worth considering, since "LoggingSessionBean" can't be an EJB.
3. I used OC4J 9.0.4. How can I define the
ejb-jar.xml in this case?Same as you define it for any version of OC4J and for any EJB container, for that matter, since the "ejb-jar.xml" file is defined by the EJB specification.
Let me suggest that you create a "Logging" class as a regular java class, and give your "ScheduleSessionBean" a member that is an instance of the "Logging" class.
Alternatively, the "ScheduleSessionBean" can extend the "Logging" class and implement the "SessionBean" interface.
Good Luck,
Avi.

Defining cmp-relation to EB contained in different ejb module project

Hello,
I have to migrate an existing J2EE Application to SAP NetWeaver and WebAS. My task is to keep the structure as similar as possible to increase the recognition factor although using Developer Studio as IDE.
In this application there are cmp relations defined that reference EntityBeans from other sub projects (that I tried to create in different ejb module projects).
References in the same ejb module project seem to work fine but I cannot select referenced EntityBeans of other projects as relation target.
Another remark:
In the given application the ejb-jar.xml-file of the referencing component contains entries of the referenced one. The Developer Studio allows to Add EJBs to ejb-jar.xml, even referenced Beans. But when I select to add referenced EJBs only the Beans of the current project can be chosen. (I did not forget to enter an ejb-local-ref from the referencing to the referenced Bean in ejb-jar.xml as well)
Can anyone give me a hint on how to solve this task? Or where I have forgotten to add a reference?
Thanks
Daniel

Hello Viliana,
Hello everybody else!
I'm currently writing the corresponding masterthesis to my project. That's why I have to deal with this "problem" again.
I tried to look up the part of the spec Viliana's hint ("When you create and use cmp-relationships your beans must be included in one and the same JAR file (that's according to the EJB specification)") bases on.
But the only thing I found addressing this issue tells something else:
"[...]Container-managed relationships can exist only among entity beans within the same local relationship
scope,[...]" (EJBSpec2.1, section 10.3.2)
In my opinion this does not necessarily mean that they have to be in the same JAR but in the same EAR file...
This would mean, that the chosen cmp-relationships strategy with ejb-module-projects is too restrictive.
Can anyone help me with this... Does anyone know further hints on how Entity Beans have to be deployed when belonging to cmp-relationships?
Thanks a lot for any hint on this
Best regards,
Daniel

In my NWDS "Build EJB Archive" is not actitivated?

Hi all!
I created an EJB project and imported some files in to my EJB project. When i try to build my EJB Archive, it is not activated. I tried even a simple EJB project, for that also Build EJB Archive is not activated. Help me
Thanks a lot in advance!

Hi
I have done what you said in your first post, Build EJB Archive is enabled very well, but i got deployment error when deploying .ear file to J2EE engine.
Actually I build an Enterprise project and addded this EJB project to that, and built .ear file and this ear file is deployed onto SAP J2EE engine:
I got this deployment error:
Result
=> deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp14071Jps_Ear.ear
Aborted: development component 'Jps_Ear'/'sap.com'/'localhost'/'2006.06.01.11.40.12':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/Jps_Ear.. Reason: Incorrect application sap.com/Jps_Ear:Bean FolderMI_PortTypeBean: the return type of a create<METHOD> method in the session bean home interface must be the session bean's remote interface type. EJB specification 7.10.6.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface does not extend javax.ejb.EJBObject. The remote interfaces must extend javax.ejb.EJBObject.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface must be valid RMI-IIOP remote interface.Error in bean FolderMI_PortTypeBean: The business method folderMI does not throw java.rmi.RemoteException. Business methods of the remote interface must throw java.rmi.RemoteException.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: No corresponding business method in the bean class jps.FolderMI_PortTypeBean was found for method folderMI.; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/Jps_Ear:Bean FolderMI_PortTypeBean: the return type of a create<METHOD> method in the session bean home interface must be the session bean's remote interface type. EJB specification 7.10.6.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface does not extend javax.ejb.EJBObject. The remote interfaces must extend javax.ejb.EJBObject.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface must be valid RMI-IIOP remote interface.Error in bean FolderMI_PortTypeBean: The business method folderMI does not throw java.rmi.RemoteException. Business methods of the remote interface must throw java.rmi.RemoteException.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: No corresponding business method in the bean class jps.FolderMI_PortTypeBean was found for method folderMI.
     at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)
     at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:253)
     at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2142)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:318)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3119)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:522)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Incorrect application sap.com/Jps_Ear:Bean FolderMI_PortTypeBean: the return type of a create<METHOD> method in the session bean home interface must be the session bean's remote interface type. EJB specification 7.10.6.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface does not extend javax.ejb.EJBObject. The remote interfaces must extend javax.ejb.EJBObject.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: the remote interface must be valid RMI-IIOP remote interface.Error in bean FolderMI_PortTypeBean: The business method folderMI does not throw java.rmi.RemoteException. Business methods of the remote interface must throw java.rmi.RemoteException.Error in the remote interface jps.FolderMI_PortType of bean FolderMI_PortTypeBean: No corresponding business method in the bean class jps.FolderMI_PortTypeBean was found for method folderMI.
     at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:66)
     at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:253)
     at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2142)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:318)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3119)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:522)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
=======================
Which says that my JPS_EJB.jar file is not properly build.
The error meant to say it is a Bean Problem: No interfaces classes found .
Thanks

File IO operation in EJB (Session Bean)

Hi all,
Requirement : Read contents of a text file and upload the same to Oracle database (table).
I have created a Java class (application kind of) which opens, reads a file and transfers its data to a Oracle table.
Can I instantiate the same class within a Session Bean to perform the same operation or as per the EJB Restrictions this is not supposed to be done?
EJB Specifications 2.1 pdf guide
(refer 25.1.2 Programming restrictions
An enterprise bean must not use the java.io package to attempt to access files and directories in the file system. The file system APIs are not well-suited for business components to access data. Business components should use a resource manager API, such as JDBC, to store data.
Awaiting ur responses at the earliest.
Thanking in advance,
Seetesh

Hi Kenneth,
Thks for ur post.
I have coded the same using Weblogic App Server 7.0 ie a jsp invoking a java class (FileIO.class)(using jsp:useBean) and writing which does the IO operation and this works just fine.
Will this work by replacing the jsp with a Session Bean.
ie Session Bean's business method executing the method in the FileIO.class
Rgds,
Seetesh

EJB compilation and deployment problems

Dear fellows
I have good understanding of EJB development process, but the compilation and deployment process of EJB is very problematic for me. Please write me the complete steps which should include:
1. Starting from class, interface programs creation
2. Package creation and accessing it along with class path setting
3. How and where to compile these classes and interfaces (app server details), JAR
4.deployment details on any app server like SUN, web logic
Kind regards
Shahzad faisal

Dear fellowsDear Shahzad faisal
Start with the JEE5 tutorial:
http://java.sun.com/javaee/5/docs/tutorial/doc/
Part 3 discusses EJB stuff
I would recommend going to a few samples, bundled with most of the appservers to see the appserver specific stuff.
>
I have good understanding of EJB development process,
but the compilation and deployment process of EJB is
very problematic for me. Please write me the complete
steps which should include:
1. Starting from class, interface programs creationSo you have the classes and interface implemented.
Next thing is to create a ejb-jar.xml in which your EJBs are defined (optional for EJB3.0)
2. Package creation and accessing it along with class
path settingPackaging all in a jar file is enough for an appserver to find your classes.
3. How and where to compile these classes and
interfaces (app server details), JARCompilation usually needs the javx.ejb.* classes, most appservers have a j2ee.jar in which the javax.* classes you need are present.
in jour jar file you package your classes and deployment descriptor
4.deployment details on any app server like SUN, web
logicDeployment to appservers is product specific, see the manual here.
you may want to add some other , vedor specific, deployment settings which are not ejb specification defined, these go into a vendor specific DD, for Sun for example the sun-ejb-jar.xml.
>
Kind regards
Shahzad faisal

JSP TagLib for EJB

Does BEA provide an EJB specific JSP Tag library with WebLogic? I know of at least one other EJB Server that does.

What version is your tag library and what version is your deployment descriptor?

URGENT::::use of multithreading in ejb

hi
I NEED TO USE MULTITHREADING IN EJB APPLICATION.
THE SCENERIO IS LIKE THIS ...==
SUPPOSE ONE USER HAS GOT MONEY IN 3 BANKS. SUPPOSE THE USER WANTS TO GET THE BALANCE OF
ALL THE 3 BANK AND WANT THE SUMMATION.IN THIS SCENARION WE NEED TO START 3 THREAD .HOW IS IT POSSIBLE IN EJB.
MY EMAIL ID IS
[email protected]
regds rupalim

Hi,
As per the ejb specification you are not supposed to manage threads explicitly from an ejb. I didn't follow the question in the right sense. However you can try to solve it by making a session bean for managing your business logic and from that session bean use entity bean for getting and setting data from database. Hope this will help you.
bye
[email protected]

Global env-entry JNDI variables space for same ejb-jar.xml file

[Software]
jboss4.0.5
jdk 1.5
[Problem]
Is there any global <env-entry> tag for a Single EJB Module. Is there any way by which the JNDI variable can be accessed by all the modules except by binding the variables in the JNDI explixity in the code
Thanks in advance
CSJakharia

Unfortunately not. The EJB specification has always scoped the component environment
(java:comp/env) as a private environment for each EJB. The advantage is you can
assign entries within each bean easily without worrying about clashing with names selected
for other beans in the ejb-jar. That eases the process of assembling beans developed
separately into one ejb-jar since there is no possibility that their component environments
will clash.
However, the downside is just what you're pointing out, which is that in many cases
developers prefer to define a single dependency that is shared among all the
beans in the ejb module. That is the behavior of the component environment in a
web application.
We'll be looking into ways to simplify this for ejbs in a future revision of the specification.
--ken

EJB Specification

Similar Messages

Maybe you are looking for