Problem in compiling ejb home interface

i am starting work on ejbs .the first thing i want to know is how to find an ejb api.I have searched the whole of java site but without success.
can anyone help me start on with ejbs.
Thank you.

there is book on the web, the author name is ed roman, it is free on the web, search in the search engine. www.google.com. this book will definitely help you
kiran

Similar Messages

ClassNotFound while narrowing JNDI ref to ejb home interface

Hello everybody
I'm quite new to BEA WebLogic. I deployed Jasmine application on Bea WLS7 (example
app from Mastering EJB 2). But when i tried to use login servlet, it threw an
exception ClassNotFound when narrowing ejb home interface (obtained via JNDI).
EJBs are in .jar file, and web files are in the .war file, maybe this is the problem.
Should I copy ejb classes to .war file, or make some tricks with CLASSPATH, or
maybe there is better way to make it work (maybe via J2EE references or something
like this).
Thanks in advance

Strange. And you do not have any application classes in the system
classpath?
Konrad R. <[email protected]> wrote:
"Dimitri I. Rakitine" <[email protected]> wrote:
Did you deploy ejbs and war in the same ear?
Yes, both were packed up into one .ear archive>>
Konrad R. <[email protected]> wrote:
Hello everybody
I'm quite new to BEA WebLogic. I deployed Jasmine application on BeaWLS7 (example
app from Mastering EJB 2). But when i tried to use login servlet, itthrew an
exception ClassNotFound when narrowing ejb home interface (obtainedvia JNDI).
EJBs are in .jar file, and web files are in the .war file, maybe thisis the problem.
Should I copy ejb classes to .war file, or make some tricks with CLASSPATH,or
maybe there is better way to make it work (maybe via J2EE referencesor something
like this).
Thanks in advance--
Dimitri

Unable to bind EJB Home Interface to the JNDI name

Why do I get this error?? What is the jndi-name in weblogic-ejb-jar.xml
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
Unable to bind EJB Home Interface to the JNDI name:
com.sempire.builder.business
_component.Organization. The error was:
javax.naming.NameAlreadyBoundException: Organization is already bound;
remaining
name 'com.sempire.builder.business_component'
<<no stack trace available>>

Slava,
In case I change the name of the jndi name to a unique name. I still get the same
problem. I checked for multiple occurences, but there aren't any.
My web.xml file is:
<ejb-local-ref>
<description>
Reference EJB resources in Weblogic Resources
</description>
<ejb-ref-name>GangsterEJB</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>com.sempire.builder.business_component.GangsterHome</local-home>
<local>com.sempire.builder.business_component.Gangster</local>
</ejb-local-ref>
My weblogic-ejb-jar.xml file is:
<weblogic-enterprise-bean>
<ejb-name>GangsterEJB</ejb-name>
<entity-descriptor>
<persistence>
<persistence-type>
<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-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
</entity-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/GangsterDB</res-ref-name>
<jndi-name>oraclePool</jndi-name>
</resource-description>
</reference-descriptor>
<local-jndi-name>Gangster_test</local-jndi-name>
</weblogic-enterprise-bean>
I do not get the problem.
Thank you
Ronak Parekh
"Slava Imeshev" <[email protected]> wrote:
Hi Ronak,
This exception means that you already have a bean
with the same JNDI name. Search your weblogic-ejb-jar.xml files
for multiple occurrences of the name and fix the problem.
Regards,
Slava Imeshev
"Ronak Parekh" <[email protected]> wrote in message
news:[email protected]...
Why do I get this error?? What is the jndi-name in weblogic-ejb-jar.xml
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
Unable to bind EJB Home Interface to the JNDI name:
com.sempire.builder.business
_component.Organization. The error was:
javax.naming.NameAlreadyBoundException: Organization is already bound;
remaining
name 'com.sempire.builder.business_component'
<<no stack trace available>>

Problem in compiling EJB in examplesServer in weblogic server6.0

Follwoing is the output of my program:--
C:\bea\wlserver6.0sp1\samples\examples\ejb\basic\statefulSession>javac -d Trad
er.java TraderHome.java TradeResult.java ProcessingErrorException.java
TraderHome.java:32: cannot resolve symbol
symbol : class Trader
location: interface examples.ejb.basic.statefulSession.TraderHome
Trader create() throws CreateException, RemoteException;
^
1 error
C:\bea\wlserver6.0sp1\samples\examples\ejb\basic\statefulSession>javac -d Trade
r.java TraderHome.java TradeResult.java ProcessingErrorException.java Client.jav
a
TraderHome.java:32: cannot resolve symbol
symbol : class Trader
location: interface examples.ejb.basic.statefulSession.TraderHome
Trader create() throws CreateException, RemoteException;
^
Client.java:94: cannot resolve symbol
symbol : class Trader
location: class examples.ejb.basic.statefulSession.Client
Trader trader = (Trader) narrow(home.create(), Trader.class);
^
Client.java:94: cannot resolve symbol
symbol : class Trader
location: class examples.ejb.basic.statefulSession.Client
Trader trader = (Trader) narrow(home.create(), Trader.class);
^
Client.java:94: cannot resolve symbol
symbol : class Trader
location: class examples.ejb.basic.statefulSession.Client
Trader trader = (Trader) narrow(home.create(), Trader.class);
^
4 errors
C:\bea\wlserver6.0sp1\samples\examples\ejb\basic\statefulSession>

hi,
it seems there is some problem with the bean class whcih you wrote.Check the bean class and make sure that everything is fine like whether it implements SessionBean interface etc. If you are not able to find anything wrong. Check with examples available on net otherwise post your code and deployment descriptors.
Ashok.

How to compile ejb home class?

hi, recently i download a program and compile in native machine , and some error happened.The home class is :
import javax.ejb.EJBObject;
import java.rmi.RemoteException;
public interface Converter extends EJBObject {
public double dollarToYen(double dollars) throws
RemoteException;
public double yenToEuro(double yen) throws RemoteException;
when I compile this program, the jvm notice that the javax.ejb can not find. I have set class_path which like this:
class_path=.;..;c:\jdk1.3\lib;c:\jdkee1.3\lib;
Is there any one who so kind to help me ? Thanks at advance.

Uh, that class path should be:
classpath=.;..;c:\jdkee1.3\lib\j2ee.jar;
If you specify a directory, Java will search for class files in that directory; if you specify an archive (zip or jar) Java will search for class files in the archive. The class files you need reside in the two archives c:\jdk1.3\lib\rt.jar and c:\jdkee1.3\lib\j2ee.jar. rt.jar is normally decided (and automatically included in the class path) by the JVM you are running, so better leave it out.

Casting error when trying to retrieve an EJB home interface from a servlet

          I am trying to call a method on a session bean from a servlet. I am receiving a Class Cast exception when trying to use the narrow method. I have this code working from an external java client. Is there something specific I have to do?


Hi
          You must check the following rules :
          1) In JAR Files ( of your EJB ) check if there are remote mehods that return
          any class that is already used in servlets
          This classes must be remove from the servlet package ( if you are using WAR
          files ).
          2) Please read the BEA WebLogic Enterprise Java Beans Manual about the class
          loader and related problemas such as ClassCastException and
          ClassNotFoundException.
          Good Luck !
          Steve Schaber <[email protected]> escribió en el mensaje de noticias
          39ee4996$[email protected]..
          >
          > I am trying to call a method on a session bean from a servlet. I am
          receiving a Class Cast exception when trying to use the narrow method. I
          have this code working from an external java client. Is there something
          specific I have to do?
          >

Error compiling home interface

I get this error when I try to compile my home interface:
c:\sun\appserver\jdk\bin\javabean\InterestCalculatorHome.java:15: cannot find sy
mbol
symbol : class InterestCalculator
location: interface javabean.InterestCalculatorHome
public InterestCalculator create() throws RemoteException,
^
1 error
Does anyone know what the means? or how to fix it?
thanks

All my files are in the same package
Advice is the remote interface, AdviceHome is the home interface & AdviceBean is the bean class.
Advice & AdviceBean have compiled fine. But i am getting this error in compiling the AdviceHome interface.
By the way i just tried doing *.java instead of giving individual files & they got compiled.
Thanks.

Undable to bind EJB Home during deploy

Hi
I'm getting an exception when I redeploy to weblogic81. I have and ear with several ejb jars in it. The following is the message I get...
Unable to bind EJB Home Interface to the JNDI name: EJBTestService. javax.naming.NameAlreadyBoundException: EJBTestService is already bound; remaining name :at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:333) at weblogic.jndi.internal.ServerNamingNode.bindHere(ServerNamingNode.java:124) at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291) at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:279) at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:384) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1116) at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1362) at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:631)
This error doesn't always occur with the same jar in the ear. Sometimes the above jar prepares and activates fine and another one fails.
If anyone has any idea I'd appreciate feedback.

Hello,
The error suggests that an object is already bound to the JNDI name.
This can happen if you have 2 or more ejbs in your EAR file wit the same JNDI name or if your application has not fully/cleanly undeployed before you try to redeploy it.
I suspect the latter is your problem. Once you have undeployed your application use the weblogic console to view your JNDI tree and make sure nothing is bound that should not be bound. Then redeploy your app. If you still have the problem check your ear does not have duplicate ejbs or ejbs using the same JNDI name.

JNDI lookups of home interface

JNDI lookups are expensive timewise. Our question is ... would it be
pratical to lookup all our EJB Home interfaces once at startup and store
these references in a global class accessible to all clients? These home
interfaces then become readily available factories for acquiring instances
of remote interfaces. Is there anything wrong with this picture? Is this a
problem because these home stubs are not reentrant and may be accessed
concurrently by more than one client? Is there a problem with have one home
reference create multiple remote references of an ejb?
Any light that can be shed on this question wouls be appreciated.
Thanks.
tiffany
San Diego

I'm using a Singleton class to cache HomeInterfaces. The first time a
HomeInterface is requested, the JNDI lookup is done, after that, all
requests to that HomeInterface are handled by the cache. Works great, no
problems. AFAIK there are no problems with storing the HomeInterface
reference and reusing it.
Hope that helps,
Nils
Tiffany wrote:
>
JNDI lookups are expensive timewise. Our question is ... would it be
pratical to lookup all our EJB Home interfaces once at startup and store
these references in a global class accessible to all clients? These home
interfaces then become readily available factories for acquiring instances
of remote interfaces. Is there anything wrong with this picture? Is this a
problem because these home stubs are not reentrant and may be accessed
concurrently by more than one client? Is there a problem with have one home
reference create multiple remote references of an ejb?
Any light that can be shed on this question wouls be appreciated.
Thanks.
tiffany
San Diego--
============================
[email protected]

Problem in compiling home interface

my home interface is this:
package examples;
public interface HelloHome extends javax.ejb.EJBHome
Hello create() throws java.rmi.RemoteException, javax.ejb.CreateException;
and on compiling i get the following error message:
cannot resolve symbol
symbol: class Hello
location: interface examples.HelloHome
Hello create() throws java.rmi.Exception,
^ javax.ejb.CreateException;
I have just started on ejbs can someone help.
thank you.

Does anyone have an answer for this query? I'm experiencing the exact same problem...
Please give some insight into this situation. Maybe it's something very simple, but when you start out like me even the smallest problem is a big one.
thanX in advance for any help given

EJB problem with home interface

Hi firends
I am beginner to EJB world, and trying first EJB object i.e. Hello World program
I prepared first Remote interface, HelloBean and it compiled also properly.
names of program
Remote interface : Hello
Bean: HelloBean
Home interface : HelloHome
But after preparing Home interface it fails to compile at position of create()
the declaration is
public Hello create() throws RemoteException,CreateException
compilation error pointing at Hello in above statement saying 'Cannot resolve symbol'
The fact is all these files are located in same directory only
can anyone help me in this problem as I am eger to execute my first program and want to go further in EJB
thanx in advance
Mandar

Hi Mandar,
How are you setting the classpath and what exactly is it set to?
Unresolved symbol can only mean that the class cannot be found in the classpath. If two files are in the same directory and one has a dependency on the other then adding '.' to the classpath is all that is needed. Questions to ask yourself. Are the files in the same directory? does either include a 'package' statement? and are you absolutely certain that the classpath is set correctly (type 'set' at the command line)? Also if you have set the CLASSPATH variable, using -classpath with the javac command will override the variable.
Check everything above and if you still have problems maybe we can get some more details if you can post the entire error message.
Mandy

JSP Home Interface Problems

Hi, I am havin some problems trying to create a home interface in a JSP from an enterprise bean, i am using the following code :
<%!
     private AddressBook addressbook = null;
     public void jspInit()
          try
               InitialContext ic = new InitialContext();
               Object objRef = ic.lookup("java:comp/env/ejb/TheAddressBook");
               AddressBookHome home = (AddressBookHome)PortableRemoteObject.narrow(objRef, AddressBookHome.class);
               %> <%!
               addressbook = home.create("a","a","a","a","a","a","a");
          catch (RemoteException ex)
            System.out.println("Couldn't create AddressBook bean."+ ex.getMessage());
        catch (CreateException ex)
            System.out.println("Couldn't create AddressBook bean."+ ex.getMessage());
        catch (NamingException ex)
            System.out.println("Unable to lookup home: "+ "AddressBook "+ ex.getMessage());
     public void jspDestroy()
     addressbook = null;
%>
     <%
     addressbook01 = home.create("b","a","a","a","a","a","a");
     %>However i cannot access the home interface in the body of the JSP, i.e. where addressbook01 is trying to be created. Does anyone know a way around creating the home interface so that it is accessible in the body of the JSP?
cheers

Milan,
I will attempt to answer some of your questions. Others I need a little more detail on:
1. There isn't a way to run a JSP directly from JDeveloper to TomCat. Our internal server, Web-to-Go, is what we provide for local testing and debugging.
We do, however, support remote debugging JSPs against TomCat. You can find out more about how to set this up from the online help, and also from the JDev 3.1 Remote Debugging Online Demo Walkthroughs available on the JDeveloper OTN page.
2. I'm not sure why this is happening, but I would just answer 'No', if your edits are getting wiped out. I have not experienced this problem myself when I select 'Yes'.
3. Are these JSP files that JDeveloper has created (i.e. via the JSP Web Application Wizard), or ones you created yourself? Does this happen each time you open the project? What are your HTML source and root directories set to in your Project Properties? Are the JSP files located there?

Unable to deploy EJB 3.0 on JBoss 4.0.4GA - no home interface

I am stuck in that my EJB3.0 project (one entity bean, one session bean and one client test bean) builds OK but somehow Eclipse Europa is unable to deploy it to JBoss (4.0.4 GA and 5 Beta) -- something to do with JNDI error as it involves javax.naming exceptions.
My Eclipse directory structure is :-
Titan (project name)
|
ejb - com.titan (package name)
| |
| domain -> Cabin.java (my entity bean)
| |
| travelagent -> TravelAgentBean.java
| -> TravelAgentRemote.java
|
META_INF -> ejb-jar.xml
-> MANIFEST.MF
-> persistence.xml
My ejb-jar.xml is :
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>Titan</display-name>
<enterprise-beans>

<session >
<display-name>TravelAgentBean</display-name>
<ejb-name>com/titan/travelagent/ejb/TravelAgentBean</ejb-name>
<remote>com.titan.travelagent.ejb.TravelAgentRemote</remote>
<ejb-class>com.titan.travelagent.ejb.TravelAgentBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
And my persistence.xml is :
<?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="Titan">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<class>com.titan.domain.Cabin</class>
<properties>
<property name="hibernate.connection.driver_class" value="oracle.jdbc.OracleDriver" />
<property name="hibernate.connection.url"
value="jdbc:oracle:thin:@localhost:1521:XE" />
<property name="hibernate.connection.username" value="SYSTEM" />
<property name="hibernate.connection.password" value="Swordfish1" />
</properties>
</persistence-unit>
</persistence>
I right-click on the Titan project name and choose Build Project. I get the following error message :-
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.2
Warning: A Session bean must implement, directly or indirectly, the javax.ejb.SessionBean interface.
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.3
Warning: A Session bean must define at least one ejbCreate method.
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.1
Warning: The session bean must implement either a remote home and remote, or a local home and a local interface or a service endpoint interface.
13:01:06,062 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.0.4.GA/server/default/deploy/Titan.jar
I don't understand, because as of EJB 3.0, you don't really need a home or local-home interface anymore...

Using @SecurityDomain("exemplo1") in my EJB and NOT providing jboss.xml, it works.
@SecurityDomain("exemplo1")
@RolesAllowed("yyy")
@Stateless(name="UserManagement")
public class UserManagementBean implements UserManagement {
public void add(User user) {
}Damn! This is some serious shit... I don�t want to configure this in every single EJB.
EJB 3.0 is nice, but some small trivial details like this and others, that was forgotten by Sun, piss me off!

Why do we use a home interface in EJB

I am trying to figure out why we need to use a HOME Interface in every EJB that we deploy in a container ? What is the significance ?
Thanks

Some info:
A home interface defines the methods that allow a client to create, find, or remove an enterprise bean. The home interface is EJB's way of creating an object. Home interfaces act as factories to create session beans and entity beans. The home interface defines the bean's life cycle methods, One of two interfaces for an enterprise bean. The home interface defines zero or more methods for creating and removing an enterprise bean. For session beans, the home interface defines create and remove methods, while for entity beans, the home interface defines create, finder, and remove methods.
You may want to also look up:
http://java.sun.com/j2ee/learning/tutorial/
http://java.sun.com/developer/onlineTraining/J2EE/Intro2/j2ee.html

Unable to lookup ejb local home interface after moving to wls 7.0

I'm getting an exception trying to lookup an ejb's local home interface
which I believe was deployed correctly. On startup I get the message:
EJB Deployed EJB with JNDI name
com.logistics.basedata.ejb.shipperspecificfveb.ShipperSpecificFVDOLocalHome.
However, when I try to do a lookup using this jndi name, I get the
following exception:
javax.naming.LinkException: . Root exception is
javax.naming.NameNotFoundException: Unable to resolve
'app/ejb/ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificfveb/local-home'
Resolved: 'app/ejb'
Unresolved:'ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificfveb'
; remaining name
'ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificfveb/local-home'
The name it can't resolve is different than the name I was trying to
look up. I can see
com.logistics.basedata.ejb.shipperspecificfveb.ShipperSpecificFVDOLocalHome
in the jndi tree through the admin console, but the attributes Object
Class, Object Hash Code, and Object To String are blank.
This worked with weblogic 6.1 sp3. Is there something I missed in the
migration to 7.0?
Any help would be appreciated. Thanks in advance,
-Brad

That explains it - in 7.0 (unlike 6.1 - then the only factor was
classloaders arrangement) client has to be
in the same application (ear) - note JNDI links used to be able to lookup
local homes.
"Brad Geddes" <[email protected]> wrote in message
news:[email protected]...
I'm looking it up from a web application. I did notice a message on thistopic
from last thursday (subject: "Pls Help! Failed to access local Sessionbean in
7.0!"). In it, the individual said he had to add ejb-local-ref elementsin the
web.xml. I tried this but can't seem to get it to work.
javax.naming.NameNotFoundException: Unable to resolve ejb-link.
ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificfveb isnot in
the context. The context includes the following link bindings: {} Makesure the
link reference is relative to the URI of the referencing module.
Also, I don't have a war or ear in the environment I'm working in; theejb's are
all deployed separately in jar files, and the web app is in explodedformat.
>
-Brad
"Dimitri I. Rakitine" wrote:
Are you looking up the local home from outside of an application ?
"Brad Geddes" <[email protected]> wrote in message
news:[email protected]...
I'm getting an exception trying to lookup an ejb's local home
interface
which I believe was deployed correctly. On startup I get the message:
EJB Deployed EJB with JNDI name
com.logistics.basedata.ejb.shipperspecificfveb.ShipperSpecificFVDOLocalHome.
>>>
However, when I try to do a lookup using this jndi name, I get the
following exception:
javax.naming.LinkException: . Root exception is
javax.naming.NameNotFoundException: Unable to resolve
'app/ejb/ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificf
veb/local-home'
Resolved: 'app/ejb'
Unresolved:'ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecif
icfveb'
; remaining name
'ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificfveb/loca
l-home'
The name it can't resolve is different than the name I was trying to
look up. I can see
com.logistics.basedata.ejb.shipperspecificfveb.ShipperSpecificFVDOLocalHome
in the jndi tree through the admin console, but the attributes Object
Class, Object Hash Code, and Object To String are blank.
This worked with weblogic 6.1 sp3. Is there something I missed in the
migration to 7.0?
Any help would be appreciated. Thanks in advance,
-Brad
Dimitri--
Dimitri

Problem in compiling ejb home interface

Similar Messages

Maybe you are looking for