Does JServer support EJB/Entity beans

What version of JServer lives in the following applications, and does it support EJB/Entity Beans or when will it.
8.1.5 OAS
8.1.5 8i
8.1.6 OAS
8.1.6 8i

Check out the following link for details about the Beta Program: http://technet.oracle.com/products/oracle8i/java_beta/index.htm
New features that will be available in the Beta include support for Entity Beans, and support for Servlets. It also includes JServer Accelerator (JServer's Native Compiler).

Similar Messages

How to delete a database record by using EJB entity beans

Hi, All,
Does anyone know how to use entity bean to delete a database record? I have all the EJB entity beans created, including access beans to each. I can successfully create records, find and update records, however, I haven't find a way to delete records yet.
Your response is appreciated.
Cathy

Please see EJB Forums for continue discussion on this subject.
Reference titile: "how to delete database record by using CMP entity beans "

EJB entity beans and BC4J

I have looked at BC4J and it looks good. Buy my question is that isn't this frame work in direct conflict with EJB entity beans. I know lot of stuff that is there in BC4J should have been in EJB enitiy beans, but as a developer why should I go with BC4J and not the standard EJB stuff considering the fact that BC4J is properietery to Oracle?Any thoughts?

Vimal,
Without going into exhaustive detail here, I would like to recommend that you take a look at the BC4J Technical White Paper available from the JDeveloper page on OTN (in the 3.0 Technical Information section):
http://technet.oracle.com/products/jdev/info/techwp20/wp.html
Amoung other things to note, BC4J is based on pure Java, and is what we consider a 'white box', meaning, you as a developer have complete control over what is going on. You can extend any of the code generated to customize it.
Primarily though, the major benefit of BC4J is that we have taken care of most of the complicated communication code for you. Communication between the client and the data server, transaction handling, row locking, etc are already written for you. You just use, extend, customize what we have provided.
In addition, BC4J allows you flexibility in your deployment environment decision. Regardless of where and how you deploy your BC4J Application Module, the client is unchanged.
Those are the key advantages. Again, for more details, I would take a look at the white paper to see if it more fully addresses your questions.

Are EJB ( entity beans) are cached ?

Are EJB ( entity beans) are cached ?
I have a doubt here . As per my understanding , the entity beans are cached from the database. In that case , If I delete a row in the database by an external application ( say using TOAD tool) , how the Entity bean will be updated / reloaded ? Entity bean will be out of sync then .
Application server : weblogic/webspehere .

>
You can use the refresh method of the EntityManager interface to read new values from the database (if you expect it to be out of sync), and use locks to prevent others from changing your data while the application is performing actions in a transaction.Did you mean I have to write code for this ? can't be made it automatic refresh by the container ? Is there any settings I can configure so that container can do it by itself proactively ?
Also, using locks ...is this a container settings or I need to configure myself in ejb-jar.xml ? Could you please shed some light here ?

Is there a better way of doing this? (regards Entity Beans, CMP, J2EE5...)

Hello everyone,
So I'm going to blurt out two classes of code. First is a plain entity bean and the second is a helper class with two static methods to help me to convert Object into byte[] and vice versa without much worrying.
Now the problem is, how to persist this entity bean and it's two Objects (two Lists) in a more "J2EE5 way". I just need to store these two Objects, or any Serializable Object, into persistent storage. So how to avoid this serialization by-hand that I'm doing... ?
Thank you for your interest - and help :),
Samuli
Maybe using a @Lob notation or such? I've tried, but I can't get it workign. @Lob itself is not enough since it results in casting problems when retrieveing the data back from the persistent storage.
And oh, I'm just using the simple CMP with this.. EJB using EntityManager's persist method to store and so on..
EntityBean class (imports and packages excluded)
@Entity
public class MessageHandlerChain implements java.io.Serializable {
    @TableGenerator(
        name="messageHandlerChainIDGenerator",
        allocationSize=1,
        initialValue=1
    @GeneratedValue(
        generator="messageHandlerChainIDGenerator",
        strategy=GenerationType.TABLE
    @Id
    private Integer messageHandlerChainID;
    @Lob
    private byte[] messageHandlers;
    @Lob
    private byte[] messageHandlerProperties;
    @Transient
    private List<String> messageHandlersObj = new ArrayList<String>();
    @Transient
    private List<Map<String,String>> messageHandlerPropertiesObj = new ArrayList<Map<String,String>>();
     * Constructs an empty instance of <code>MessageHandlerChain</code> without any properties.
    public MessageHandlerChain() {
    public Integer getMessageHandlerChainID() {
        return messageHandlerChainID;
    public void setMessageHandlerChainID(Integer messageHandlerChainID) {
        this.messageHandlerChainID = messageHandlerChainID;
    public List<String> getMessageHandlers() {
        return messageHandlersObj;
    public void setMessageHandlers(List<String> messageHandlersObj) {
        if (messageHandlersObj == null) {
            System.out.println("[MessageHandlerChain] setMessageHandlers() can't be given a null value.");
            return;
        this.messageHandlersObj = messageHandlersObj;
    public List<Map<String,String>> getMessageHandlerProperties() {
        return messageHandlerPropertiesObj;
    public void setMessageHandlerProperties(List<Map<String,String>> messageHandlerPropertiesObj) {
        if (messageHandlerPropertiesObj == null) {
            System.out.println("[MessageHandlerChain] setMessageHandlerProperties() can't be given a null value.");
            return;
        this.messageHandlerPropertiesObj = messageHandlerPropertiesObj;
    @PrePersist
     * This method is invoked by the persistence provider prior to every persist operation.
     * This is needed because we need to convert, serialize, our <code>@Transient</code> annotated objects into <code>byte[]</code> streams
     * so that they can be written into the database.
    public void prePersist() {
        System.out.println("[MessageHandlerChain] prePersist()");
        if (messageHandlerPropertiesObj != null)
            messageHandlerProperties = BlobConverter.objectToBytes(messageHandlerPropertiesObj);
        if (messageHandlersObj != null)
            messageHandlers = BlobConverter.objectToBytes(messageHandlersObj);
    @PostLoad
     * This method is invoked by the persistence provider after every load operation.
     * This is needed because we need to convert, deserialize, <code>byte[]</code> streams back to our <code>@Transient</code> annotated objects.
    public void postLoad() {
        System.out.println("[MessageHandlerChain] postLoad()");
        try {
            if (messageHandlerProperties != null)
                messageHandlerPropertiesObj = (List<Map<String,String>>)BlobConverter.bytesToObject(messageHandlerProperties);
            if (messageHandlers != null)
                messageHandlersObj = (List<String>)BlobConverter.bytesToObject(messageHandlers);
        } catch (ClassCastException e) {
            System.out.println("[MessageHandlerChain] postLoad() Class Cast Exception: "+e);
    public String toString() {
        return "[MessageHandlerChain] messageHandlerChainID="+getMessageHandlerChainID()+", messageHandlers="+getMessageHandlers()+", messageHandlerProperties="+getMessageHandlerProperties();
The helper class
* <code>BlobConverter</code> is a simple helper class to encode and decode classes as byte[] so that they can be stored into persistent storage.
* @author Samuli Piela
public class BlobConverter {
    public static byte[] objectToBytes(Object o) {
        ByteArrayOutputStream baos = new ByteArrayOutputStream(512);
        ObjectOutputStream oos = null;
        try {
            oos = new ObjectOutputStream(baos);
            oos.writeObject(o);
            return baos.toByteArray();
        } catch (InvalidClassException e) {
            System.out.println("objectToBytes("+o+"): Invalid Class: "+e);
        } catch (NotSerializableException e) {
            System.out.println("objectToByte("+o+"): Object not serializable: "+e);
        } catch (Exception e) {
            System.out.println("objectToBytes("+o+"): Exception: "+e);
        } finally {
            if (oos != null) {
                try {
                    oos.close();
                } catch (IOException e) {
                    System.out.println("objectToBytes(): Stream could not be closed: "+e);
            if (baos != null) {
                try {
                    baos.close();
                } catch (IOException e) {
                    System.out.println("objectToBytes(): Stream could not be closed: "+e);
            oos = null;
            baos = null;
        return null;
    public static Object bytesToObject(byte[] byteArray) {
        ByteArrayInputStream bais = new ByteArrayInputStream(byteArray);
        ObjectInputStream ois = null;
        try {
            ois = new ObjectInputStream(bais);
            Object o = ois.readObject();
            return o;
        } catch (ClassNotFoundException e) {
            System.out.println("bytesToObject(): Class not found: "+e);
        } catch (InvalidClassException e) {
            System.out.println("bytesToObject(): Invalid Class: "+e);
        } catch (IOException e) {
            System.out.println("bytesToObject(): IOException: "+e);
        } catch (Exception e) {
            System.out.println("bytesToObject(): Exception: "+e);
        } finally {
            if (ois != null) {
                try {
                    ois.close();
                } catch (IOException e) {
                    System.out.println("bytesToObject(): Stream could not be closed: "+e);
            if (bais != null) {
                try {
                    bais.close();
                } catch (IOException e) {
                    System.out.println("bytesToObject(): Stream could not be closed: "+e);
            ois = null;
            bais = null;
        return null;
}

anyone?

Problems accessing tables in oracle database with ejb entity bean

I have created a simple server application that uses an entity bean (version 2.0) for an existing table in oracle database, and a session bean that is used as an outside interface for performing operations on that table.
after deploying the server and client application the client attempts to perform an operation with the session bean remote interface it obtained.
The session bean uses a locale interface to communicate with the entity bean, but when it tries to use its methods (create, findByXXX) it always get the following Exception: java.sql.SQLException: ORA-00942: table or view does not exist.
the table of course exists, and the username password I'm using has all the permissions needed for this table.
note - I'm using the Forte enterprise edition 4.0 as developer tool.
I'll be glad to get some help.
Here is the full stack trace of the exception:
javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean; nested exception is: javax.ejb.EJBException: nested exception is: java.sql.SQLException: ORA-00942: table or view does not exist
javax.ejb.EJBException: nested exception is: java.sql.SQLException: ORA-00942: table or view does not exist
java.sql.SQLException: ORA-00942: table or view does not exist
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:643)
at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:1674)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1870)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:363)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:314)
at com.sun.ejb.persistence.SQLEngine.ejb20Finder(SQLEngine.java:226)
at com.sun.ejb.persistence.PartitionImpl.ejbFinder(PartitionImpl.java:736)
at com.cti2.telco.core.ejb.entity.userInfo.UserInfoEJB_PM.ejbFindByEmail(UserInfoEJB_PM.java:393)
at com.cti2.telco.core.ejb.entity.userInfo.UserInfoEJB_PM_LocalHomeImpl.findByEmail(UserInfoEJB_PM_LocalHomeImpl.java:64)
at com.cti2.telco.core.ejb.UserManagerEJB.authenticate(UserManagerEJB.java:77)
at com.cti2.telco.core.ejb.UserManagerEJB.authenticate(UserManagerEJB.java:68)
at com.cti2.telco.core.ejb.UserManagerEJB_EJBLocalObjectImpl.authenticate(UserManagerEJB_EJB
LocalObjectImpl.java:63)
at com.cti2.telco.core.ejb.dispatch.TelcoFacadeEJB.userLogin(TelcoFacadeEJB.java:80)
at com.cti2.telco.core.ejb.dispatch.TelcoFacadeEJB_EJBObjectImpl.userLogin(TelcoFacadeEJB_EJBObjectImpl.java:24)
at com.cti2.telco.core.ejb.dispatch._TelcoFacadeEJB_EJBObjectImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:519)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:204)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:112)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:273)
at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:84)
at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:99)
...

Well it seems like the problems has a simple explanation. The Forte assigns a default table name (<entityName>EJBTable) when creating an entity bean from an existsing table in DB (which is not the same as the one it was created from !!!). Also, for reason unknown, when you deploy these entity beans, it doesn't even create the new table under its new name (even if instructed to).
So using the Forte we managed to use successfuly only entity beans that were created "from scretch" (when deployed their tables are created).
Does anyone know how to change the default name the Forte uses, and make it work properly with entity beans created from an existsing table (without going over the xml's) ?

Problem deploying EJB entity bean

Hi all!
I'm trying to deploy an CMP entity bean with composite primary key.
My environment is Oracle 8i (8.1.7) on W2K Professional and I'm using JDK 1.3.1_02.
The error I get is:
Compiling Stubs...done
Generating Jar File...done
Loading EJB Jar file and Comm Stubs Jar file...done
Generating EJBHome and EJBObject on the server...
An exception occurred during code generation: null
I don't understand what am I doing wrong...
Any help will be highly appreciated.
[Could anyone point me out sample code for CMP entity beans with composite primary key?]
Apologies for the length of the POST, just trying to pass as much info as I can...
The table is the following:
CREATE TABLE GPS_HIST (
gps_date_of_fix     VARCHAR2(40) NOT NULL,
gps_time_of_fix     VARCHAR2(40) NOT NULL,
issi               NUMBER(10) NOT NULL,
gps_condition          NUMBER(5),
gps_latitude          VARCHAR2(40),
gps_longitude          VARCHAR2(40),
gps_speed_knt          NUMBER(10),
constraint gps_hist_pk primary key (gps_date_of_fix, gps_time_of_fix, issi))
TABLESPACE AVLDATA
PCTFREE 10     PCTUSED 40
INITRANS 1     MAXTRANS 255
STORAGE (
INITIAL 128K NEXT 128K PCTINCREASE 0
MINEXTENTS 1 MAXEXTENTS 4096)
NOCACHE;
The primary key class is the following:
package gps;
public class GPSEntryPK implements java.io.Serializable
     public int ISSI;
     public String gpsTimeOfFix;
     public String gpsDateOfFix;
     public GPSEntryPK() {}
     public GPSEntryPK (String gpsDateOfFix, String gpsTimeOfFix, int ISSI)
          this.gpsDateOfFix = gpsDateOfFix;
          this.gpsTimeOfFix = gpsTimeOfFix;
          this.ISSI = ISSI;
     public String getGPSDateOfFix()
          return this.gpsDateOfFix;
     public String getGPSTimeOfFix()
          return this.gpsTimeOfFix;
     public int getISSI()
          return this.ISSI;
     public boolean equals(Object obj) {
          if ((obj instanceof GPSEntryPK) &&
               (this.ISSI == ((GPSEntryPK)obj).ISSI) &&
               (this.gpsTimeOfFix.equals(((GPSEntryPK)obj).gpsTimeOfFix)) &&
               (this.gpsDateOfFix.equals(((GPSEntryPK)obj).gpsDateOfFix)))
               return true;
          return false;
     public int hashCode() {
          return (this.gpsTimeOfFix.concat(this.gpsDateOfFix)).hashCode() * this.ISSI;
The bean implemantation (part of it) is as follows:
public void setEntityContext(EntityContext ctx)
this.ctx = ctx;
Properties props = ctx.getEnvironment();
public void unsetEntityContext()
this.ctx = null;
public GPSEntryPK ejbCreate(String gpsDateOfFix, String gpsTimeOfFix, int ISSI, int gpsCondition,
String gpsLatitude, String gpsLongitude, double gpsSpeedKnt)
throws CreateException, RemoteException
try {
setGPSDateOfFix(gpsDateOfFix);
setGPSTimeOfFix(gpsTimeOfFix);
setISSI(ISSI);
setGPSCondition(gpsCondition);
setGPSLatitude(gpsLatitude);
setGPSLongitude(gpsLongitude);
setGPSSpeedKnt(gpsSpeedKnt);
} catch (java.rmi.RemoteException e) {
throw new CreateException();
return null;
public GPSEntryPK ejbFindByPrimaryKey(GPSEntryPK pk) throws RemoteException, FinderException {
return null;
public void ejbPostCreate(String gpsDateOfFix, String gpsTimeOfFix, int ISSI, int gpsCondition,
String gpsLatitude, String gpsLongitude, double gpsSpeedKnt)
     throws CreateException
// get primarykey
GPSEntryPK pk = (GPSEntryPK)ctx.getPrimaryKey();
public void ejbActivate() {}
public void ejbPassivate() {}
public void ejbRemove() {}
public void ejbLoad()
// You can get to the primary key
GPSEntryPK pk = (GPSEntryPK)ctx.getPrimaryKey();
public void ejbStore(){}
The descriptors are the following:
"gpsentry.xml"
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems Inc.//DTD Enterprise JavaBeans 1.1//EN" "ejb-jar.dtd">
<ejb-jar>
<enterprise-beans>
<entity>
<description>no description</description>
<ejb-name>GPSEntry</ejb-name>
<home>gps.GPSEntryHome</home>
<remote>gps.GPSEntry</remote>
<ejb-class>gpsServer.GPSEntryBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>gps.GPSEntryPK</prim-key-class>
<reentrant>False</reentrant>
<cmp-field><field-name>gpsDateOfFix</field-name></cmp-field>
<cmp-field><field-name>gpsTimeOfFix</field-name></cmp-field>
<cmp-field><field-name>ISSI</field-name></cmp-field>
<env-entry>
<env-entry-name>realmName</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>gps.realm</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>GPSEntryBean.databaseURL</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>jdbc:oracle:kprb:</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>GPSEntryBean.JDBCDriverName</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>oracle.jdbc.driver.OracleDriver</env-entry-value>
</env-entry>
</entity>
</enterprise-beans>
</ejb-jar>
"oracle_gpsentry.xml"
<?xml version="1.0"?>
<!DOCTYPE oracle-descriptor PUBLIC "-//Oracle Corporation.//DTD Oracle 1.1//EN" "oracle-ejb-jar.dtd">
<oracle-descriptor>
<mappings>
<ejb-mapping>
<ejb-name>GPSEntry</ejb-name>
<jndi-name>test/gpsentry</jndi-name>
</ejb-mapping>
</mappings>
<persistence-provider>
<description> specifies a type of persistence manager </description>
<persistence-name>psi-ri</persistence-name>
<persistence-deployer>oracle.aurora.ejb.persistence.ocmp.OcmpEntityDeployer</persistence-deployer>
</persistence-provider>
<persistence-descriptor>
<description> This specifies a particular type of persistence manager to be used for a bean. param is where you would put bean specific persistence info in the format of params. The deployment process just passes what's in the param to the persistence deployer. For the baby persistence, we do parse the persistence-mapping but for other persistence backend we don't do anything with the params </description>
<ejb-name>customerbean</ejb-name>
<persistence-name>psi-ri</persistence-name>
<psi-ri>
<schema>AVLMIS</schema>
<table>gps_hist</table>
<attr-mapping>
<field-name>gpsDateOfFix</field-name>
<column-name>gps_date_of_fix</column-name>
</attr-mapping>
<attr-mapping>
<field-name>gpsTimeOfFix</field-name>
<column-name>gps_time_of_fix</column-name>
</attr-mapping>
<attr-mapping>
<field-name>ISSI</field-name>
<column-name>issi</column-name>
</attr-mapping>
<attr-mapping>
<field-name>gpsCondition</field-name>
<column-name>gps_condition</column-name>
</attr-mapping>
<attr-mapping>
<field-name>gpsLatitude</field-name>
<column-name>gps_latitude</column-name>
</attr-mapping>
<attr-mapping>
<field-name>gpsLongitude</field-name>
<column-name>gps_longitude</column-name>
</attr-mapping>
<attr-mapping>
<field-name>gpsSpeedKnt</field-name>
<column-name>gps_speed_knt</column-name>
</attr-mapping>
</psi-ri>
</persistence-descriptor>
</oracle-descriptor>
Thanks in advance.

Hi Nikos,
I obviously don't know what your entire situation is, but you may not
be aware that Oracle's DBMS embedded EJB container does not work well,
and as a result, Oracle decided to replace it with an external EJB
container which is part of a product called "Oracle Containers for
J2EE" (otherwise known as "OC4J"). The "other" forum (the J2EE forum)
deals mainly with OC4J.
As far as I know, Oracle recommends doing your EJB related work with
OC4J and not with the embedded EJB container.
Good Luck,
Avi. That's correct
Java code, implementing data bound logic, can still run in the database as Java stored procedures/packages/functions/triggers
while J2EE componentsdeployed in middle-tier implement business logic. Java in database enable the database to be an active participant to your deployment platform
in 9iDB R2 you will even be able to call-out Web client (using HTTP Client), EJB client (using oc4jclient.jar) or Web Service client
(using SOAP libraries)
Kuassi

EJB Entity beans ,JDBC Stored procedures

Hi ,
I am new to EJB and i have some general questions
---Every table in an existing database is an entity bean for my application?
--- how do i define the queries in the entity bean ? (With PreparedStatement ?)
---The persistent fields,the ejbmethods,constructors, the table relationships, the prepared statements and stored procedures, are defined in the entity beans ?
--- how do i define the primary Keys in an Entity Bean !!! I will use EJB 2.1 and BMP
thanks in advance ...

Sandeep...
I have dblinks going all over the place. What you are talking about is a clustered or distributed database. That is the future (or present ) of large databases. My code is set up because an 'architecture' is not yet available in the database itself to support the concepts I've posted to Steve in other threads.
I fully believe that we'll eventually have BC4J ( or something like it ) directly in the database. I fully believe that the database will load balance these across a cluster of databases, within the database structure itself. For example... there is NOTHING to stop the JVM from deciding that it needs to load balance and submit the thread to a remote machine for processing... independent of creating a "middle tier" outside the database.
I believed that client-server model was flawed for most (not all) applications in the 80's. Looking at the "application tier" model I have the same feeling that we're creating an overly complex scheme at the wrong layer... just pushed back one stage so that we have to rewrite everything...
If you go back to the megalithic server design ( or cluster of servers ) with a thin thin front end... just why is the middle tier needed under the scenario I've outlined?
As such, stored procedures/triggers be they in java or pl/sql seems best bet to me... seeing's how a call spec to java or a pl/sql wrapper is transparent to the caller using jdbc or any other future technology.
grin Way outside the scope of the universe today... I see it as inevitable.
null

Does JServer Support JSP

Does Oracle 8i with JServer support JSP, and if it does not can we use Apache Tomcat and Oracle 8i.

John,
We are working with the Apache/Tomcat/JServer architecture right now, and haven't ironed out all the wrinkles, but are making progress. This is a test system, not production, so we don't yet know what the performance issues are but it should be possible. Oracle Support says they support deployment to Tomcat 3.0 and Apache 1.3.9
I have a follow on question to this thread. Running with Tomcat and EJB leads to two JVMs running, with performance issues. Deploying JSPs to JServer will help us overcome part of this barrier, but our architecture also employs a servlet Command Pattern to handle Application Logic, while the BC4J deployed as an EJB handles business rules. Will we be able to deploy the servlet to JServer in the future as well? Thanks

Does Tomcat support EJB's?

Does Tomcat support the deployment of EJB's? If so how do you go about deploying them. i cant seem to find anything on the apache web site

Hi,
Does Tomcat support the deployment of EJB's? If soNo, Tomcat is the open source servlet Container by Apache and to my knowledge they dont have any ejb Container as open source,so you have to make the tomcat configure with the EjbContainer for EJB to be deployed.......
how do you go about deploying them. i cant seem to
find anything on the apache web siteYou require the EJB Container for deploying the EJB's.You can go for Jboss,Weblogic,Websphere.....
regards
Vicky

EJB Entity Beans

"Entity Beans are suitable for read/write database access when transaction control
is important. Container managed Entity beans should be suitable for simple entity
relationships and offer much easier maintenance and development."
Tell me why or why not you agree with the above statement.
This is one of the most talked about issues, and I like to see this group's view
point, regardless of what Sun says in their blueprint.
On a unrelated note, i like to see what you think about this:
What are the benefits and disadvantages of using Inner Classes?

I agree. How are you gonna find the marks without primary key? Sequential seek??
What you should do is having student_id as primary key of the marks table and create a 1-* relationship between them by student_id.
Cheers.

Ejb : entity beans limitations

what are the limitations of bmp & cmp?

"Chinthala Upender" <[email protected]> wrote in message news:28421839.1104135395183.JavaMail.root@jserv5...
what are the limitations of bmp & cmp?According to my experience the main limitation is that engineers are
sometimes reluctant to read books on basics of Enterprise Java Beans.
To overcome this limitation please check this:
http://www.amazon.com/exec/obidos/tg/detail/-/0471417114
Regards,
Slava Imeshev

SQL Server Compact data provider for EF does not support some Entity SQL canonical functions

I would like to get some comments on this issue:
http://connect.microsoft.com/SQLServer/feedback/details/812735

Dennis,
Yes, I meant the CodePlex tracker for EF. As the code you are talking about is in the EF codebase, not in the SQLCE codebase. I had a closer look, and I think that Contains and StartsWith can be made to work based on the SQL Server implementation. And EndsWith
should at leats report "Not supported" instead of generating failing T-SQL.
Do not expect any changes to the SQLCE engine but the SQLCE EF provider code is fully supported by the team, I would imaging also to prove that EF is not SQL Server only.
BUT - in order to priovide a fix, which could be included in EF 6.1, PLEASE provide a simple repre project/unit tests with some failing ESQL code in it, I could end up contributing the fix, but do not know anything about ESQL.
I regularly contribute mainly SQLCE provider related fixes, and the EF team is very receptive to those, so I think there is a REAL chance of getting it fixed.
Please mark as answer, if this was it. Visit my SQL Server Compact blog http://erikej.blogspot.com

When will ias 6.0 sp4 be available and does it support EJB CMP 2.0

It is similar to a class not found exception. It means that what the JNDI manager is pulling out of the directory it doesn't know how to deserialize. Double check your classpaths & classloaders.

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

Does JServer support EJB/Entity beans

Similar Messages

Maybe you are looking for