Session bean with 2 entity bean

i have a phonebook manager (session bean) taht controls the category of contacts such as group a , group b, group c and group d. where group a b c and d are all entity beans.
may i know how to control a session bean so that it can diferent which entity beans to invoke ?

Group might be a table in a database,
GroupEJB referes to Entity Bean.
with the following fields. Group Id , Group disciption. where group ID is primary Key.
Use a session bean and create your group A B C D.( EJB create method).
Simple i guess.
Enjoy
Zoha.

Similar Messages

Can Entity Bean with Home Business Method replace Stateless Session Bean?

Since Entity Bean can have business methods in the Home Interface, can we use Entity Bean with Home Business Methods to replace Stateless Session Bean?
I am assuming we can get better performance by doing this since the overhead of creating Component Object can be avoided as compared to stateless session beans.

Requires-new makes the container start a new transaction. Only use that flag
          at the point that you are certain that a NEW transaction should BEGIN. I
          suggest you use Required as your default for all methods in the application,
          and only change that to anything else when you are certain that you should.
          Peace,
          Cameron Purdy
          Tangosol Inc.
          << Tangosol Server: How Weblogic applications are customized >>
          << Download now from http://www.tangosol.com/download.jsp >>
          "A.J,LEE" <[email protected]> wrote in message
          news:3ba5adb2$[email protected]..
          >
          > I find it result in "dead lock"
          > when I call RequiresNew attributed CMP method in session Bean.
          > Then, Is it possible to use CMP which is set with "RequiresNew"
          transaction attribute?
          >
          > I Wonder why.
          >
          > Thanx in advance.

How to make a session bean interact with a entity bean?

hi,
An entity bean has been created and tested successfully. Values entered into the test app are successfully entered into the pointbase db.
Now trying to create the same feature through session beans. when the method is invoked, it appears ok, but when the database is queried the values have not been entered. Is there anything that could have been missed or incorrect?
the steps to setting up session bean
1)add code to create for JNDI lookup
public void ejbCreate() {
System.out.println("Entering oneManagerEJB.ejbCreate()");
Context c = null;
Object result = null;
if (this.myoneHome == null) {
try {
c = new InitialContext();
result =
c.lookup("java:comp/env/ejb/one");
myoneHome =
(oneHome)javax.rmi.PortableRemoteObject.narrow(result,
oneHome.class);
catch (Exception e) {System.out.println("Error: "+
e); }
2) add business method to enter values into entity bean
public void createone(int number) {
System.out.println("Entering ");
try {
one oneinfo =
myoneHome.create(number);
} catch (Exception e) {
// Join the following two lines in the Source Editor
System.out.println("Error in " + e);
// Join the following two lines in the Source Editor
System.out.println("Leaving ");
3) declare variables and namings
import javax.naming.*;
private oneHome myoneHome;
4) add reference to logical session bean
ejb/one
5) create test app and add entity bean "one" to module. check mappings.
run app

I would do several things which will help track down the problem:
1. Where you have println statements you may want to change these to exceptions, the session bean won't really work if these problems occur and may silently fail. For example, throw a runtime exeption or EJBException to indicate that the entity bean home interface cannot be found.
2. When you create the test application you should replace the ejb module which is automatically created with the ejb module or module(s) containing both of the ejb's. This will ensure that the configuration is preserved. The test application is a standard J2EE application, so modules can be added (you could even have multiple test applications each testing a different ejb, make sure that you use different context roots).
Chris

Problem with getting Entity Beans refreshed within Session bean methods

I hav following code in session and entity beans:
Session bean pseudo code: (PrimaryKey is primary key class for the entity
bean referred here, and MySessionHome is the home interfac class for this
session bean).
public class MySession implements SessionBean {
// This method is present in remote interface class as well.
public void methodA(PrimaryKey pk) {
// code to find entity bean by primary key specified.
update the entity bean, and mark it as isModified.
public void methodB(PrimaryKey pk) {
// code to find entity bean by primary key specified.
do something.
public void methodC() {
MySessionHome sessHome = code to lookup sessionhome from JNDI.
MySessionRI sess = sessHome.create(); // MySessionRI is the remote
interface class for MySession
PrimaryKey pk = new PrimaryKey(params);
sess.methodA(); // LINE ABC1
sess.methodB(); // LINE ABC2
all the entity and session bean methods have required as the TX attribute.
In methodB() on LINE ABC2, the entity bean obtained by findByPrimaryKey does
not reflect the changes made in call to methodA() on LINE ABC1.
Now if I change the LINE ABC1 and LINE ABC2 to
methodA(); // LINE ABC1
methodB(); // LINE ABC2
in this case the entity bean obtained in methodB() has the changes made in
methodA().
Any idea why this is happening?

Hi ad13217 and thanks for reply.
I'm sorry but my code is like this:
javax.naming.Context ctx=new javax.naming.InitialContext();
arguments was an error on copy, but it doesn't work.
Thanks
Fil

EJB 3.0 - Communicate an Applet with a Session Bean

Hello
I'm developing an EJB 3.0 app (eclipse and glassfish tools bundle), and I have an applet that has to use remote session beans.
QUESTION: Is it possible for the applet to connect to EJB?
QUESTION: By creating a J2EE application client project, can I use @EJB annotations to inject the session bean directly to the applet, avoiding the JNDI lookup?
(since I imagine that the anwser to the second one is NO, I do the following consideration)
Given an application client project, I imagine that this application can run remotely on a client machine/JRE. Then this application can use Annotations/injection facilities whenever it runs on a J2EE client container (which I assume consists of a set of libraries provided by the application server vendor, Glassfish in that case). Could this application be deployed using Java Web Start? If so, why can't it be deployed as an applet? (both options run in a client JRE, don't they?).
QUESTION: In either case (applet or JWS), how do I have to package the JAR file (using Eclipse) so that it contains the needed libraries for accessing the EJB? Which are those libraries?
At the time being, I'm trying to implement a sample application that follows the "Applet doing JNDI lookup" approach. I have:
- an EAR project
- an EJB project (containing an Entity Bean and a Stateless Session Bean with a @Remote interface)
@Remote
public interface HelloRemote {
     public String hello(String name);
@Stateless
public class Hello implements HelloRemote {
     @Override
     public String hello(String name) {
          return "Hello "+name+"!!";
}- an Application Client project (containing the applet code):
public class ClientApplet extends JApplet {
     public void init(){
          try {
               Context jndiContext = getInitialContext( );
               HelloRemote server = (HelloRemote) jndiContext.lookup(HelloRemote.class.getName());
               setContentPane(new JLabel(server.hello("Gerard")));
          } catch (NamingException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
     private Context getInitialContext() throws NamingException{
          Properties props = new Properties();
          props.setProperty("java.naming.factory.initial", "com.sun.enterprise.naming.SerialInitContextFactory");
          props.setProperty("org.omg.CORBA.ORBInitialHost", "myhost");
          props.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
          return new InitialContext(props);
}- a static web project (with a sample web page that contains the applet object the corresponding applet JAR file)
I tried to export the Application Client project as an "application client JAR", in the hope that the java EE libraries bundled with glassfish (listed as libraries of this project) would be packaged too.
No success, so now I'll try to copy all the JAR files (one by one) into the +\WebContent\+ folder of the Web Project, and add references to each of them in the archive="" attribute of the +<applet>+ HTML tag. Although this might work, I suspect that I am missing the good/easy way of doing it. Any suggestions?
Thanks in advance,
Gerard
Edited by: gsoldevila on May 6, 2009 7:09 AM

An Applet can communicate with an EJB via JNDI lookup but I would (personally) use an intermediate Servlet to handle this. Client to Servlet communication is http whereas to ejb is iiop - which might be blocked.
Injection only works in managed classes (EJB, Servlet, Listeners..) and an Application Client main class. So yes you could use an app client for handling resource injection.
m

EJB 3.0 Session bean transfers null Entity

Hello all
I am having trouble trying to transfer an Entity from a stateful session bean to a JSP. When I try an identical method with a java client within the OC4J container of JDeveloper, it works fine. However when I deploy the application to OracleAS 10.1.3, I get a null pointer on the entity.
Please help. I have been stuck on this for about 3 weeks, and I've followed documentation to the letter as far as I can see.
Here is the code for the JSP, the (simplified) bean and the Entity in question.
Bean:
import java.util.List;
import javax.annotation.Resource;
import javax.ejb.Stateful;
import javax.persistence.EntityManager;
import javax.persistence.Query;
@Stateful(name="cart")
public class CartBean implements CartRemote, CartLocal {
    @Resource
    protected EntityManager manager;
    public CartBean() {
         public User getUser(String username){
                User user = manager.find(User.class, username);
         return user;
    }The JSP:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<%@ page contentType="text/html;charset=windows-1252"%>
<%@ page import="com.evotec.ereq.CartLocal" %>
<%@ page import="com.evotec.ereq.User" %>
<%@ page import="javax.naming.InitialContext" %>
<%@ page import="java.util.List" %>
<%@ page import="java.util.ArrayList" %>
<%!String m_username = "pbarrett";%>
<%!String emailAddress = "";%>
<%
try {
    InitialContext ctx = new InitialContext();
    CartLocal cart = (CartLocal) ctx.lookup("java:comp/env/cart");
        User user = cart.getUser(m_username);
        emailAddress = user.getEmailAddress();
%>
<html>
<body>
you are: <%= m_username %><BR>
your email address is: <%= emailAddress %><BR>
</body>
</html>
<%
catch (Exception e){
    e.printStackTrace();
%>and the User entity:
import java.io.Serializable;
import java.sql.Timestamp;
import static javax.persistence.AccessType.FIELD;
import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.Table;
import javax.persistence.Id;
@Entity(access=FIELD)
@Table(name="USERS")
public class User implements Serializable {
    @Column(name="CREATION_DATE")
    protected Timestamp creationDate;
    @Column(name="DISPLAY_NAME")
    protected String displayName;
    @Column(name="EMAIL_ADDRESS")
    protected String emailAddress;
    @Id
    @Column(name="USERNAME")
    protected String username;
    @Column(name="USER_ID")
    protected Long userId;
    @Column(name="USER_STATUS")
    protected Long userStatus;
    public User() {
          //JDeveloper-generated getters and setters
}I should point out that I have established that the null pointer is not coming from the CartLocal lookup.
Any help welcome, thanks in advance.
Paul

Hi,
Thanks for the quick response.
I have tried this approach before but when I try and deploy to the server, I get this message:
@PersistenceContext annotation can only be used when a javax.spi.PersistenceProvider is installed.
Is this a missing jar file? If so, which one?
Thanks
Paul

Problems accessing fields in a CMP entity bean from a session bean

Hello everybody,
I'm getting the next problem: when I try to access a field in a CMP entity bean that I have instantiated from a session bean (trhoug entitybean.getNameOfField), I get the error "the entity bean does not exist in the database".
This entity bean is accessing a table in an external database (not the DB of the WAS), but I know that it's getting the correct data from the table, since I check the entitybean.size() and the entitybean.findByPrimaryKey(), and I get the right information. For some reason, the only thing that it doesn't work in the entity bean are the getter/setter methods (I created them automatically after having created the entity fields).
I access the entity bean through its local interface...
I know it's really difficult to give an answer with so few details, but... does anybody think I forgot something important to configure??
Thank very much in advance!!
Isidro

getter and setter methods for cmp-fields are abstract.
getter and setter methods for cmr-fields are abstract.
"John Lee" <[email protected]> wrote:
>
Hi:
Which method in a CMP Entity bean should be abstract? just only SetXXX
and
GetXXX?
Thanks!
John Lee

How does a session bean find entity beans in EJB 3.0

Hi,
I am new to J2EE. I have difficulties finding out how a session bean locates the entity-manager for a group of entity beans. I understand that the entitymanager in the session bean is injected using the PersistenceContext annotation, but I dont see how it locates the intended EntityManager (which could be on another server).
I realize this is probably trivial, but can any of you guys tell me what I am missing?
Best Regards
Thomas

Hi Thomas,
Good question. Each @PersistenceContext annotation is associated with a single Persistence Unit. A Persistence Unit is defined either at the module level or at the .ear level. Each persistence unit has a name associated with it. The unitName() attribute is used to map @PersistenceContext to the associated PersistenceUnit. Since the most common case is that an application will only define one persistence unit, the spec requires that if the unitName() is not specified, it will automatically map to that single persistence unit.
--ken

How to integrate hibernate with Stateless Session bean in weblogic10.0

Hi,
I need to invoke hibernate(3.x) DAO from EJB Stateless Session bean(EJB2.x). I am using mysql database. Can somebody please post the configuration.
Thanks in advance,
Rushi.

Hi Deepak,
Thanks for your reply.
Actually, our stand alone java application already using spring-hibernate feature. Now we are planning divide our application into modules and deploy each module as ejb beans. As it is already integrated with spring-hibernate we are not using entity beans as of now. My understanding is container uses some default transcation management .so, my question is what are all the configurations needs to be done to let weblogic 10.0 server uses org.springframework.orm.hibernate3.HibernateTransactionManager. I mean, is there are any .xml file in weblogic to configure all these? please reply deepak I am struck here..
Regards,
Rushi.

How to achieve Entity Bean methods ONLY by calling them from a Session Bean

Hi,
I used a session bean as a business facade to a entity bean.
In the session bean I achieve the entity bean with a jndiContext.lookup("java:comp/env/ejbEntityBean").
Now I am looking for a solution that it is only possible to call the entity bean methods or the whole entity bean from the corresponding session bean.
In other words: "How can I forbid the access to the entity bean, if the calling object is not the corresponding session bean?"
--->
I only found a way the regulate the access to the entity bean methods by declaring a security-role.
But the existence of the security-role at runtime depends on the calling user-authorizations!
Is there a way to set the entity-security-role within the session bean context?
Best Regards
Steffen

Hi Srikanth Reddy.T,
sorry, I am not looking for a special tag <entity-security-role>.
I am looking for a way to specifiy that my session bean "has" the special security-role (in my case "WebZaehlerEjbRole") of my entity bean "in my case "WebZaehlerEjbRole") that is necessary to call the methods (findAlleEntries, findByWindowId,...) of my entity-bean.
Here is the relevant part of my ejb-jar.ml:
     <assembly-descriptor>
          <security-role>
               <role-name>WebZaehlerEjbRole</role-name>
          </security-role>
          <method-permission>
               <description>method-permission</description>
               <role-name>WebZaehlerEjbRole</role-name>
               <method>
                    <ejb-name>WebZaehlerBean</ejb-name>
                    <method-name>findAllEntries</method-name>
                    <method-params/>
               </method>
               <method>
                    <ejb-name>WebZaehlerBean</ejb-name>
                    <method-name>findByWindowId</method-name>
                    <method-params>
                         <method-param>java.lang.Long</method-param>
                    </method-params>
               </method>
Regards,
Steffen

NON-transactional session bean access entity bean

We are currently profiling our product using Borland OptmizeIt tool, and we
found some interesting issues. Due to our design, we have many session beans which
are non transactional, and these session beans will access entity beans to do
the reading operations, such as getWeight, getRate, since it's read only, there
is no need to do transaction commit stuff which really takes time, this could
be seen through the profile. I know weblogic support readonly entity bean, but
it seems that it only has benefit on ejbLoad call, my test program shows that
weblogic still creates local transaction even I specified it as transaction not
supported, and Transaction.commit() will always be called in postInvoke(), from
the profile, we got that for a single method call, such as getRate(), 80% time
spent on postInvoke(), any suggestion on this? BTW, most of our entity beans are
using Exclusive lock, that's the reason that we use non-transactional session
bean to avoid dead lock problem.
Thanks

Slava,
Thanks for the link, actually I read it before, and following is what I extracted
it from the doc:
<weblogic-doc>
Do not set db-is-shared to "false" if you set the entity bean's concurrency
strategy to the "Database" option. If you do, WebLogic Server will ignore the
db-is-shared setting.
</weblogic-doc>
Thanks
"Slava Imeshev" <[email protected]> wrote:
Hi Jinsong,
You may want to read this to get more detailed explanation
on db-is-shared (cache-between-transactions for 7.0):
http://e-docs.bea.com/wls/docs61/ejb/EJB_environment.html#1127563
Let me know if you have any questions.
Regards,
Slava Imeshev
"Jinsong HU" <[email protected]> wrote in message
news:[email protected]...
Thanks.
But it's still not clear to me in db-is-shared setting, if I specifiedentity
lock as database lock, I assumed db-is-shared is useless, because foreach
new
transaction, entity bean will reload data anyway. Correct me if I amwrong.
Jinsong
"Slava Imeshev" <[email protected]> wrote:
Jinsong,
See my answers inline.
"Jinsong Hu" <[email protected]> wrote in message
news:[email protected]...
Hi Slava,
Thanks for your reply, actually, I agree with you, we need to
review
our db
schema and seperate business logic to avoid db lock. I can not say,guys,
we need
to change this and that, since it's a big application and developedsince
EJB1.0
spec, I think they are afraid to do such a big change.Total rewrite is the worst thing that can happen to an app. The
better aproach would be identifying the most critical piece and
make a surgery on it.
Following are questions in my mind:
(1) I think there should be many companies using weblogic serverto
develop
large enterprise applications, I am just wondering what's the maintransaction/lock
mechanism that is used? Transional session / database lock,
db-is-shared
entity
I can't say for the whole community, as for my experience the standard
usage patthern is session fasades calling Entity EJBs while having
Required TX attribute plus plain transacted JDBC calls for bulk
reads or inserts.
is the dominant one? It seems that if you speficy database lock,
the
db-is-shared
should be true, right?Basically it's not true. One will need db-is-shared only if thereare
changes
to the database done from outside of the app server.
(2) For RO bean, if I specify read-idle-timeout to 0, it shouldonly
load
once at the first use time, right?I assume read-timeout-seconds was meant. That's right, but if
an application constantly reads new RO data, RO beans will be
constantly dropped from cache and new ones will be loaded.
You may want to looks at server console to see if there's a lot
of passivation for RO beans.
(3) For clustering part, have anyone use it in real enterpriseapplication?
My concern, since database lock is the only way to choose, how aboutthe
affect
of ejbLoad to performance, since most transactions are short live,if high
volume
transactions are in processing, I am just scared to death about
the
ejbLoad overhead.
ejbLoad is a part of bean's lifecycle, how would you be scared ofit?
If ejbLoads take too much time, it could be a good idea to profile
used SQLs. Right index optimization can make huge difference.
Also you may want cosider using CMP beans to let weblogic
take care about load optimization.
(4) If using Optimization lock, all the ejbStore need to do
version
check
or timestamp check, right? How about this overhead?As for optimistic concurrency, it performs quite well as you can
use lighter isolation levels.
HTH,
Slava Imeshev
"Jinsong Hu" <[email protected]> wrote in message
news:[email protected]...
We are using Exclusive Lock for entity bean, because of we do
not
want
to
load
data in each new transaction. If we use Database lock, that means
we
dedicate
data access calls to database, if database deadlock happens,
it's
hard
to
detect,
while using Exclusive lock, we could detect this dead lock in
container
level.
The problem is, using Exclusive concurrency mode you serialize
access to data represented by the bean. This aproach has negative
effect on ablity of application to process concurrent requests.As
a
result the app may have performance problems under load.
Actually, at the beginnning, we did use database lock and usingtransactional
The fact that you had database deadlocking issues tells that
application logic / database schema may need some review.
Normally to avoid deadlocking it's good to group database
operations mixing in updattes and inserts into one place so
that db locking sequence is not spreaded in time. Moving to
forced serialized data access just hides design/implementation
problems.
session bean, but the database dead lock and frequent ejbLoad
really
kill
us,
so we decided to move to use Exclusive lock and to avoid dead
lock,
we
change
some session bean to non-transactional.Making session beans non-transactions makes container
creating short-living transactions for each call to entity bean
methods. It's a costly process and it puts additional load to
both container and database.
We could use ReadOnly lock for some entity beans, but since weblogicserver will
always create local transaction for entity bean, and we found
transaction
commit
is expensive, I am arguing why do we need create container leveltransaction for
read only bean.First, read-only beans still need to load data. Also, you may seeRO
beans
contanly loading data if db-is-shared set to true. Other reason
can
be
that
RO semantics is not applicable the data presented by RO bean (forinstance,
you have a reporting engine that constantly produces "RO" data,
while
application-consumer of that data retrieves only new data and neverasks
for "old" data). RO beans are good when there is a relatively stable
data
accessed repeatedly for read only access.
You may want to tell us more about your app, we may be of help.
Regards,
Slava Imeshev
I will post the performance data, let's see how costful
transaction.commit
is.
"Cameron Purdy" <[email protected]> wrote:
We are currently profiling our product using Borland
OptmizeIt
tool,
and we
found some interesting issues. Due to our design, we have
many
session
beans which
are non transactional, and these session beans will access
entity
beans
to
do
the reading operations, such as getWeight, getRate, since
it's
read
only,
there
is no need to do transaction commit stuff which really takes
time,
this
could
be seen through the profile. I know weblogic support readonly
entity
bean,
but
it seems that it only has benefit on ejbLoad call, my test
program
shows
that
weblogic still creates local transaction even I specified
it
as
transaction not
supported, and Transaction.commit() will always be called
in
postInvoke(),
from
the profile, we got that for a single method call, such as
getRate(),
80%
time
spent on postInvoke(), any suggestion on this? BTW, most of
our
entity
beans are
using Exclusive lock, that's the reason that we use
non-transactional
session
bean to avoid dead lock problem.I am worried that you have made some decisions based on an improper
understand of what WebLogic is doing.
First, you say "non transactional", but from your description
you
should
have those marked as tx REQUIRED to avoid multiple transactions
(since
non-transactional just means that the database operation becomesits
own
little transaction).
Second, you say you are using exclusive lock, which you shouldonly
use
if
you are absolutely sure that you need it, (and note that it
does
not
work in
a cluster).
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"Jinsong Hu" <[email protected]> wrote in message
news:[email protected]...
>

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) ?

Paradox - Should entity CMP EJB be faster than stateless session bean?

Please bear with me on this.
Just thinking of this scenario: hello world application. It can be implemented both as stateless session bean and entity bean.
There's no persistent. So for the entity bean, it will be container managed, and no code to do anything to the load/remove/create. - comparably the same as stateless bean.
Next, for the stateless session bean, each client call would require a dedicated instance of the EJB on the server (although for a very short amount of time). For the entity bean, it's shared, so only 1 instance is needed. It's also thread safe.
So, for a very high traffic, shouldn't the entity bean do better because of single instance?
What's other overhead?
Does the entity bean cost more connections than the stateless bean?

Feels like a comparison between apples and oranges.
A stateless session bean is like every other instance, so these can be pooled by the EJB container. The container is free to create an instance for each client if necessary. That's different.
A stateless session bean doesn't have to deal with a database that may or may not be located on another machine the way an entity bean does. There could be another network round trip involved. That's different.
Session and entity beans are intended for entirely different purposes. Just because you can write Hello World with both doesn't mean it's representative of what EJBs are used for. I don't think it's a good, meaninful comparison. JMO - MOD

Can CMT Session Bean call BMP Entity Bean in WebLogic 6.0?

          Hi
          Does anybody successfully use CMT Session Bean calling BMP +CMT Entity bean in
          WebLogic6.0? I have the following problem.
          Any idea will be appreciated.
          --Winston
          Let's say we have a Session bean SB, it uses container to manage the transaction.
          A method of SB will call an Entity Bean EB which adopts bean-managed persistence.
          Both SB and EB use CMT and all of their methods use "required" in the descriptor
          file.
          1. If the connection con.getAutoCommit() is true in the EB, then the transaction
          within SB cannot be rolled back as the ejbCreate() has already commit into the
          database.
          2. On the other hand if Connecton of EB con.getAutoCommit() is false, then container
          cannot successfully commit the transaction from SB's method, as EjbCreate and
          EjbStore() in EB are likely using the different database connections, which causes
          EbjStore() fail and the following error message will be sent to the Console:
          ============================================================
          "<Jul 9, 2001 4:16:48 PM PDT> <Error> <EJB> <Exception during commit of transacti
          on transaction=(IdHash=7738920,Name = [EJB TraderBeanImpl.buy()],Xid=105:5e6719a
          ded42e332,Status=Rolled back. [Reason = weblogic.utils.NestedRuntimeException:
          E
          rror writing from beforeCompletion - with nested exception:
          [java.rmi.NoSuchObjectException: Exception from ejbStore:javax.ejb.NoSuchEntityE
          xception: ejbStore: AccountBean (4003) not updated]],numRepliesOwedMe=0,numRepli
          esOwedOthers=0,seconds since begin=0,seconds left=30,SCInfo[examplesServer]=(sta
          te=rolledback),properties=({weblogic.transaction.name=[EJB TraderBeanImpl.buy()]
          })): java.rmi.NoSuchObjectException: Exception from ejbStore:javax.ejb.NoSuchEnt
          ityException: ejbStore: AccountBean (4003) not updated
          at weblogic.ejb20.internal.EJBRuntimeUtils.throwRemoteException(EJBRunti
          meUtils.java:57)
          at weblogic.ejb20.manager.DBManager.beforeCompletion(DBManager.java:364)
          at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManag
          er.java:211)
          at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(Serv
          erSCInfo.java:511)
          at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(Se
          rverSCInfo.java:78)
          at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAn
          dChain(ServerTransactionImpl.java:893)
          at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(
          ServerTransactionImpl.java:1229)
          at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
          sactionImpl.java:168)
          at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:2
          01)
          at examples.ejb.basic.statefulSession.TraderBeanEOImpl.buy(TraderBeanEOI
          mpl.java:37)
          at examples.ejb.basic.statefulSession.TraderBeanEOImpl_WLSkel.invoke(Tra
          derBeanEOImpl_WLSkel.java:76)
          at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
          va:373)
          at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
          va:237)
          at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
          andler.java:118)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:17)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          --------------- nested within: ------------------
          weblogic.utils.NestedRuntimeException: Error writing from beforeCompletion - wit
          h nested exception:
          [java.rmi.NoSuchObjectException: Exception from ejbStore:javax.ejb.NoSuchEntityE
          xception: ejbStore: AccountBean (4003) not updated]
          at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManag
          er.java:220)
          at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(Serv
          erSCInfo.java:511)
          at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(Se
          rverSCInfo.java:78)
          at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAn
          dChain(ServerTransactionImpl.java:893)
          at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(
          ServerTransactionImpl.java:1229)
          at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
          sactionImpl.java:168)
          at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:2
          01)
          at examples.ejb.basic.statefulSession.TraderBeanEOImpl.buy(TraderBeanEOI
          mpl.java:37)
          at examples.ejb.basic.statefulSession.TraderBeanEOImpl_WLSkel.invoke(Tra
          derBeanEOImpl_WLSkel.java:76)
          at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
          va:373)
          at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
          va:237)
          at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
          andler.java:118)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:17)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          --------------- nested within: ------------------
          weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion
          : sync = weblogic.ejb20.internal.TxManager$TxListener@356eb0
          Error writing from beforeCompletion - with nested exception:
          [weblogic.utils.NestedRuntimeException: Error writing from beforeCompletion -
          wi
          th nested exception:
          [java.rmi.NoSuchObjectException: Exception from ejbStore:javax.ejb.NoSuchEntityE
          xception: ejbStore: AccountBean (4003) not updated]]
          at weblogic.transaction.internal.TransactionImpl.throwRollbackException(
          TransactionImpl.java:1261)
          at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
          sactionImpl.java:218)
          at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:2
          01)
          at examples.ejb.basic.statefulSession.TraderBeanEOImpl.buy(TraderBeanEOI
          mpl.java:37)
          at examples.ejb.basic.statefulSession.TraderBeanEOImpl_WLSkel.invoke(Tra
          derBeanEOImpl_WLSkel.java:76)
          at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
          va:373)
          at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
          va:237)
          at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
          andler.java:118)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:17)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >"


We did receive a 4.5.1 / 5.1 interoperability patch - but it wasn't quite 'seamless'.
We never tried to use it.
SOAP? Isn't that around 50 times slower than RMI?
Mike
"Gary Mui" <[email protected]> wrote:
We ran into this issue last fall and got some feedback from weblogic
support. They originally said that it could be done (as well as different
versions talking to one another via JMS) but it turned out that they
were
incorrect and ended up saying that it is not possible. Before 6.0 went
GA,
BEA said that there would be a interoperability patch to do this, but
I've
never seen nor heard of anything regarding it. As a workaround, we
implemented 4.5.1 / 6.0 communication via SOAP.
Mike Reiche wrote in message <3b1bcaec$[email protected]>...
I have the same question - and more. Last year we were told that wecould
not use
RMI (and ejbs) between 4.5.1 and 5.1. Which seems kinda weird becauseI've
heard
of people using WL ejbs from Tomcat. This issue has caused us to avoidusing
WL ejbs in any future development which has any chance of ever beingused
by any
app server (WL included) that is not under the direct control of thedata
center.
I've been trying to convince the Architecture team here that we canuse WL
EJBs
and we can call them from other app servers - but can't seem to getany
supporting
statement from BEA (maybe I haven't tried hard enough).
Anyway, a response from BEA would be appreciated.
- Mike
"Madhu K" <[email protected]> wrote:
Is it possible to call a (stateless session) bean deployed in weblogic
6.0
from a bean in weblogic 5.1? I have two versions of weblogic running
on two
different hosts and I have to call a bean that is running in 6.0 from
5.1.
Are there any limitations?
Appreciate any feedback/suggestions.
Thanks,
Madhu

TX isolation level with stateless session bean in oc4j

Hi All,
I have a stateless session bean with container managed transaction method. This method is called in a Servlet. This method retrieves data from database using 'ejb-location'connection pool and closes the connection inside. Max-connection setting for connection pool is 50
I am facing a problem running servlet multiple times.
When i have the tx_attribute as Supports, it works fine. I can run the servlet hundreds of times
But when i have the tx_attribute as Required, i am able to run servlet only 50 times and further it says 'Max connection limit exceed..unable to get the connection'.
I assume that with 'Required' attribute, it starts a transaction. Why is the transaction not getting completed at end of method? Is transaction hanging somewhere?
I assume that i am closing the connection properly as it is working fine with supports attribute.
When i monitor database, there are only 20 connections.
Why am i seeing this behaviour?
Thanks
srinath

Hi Deepak,
Thanks for your reply.
Actually, our stand alone java application already using spring-hibernate feature. Now we are planning divide our application into modules and deploy each module as ejb beans. As it is already integrated with spring-hibernate we are not using entity beans as of now. My understanding is container uses some default transcation management .so, my question is what are all the configurations needs to be done to let weblogic 10.0 server uses org.springframework.orm.hibernate3.HibernateTransactionManager. I mean, is there are any .xml file in weblogic to configure all these? please reply deepak I am struck here..
Regards,
Rushi.

Session bean with 2 entity bean

Similar Messages

Maybe you are looking for