Query related to Entity Beans

Hi Java Friends,
Iam Vijay Kumar.
Iam developing Entity Bean.
I have written a EntityBean called StudentEJB which implements EntityBean
My Student component consists of
- StudentHome
- StudentRemote
- StudentEJB [ implements EntityBean]
- StudentDAO [consists of Method prototype for storing, deleting, retrieving the Students Data ]
- StudentDAOPB [consists of implentation of Methods of the StudentDAO Interface.]
- StudentDetails [consists of the implementation of the methods for getting the Student data]
- StudentDAOSysExcetion [which consists of Implementaion for the creation of Exception.]
May i know the deployment process for Entity Beans without IDE in WebLogic Server.
regards.,
vijay kumar

it would be something like this, Try this
1 localejbs/AF_Modules/PayloadSwapBean Local Enterprise Bean swaptxt
2 localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean trans3
3 localejbs/AF_Modules/PayloadSwapBean Local Enterprise Bean swapxml
4 localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean trans2
5 localejbs/AF_Modules/PayloadSwapBean Local Enterprise Bean swappdf
6 localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean trans1
7 sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean Local Enterprise Bean mail
swapxml -> swap.keyName -> payload-name
swapxml> swap.keyValue> file2
swappdf -> swap.keyName -> payload-name
swappdf> swap.keyValue> file1
trans1> Transform.ContentDescription>file1
trans1> Transform.ContentDisposition>attachment
trans1> Transform.ContentType>application/pdf;name="file1.pdf"
trans2>Transform.ContentDescription>file2
trans2>Transform.ContentDisposition>attachment
trans2> Transform.ContentType>application/xml;name="file2.xml"
trans3> Transform.ContentDescription>file3
trans3> Transform.ContentDisposition>attachment
trans3> Transform.ContentType>application/txt;name="file3.txt"
mail --> mime.contenttype --> multipart/mixed
I have not tried this myself. but it should work

Similar Messages

Named query in Entity Bean - Problem with embedded class

Hello Forum,
I'm trying to set up a named query in my Entity Bean and I'm unable to get
it up and running for an embedded class object.
The class hierarchy is as follows:
         @MappedSuperclass
         AbstractSapResultData (contains dayOfAggregation field)
                 ^
                 |
        @MappedSuperclass
        AbstractSapUserData (contains the timeSlice field)
                 ^
                 |
          @Entity
          SapUserDataThe named query is as follows:
@NamedQuery(name = SapUserDataContext.NAMED_QUERY_NAME_COUNT_QUERY,
                            query = "SELECT COUNT(obj) FROM SapUserData AS obj WHERE "
                                     + "obj.sapCustomerId"
                                     + "= :"
                                     + SapResultDataContext.COLUMN_NAME_SAP_CUSTOMER_ID
                                     + " AND "
                                     + "obj.sapSystemId"
                                     + "= :"
                                     + SapResultDataContext.COLUMN_NAME_SAP_SYSTEM_ID
                                     + " AND "
                                     + "obj.sapServerId"
                                     + "= :"
                                     + SapResultDataContext.COLUMN_NAME_SAP_SERVER_ID
                                     + " AND "
                                     + "obj.dayOfAggregation.calendar"
                                     + "= :"
                                     + DayContext.COLUMN_NAME_DAY_OF_AGGREGATION
                                     + " AND "
                                     + "obj.timeSlice.startTime"
                                     + "= :"
                                     + "timeSliceStartTime"
                                     + " AND "
                                     + "obj.timeSlice.endTime"
                                     + "= :"
                                     + "timeSliceEndTime")The query deploys and runs except that part:
                                     + "obj.dayOfAggregation.calendar"
                                     + "= :"
                                     + DayContext.COLUMN_NAME_DAY_OF_AGGREGATIONI don't see any difference to the part of the query accessing the timeSlice
field which is also an embedded class object - I access it in exactly the same way:
                                     + "obj.timeSlice.startTime"
                                     + "= :"
                                     + "timeSliceStartTime"
                                     + " AND "
                                     + "obj.timeSlice.endTime"
                                     + "= :"
                                     + "timeSliceEndTime"The problem is that the complete query runs on JBoss application server
but on the SAP NetWeaver application server it only rund without the
                                     + "obj.dayOfAggregation.calendar"
                                     + "= :"
                                     + DayContext.COLUMN_NAME_DAY_OF_AGGREGATIONpart - If I enable that part on SAP NetWeaver the server complains:
[EXCEPTION]
{0}#1#java.lang.IllegalArgumentException: line 1: Comparison '=' not defined for dependent objects
SELECT COUNT(obj) FROM SapUserData AS obj WHERE obj.sapCustomerId= :sap_customer_id AND obj.sapSystemId= :sap_system_id AND obj.sapServerId= :sap_server_id AND obj.dayOfAggregation.calendar= :day_of_aggregation AND obj.timeSlice.startTime= :timeSliceStartTime AND obj.timeSlice.endTime= :timeSliceEndTime
                                                                                                                                                                                             ^I know that this isn't an application server specific forum but the SAP NetWeaver server is the most strict EJB 3.0 and JPA 1.0 implementation I've seen so far so I think I'm doing something wrong there.
Someone in the SAp forum mentioned:
The problem here is that you compare an input-parameter with an embeddable field of your entity.
Regarding to the JPQL-grammer (spec 4.14) you are not allowed to compare
with the non-terminal embeddable field but with the terminal fields of your
embeddable. Stating that your embedded class might have the fields
startTime and endTime your JPQL query might look like this:
Query q = em.createQuery("SELECT count(obj.databaseId) FROM SapUserData obj WHERE obj.timeSlice.startTime = :startTime AND obj.timeSlice.endTime = :endTime");
q.setParameter("startTime", foo.getStartTime());
q.setParameter("endTime", foo.getEndTime());
q.getResultList();
This limitation in the JPQL grammar is rather uncomfortable.
An automatic mapping of the parameter's fields to the terminal fields of your
embedded field would be more convenient. The same can be said for lists
as parameter-values which is possible in HQL, too. I think we have to wait
patiently for JPA 2.0 and hope for improvements there. :-)
With that help I was able to get it up and running for the timeSlice field but
I don't see the difference to the dayOfAggregation field which is also just
another embedded class using an object of a class annotated with
@Embeddable.
The get method of the dayOfAggregation field is as follows:
     * Get method for the member "<code>dayOfAggregation</code>".
     * @return Returns the dayOfAggregation.
    @Embedded
    @AttributeOverrides({@AttributeOverride(name = "calendar", /* Not possible to use interface constant here - field name must be used for reference */
                                            column = @Column(name = DayContext.COLUMN_NAME_DAY_OF_AGGREGATION,
                                                             nullable = false)),
                         @AttributeOverride(name = "weekday",
                                            column = @Column(name = DayContext.COLUMN_NAME_WEEKDAY,
                                                             nullable = false)),
    public Day getDayOfAggregation() {
        return this.dayOfAggregation;
    }The link to my question in the SAP forum for reference:
https://www.sdn.sap.com/irj/sdn/thread?messageID=3651350
Any help or ideas would be greatly appreciated.
Thanks in advance.
Henning Malzahn

Hello Forum,
got a response in the SAP forum - Issue is a bug in the SAP NetWeaver
app. server.
Henning Malzahn

Data Warehouse report query using Entity Beans

I have used the EJB technology on one project, so I am not all that familiar with
best practices.
In my new project, I have to produce reports using a query that goes against a
dimensional database. I am wondering what options I have to run the query and
extract the results given that the application will run on WebLogic.
1) Straight JDBC
2) BMP
3) CMP (could be a problem because the quety is a join query, but I am not sure
if WebLogic requires that the query is against a table rather than a view)
The query is read-only. I am more interested in ease of coding and code management
rather than application performance at this point because I think the query will
spend a relatively large time executing on the Oracle database.
I would like to hear the best practices to be employed in this case. Thanks very
much!
Ravi.

Don't use entity beans for this. Straight JDBC is not perfect either, but it
is preferable to entity beans for this type of work.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Ravi Navanee" <[email protected]> wrote in message
news:3c92693d$[email protected]..
>
I have used the EJB technology on one project, so I am not all thatfamiliar with
best practices.
In my new project, I have to produce reports using a query that goesagainst a
dimensional database. I am wondering what options I have to run the queryand
extract the results given that the application will run on WebLogic.
1) Straight JDBC
2) BMP
3) CMP (could be a problem because the quety is a join query, but I am notsure
if WebLogic requires that the query is against a table rather than a view)
The query is read-only. I am more interested in ease of coding and codemanagement
rather than application performance at this point because I think thequery will
spend a relatively large time executing on the Oracle database.
I would like to hear the best practices to be employed in this case.Thanks very
much!
Ravi.

Nested EJB QL Query in Entity Bean

Hi All
We are using CMP based Entity bean which has name <i>EmployeeBean</i> with a field pSALARY. We want a finder method which return an employee with maximum salary. we are using following Query.
<b>select object(b) from EmployeeBean b where
b.pSALARY = (select max(c.pSALARY) from EmployeeBean c)</b>
But we validate the query in NWDS but we get following error
<b>EJB QL statement is invalid. See General User Output View for details.</b>
General User output view is blank. so we could not analyze the error in this query.
can anybody tell us what's wrong with this Query. Or else how we should formulate the query in another way so that it gives us required result.
Thanks in Advance

Hi
just try like this...
MAX() and MIN() can be used to find the largest or smallest value in a collection of any type of CMP field. It cannot be used with identifiers or paths that terminate in a CMR field. The result type will be the type of CMP field that is being evaluated. For example, the following query returns the highest amount paid for a Job.
<b>SELECT MAX( job.pSALARY )
FROM EmployeeBean AS c, IN (c.EmployeeBean) AS job</b>
The MAX() and MIN() functions can be applied to any valid CMP value including primitive types, strings, and even serializable objects. As you may recall, a CMP field can be a serializable application object that is converted to a binary field and stored in a database. The result of applying the MAX() and MIN() functions to serializable objects is not specified, however, because there is no standardized way of determining which serializable object is greater than another.
The result of applying the MAX() and MIN() functions to a String is type depends on the underlying data store used. This uncertainty results from problems inherent in String comparisons, which are addressed fully in the section "The Problems with Strings."
just refer this link also..
http://www.theserverside.com/articles/article.tss?l=MonsonHaefel-Column5
Regards
Kishor Gopinathan

Change one entity bean query, errors pop up in another... why?

In my application I have the following entity bean:
@Entity
@Table(name = "ventureprofile")
@SecondaryTable(name = "venture")
@NamedQueries( {
        @NamedQuery(name = "Ventureprofile.findByVentureprofileid", query = "SELECT v FROM Ventureprofile v WHERE v.ventureprofileid = :ventureprofileid"),
        @NamedQuery(name = "Ventureprofile.findByVentureid", query = "SELECT v FROM Ventureprofile v WHERE v.ventureid = :ventureid"),
        @NamedQuery(name = "Ventureprofile.findByLogoimagelocation", query = "SELECT v FROM Ventureprofile v WHERE v.logoimagelocation = :logoimagelocation"),
        @NamedQuery(name = "Ventureprofile.findByVisible", query = "SELECT v FROM Ventureprofile v WHERE v.visible = :visible ORDER BY v.venturename")
        //@NamedQuery(name = "Ventureprofile.findByVisibleRange", query = "SELECT v FROM Ventureprofile v WHERE v.visible = :visible ORDER BY v.venturename OFFSET 1 LIMIT 2")
public class Ventureprofile implements Serializable {
    @GeneratedValue(strategy=GenerationType.AUTO, generator="Ventureprofile.ventureprofileid.seq")
    @SequenceGenerator(name="Ventureprofile.ventureprofileid.seq", sequenceName="ventureprofile_ventureprofileid_seq", allocationSize=1)
    @Column(name = "ventureprofileid", nullable = false)
    private BigInteger ventureprofileid;
    @Id
    @JoinColumn(name = "ventureid", referencedColumnName = "ventureid")
    private long ventureid;
    @Lob
    @Column(name = "venturesummary")
    private String venturesummary;
    @Column(name = "logoimagelocation")
    private String logoimagelocation;
    @Column(name = "visible", nullable = false)
    private char visible;
    @Column(table = "venture", name = "venturename", insertable=false)
    private String venturename;
...and another entity bean:
@Entity
@Table(name = "venturelink")
@NamedQueries( {
        @NamedQuery(name = "Venturelink.findByVenturelinkid", query = "SELECT v FROM Venturelink v WHERE v.venturelinkid = :venturelinkid"),
        @NamedQuery(name = "Venturelink.findByVentureprofileid", query = "SELECT v FROM Venturelink v WHERE v.ventureprofileid = :ventureprofileid"),
        @NamedQuery(name = "Venturelink.findByLinkurl", query = "SELECT v FROM Venturelink v WHERE v.linkurl = :linkurl"),
        @NamedQuery(name = "Venturelink.findByLinkname", query = "SELECT v FROM Venturelink v WHERE v.linkname = :linkname")
public class Venturelink implements Serializable {
    @Id
    @GeneratedValue(strategy=GenerationType.AUTO, generator="Venturelink.venturelinkid.seq")
    @SequenceGenerator(name="Venturelink.venturelinkid.seq", sequenceName="venturelink_venturelinkid_seq", allocationSize=1)
    @Column(name = "venturelinkid", nullable = false)
    private BigInteger venturelinkid;
    @Column(name = "ventureprofileid", nullable = false)
    private long ventureprofileid;
    @Column(name = "linkurl", nullable = false)
    private String linkurl;
    @Column(name = "linkname", nullable = false)
    private String linkname;
...    If I uncomment the last NamedQuery ~
@NamedQuery(name = "Ventureprofile.findByVisibleRange", query = "SELECT v FROM Ventureprofile v WHERE v.visible = :visible ORDER BY v.venturename OFFSET 1 LIMIT 2")I experience the following runtime error:
javax.ejb.EJBException: nested exception is: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.RemoteException: null; nested exception is:
        java.lang.IllegalArgumentException: NamedQuery of name: Venturelink.findByVentureprofileid not found.Container: Glassfish
Database: Postgres
OS: WinXP sp2
Persistence provider: Toplink
Note that I am not altering 'Venturelink', I am only altering 'Ventureprofile', however errors are manifesting themselves in 'Venturelink'.
I have heard a rumor that 'OFFSET' and 'LIMIT' are not supported by the majority of persistence providers, but that would be a ridiculous situation... unless the majority of persistence providers lazy-load results when they are pulled from a result set. Is that the case?
Regardless, this is making me guess what is going on behind the scenes. So, at some point during runtime, is all of my EJB query code getting munged together? And then whatever interprets them into SQL is giving up as soon as it finds a query it doesn't like? That's what this smells like, at least...
Typically, I find weird errors like this crop up when I'm doing something stupid that a system wasn't designed to handle. So I'd really appreciate it if someone would set me straight.

Solution, via Doug Clarke at the TopLink forums:
2. JPA's query language does not support OFFSET and LIMIT. Instead JPA offers setFirstResult(int) and setMaxResult(int) on the Query object. In TopLink this generally translates to JDBC calls of similar names.
(Thanks Doug!)
so yeah... unless somebody knows otherwise and I'm wrong (often the case), looks like things choke across multiple entity beans as soon as one malformed query is found. Not good.

Query about reentrant in ejb-jar.xml file(in case of entity Bean)

Hi all friends,
I am new to EJB I couldn't understand in ejb-jar.xml file in case Entity Bean[<reentrant>False</reentrant>
&<reentrant>true</reentrant>]what is the function of this tag and what is the effect of value true and false of this tag.Can any one please explain it.
Regards
Bikash

Hi,
Re-entrant tag is used in the ejb-jar.xml to notify the container if you would want your bean to call itself through another bean.
Most of the time you would want it to be set to FALSE because you would have to consider the multi-threading issues if you set it TRUE.
Regards
Meka Toka

Container Managed Persistence entity bean relationship fields

I want to ask something that until now still confuse. Did Relationship fields in Container Managed Persistence entity beans declare , inside Database table or only Persistence fields .
If Relationship fields not declare inside database table ,how if SQL calls the relationship fields between related entity bean.
did container handle this task.
example: I have 2 entity bean with CMP(Container Managed Persistence)version 2.0
call Player and Team. every entity bean have own relationship fields and persistence fields.
player has playerId(primary key),name,position,age persistence fields and teams is relationship fields.
team has teamId(primary key),name,city and players is relationship fields.
I know that all persistence fields is declare in own database table but how about relationship fields.
can you tellme, How SQL calls can access relationship fields if relatiosnship fields is not declare in database table.
I use J2EE RI SDK version 1.3
and deploytool .
thank's .

thank's for your reply .Now I have another problem
I use J2EE RI from java.sun .I try to follow example in j2eetutorial about CMP Example call RosterApp.ear .
I dont'change anything code inside RosterApp.ear but when I deploy and runclient command thereis syntax error :
java.rmi.ServerException: Remote exception occured in server thread :nested exception is java.rmi.ServerException :exception thrown from bean :nested exception is : java.ejb.EJBException :nested exception is :java.sql.SQLException :syntax error or access violation ,message from server: "you have an error in SQL syntax near "
"leagueBeanTable" WHERE "leagueId" = 'L1' at line 1
in example ,RosterApp.ear use Cloudscape database ,but I try to use Mysql database for RosterApp.ear ,is there any different syntax SQL from Cloudscape to Mysql .
if like that ,so I must edit first SQL calls from Cloudscape to MYSQL . I think because relationship fields is for entity beans only ,so how if mysql database want to access foreign key another table because foreign key isn't declare in databse table.
example : I have 3 entity bean call player, team, league .
1. PlayerEJB have persistence fields name, position, playerId(primary key), cmr fields is teams
2. TeamEJB have persistence fields name, city, teamId (primary key) , cmr fields is players and leagues .
3. LeagueEJB have persistence fields name ,sport, leagueId(primary key), cmr fields is teams
so table is
PlayerEJB <--->TeamEJB<--->LeagueEJB
Player have some finder method call findBySport(String Sport) .
because Sport is persistence fields for LeagueEJB
so PlayerEJB must traverse TeamEJB first before LeagueEJB
EJB QL : SELECT distinct object(p) FROM Player (p) IN (p.teams) AS t
WHERE t.league.sport = ?1
I know that Container will translates EJB QL to SQL calls ,but default is only for cloudscape database and I use for MYsql .
so can you helpme how to query method findBySport(String sport) to Mysql calls .
thereis no foreign key between table in database table there is only Relationship fields in entity bean.

Error in deploying entity beans - migration from JBoss to Weblogic 10.3.4

Hi,
I am migrating EJB2.x code from JBoss to Weblogic 10.3.4. As a first step, I am tyring to deploy just Entity beans. I get following error when deploying to server.
'weblogic.application.ModuleException: Exception preparing module: EJBModule(myEJB.jar)
Unable to deploy EJB: CollMetaData from myEJB.jar:
[EJB:011017]Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'. The error was:
There are 1 nested errors:
java.lang.NullPointerException
     at weblogic.ejb.container.cmp.rdbms.finders.EjbqlFinder.setMethods(EjbqlFinder.java:288)
     at weblogic.ejb.container.cmp.rdbms.Deployer.processFinders(Deployer.java:744)
     at weblogic.ejb.container.cmp.rdbms.Deployer.readTypeSpecificData(Deployer.java:446)
     at weblogic.ejb.container.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:506)
     at weblogic.ejb.container.persistence.PersistenceType.setupDeployer(PersistenceType.java:455)
     at weblogic.ejb.container.deployer.CMPInfoImpl.setup(CMPInfoImpl.java:118)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1214)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Can someone help me fixing the issue?
I changed schema locations of descriptor files as suggested at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13706/overview.htm#i1074199 (see the third category for '*Enterprise Bean 2.1*' in the listing Table 1-1). Alternatively, you may see the schema locations for EJB2.0 directly at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13719/dd_reference.htm#EJBPG481

JRE version in JBoss is 1.6.0_16. JVM in web logic is pointing to jrockit_160_22_D1.1.1-3 which is come in the package. It doesn't seem to be related to JVM version mismatch.
I think it is an issue with definitions in weblogic-cmp-rdbms-jar.xml file. How should be the definition of entity-descriptor appear for entity bean which has finder methods in ejb-jar.xml?
Please see the snippets from corresponding descriptor files below.
ejb-jar.xml
=========
<entity>
<display-name>EmpBean</display-name>
<ejb-name>EmpBean</ejb-name>
<local-home>LocalEmpBeanHome</local-home>
<local>LocalEmpBean</local>
<ejb-class>EmpBeanBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>EmpBean</abstract-schema-name>
<cmp-field>
<field-name>firstName</field-name>
</cmp-field>
<cmp-field>
<field-name>lastName</field-name>
</cmp-field>
<cmp-field>
<field-name>phone</field-name>
</cmp-field>
<cmp-field>
<field-name>address</field-name>
</cmp-field>
<primkey-field>lastName</primkey-field>
<query>
<query-method>
          <method-name>findByPrimaryKey</method-name>
               <method-params>
               <method-param>java.lang.String</method-param>
               </method-params>
          </query-method>
          <ejb-ql>SELECT Object(o) FROM EmpBean o WHERE o.lastName= ?1</ejb-ql>
     </query>
</entity>
weblogic-jar.xml
============
<weblogic-enterprise-bean>
<ejb-name>EmpBean</ejb-name>
<entity-descriptor>
     <pool>
          <max-beans-in-free-pool>20</max-beans-in-free-pool>
          <initial-beans-in-free-pool>5</initial-beans-in-free-pool>
     </pool>
<persistence>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>meta-inf/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-use>
<finders-load-bean>true</finders-load-bean>
</persistence>
</entity-descriptor>
<local-jndi-name>ejb/EmpBean</local-jndi-name>
</weblogic-enterprise-bean>
weblogic-cmp-rdbms-jar.xml
====================
<weblogic-rdbms-bean>
<ejb-name>EmpBean</ejb-name>
<data-source-jndi-name>mysqlDS</data-source-jndi-name>
<table-map>
<table-name>emp</table-name>
<field-map>
<cmp-field>firstName</cmp-field>
<dbms-column>first_namel</dbms-column>
</field-map>
<field-map>
<cmp-field>lastName</cmp-field>
<dbms-column>last_name</dbms-column>
</field-map>
<field-map>
<cmp-field>phone</cmp-field>
<dbms-column>phone</dbms-column>
</field-map>
<field-map>
<cmp-field>address</cmp-field>
<dbms-column>address</dbms-column>
</field-map>
</table-map>
<weblogic-rdbms-bean>
Please ignore any typos that you may notice in above sample descriptions (because I just typed it here changing original names).
When I try to deploy the application, I get error message as posted in my first post above in this thread. Please correct me if I am making any erros in descriptor files.
Edited by: 839281 on Feb 25, 2011 10:55 AM
Edited by: venkatp on Mar 1, 2011 9:31 AM

Question on Persistence (Entity Beans, Hibernate, JDBC)

Hi everybody!
Until now, I have read a lot about persistence in the J2EE-sector, but I am still confused about which technology to used in my case.
I hope, that maybe you can give me some hints, by telling me which technology is good or bad regarding my requirements:
I want to build a customer- and order-management system fullfilling the following requirements:
1. The client is a Java application, the server is a JBOSS 4.0.1
2. The databasa scheme exists already and I'm not allowed to change it.
Some data, that logically belongs together and which shall be presented together to the client is distributed over 2 database tables.
3. The user cannot just create new and view data, but will also edit existing data quite often.
4. The user can assign products to an order. Often, there will be more than 1000 products assigned to an order, which will be presented to the user as a table (e.g. JTable). The user can then edit each cell of that 1000-row table, which of course will lead to an update in the db.
5. The user can also assign customers to a specific role in an order-process. On the other hand, each customer can make many orders.
So, we have a n:m relation here with the db-tables Customer, Order, OrderCustomer.
6. A complex search functionality has to be implemented, where the db-query is created dynamically at runtime.
7. The application is a multi-user application (about 10 users). It will be very rare, that users will work on the same data at the same time, but it might happen.
8. The database type (SAP DB) will not be changed in the near future.
With these 8 requirements in mind, I dealed a lot with EntityBeans, Hibernate and JDBC with SesseionBeans during the last 2 weeks.
Until now, I came to the following conclusions.
Hibernate is too slow. That'S bad, for data is edited very often and sometimes I want to edit just a single cell in 1000-row table.
Hibernate's biggest advantage - that it makes your application independent of the database type - is not even required (see point 8).
JDBC with SessioBeans: Very fast (I tried a simple query and it was about 10 times faster than Hibernate).
The disadvantage is, that I have to take care about all the transaction, concurrency control etc. things.
If I use JDBC, I want to do it that way: A SessionFacade accesses a DAO-object which executes the DB-query and returns the result to the SessionFacade which in the last step will pass the result to the client.
Entity Beans: I am completely confused with Entity Beans.
I read a lot about the CompositeEntity-Pattern for BMP. But on sun's J2EE Pattern page (http://java.sun.com/blueprints/corej2eepatterns/Patterns/CompositeEntity.html)
they said, that it's just useful when using the EJB 1.1 specification, because from EJB 2.0. the container or whatever will take care about lazy loading and store optimization.
So, from EJB 2.0. you should prefer using CMP-Beans with Container Managed Relationships (CMR), but as I heard, the dependent objects cannot be accessed and changed by the client when using CMPBeans with CMR.
However, a simple DB/Entity-mapping will not work in my case, because as mentioned above, there are thousands of products from the db to be managed at the same time. So here, I thought, the Composite pattern with its lazy loading strategy would be useful.
Furthermore, I have an n:m relationship in my database scheme, which is not trivial to map to entity beans. And don't forget that some related data is spread over 2 databse tables.
To sum it up, it would be very nice if some of you could clarify this perisistence nightmare, especially some clarification about if and how to use EntityBeans when having n:m relationships, editing data a lot, managing lots of table rows at once and having related data distributed over 2 database tables.
So, which technology would you prefer with the 8 requirements in mind? Hibernate, Entity Beans or JDBC with SessionBeans? Or would you prefer a mixed solution?
Thanx for every hint.
Regards,
egon

Here the requested information about the test:
Goal:
Find all customers, who's branches have the String "Branch" in their name.
Both times, a simple client accesses the same SessionBean in a JBOSS-Container.
This Bean has 2 methods. One accesses the DB via Hibernate (executeCriteria), the other one via JDBC (executeCriteriaJDBC).
The code to count the seconds of computation is as follows:
long startTime = System.currentTimeMillis();
List customerList = bean.executeCriteria(dc);
System.out.println("Hibernate: "+((System.currentTimeMillis()-startTime)/1000.0f)+" sek");
startTime = System.currentTimeMillis();
List customerListJDBC = bean.executeCriteriaJDBC(query);
System.out.println("JDBC: "+((System.currentTimeMillis()-startTime)/1000.0f)+" sek");
HIBERNATE:
CODE:
Branch Branch = new Branch();
Branch.setName("%Branch%");
Example example = Example.create(Branch);
DetachedCriteria dc = DetachedCriteria.forClass(Customer.class)
.createCriteria("branches").add(example.enableLike()).setResultTransformer(Criteria.DISTINCT_ROOT_ENTITY);
QUERY:
select
        this_.UUID as UUID1_1_,
        this_.NAME as NAME1_1_,
        this_.CUSTOMERNO as CUSTOMERNO1_1_,
        this_.SHORTDESC as SHORTDESC1_1_,
        this_.LONGDESC as LONGDESC1_1_,
        this_.TAXNUMBER as TAXNUMBER1_1_,
        this_.SALESTAXID as SALESTAXID1_1_,
        this_.ACCOUNTHOLDER as ACCOUNTH8_1_1_,
        this_.BANKACCOUNT as BANKACCO9_1_1_,
        this_.BANKCODE as BANKCODE1_1_,
        this_.BANKNAME as BANKNAME1_1_,
        this_.AREA1TEXT as AREA12_1_1_,
        this_.AREA2TEXT as AREA13_1_1_,
        this_.AREA3TEXT as AREA14_1_1_,
        this_.AREA4TEXT as AREA15_1_1_,
        this_.AREA5TEXT as AREA16_1_1_,
        this_.CH_UUID as CH17_1_1_,
        this_.REFTEXT1 as REFTEXT18_1_1_,
        this_.REFTEXT2 as REFTEXT19_1_1_,
        this_.REFTEXT3 as REFTEXT20_1_1_,
        branch1_.UUID as UUID0_0_,
        branch1_.NAME as NAME0_0_,
        branch1_.ILN as ILN0_0_,
        branch1_.BRANCHID as BRANCHID0_0_,
        branch1_.SHORTDESC as SHORTDESC0_0_,
        branch1_.LONGDESC as LONGDESC0_0_,
        branch1_.BAGSRECEIVED as BAGSRECE7_0_0_,
        branch1_.CUSTOMER_UUID as CUSTOMER8_0_0_
    from
        CUSTOMER this_,
        BRANCH branch1_
    where
        this_.UUID=branch1_.CUSTOMER_UUID
        and (
            branch1_.NAME like ?
RESULT:
Customername: Customer_A
Customername: Customer_F
Customername: Customer_D
Customername: Customer_R
Customername: Customer_S
TIME:
Hibernate: 1.343 sek
JDBC:
QUERY:
Select distinct c.* from Customer c, Branch b where b.id=b.Customer_id and b.name like '%Branch%'
// After getting the result of the query: Create a list of Customer-objects. Set all attributes of each Customer-object.
RESULT:
Customername: Customer_R
Customername: Customer_A
Customername: Customer_S
Customername: Customer_D
Customername: Customer_F
TIME:
JDBC: 0.125 sek
The Customer.hbm.xml (auto-generated in Eclipse with Middlegen)
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC
    "-//Hibernate/Hibernate Mapping DTD 3.0//EN"
    "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd" >
<hibernate-mapping>

<class
    name="hibernate.hibernate.Customer"
    table="CUSTOMER"
    lazy="false"
>
    <id
        name="uuid"
        type="java.lang.String"
        column="UUID"
    >
        <generator class="assigned" />
    </id>
    <property
        name="name"
        type="java.lang.String"
        column="NAME"
        length="100"
    />
    <property
        name="customerno"
        type="java.lang.Integer"
        column="CUSTOMERNO"
        length="5"
    />
    <property
        name="shortdesc"
        type="java.lang.String"
        column="SHORTDESC"
        length="50"
    />
    <property
        name="longdesc"
        type="java.lang.String"
        column="LONGDESC"
        length="100"
    />
    <property
        name="taxnumber"
        type="java.lang.String"
        column="TAXNUMBER"
        length="50"
    />
    <property
        name="salestaxid"
        type="java.lang.String"
        column="SALESTAXID"
        length="50"
    />
    <property
        name="accountholder"
        type="java.lang.String"
        column="ACCOUNTHOLDER"
        length="50"
    />
    <property
        name="bankaccount"
        type="java.lang.String"
        column="BANKACCOUNT"
        length="50"
    />
    <property
        name="bankcode"
        type="java.lang.String"
        column="BANKCODE"
        length="50"
    />
    <property
        name="bankname"
        type="java.lang.String"
        column="BANKNAME"
        length="50"
    />
    <property
        name="area1text"
        type="java.lang.String"
        column="AREA1TEXT"
        length="50"
    />
    <property
        name="area2text"
        type="java.lang.String"
        column="AREA2TEXT"
        length="50"
    />
    <property
        name="area3text"
        type="java.lang.String"
        column="AREA3TEXT"
        length="50"
    />
    <property
        name="area4text"
        type="java.lang.String"
        column="AREA4TEXT"
        length="50"
    />
    <property
        name="area5text"
        type="java.lang.String"
        column="AREA5TEXT"
        length="50"
    />
    <property
        name="chUuid"
        type="java.lang.String"
        column="CH_UUID"
        length="50"
    />
    <property
        name="reftext1"
        type="java.lang.String"
        column="REFTEXT1"
        length="50"
    />
    <property
        name="reftext2"
        type="java.lang.String"
        column="REFTEXT2"
        length="50"
    />
    <property
        name="reftext3"
        type="java.lang.String"
        column="REFTEXT3"
        length="50"
    />
    
    
    <set
        name="branches"
        lazy="true"
        inverse="true"
       cascade="all"
    >
        <key>
            <column name="CUSTOMER_UUID" />
        </key>
        <one-to-many
            class="hibernate.hibernate.Branch"
        />
    </set>
</class>
</hibernate-mapping>So, seems to me like Hibernate is also getting the data from the Branch-Table related to each Customer. Maybe this is the reason, why Hibernate is slower.
But as you can see in the mapping-File of the customer, I wanted Branches to be lazy loaded.
Do you have any ideas, why Hibernate is so much slower? Any hints for optimizing that code?
Do you have any further tricks to optimize Hibernate? Unfortunately I am not allowed to make changes at the database, so I cannot e.g. set indices for optimization.
However, I�m a Hibernate-Newbie. In fact, I just made this test and was very disappointed about its result, so I didn�t keep on working with Hibernate.
But maybe you can proof me, that Hibernate is a good choice. If so, do you have any good resources (links, books) that help working with Hibernate in connection with JBOSS, describe how to map n:m relationships, show how to work with large results and so forth?
Thanx for help,
egon

CMP Entity Bean from dataBase views

Hi forum,
I Have to migrate an existing application to JEE (with EJB3).
In this application there are a lot of dataBase views.
I'm new in EJB3 and I don't know how to structure cleanly entity beans (Specially when it are created from dataBase views).
My problem is that for each query made from the same dataBase view I almost have to create a new entity bean with a different @Id.
What can I do to to avoid it?
I had thought to genrate a new @Id (attribute not persistent) but I think is not possible. It's right ?
Someone can help me ?
Thanks

"CMP provides you with database independence and less coding efforts."
BMP is not database dependent, unless you invoke database specific things in your SQL (something I do not do). CMP on the otherhand is inherently appserver specific (which was it's goal when BEA, IBM, et al. came up with it), and still limits your design possibilities. See this thread for an example:
http://forum.java.sun.com/thread.jsp?forum=13&thread=318785
As for less coding effort, that is a relative statment. Yes a simple CMP bean requires less coding to develop the first time. I personally view a few lines of SQL to load and store the data as being fairly trivial. But that needs to be offset with the problems inherent in using appserver specific CMP implementations.
As an example, try mapping WebSphere CMP to a pre-existing database without using IBM's IDE. It's an incredible pain in the ass since WebSphere does not come with a "meet-in-the-middle" solution. Any J2EE developer that has had the experience of working with different appservers (especially if they have had to port an app, as I have) can attest to the complications that arise with each implementation.
A BMP bean, written with non-DB-specific SQL, is the most portable, most flexible approach to EntityBeans. Yes, it requires the developer to be able to write some SQL, which should not take a significant amout of time. WRT queries, you have to write them, either SQL, EQL, or some appserver specific format.
As an aside, the use of code generators to simplify the creation of EJBs lends itself well to BMP. By using a (or writing your own) code generator, you can mitigate the annoying SQL bugs that creep up early in development.

CMP entity bean update after database update

I'm new to JDeveloper and J2EE. Since JDev 10.1.3 is now production software I finally got started with it. Everything was quite simple to achieve however I have one problem.
My current setup is faily easy. I have a statelss session bean and a CMP entity bean using TopLink (both EJB 2.1). Getting them both created went smooth and having the two talk was as easy as pie thanks to Jdev.
The problem I have is with the entity bean. I'm using a custom finder method to retrieve records using non-PK fields. This works like a charm and I'm getting the data I need. But when I update the data in the database (OracleXE) and I rerun the client I get the old data. The only way for me to get new data is to restart the embedded OC4J server in JDev.
How can I have the entity bean updated by changes in the database?

Thanks Avi!
I spent some time with the documentation and I see I can configure the cache. However how to do this is not clear to me. I have the impression that most of it relates to BMP entity beans.
Apparantly there is a DoNotCheckCache method I can invoke on the query, but I have no idea how to achieve this...
Message was edited by:
Deddiekoel

Relationships in CMP Entity Beans

Hi everyone;
There is a way to implement one-to-many and many-to many relationships in CMP Entity Beans, is there a way to specify a parametrized query or something that do the job on the DBMS?
Regards Francisco.

Container's cascade-deleting in jboss(tm)3.2.x working properly with any scope:
This example with 1 scope:
    <relationships>
        <ejb-relation>
            <ejb-relation-name>Region-Town</ejb-relation-name>
            <ejb-relationship-role>
                <ejb-relationship-role-name>region-has-towns</ejb-relationship-role-name>
                <multiplicity>One</multiplicity>
                <relationship-role-source>
                    <ejb-name>RegionBean</ejb-name>
                </relationship-role-source>
                <cmr-field>
                    <cmr-field-name>regionTowns</cmr-field-name>
                    <cmr-field-type>java.util.Set</cmr-field-type>
                </cmr-field>
            </ejb-relationship-role>
            <ejb-relationship-role>
                <ejb-relationship-role-name>town-belongs-to-region</ejb-relationship-role-name>
                <multiplicity>Many</multiplicity> <cascade-delete/>
                <relationship-role-source>
                    <ejb-name>TownBean</ejb-name>
                </relationship-role-source>
                <cmr-field>
                    <cmr-field-name>region</cmr-field-name>
                </cmr-field>
            </ejb-relationship-role>
        </ejb-relation>
    </relationships>

Disadvantages of using entity beans.

can I know the disadvantages of using entity beans.

sigh I guess if someone puts it on a website it must be true...
"Forces the use of a heavy component mechanism for fine grained business objects."
Heaviness is not some arbitrary side-effect. It is directly due to the services provided by the EntityBeans (transactions, etc). If you need those services, you pay the price. If you don't then you shouldn't be using EJB to begin with. Also with the advent of LocalInterfaces, fine-grainedness is no longer a liability.
"More complex than JDO limiting developer productivity."
Perhaps it has less to do with limited productivity, and more to do with limited developers.
"More difficult to achieve good performance."
Compared to a simple data storage mechanism, sure.
"Inheritance not supported."
Really? Wow, I guess all the EJB code I've written for the last 3 years doesn't really work.
"Cannot be used for persistence in non-application server environments."
Uhh, yeah, but seeing as how the decision to use EJBs is not limited to the persistance scheme, the non-use of an application server is moot.
"There is no dynamic query mechanism to lookup entity beans (finders are specified at compile time)."
And what compiled business process (i.e SessionBeans) requires dynamic lookup of arbitrary data? Humans performing search functions can be done via entity beans, but probably should not be done since a large searches do not (or very rarely) need to be transactional.
"It is not easy to write unit tests for beans as it is not possible to use them outside of the application server."
For a long time this was true, but there are now many unit test suites designed for J2EE.
"No support for automatic primary key generation."
In the spec, no. But it's fairly trivial to implement on your own.
"Only relational databases are supported."
If you use CMP, yes. If you use BMP, you can do whatever you want inside your ejbLoad()/ejbStore() methods. Another reason to not use CMP.

Session Bean or Entity Bean

I am building application in which I query 4 to 5 tables and display the reports
. Presently I am using JSP and Servlets but would like to move to EJBs.
What would be my best bet between Entity and Session beans ?
Thanks in advance ..Frank

Frank,
You may want to peruse the following snippet from Sun's Java site on when to use
session beans vs. entity beans
http://java.sun.com/j2ee/j2sdkee/techdocs/guides/ejb/html/Overview4.html#9377
Chuck Nelson
Developer Relations Engineer
BEA Technical Support

Noob Question: Problem with Persistence in First Entity Bean

Hey folks,
I have started with EJB3 just recently. After reading several books on the topic I finally started programming myself. I wanted to develop a little application for getting a feeling of the technology. So what I did is to create a AppClient, which calls a Stateless Session Bean. This Stateless Bean then adds an Entity to the Database. For doing this I use Netbeans 6.5 and the integrated glassfish. The problem I am facing is, that the mapping somehow doesnt work, but I have no clue why it doesn't work. I just get an EJBException.
I would be very thankfull if you guys could help me out of this. And don't forget this is my first ejb project - i might need a very detailed answer ... I know - noobs can be a real ....
So here is the code of the application. I have a few methods to do some extra work there, you can ignore them, there are of no use at the moment. All that is really implemented is testConnection() and testAddCompany(). The testconnection() Methode works pretty fine, but when it comes to the testAddCompany I get into problems.
Edit:As I found out just now, there is the possibility of Netbeans to add a Facade pattern to an Entity bean. If I use this, everythings fine and it works out to be perfect, however I am still curious, why the approach without the given classes by netbeans it doesn't work.
public class Main {
    private EntryRemote entryPoint = null;
    public static void main(String[] args) throws NamingException {
        Main main = new Main();
        main.runApplication();
    private void runApplication()throws NamingException{
        this.getContext();
        this.testConnection();
        this.testAddCompany();
        this.testAddShipmentAddress(1);
        this.testAddBillingAddress(1);
        this.testAddEmployee(1);
        this.addBankAccount(1);
    private void getContext() throws NamingException{
        InitialContext ctx = new InitialContext();
        this.entryPoint = (EntryRemote) ctx.lookup("Entry#ejb.EntryRemote");
    private void testConnection()
        System.err.println("Can Bean Entry be reached: " + entryPoint.isAlive());
    private void testAddCompany(){
        Company company = new Company();
        company.setName("JavaFreaks");
        entryPoint.addCompany(company);
        System.err.println("JavaFreaks has been placed in the db");
    }Here is the Stateless Session Bean. I added the PersistenceContext, and its also mapped in the persistence.xml file, however here the trouble starts.
import javax.ejb.Stateless;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
@Stateless(mappedName="Entry")
public class EntryBean implements EntryRemote {
    @PersistenceContext(unitName="PersistenceUnit") private EntityManager manager;
    public boolean isAlive() {
        return true;
    public boolean addCompany(Company company) {
        manager.persist(company);
        return true;
    public boolean addShipmentAddress(long companyId) {
        return false;
    public boolean addBillingAddress(long companyId) {
        return false;
    public boolean addEmployee(long companyId) {
        return false;
    public boolean addBankAccount(long companyId) {
        return false;
}That you guys and gals will have a complete overview of whats really going on, here is the Entity as well.
package ejb;
import java.io.Serializable;
import javax.persistence.*;
@Entity
@Table(name="COMPANY")
public class Company implements Serializable {
    private static final long serialVersionUID = 1L;
    @Id
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Long id;
    @Column(name="COMPANY_NAME")
    private String name;
    public Long getId() {
        return id;
    public void setId(Long id) {
        this.id = id;
   public String getName() {
        return name;
    public void setName(String name) {
        this.name = name;
        System.err.println("SUCCESS: CompanyName SET");
    @Override
    public int hashCode() {
        int hash = 0;
        hash += (id != null ? id.hashCode() : 0);
        return hash;
    @Override
    public boolean equals(Object object) {
        // TODO: Warning - this method won't work in the case the id fields are not set
        if (!(object instanceof Company)) {
            return false;
        Company other = (Company) object;
        if ((this.id == null && other.id != null) || (this.id != null && !this.id.equals(other.id))) {
            return false;
        return true;
    @Override
    public String toString() {
        return "ejb.Company[id=" + id + "]";
}And the persistence.xml file
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="PersistenceUnit" transaction-type="JTA">
    <provider>oracle.toplink.essentials.PersistenceProvider</provider>
    <jta-data-source>jdbc/sample</jta-data-source>
    <exclude-unlisted-classes>false</exclude-unlisted-classes>
    <properties>
      <property name="toplink.ddl-generation" value="create-tables"/>
    </properties>
</persistence-unit>
</persistence>And this is the error message
08.06.2009 10:30:46 com.sun.enterprise.appclient.MainWithModuleSupport <init>
WARNUNG: ACC003: Ausnahmefehler bei Anwendung.
javax.ejb.EJBException: nested exception is: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.RemoteException: Transaction aborted; nested exception is: javax.transaction.RollbackException: Transaktion für Zurücksetzung markiert.; nested exception is:
        javax.transaction.RollbackException: Transaktion für Zurücksetzung markiert.
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.RemoteException: Transaction aborted; nested exception is: javax.transaction.RollbackException: Transaktion für Zurücksetzung markiert.; nested exception is:
        javax.transaction.RollbackException: Transaktion für Zurücksetzung markiert.
        at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:243)
        at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:205)
        at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:152)
        at com.sun.corba.ee.impl.presentation.rmi.bcel.BCELStubBase.invoke(BCELStubBase.java:225)
        at ejb.__EntryRemote_Remote_DynamicStub.addCompany(ejb/__EntryRemote_Remote_DynamicStub.java)I spend half the night figuring out whats wrong, however I couldnt find any solution.
If you have any idea pls let me know
Best regards and happy coding
Taggert
Edited by: Taggert_77 on Jun 8, 2009 2:27 PM

Well I don't understand this. If Netbeans created a Stateless Session Bean as a facade then it works -and it is implemented as a CMP, not as a BMP as you suggested.
I defenitely will try you suggestion, just for curiosity and to learn the technology, however I dont have see why BMP will work and CMP won't.
I also don't see why a stateless bean can not be a CMP. As far as I read it should not matter. Also on the link you sent me, I can't see anything related to that.
Maybe you can help me answering these questions.
I hope the above lines don't sound harsh. I really appreciate your input.
Best regards
Taggert

Query related to Entity Beans

Similar Messages

Maybe you are looking for