Problems accessing ejb 3.0 entity bean from project

I have written some code using ejb 3.0 and was previously accessing the entity bean without problem when both ejbs and the accessing code were in the same project. However I have moved the accessing code into a different project within the same application and now when the code tries to accessing the entity bean I get the following error:
com.colwilson.web.ingestion.IdentifiedException: java.lang.ClassCastException: __Proxy3
     at com.colwilson.web.ingestion.IngestionHandler.recordArrived(IngestionHandler.java:140)
     at com.colwilson.web.ingestion.IngestionHandler.main(IngestionHandler.java:52)
Caused by: java.lang.ClassCastException: __Proxy3
     at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.getFreshObject(StatelessSessionRemoteInvocationHandler.java:21)
     at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.getReplacementObject(RecoverableRemoteInvocationHandler.java:64)
     at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.handleRecovery(RecoverableRemoteInvocationHandler.java:41)
     at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:30)
     at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
     at __Proxy1.mergeEntity(Unknown Source)
     at com.colwilson.web.ingestion.IngestionHandler.recordArrived(IngestionHandler.java:137)
     ... 1 more
Now, of course I could move the code back into the same project, but as I understand it that is just the point of ejbs. I'm looking up the entity bean thus:
final Context context = InitialContext();
ingestionSessionEJB =
(IngestionSessionEJB)context.lookup("IngestionSessionEJB");
It may be true that I don't understand the way lookup works, but to be honest I can't find the docs that explain what I've got wrong.
Please help.

hi
Double Click on the project which is goin to use the project which contains bean from the Application Navigator window. The project properties window will open. Choose the "Dependencies" item from left panel. click on the radio "User Project Settings" and select another project which contain ejb which you're goin to access...
Best Of Luck
Ravi A. Trivedi

Similar Messages

Problem with ejb 3.0 entity beans with manyToMany relationship

Hello everyone!
I am using struts 1.2.9 and java ee 5 sdk update 2 for my enterprise application. Besides others i have these entity beans Targetgroup.java and City.java, (i would upload file but i do not know how:)
with manytomany relationship with join table.
when user updates Targetgroup, by clicking on web page with checkboxes and textfields, struts dispatch action calls following method stateless bean:
public void update(String firmId, String targetgroupId, String newGender, String newMinYearsOld, String newMaxYearsOld, String[] newCities) {
TargetgroupPK pkForUpdate = new TargetgroupPK(targetgroupId, firmId);
Targetgroup targetgroupForUpdate = find(pkForUpdate);
targetgroupForUpdate.setGender(newGender);
targetgroupForUpdate.setMinyearold(Integer.parseIn t(newMinYearsOld));
targetgroupForUpdate.setMaxyearold(Integer.parseIn t(newMaxYearsOld));
//pronalazenje gradva za koje je vezana ciljna grupa
Collection<City> newCitiesCollection = new ArrayList<City>();
for(int i = 0; i < newCities.length; i++){
String tmp_city_name = newCities;
City city_obj = cityFacade.find(tmp_city_name);
newCitiesCollection.add(city_obj);
targetgroupForUpdate.setCityidCollection(newCities Collection);
parameter newCities represents names of cities which user checked on his update page. When the page is showen to him some cities are allready check because they were connected with Targetgruoup when it was created (targetgroup).
this code throws following exception:
[#|2007-07-26T12:13:36.993+0200|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.container.web|_Threa dID=16;_ThreadName=httpWorkerThread-8080-0;_RequestID=f79d9c50-86b0-4b6c-96ab-97956dfb39c1;|StandardWrapperValve[action]: Servlet.service() for servlet action threw exception
javax.ejb.EJBException: Transaction aborted; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback.
javax.transaction.RollbackException: Transaction marked for rollback.
at
.com.sun.enterprise.web.connector.grizzly.WorkerTh read.run(WorkerThread.java:75)
javax.ejb.EJBException: Transaction aborted; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback.
at com.sun.ejb.containers.BaseContainer.completeNewTx (BaseContainer.java:3659)
at com.sun.ejb.containers.BaseContainer.postInvokeTx( BaseContainer.java:3431)
at com.sun.ejb.containers.BaseContainer.postInvoke(Ba seContainer.java:1247)
at com.sun.ejb.containers.EJBLocalObjectInvocationHan dler.invoke(EJBLocalObjectInvocationHandler.java:1 92)
at com.sun.ejb.containers.EJBLocalObjectInvocationHan dlerDelegate.invoke(EJBLocalObjectInvocationHandle rDelegate.java:71)
at $Proxy149.update(Unknown Source)
at audiotel.sms.actions.backoffice.TargetgroupDispatc hAction.updateOrDelete(TargetgroupDispatchAction.j ava:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.struts.actions.DispatchAction.dispatchM ethod(DispatchAction.java:270)
at org.apache.struts.actions.DispatchAction.execute(D ispatchAction.java:187)
at org.apache.struts.action.RequestProcessor.processA ctionPerform(RequestProcessor.java:431)
at org.apache.struts.action.RequestProcessor.process( RequestProcessor.java:236)
at org.apache.struts.action.ActionServlet.process(Act ionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doPost(Acti onServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
com.sun.enterprise.web.connector.grizzly.WorkerThr ead.run(WorkerThread.java:75)
|#]
exceprion is throwen ONLY when in parameter newCities are city names allready connected to Targetgroup. when NewCities contains names of
City objects which are not connected to Targetgroup it works fine, but it's of no use for me, because user must be able to add or remove certian cities from relaionship with Targetgroup. I think it's because there are rows in join table that contain primary keys of city and targetgroup which are connected so perisistence manager cann't write them again.
i thought it was going to figure it out by itself, and only update those rows.
Does anyone know what is the problem and solution?
Thanks! (forgive my spelling errors :)

solved the problem!
I moved code from sesion bean to struts action as follows:
CityFacadeLocal cityFacade = lookupCityFacade();
//prikupljanje novih podataka o ciljnoj grupi
String newGender = ctf.getGender();
String newMaxYears = ctf.getMaxyears();
String newMinYears = ctf.getMinyears();
String[] newSelectedCities = ctf.getSelectedCities();
//niz imena gradova se prevodi u kolekcju objekata City
Collection<City> newCitiesObjCollection = new Vector<City>();
for(int i = 0; i < newSelectedCities.length; i++){
String tmpCityName = newSelectedCities;
City tmpCityObj = cityFacade.find(tmpCityName);
newCitiesObjCollection.add(tmpCityObj);
//setovanje novih podataka
targetgroupForUD.setGender(newGender);
targetgroupForUD.setMinyearold(Integer.parseInt(newMinYears));
targetgroupForUD.setMaxyearold(Integer.parseInt(newMaxYears));
targetgroupForUD.setCityidCollection(newCitiesObjCollection);
//pozivanje update metdoe u session beany
targetgroupFacade.edit(targetgroupForUD);
//korisnik se vraca na stranu sa svim postojecim ciljnim grupama
forward = mapping.findForward("backend.targetgroups");
and now it works fine. I guess probelm was same transaction scope for Targetgroup and City entities. Now when they are separated it works.
Thanks!

Problem creating EJB 3.0 Entity bean in JDeveloper

Hello all,
I trying to create my first entity bean in JDeveloper.
JDevelper create the entity bean with the code below:
package model;
import java.io.Serializable;
import javax.persistence.Entity;
@Entity
public class BatchSettlementT implements Serializable {
public BatchSettlementT() {
The problem is that JDeveloper don't find the import command import javax.persistence.Entity;
What am I doing wrong?
I'm using JDeveloper Studio Edition Version 10.1.3.1.0.3914.
My libraries are:
- TopLink
- Oracle XML Parser 2
- EJB 3.0
- Toplink Essentials JPA
- J2EE
Thanks in advance.

It's very strange, when I type import.javax. in my class there is no persistence package available, do you have any idea what's wrong.
I did set the technology scope to EJB either.
Thanks!

EJB 3.0 Entity Bean

Hi Friends,
I am Facing a problem in EJB 3.0 Entity Bean. I am Using Eclipse 3.3.2 and JBoss 4.2 Application Server. Im getting the error such as *"javax.naming.NameNotFoundException: EntityBean not bound"* when im trying to lookup the entity bean. Herewith i had attached the servlet code. Can anyone suggest me.
package common;
import java.io.IOException;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import example.BookRemote;
public class CounterServlet extends javax.servlet.http.HttpServlet implements javax.servlet.Servlet {
static final long serialVersionUID = 1L;
private BookRemote hello;
     public CounterServlet() {
          super();
     protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
          // TODO Auto-generated method stub
          try
     InitialContext ctx = new InitialContext();
     hello = (BookRemote) ctx.lookup("EntityBean/remote");
     hello.test();
     Integer count = 1;
     request.setAttribute("counter", count);
     request.getRequestDispatcher("result.jsp").forward(request, response);
     catch (NamingException e)
     e.printStackTrace();
     protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
          // TODO Auto-generated method stub
     }

I think the Bean haven't been registered. I had look into the jmx-console and this is the result which i have got for my sample application (EntityBean).
java:comp namespace of the EntityBean.ear/EntityBeanWeb.war application:
+- UserTransaction[link -> UserTransaction] (class: javax.naming.LinkRef)
+- env (class: org.jnp.interfaces.NamingContext)
| +- security (class: org.jnp.interfaces.NamingContext)
| | +- realmMapping[link -> java:/jaas/other] (class: javax.naming.LinkRef)
| | +- subject[link -> java:/jaas/other/subject] (class: javax.naming.LinkRef)
| | +- securityMgr[link -> java:/jaas/other] (class: javax.naming.LinkRef)
| | +- security-domain[link -> java:/jaas/other] (class: javax.naming.LinkRef)
Global JNDI Namespace
+- persistence.units:ear=EntityBean.ear,unitName=CounterServlet (class: org.hibernate.impl.SessionFactoryImpl)
+- persistence.units:ear=TaskEnitity.ear,unitName=FirstEjb3Tutorial (class: org.hibernate.impl.SessionFactoryImpl)
+- TopicConnectionFactory (class: org.jboss.naming.LinkRefPair)
+- jmx (class: org.jnp.interfaces.NamingContext)
| +- invoker (class: org.jnp.interfaces.NamingContext)
| | +- RMIAdaptor (proxy: $Proxy48 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt)
| +- rmi (class: org.jnp.interfaces.NamingContext)
| | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef)
+- HTTPXAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
+- ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
+- UserTransactionSessionFactory (proxy: $Proxy14 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory)
+- HTTPConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
+- XAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
+- TransactionSynchronizationRegistry (class: com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple)
+- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
+- OnlineSurveyTool (class: org.jnp.interfaces.NamingContext)
| +- RegisterBean (class: org.jnp.interfaces.NamingContext)
| | +- remote (proxy: $Proxy79 implements interface online.IRegister,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject)
| +- OnlineSurveyBean (class: org.jnp.interfaces.NamingContext)
| | +- remote (proxy: $Proxy75 implements interface online.OnlineSurveyRemote,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject)
+- UILXAConnectionFactory[link -> XAConnectionFactory] (class: javax.naming.LinkRef)
+- UIL2XAConnectionFactory[link -> XAConnectionFactory] (class: javax.naming.LinkRef)
+- queue (class: org.jnp.interfaces.NamingContext)
| +- A (class: org.jboss.mq.SpyQueue)
| +- testQueue (class: org.jboss.mq.SpyQueue)
| +- ex (class: org.jboss.mq.SpyQueue)
| +- DLQ (class: org.jboss.mq.SpyQueue)
| +- D (class: org.jboss.mq.SpyQueue)
| +- C (class: org.jboss.mq.SpyQueue)
| +- B (class: org.jboss.mq.SpyQueue)
+- topic (class: org.jnp.interfaces.NamingContext)
| +- testDurableTopic (class: org.jboss.mq.SpyTopic)
| +- testTopic (class: org.jboss.mq.SpyTopic)
| +- securedTopic (class: org.jboss.mq.SpyTopic)
+- console (class: org.jnp.interfaces.NamingContext)
| +- PluginManager (proxy: $Proxy49 implements interface org.jboss.console.manager.PluginManagerMBean)
+- UIL2ConnectionFactory[link -> ConnectionFactory] (class: javax.naming.LinkRef)
+- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory)
+- UILConnectionFactory[link -> ConnectionFactory] (class: javax.naming.LinkRef)
+- persistence.units:unitName=TestServlet (class: org.hibernate.impl.SessionFactoryImpl)
+- QueueConnectionFactory (class: org.jboss.naming.LinkRefPair)
+- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory)

EJB 3.0: CMP Entity bean from view

Hi,
I have created an entity bean from a database view.
I don't have a good filed to use as id in my view. So I want to generate the id in my entity bean.
How can I do this ?
Thanks

Hi,
I didn't get your question.
CMP is something, which can be done by hand.
So maybe it is better, to do it manually.
Bea has some workaround, I am sure.
Maybe it is something with deployment descriptors, which
have to be configured to the underlying database.
Sorry for my stupid first answer.
Volker.

Accessing the same stateful session bean from multiple clients in a clustered environment

I am trying to access the same stateful session bean from multiple
 clients. I also want this bean to have failover support so we want to
 deploy it in a cluster. The following description is how we have tried
 to solve this problem, but it does not seem to be working. Any
 insight would be greatly appreciated!
 I have set up a cluster of three servers. I deployed a stateful
 session bean with in memory replication across the cluster. A client
 obtains a reference to an instance of one of these beans to handle a
 request. Subsequent requests will have to use the same bean and could
 come from various clients. So after using the bean the first client
 stores the handle to the bean (actually the replica aware stub) to be
 used by other clients to be able to obtain the bean. When another
 client retrieves the handle gets the replica aware stub and makes a
 call to the bean the request seems to unpredictably go to any of the
 three servers rather than the primary server hosting that bean. If the
 call goes to the primary server everything seems to work fine the
 session data is available and it gets backed up on the secondary
 server. If it happens to go to the secondary server a bean that has
 the correct session data services the request but gives the error
 <Failed to update the secondary copy of a stateful session bean from
 home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
 to the primary server will not reflect changes made on the secondary
 and vice versa. If the request happens to go to the third server that
 is not hosting an instance of that bean then the client receives an
 error that the bean was not available. From my understanding I thought
 the replica aware stub would know which server is the primary host for
 that bean and send the request there.
 Thanks in advance,
 Justin


 If 'allow-concurrent-call' does exactly what you need, then you don't have a problem,
 do you?
 Except of course if you switch ejb containers. Oh well.
 Mike
 "FBenvadi" <[email protected]> wrote:
 >I've got the same problem.
 >I understand from you that concurrent access to a stateful session bean
 >is
 >not allowed but there is a
 >token is weblogic-ejb-jar.xml that is called 'allow-concurrent-call'
 >that
 >does exactly what I need.
 >What you mean 'you'll get a surprise when you go to production' ?
 >I need to understand becouse I can still change the design.
 >Thanks Francesco
 >[email protected]
 >
 >"Mike Reiche" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> Get the fix immediately from BEA and test it. It would be a shame to
 >wait
 >until
 >> December only to get a fix - that doesn't work.
 >>
 >> As for stateful session bean use - just remember that concurrent access
 >to
 >a stateful
 >> session bean is not allowed. Things will work fine until you go to
 >production
 >> and encounter some real load - then you will get a surprise.
 >>
 >> Mike
 >>
 >> [email protected] (Justin Meyer) wrote:
 >> >I just heard back from WebLogic Tech Support and they have confirmed
 >> >that this is a bug. Here is their reply:
 >> >
 >> >There is some problem in failover of stateful session beans when its
 >> >run from a java client.However, it is fixed now.
 >> >
 >> >The fix will be in SP2 which will be out by december.
 >> >
 >> >
 >> >Mike,
 >> >Thanks for your reply. I do infact believe we are correctly using
 >a
 >> >stateful session bean however it may have been misleading from my
 >> >description of the problem. We are not accessing the bean
 >> >concurrently from 2 different clients. The second client will only
 >> >come into play if the first client fails. In this case we want to
 >be
 >> >able to reacquire the handle to our stateful session bean and call
 >it
 >> >from the secondary client.
 >> >
 >> >
 >> >Justin
 >> >
 >> >"Mike Reiche" <[email protected]> wrote in message
 >news:<[email protected]>...
 >> >> You should be using an entity bean, not a stateful session bean
 >for
 >> >this application.
 >> >>
 >> >> A stateful session bean is intended to be keep state (stateful)
 >for
 >> >the duration
 >> >> of a client's session (session).
 >> >>
 >> >> It is not meant to be shared by different clients - in fact, if
 >you
 >> >attempt to
 >> >> access the same stateful session bean concurrently - it will throw
 >> >an exception.
 >> >>
 >> >> We did your little trick (storing/retrieving handle) with a stateful
 >> >session bean
 >> >> on WLS 5.1 - and it did work properly - not as you describe. Our
 >sfsb's
 >> >were not
 >> >> replicated as yours are.
 >> >>
 >> >> Mike
 >> >>
 >> >> [email protected] (Justin Meyer) wrote:
 >> >> >I am trying to access the same stateful session bean from multiple
 >> >> >clients. I also want this bean to have failover support so we want
 >> >to
 >> >> >deploy it in a cluster. The following description is how we have
 >tried
 >> >> >to solve this problem, but it does not seem to be working. Any
 >> >> >insight would be greatly appreciated!
 >> >> >
 >> >> >I have set up a cluster of three servers. I deployed a stateful
 >> >> >session bean with in memory replication across the cluster. A client
 >> >> >obtains a reference to an instance of one of these beans to handle
 >> >a
 >> >> >request. Subsequent requests will have to use the same bean and
 >could
 >> >> >come from various clients. So after using the bean the first client
 >> >> >stores the handle to the bean (actually the replica aware stub)
 >to
 >> >be
 >> >> >used by other clients to be able to obtain the bean. When another
 >> >> >client retrieves the handle gets the replica aware stub and makes
 >> >a
 >> >> >call to the bean the request seems to unpredictably go to any of
 >the
 >> >> >three servers rather than the primary server hosting that bean.
 >If
 >> >the
 >> >> >call goes to the primary server everything seems to work fine the
 >> >> >session data is available and it gets backed up on the secondary
 >> >> >server. If it happens to go to the secondary server a bean that
 >has
 >> >> >the correct session data services the request but gives the error
 >> >> ><Failed to update the secondary copy of a stateful session bean
 >from
 >> >> >home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
 >> >> >to the primary server will not reflect changes made on the secondary
 >> >> >and vice versa. If the request happens to go to the third server
 >that
 >> >> >is not hosting an instance of that bean then the client receives
 >an
 >> >> >error that the bean was not available. From my understanding I
 >thought
 >> >> >the replica aware stub would know which server is the primary host
 >> >for
 >> >> >that bean and send the request there.
 >> >> >
 >> >> >Thanks in advance,
 >> >> >Justin
 >>
 >
 >

Deploying EJB 3.0 entity beans without a Datasource

[Cross-posted from the TopLink list]
My question: Is there any way to configure the container or persistence provider to defer trying to connect to the Datasource until I make some call that involves persistence? Or any other way to deploy an app containing entity beans without having a database configured?
Background: I am working on a component that can be configured to run in either persistent or in-memory mode. For the persistent mode we would like to use EJB 3.0 entity beans; for the in-memory mode we would like the component to be deployable without having to have a database available.
However in my prototype of the application, when I try to deploy to OC4J 10.1.3, as soon as the entity beans are detected the TopLink persistence provider tries to establish a connection to the db via either the configured or default DataSource. So if the db is unavailable, deployment fails. Since this is occuring at deployment, it happens regardless of whether I am actually using any persistence features or not.

Hi,
I'm experiencing same problems, is this a bug or an feature?

Create CMP Entity Beans from Tables Wizard - Can't see any tables with DB2

Hi,
I'm trying to use the "Create CMP Entity Beans from Tables Wizard" to create an entity from a table in a DB2 database. The problem is, on page 2, I can't see any available tables. I have verified that the connection works (I can open the connection in the Navigator frame and I can see that table).
Note that if I try this wizard on an Oracle database, I can see tables.
WTF? Can someone please help?

I second the motion. I too work in an environment with centralized data management (DBA's) that create and maintain all tables under a generic schema. This has prevented me from using the Create Entity Beans from Table feature of Jdev r3 preview.
At least I can see that I'm not alone.
Thanks
When I select the "Create CMP Entity Beans from Tables Wizard," no tables or views are available to select. The JDev database connection is using an ID assigned to me.
The tables that I am looking for were created by the DBA under his ID and are therefore in that schema. He did create Public Synonyms for them, but the tables still do not show up in the wizard.
Is there a configuration step that I need to do to have those tables show up?
Tables created by a DBA and then accessed by developers using a public synonym is a very common scenario and should be supported by JDeveloper (IMO).
Thanks.
I'm using JDev 9.0.2.8.2.

Deployment descriptor error for an EJB 3.0 entity bean module

Hi all,
i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
The application is composed as follows:
WASEnterprise.ear
|-META-INF
|-application.xml
|-WAS.jar
|-META-INF
|-persistence.xml
In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
<Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
The persistence.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<persistence>
<persistence-unit name="CNT4">
<non-jta-data-source>cnt5ds</non-jta-data-source>
<class>it.eni.italgas.was.db.entity.AsiDisco</class>
<class>it.eni.italgas.was.db.entity.AsiErrori</class>
<class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
<class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
<class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
</persistence-unit>
</persistence>
and the application.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>WASEnterprise</display-name>
<module id="myeclipse.1188512259959">
<ejb>WAS.jar</ejb>
</module>
</application>
I don't use any other weblogic specific deployment descriptor.
Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
Thanks inadvance.
Denis Maggiorotto

Hi all,
i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
The application is composed as follows:
WASEnterprise.ear
|-META-INF
|-application.xml
|-WAS.jar
|-META-INF
|-persistence.xml
In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
<Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
The persistence.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<persistence>
<persistence-unit name="CNT4">
<non-jta-data-source>cnt5ds</non-jta-data-source>
<class>it.eni.italgas.was.db.entity.AsiDisco</class>
<class>it.eni.italgas.was.db.entity.AsiErrori</class>
<class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
<class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
<class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
</persistence-unit>
</persistence>
and the application.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>WASEnterprise</display-name>
<module id="myeclipse.1188512259959">
<ejb>WAS.jar</ejb>
</module>
</application>
I don't use any other weblogic specific deployment descriptor.
Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
Thanks inadvance.
Denis Maggiorotto

Generating an Entity Bean from a Database Table

I am following the tutorial "How Do I: Generate an Entity Bean from a Database
Table?" and in that process doing the "Configuring a Data Source". This is the
message I get when I configure a data source per the tutorial and click OK. This
data source exists and the information is correct that I have supplied.
Do I need to put the MS jars somewhere to enable this?
See attached file

I've just figured it out. An input source also takes a Reader in its constructor. I was thinking that it only took an InputStream, and as the Serializer requires you to set a Writer on it, I was finding it impossible to convert between bytes and chars. Now, I have simply set a blank CharArrayWriter on the Serializer, got a char[] from it once the Serializer has written the Document to the stream, and then constructed a CharArrayReader with this char[]. It works fine now. Not that anyone read the problem anyway cos I solved it a few minutes after I posted it. Considering it first cropped up about 4 months ago and it has been niggling ever since, I am pleased!

CMP entity beans from tables in 9.0.3 jdev preview

I am trying to generate CMP entity beans from oracle tables using 9.0.3 jdeveloper preview. My oracle db version is 9.2. I notice that if a table has a single column primary key, no xxxPK.java file is created. However, if the primary key is multi-column an xxxPK.java file is created. Is this correct behavior? I expected an xxxPK.java file to be created regardless of the number of columns in the primary key for the table. Has anyone else noticed this? I am new to EJB so forgive my ignorance.

Comparing to JDev 902, I think this is a much better decision. Having to change beans with a single field PK to not using a custon PK class, to avoid using that class was a pain in JDev 902. There4s little benefit in using a custom class when there4s only a single field in it... some will say that it prevents having to do majot changes to your code if the PK changes in the future and add another field. But a careful database design will void this almost completely. So having JDev 903 use a java native class is a better option in this situation. At least from my personal point of view.

Problem accessing R/3 with SSO ticket from the EP6.0

Hi all,
I have seen this thread: Problem accessing R/3 with SSO ticket from the EP6.0
I know that it is possible to read SSO ticket from the Cookie in WebDynpro application.
Now we are at the first step, we don't know how to read SSO ticket from the Cookie in WebDynpro application with java code.
So anyone can help us?

Hi,
This has been discussed in a previous forum.Check this link.A code snippet is also there to read a cookie in webdynpro with this question
How to implement SSO between Portal, Webdypro and ABAP system?
I am not able to send the link exactly.
Regards,
Sowjanya.
Message was edited by: Sowjanya Chintala

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

Problem accessing ejb from servlet

Hi,
I'm aving a problem accessing a stateful session bean from a servlet. I'm using a jndi lookup to do it because I need that a client has its own bean reference...
My code into the service method is:
InitialContext ctx;
try {
ctx = new InitialContext();
carrelloService = (CarrelloLocal)ctx.lookup("java:comp/env/ejb/Carrello");
and I have a reference to EJB into web.xml:
<ejb-local-ref>
<ejb-ref-name>ejb/Carrello</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home></local-home>
<local>carrello.model.CarrelloLocal</local>
</ejb-local-ref>
If I use @EJB annotation to inject the servlet, it works fine.
Instead using jndi lookup throws a NamingException because it doesn't find java:comp/env/ejb/Carrello entry.
Any idea about the problem?

Here's something simple that I have that works:
 
SimpleBean
 
@Stateless(name="SimpleBean")
public class SimpleBeanBean implements SimpleBeanLocal {
 
web.xml; -- note I use a whacko ejb-ref-name just to make it obvious where I'm using it.
 
 <ejb-local-ref>
 <ejb-ref-name>ejb_mapping_doodad/SimpleBean</ejb-ref-name>
 <ejb-ref-type>Session</ejb-ref-type>
 <local>sab.otn681398.ejb.SimpleBeanLocal</local>
 </ejb-local-ref> 
servlet:
 
package sab.otn681398.web;
import java.io.IOException;
import java.io.PrintWriter;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.servlet.*;
import javax.servlet.http.*;
import sab.otn681398.ejb.SimpleBeanLocal;
public class TestServlet extends HttpServlet {
 private static final String CONTENT_TYPE = "text/html; charset=windows-1252";
 private static final String SIMPLE_BEAN_JNDI = "ejb_mapping_doodad/ASimpleBean";
 private final boolean USEENC = true;
 private SimpleBeanLocal simple = null;
 public void init(ServletConfig config) throws ServletException {
 super.init(config);
 public void doGet(HttpServletRequest request,
 HttpServletResponse response) throws ServletException, IOException {
 response.setContentType(CONTENT_TYPE);
 PrintWriter out = response.getWriter();
 try {
 if(simple==null) {
 simple = createSimple();
 } catch(NamingException ne) {
 throw new ServletException("Error in looking up the EJB", ne);
 out.println("<html>");
 out.println("<head><title>TestServlet</title></head>");
 out.println("<body>");
 out.printf("The %s bean has been hit: %s times", simple, simple.getHitCount());
 out.println("</body></html>");
 out.close();
 private SimpleBeanLocal createSimple() throws NamingException {
 return (USEENC==true? createSimpleViaENC(): createSimpleViaName());
 private SimpleBeanLocal createSimpleViaENC() throws NamingException {
 InitialContext ic = new InitialContext();
 SimpleBeanLocal simple = (SimpleBeanLocal)ic.lookup("java:comp/env/" + SIMPLE_BEAN_JNDI);
 return simple;
 private SimpleBeanLocal createSimpleViaName() throws NamingException {
 InitialContext ic = new InitialContext();
 SimpleBeanLocal simple = (SimpleBeanLocal)ic.lookup(SIMPLE_BEAN_JNDI);
 return simple;
} 
-steve-

Problem in calling single entity bean from other beans

Hi,
I am implementing session facade with SUN's J2EE 1.3 deploy tool for JBoss server.
I have a entity bean UserBean which creates users in database ( create() )and tells if user exists or not ( findByPrimaryKey() ).
Initially, I had implemented UserBean with remote interfaces. So, any servlet ( my client ) which needed to use UserBean would make a remote call to it. It was used by 5 different servlets.
Now I am going for Local interfaces. So, I am packaging UserBean with other beans which need it.
Problem is, if I package UserBean with , say , ChatLogsBean ( Stateless bean ), it works fine. But when I package it with WebLogsBean ( Stateless bean ) also and deploy all beans together, JBoss gives error messages that instances of UserBean are already created.
How should structure my beans sothat I can avoid these duplication problem ?
Present flow is as follow:
Servlet Stateless Bean Other beans
ChatLogs Servlet --> ChatLogsWrapper --> ChatLogsBean ( Stateless bean ) & UserBean( Entity bean )
WebLogs servlet --> WebLogsWrapper --> WebLogsBean ( Stateless bean ) & UserBean
WordLogs servlet --> WordLogsWrapper --> WordLogsBean ( Stateless bean ) & UserBean
All servlets are packaged into corresponding WARs.
ChatLogsWrapper , ChatLogsBean ,UserBean are packaged into 'ChatWrapper' JAR.
WebLogsWrapper , WebLogsBean , UserBean are packaged into 'webWrapper' JAR
and similarly for WordLogs.
Any help ?
Regards,
Suraj

I suggest you post to one of the forums on jboss.org. There should not be a problem AFAIK having remote and local interfaces to the same EJB. I assume that you gave these unique names (FooHome/FooLocalHome..etc...) for the home and remote interfaces and declared both in the ejb DD.

Problems accessing ejb 3.0 entity bean from project

Similar Messages

Maybe you are looking for