Local Interfaces using CMP

I am trying to implement a relationship between two entity beans using RI. Entity A defines a remote interface and references Entity B, to which it has a reference, through Entity B's local interface.
I cannot get this to work. I get a compile error when trying to deploy the application. When I run the Verifier, I get the following error for Entity A:
Error: No local interfaces defined
If I take out the relationship and reference to Entity B, everything works fine. I also downloaded an example from the WROX website which does the same thing I'm trying to do. It also brought up the same error.
Has anyone been able to get this to work with RI?

http://forum.java.sun.com/thread.jsp?forum=136&thread=166475

Similar Messages

Problem with local interfaces using oc4j 9.0.4 standalone

I am not able to get oc4j 9.0.4 standalone to use local interfaces. I belive that my configurations and code are correct. I am receiving javax.naming.NameNotFoundException
whenever I attempt to lookup a local ejb
lookup code
Context context = new InitialContext();
ApplicationBMPLocalHome appBMPLocalHome = (ApplicationBMPLocalHome)context.lookup("java:comp/env/ejb/ApplicationBMPLocalHome");
part of ejb-jar.xml
<ejb-local-ref>
<ejb-ref-name>ejb/ApplicationBMPLocal</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>JRun2.ApplicationBMPLocalHome</local-home>
<local>JRun2.ApplicationBMPLocal</local>
<ejb-link>ApplicationBMP</ejb-link>
</ejb-local-ref>
I know that local interfaces did not work in 9.0.3 oc4j, bu t I assume that this problem was fixed in 9.0.4. Correct me if that is not the case.

In your code you look up ApplicationBMPLocalHome, but your <ejb-ref-name> is ApplicationBMPLocal.
Try too change your lookup to
(ApplicationBMPLocalHome)context.lookup("java:comp/env/ejb/ApplicationBMPLocal");
/Fredrik

Local Interfaces in WebLogic 7.0 Not Faster Than Remote Interfaces?

I was curious how much faster calling business methods in
a stateless session EJB in WebLogic 7.0 would be through
a local interface than calling the same business methods
through a remote interface. I timed both ways of calling
the same methods and much to my surprise the times were
nearly identical. I double-checked that in one case I really
used the local interface (using ejb-local-ref, local-jndi-name,
local interfaces in source code). Does anybody (perhaps from
BEA) have an explanation for this? By the way, I ran the
same experiment with other J2EE application servers such
as IBM's WebSphere 5 (Beta) and there was a tremendous
performance difference between local and remote interface
usage.
Thanks,
Reinhard

"Reinhard Klemm" <[email protected]> wrote in message
news:[email protected]...
I appreciate your response and, at the same time, I am somewhat
surprised about it. Here are the reasons for my surprise:
1. Your response indicates that WebLogic uses RMI for
EJB local method calls, i.e., even if the client is on the same VM.
I would have assumed that WebLogic would bypass RMI in such
a situation.That is not what I said. Local interfaces wont use rmi.
But remote interfaces do better if the call is from the same VM. This is
weblogic rmi optimization. Please see Rob's posting also.
2. Other J2EE application servers fare a lot better. In one
experiment, I timed WebLogic against WebSphere 5.0 Technology
for Developers (i.e., WebSphere 5.0 Beta, which is expressly
NOT for performance testing) and against the Sun Reference
Implementation. Here are the numbers for calling business
methods in a stateless session EJB through its local interface:
WebLogic: 5.15 ms on the average
WebSphere: 0.41 ms on the average
Sun Reference Implementation: 0.11 ms on the average
This indicates to me that both WebSphere and the Sun Reference
Implementation are better optimized than WebLogic by excluding
RMI when making local EJB calls.
Reinhard
"Maruthi Nuthikattu" <[email protected]> wrote in message
news:<[email protected]>...
Can you post some numbers so that we can visualize the difference.
Please add the numbers with other J2EE appserver also.
Otherwise top of my head, the reason is:
Weblogic rmi is well optimized for the calls with in the same JVM andsame
J2EE application.
This could be the reason you are not seeing much difference.
..maruthi
"Reinhard Klemm" <[email protected]> wrote in message
news:[email protected]...
I was curious how much faster calling business methods in
a stateless session EJB in WebLogic 7.0 would be through
a local interface than calling the same business methods
through a remote interface. I timed both ways of calling
the same methods and much to my surprise the times were
nearly identical. I double-checked that in one case I really
used the local interface (using ejb-local-ref, local-jndi-name,
local interfaces in source code). Does anybody (perhaps from
BEA) have an explanation for this? By the way, I ran the
same experiment with other J2EE application servers such
as IBM's WebSphere 5 (Beta) and there was a tremendous
performance difference between local and remote interface
usage.
Thanks,
Reinhard

CMP Entity beans using local interfaces

Why CMP entity beans with CMR relation ship using local interfaces only?
Why we should not use remote interface to get the CMR field relationship?
Pls give me the solutions

"Local interfaces provide the foundation for container-managed relationships among entity beans and session beans. The bean uses the local interface to maintain its references to other beans. For example, an entity bean uses its local interfaces to maintain relationships to other entity beans. Using local interfaces, beans can also expose their state and use pass-by-reference to pass their state between related bean instances. "
http://java.sun.com/developer/technicalArticles/ebeans/EJB20CMP/

Use remote or local interface in my CMP EB?

I found it's suggested to writer your CMP EB with Local interface.and a Session Bean with Remote interface.and bundle them into a same EJB JAR file.my end-user client (WAR file) call SB in another JVM.
I wrote two methods in my SB named [CreateAuser & DeleteAuser] which call enity bean by local interface.
and I found it wokrs good anywhere while doing Create or Remove an enity object in my jsp files;
But I have no way to directly call enity bean in jsp files to do database query.
Do I have to write a method like findbyuserid which calls entity bean's home method findByPrimaryKey()? if so I should rewriter many methods in my SB to meet my jsp files need.
What shall I do ,what is the common way to do sth like that?

Hi,
You SessionBean (Session Facade pattern) should provide service such as Business Service (Create User, Remote User, GetUser ...) that's the role of SessionBean as Session Facade.
All the method you expect to call from Presentation Tier.
Regards
Sebastien Degardin.

Use of local interface btw EAR

hi,
Can i use local interfaces to call session bean of EAR1 from EAR2. in my case EAR1 and EAR2 are deployed in the weblogic instance(same jvm). and parameters are being passed by value(because of 2 different classloaders).
I tried doin this ... but resulted in exception being thrown when i tried to do a lookup to the localhome of EAR1.
Please advise,
venkat

Hi,
Even though they are running in the same JVM, the classes are not visible between EAR1 and EAR2 because they are loaded in separate classloaders, therefore local interfaces won't work.
-thorick

How use a proxy consumer web service in ABAP Program with local interface

I generate a proxy class based on a WSDL file.
I want to use this class in an abap programm without a connection but using XML files in local.
I see with the class CL_PROXY_LOCAL_ADAPTER that it is possible to execute without connection but for use this, it's necessary to use the method REGISTER.
This method have two parameters : Class Name and Interface Name.
Class name is the name of my proxy class, but I don't know how to find the interface name.
I think that a local interface is needed to generate but I don't know how to generate in interface with entries in SPROXSIG table ?
Could you help me ?

Check out the following links to see if it meets your needs.. Has examples to call a ABAP proxy (that consumes a webservice) from ABAP program...
http://help.sap.com/saphelp_nw04/helpdata/en/bf/d005244e9d1d4d92b2fe7935556b4c/frameset.htm (webservices ->webservices toolset -> examples)
http://help.sap.com/saphelp_dm40/helpdata/en/1a/b69d427cab0831e10000000a1550b0/frameset.htm

Using local interfaces for EJB (session bean)

Hi,
I�ve a question regarding when to use the Local interfaces(EJBLocal and EJBLocalHome) of a enterprise bean. I understand that calls to enterprise bean can be made locally if the client which is invoking is in the same JVM as that of EJB. I�ve written a web client (servlet) which is packaged in a EAR and this servlet is trying to invoke a session bean which is in a �different� EAR using local interfaces. Both the EARs have been deployed in a single server (websphere 6.0 server). It didn�t work for me this way�..If I package the servlet in the same EAR of session bean then it works fine.
So is this to say that both EARs are not running on the same JVM? Or should it work even if the client and the session bean are in different EARs but in same server?
Can anyone explain me the fundamentals behind this.
Thanks in advance

Local access is only portable within the same .ear. For example, the Java EE SDK and SUN's
application servers have never supported local EJB access from a web/EJB component in a different
.ear. One issue is that local access requires that both the caller and target EJB have the same
classloader. By definition, different Java EE applications have distinct classloaders. In addition,
in Java EE 5 persistence context propagation does not span applications, so it wouldn't work in the
local case.
--ken

No performance gain when using local interfaces

Hello,
I'm doing some tests to compare performances between remote ejb interfaces and local ejb interfaces.
I have two stateless session beans EJB1 and EJB2, EJB1 calls a method on EJB2, this method receives one object as the only parameter and returns it immediately. The parameter is a big object (~700ko). My test consists simply of making 1000 calls from EJB1 to EJB2, one time with remote interfaces, one time with local interface. For both tests, the EJBs run in the same container, same VM.
The results show absolutely no differences between the remote and the local interface !
As I found these results a bit surprising, I changed the serialization method of my parameter object this way:
private void writeObject(java.io.ObjectOutputStream out) throws IOException {
System.out.println("writeObject(MyBigObject)");
out.defaultWriteObject();
just to check if my object is serialized when using remote interface. And the response is no.
So question is: is there an "undocumented optimization" of the stub/skel generated by weblogic which make local calls when calling a remote method inside the same VM ?
Some precisions:
- I'am using weblogic 8.1sp2
- When calling remotely my EJB2 from an external batch (running in a separate VM), I see the message "writeObject(MyBigObject)" so the serialization is done in this case.

<Fr?d?ric Chopard> wrote in message news:[email protected]..
So question is: is there an "undocumented optimization" of the stub/skel generated by weblogic which make local calls when callinga remote method inside the same VM ?
>
Some precisions:
- I'am using weblogic 8.1sp2
- When calling remotely my EJB2 from an external batch (running in a separate VM), I see the message "writeObject(MyBigObject)" sothe serialization is done in this case.
WebLogic 5.x, 6.x and 7.x do call by reference for co-located EJBs by default. 8.1 has this behavior turned off by default. You may
experience call-by-reference optimization in 8.1 only if it has been turned on explicitly in the deployment descriptor.
Hope this helps.
Regards,
Slava Imeshev

How to use local interface in my easy code ?

hi everybody
I work on an ejb project. My code is like that to test remote interface (and it works) :
public class TestStudent {
   Properties properties;
   public TestStudent() {
      properties = new Properties();
      properties.put("java.naming.factory.initial",
      "org.jnp.interfaces.NamingContextFactory");
      properties.put("java.naming.factory.url.pkgs",
      "org.jboss.naming:org.jnp.interfaces");
      properties.put("java.naming.provider.url", "jnp://localhost:1099");
      properties.put("jnp.disableDiscovery", "true");
   public static void main(String[] args) {
      TestStudent beanStudent = new TestStudent();
      beanStudent.createBean();
   public void createBean() throws EJBException {
      try {
         InitialContext context = new InitialContext(properties);
         Object object = context.lookup(StudentHome.JNDI_NAME);
         StudentHome studentHome = (StudentHome) PortableRemoteObject.narrow(object,StudentHome.class);
         Student student = studentHome.create();
         student.setName("pirlouit");
         System.out.println(student.getId());
         System.out.println(student.getName());
      } catch (NamingException e) {
         throw new EJBException(e);
      } catch (RemoteException e) {
         throw new EJBException(e);
      } catch (CreateException e) {
         throw new EJBException(e);
}Then I do quite the same thing to test local interface like in the following code but it doen't work :
public class TestStudent {
   Properties properties;
   public TestStudent() {
      properties = new Properties();
      properties.put("java.naming.factory.initial",
      "org.jnp.interfaces.NamingContextFactory");
      properties.put("java.naming.factory.url.pkgs",
      "org.jboss.naming:org.jnp.interfaces");
      properties.put("java.naming.provider.url", "jnp://localhost:1099");
      properties.put("jnp.disableDiscovery", "true");
   public static void main(String[] args) {
      TestStudent beanStudent = new TestStudent();
      beanStudent.createBean();
   public void createBean() throws EJBException {
      try {
         InitialContext context = new InitialContext(properties);
         Object object = context.lookup(StudentLocalHome.JNDI_NAME);
         StudentLocalHome studentLocalHome = (StudentLocalHome)object;
         System.out.println("studentLocalHome is null ? "+studentHome.equals(null));
         StudentLocal student = studentLocalHome.create();
         student.setName("pirlouit");
         System.out.println(student.getId());
         System.out.println(student.getName());
      } catch (NamingException e) {
         throw new EJBException(e);
      } /*catch (RemoteException e) {
         throw new EJBException(e);
      }*/ catch (CreateException e) {
         throw new EJBException(e);
}The print of "student local home is null ?" give me 'true' which is not the answer I want ... so here is the problem. How can I get my entity bean using local interface ?
For the moment 've got the exception (which appears on instruction "StudentLocal student = studentLocalHome.create();") :
Exception in thread "main" java.lang.NullPointerException
     at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:118)
     at $Proxy0.create(Unknown Source)Please help !! Thank you very much !

Write a JSP to test Local Interface. You cannot call Local Interface from a remote JVM.
Jay
http://www.javarss.com - Java News from around the world.
Visit JavaRSS.com and add above signature to your messages. Thanks!

Accessing bean using its Local interface

Hi,
I have a problem accessing a bean using its local interface in J2EE1.3 environment on J2EE test server. I have two beans, one trying to access other, residing in two different ears. During deployment, after I select "Local" interface option in EJB-refs tag of the standard deployment tool of J2ee, it does not show me the bean-name in the "Enterprise Bean Name" combo-box. When I put the name of the actual bean in the box and try to deploy it, gives the null-pointer exception for the above tag as it does not find the corresponding ejb to be referred.
Is it necessary to have a client bean and actual bean to be in the same ear for local interface access? The specifications says that both the beans must be in the same container that does not mean same ear, right????
Thanks

i am having the exact same problem now.
did anyone solve this.(you can email [email protected])

Using EJB Local Interface problem

Hi to all
I have got a problem in using Local EJB Interface in Weblogic , please attention to my description
I use JDeveloper as IDE
At first I create an Application in JDeveloper that has two projects that their names are Model and ViewContorller that first one contains my EJB and another contains my JSP page respectively
The EJB code is :
@Stateless(name="AliEJB001Bean")
@Remote
@Local
public class AliEJB001Bean implements AliEJB001, AliEJB001Local {
public AliEJB001Bean() {
public String Hi(){
return "Hi000";
And its Local Interface code is :
@Local
public interface AliEJB001Local {
String Hi();
I deploy Model project to an EJB Jar file that its name is AliEE1ejb1.jar
and I deploy the ViewContorller project to a WAR file that its name is AliEE1WebApp.war
Now I add this tags to web.xml
<ejb-local-ref>
<ejb-ref-name>ali/testejb</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local>model.AliEJB001Local</local>
</ejb-local-ref>
Then I deploy the Application to an EAR file by name AliEE1
After those I run my JSP page witch calls the EJB in JDeveloper (through Local EJB Interface) , JDeveloper deploy my Application to the ItegratedWeblogicServer
Ultimately the JSP can calls the EJB through Local Interface and use the Hi method and shows me the result but JDeveloper while compiles the application give me these Warnings :
Warning: <May 15, 2011 9:02:52 AM PDT> <Error> <J2EE> <BEA-160187> <weblogic.appc failed to compile your application. Recompile with the -verbose option for more details. Please see the error message(s) below.>
Warning: There are 1 nested errors:
Warning: weblogic.servlet.internal.dd.compliance.ComplianceException: Element "<ejb-local-ref>" with ejb-ref-name "ali/testejb" must either specify a valid ejb-link element or have a corresponding ejb-reference-descriptor element in weblogic.xml with a valid jndi-name.
Warning:      at weblogic.servlet.internal.dd.compliance.BaseComplianceChecker.addDescriptorError(BaseComplianceChecker.java:74)
Warning:      at weblogic.servlet.internal.dd.compliance.BaseComplianceChecker.addDescriptorError(BaseComplianceChecker.java:80)
Warning:      at weblogic.servlet.internal.dd.compliance.EJBRefsComplianceChecker.validate(EJBRefsComplianceChecker.java:97)
Warning:      at weblogic.servlet.internal.dd.compliance.EJBRefsComplianceChecker.checkEJBLocalRef(EJBRefsComplianceChecker.java:47)
Warning:      at weblogic.servlet.internal.dd.compliance.EJBRefsComplianceChecker.check(EJBRefsComplianceChecker.java:39)
Warning:      at weblogic.servlet.internal.dd.compliance.ComplianceUtils.checkCompliance(ComplianceUtils.java:48)
Warning:      at weblogic.servlet.jsp.JspcInvoker.checkCompliance(JspcInvoker.java:145)
Warning:      at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:198)
Warning:      at weblogic.application.compiler.AppcUtils.compileWAR(AppcUtils.java:376)
Warning:      at weblogic.application.compiler.WARModule.compile(WARModule.java:245)
Warning:      at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:18)
Warning:      at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
Warning:      at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
Warning:      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
Warning:      at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
Warning:      at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
Warning:      at weblogic.application.compiler.WARCompiler.compile(WARCompiler.java:29)
Warning:      at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:112)
Warning:      at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:37)
Warning:      at weblogic.application.compiler.Appc.runBody(Appc.java:198)
Warning:      at weblogic.utils.compiler.Tool.run(Tool.java:158)
Warning:      at weblogic.utils.compiler.Tool.run(Tool.java:115)
Warning:      at weblogic.application.compiler.Appc.main(Appc.java:257)
Warning:      at weblogic.appc.main(appc.java:14)
According to the warning messages I wanna add <ejb-link> tag to the web.xml for resolving warnings I add the <ejb-link> like this:
<ejb-local-ref>
<ejb-ref-name>ali/testejb</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local>model.AliEJB001Local</local>
<ejb-link>AliEE1ejb1.jar#AliEJB001Bean </ejb-link>
</ejb-local-ref>
But when JDeveloper want deploy my application again it shows me this Error
[09:29:59 AM] Redeploying Application...
<May 15, 2011 9:29:59 AM PDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1305476999381' for task '7'. Error is: 'weblogic.application.ModuleException: Could not setup environment'
weblogic.application.ModuleException: Could not setup environment
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1499)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:442)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'AliEE1ejb1.jar#AliEJB001Bean' declared in the ejb-ref or ejb-local-ref 'ali/testejb' in the application module 'ViewControllerWebApp.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct.
     at weblogic.deployment.BaseEnvironmentBuilder.addEJBLinkRef(BaseEnvironmentBuilder.java:464)
     at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:485)
     at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:157)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3117)
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1497)
     Truncated. see log file for complete stacktrace
>
<May 15, 2011 9:29:59 AM PDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 9 task for the application 'AliEE1'.>
<May 15, 2011 9:29:59 AM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'AliEE1'.>
<May 15, 2011 9:29:59 AM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Could not setup environment
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1499)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:442)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'AliEE1ejb1.jar#AliEJB001Bean' declared in the ejb-ref or ejb-local-ref 'ali/testejb' in the application module 'ViewControllerWebApp.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct.
     at weblogic.deployment.BaseEnvironmentBuilder.addEJBLinkRef(BaseEnvironmentBuilder.java:464)
     at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:485)
     at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:157)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3117)
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1497)
     Truncated. see log file for complete stacktrace
>
[09:30:00 AM] #### Deployment incomplete. ####
[09:30:00 AM] Remote deployment failed
Do you know how I can solve this issue ?
thanks

Thank you so much
I find out the solution
I have to define my EJB in ejb-jar.xml like this
<enterprise-beans>
     <session>
     <ejb-name>ReplicableSFSB2</ejb-name>
     <business-local>model2.AliEJB001Local</business-local>
     <business-remote>model2.AliEJB001</business-remote>
     <ejb-class>model2.AliEJB001Bean</ejb-class>
     <session-type>Stateless</session-type>
     </session>
</enterprise-beans>
And then I use the EJB name witch I defined in <ejb-name> tag in <ejb-link> tag of web.xml
like this
<ejb-local-ref>
<ejb-ref-name>ali/testejb2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local>model2.AliEJB001Local</local>
<ejb-link>Model2EJB.jar#ReplicableSFSB2</ejb-link>
</ejb-local-ref>

ClassCastException by using Local Interface of EJB in other, but local EAR

Hi,
I get a ClassCastException if I try to cast the EJSWrapper-Class returned from local EJB Lookup to the interface it implements.
The environment I use is WSADIE 5.1.1 with integrated Testenvironment.
I have defined two EARs. One with a Web-Application and one wich contains the EJB to call from the WebApp. Both run in the same appserver instance wich means both run in the same JVM and i should be able to use Local Interface of the EJB.
The EJB should use Libraries from the Server Environment while the WebApp uses newer Libs than the Server Environment offers(eg axis-rpc,wsdl4j,saaj). The Classloader-Policy of the EAR with the WebApp is set to PARENT_LAST while the Classloader-Policy of the EAR with the EJB is set to PARENT_FIRST.
I do a Lookup by using an EJB-Local-Reference. The returned object is an EJSLocalStatelessHome-Object, wich implements my LocalEJBInterface. But if i try to cast to Object to this interface a ClassCastException occurs.
The Classes of the EJB are packaged as follows:
EJBName.jar contains the EJB-Impl class, the Serverside Implementations for RMI/IIOP interaction an EJSWrapper classes. This jar is packaged with the EJB-EAR.
EJBClient.jar contains the Local- and Remote-Interface classes and the Stub-classes for EJBHome and EJB-Implementation. This jar is packaged wich both EARs, because of the interfaces, wich are needed in both projects.
The Classloader of the EAR with the WebApp has no access the jar with the EJB-Impl, the generated Ties- and EJSWrapperclasses because it is located in only the EJB-EAR. But the interface-class is contained in the WebApp-EAR as described above.
The exact Exception is as follows:
java.lang.ClassCastException: com/ibm/wsrf/EJSLocalStatelessBPEAdapterHome_c2546ef5 incompatible with com/ibm/wsrf/BPEAdapterLocalHome
java.lang.Throwable.<init>(Throwable.java)
java.lang.Throwable.<init>(Throwable.java)
java.lang.ClassCastException.<init>(ClassCastException.java:53)
org.tempuri.ResourceDiscoveryService.DiscoverySoapHttpBindingImpl.getResourceEPR(DiscoverySoapHttpBindingImpl.java)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java)
... The EJSLocalStatelessBPEAdapterHome_c2546ef5 implements the BPEAdapterLocalHome interface.
Please, can anyone give me a hint how to solve this problem?
Thanks in advance, Michael

Problem solved!
The different EAR contained each an own copy of the jar with the local and remote interfaces of the EJB. The Problem is caused by the separate classloaders of the EARs in an application server. Each EAR Classloader loads his own version of the interface classes. Is the same class loaded by different classloaders, the JVM handles this classes as different classes. An example if you create an instance of a class in one classloader and try to reference the created instance by the same class from another classloader, the association will fail, because of different classloaders in the same JVM.
The solution in an application server where you have deployed two projects and want to use local interfaces is, store the interfaces(and only the interfaces) in an directory, where it is found by the parent classloader of the EAR classloaders. Remove the Jar with the interface from the EARs. The EAR Classloaders will then search in the their parent classloader for the interfaces. The interfaces will be loaded by the parent classloader and will recognized as compatible by the JVM.
Greetings, hope this helps help others!
Michael

How to get Initial context of Local Interface in weblogic 8.1

I have developed a local entity bean but i wouldnt able to initial context of that bean
CAN ANYBODY HELP ME
bean deployment descriptor
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>

<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>CabinBean</ejb-name>
<home>my.CabinRemoteHome</home>
<remote>my.CabinRemote</remote>
<ejb-class>my.CabinBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>True</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>CabinBean</abstract-schema-name>
<cmp-field>
<field-name>bedCount</field-name>
</cmp-field>
<cmp-field>
<field-name>deckLevel</field-name>
</cmp-field>
<cmp-field>
<field-name>id</field-name>
</cmp-field>
<cmp-field>
<field-name>name</field-name>
</cmp-field>
<cmp-field>
<field-name>shipId</field-name>
</cmp-field>
<primkey-field>id</primkey-field>
<security-identity>
<use-caller-identity/>
</security-identity>
</entity>
<entity>
<ejb-name>CabinLocal</ejb-name>
<local-home>my.CabinLocalHome</local-home>
<local>my.CabinLocalLocal</local>
<ejb-class>my.CabinLocal</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>True</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>CabinLocal</abstract-schema-name>
<cmp-field>
<field-name>bedCount</field-name>
</cmp-field>
<cmp-field>
<field-name>deckLevel</field-name>
</cmp-field>
<cmp-field>
<field-name>id</field-name>
</cmp-field>
<cmp-field>
<field-name>name</field-name>
</cmp-field>
<cmp-field>
<field-name>shipId</field-name>
</cmp-field>
<primkey-field>id</primkey-field>
<ejb-local-ref>
<ejb-ref-name>LocalCabin</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>CabinLocalHome</local-home>
<local>CabinLocal</local>
<ejb-link>LocalCabin</ejb-link>
</ejb-local-ref>
<security-identity>
<use-caller-identity/>
</security-identity>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>CabinLocal</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>CabinBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
<ejb-client-jar>EjbClient</ejb-client-jar>
</ejb-jar>
************************************** Client Code****************
package com;
import my.CabinBean;
import my.CabinRemoteHome;
import my.CabinRemote;
import javax.naming.InitialContext;
import javax.naming.Context;
import javax.naming.NamingException;
import java.rmi.RemoteException;
import java.util.Properties;
import javax.rmi.PortableRemoteObject;
import weblogic.jndi.Environment;
public class Test
    public static void main(String args[])
        try{
             Context context = getInitialContext();
                      Object cab = context.lookup("CabinLocalHome");
            ///**********-- Exception is thrown at this point -******************
            System.out.println("============ done====");
            Context ct = getInitialContext();
            Object ref = ct.lookup("CabinHomeRemote");
            CabinRemoteHome home = (CabinRemoteHome)PortableRemoteObject.narrow(ref,CabinRemoteHome.class);
            //CabinRemote cab = home.create(new Integer(1));
            //cab.setName("Master Suite");
            //cab.setDeckLevel(new Integer(1));
            //cab.setShipId(new Integer(1));
            //cab.setBedCount(new Integer(1));
            Integer pk = new Integer(1);
            CabinRemote cab1 = home.findByPrimaryKey(pk);
            System.out.println("--->>>>>>>> "+cab1.getName());
            System.out.println("--->>>>>>>> "+cab1.getShipId());
            System.out.println("--->>>>>>>>"+cab1.getBedCount());
            System.out.println("--->>>>>>>>"+cab1.getDeckLevel());
            System.out.println("---");
      }catch(java.rmi.RemoteException e){e.printStackTrace();}
       catch(javax.naming.NamingException e){e.printStackTrace();}
       //catch(javax.ejb.CreateException e){e.printStackTrace();}
       catch(javax.ejb.FinderException e){e.printStackTrace();}
    public static Context getInitialContext() throws javax.naming.NamingException
       Properties p = new Properties();
       p.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
       p.put(Context.PROVIDER_URL,"t3://localhost:7001");
       return new javax.naming.InitialContext(p);
} ************************************** Error ***********************
javax.naming.LinkException: [Root exception is javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException: remaining name: /app/ejb/myejb.jar#CabinLocal/local-home]; Link Remaining Name: 'null']; Link Remaining Name: 'java:app/ejb/myejb.jar#CabinLocal/local-home'
     at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
     at weblogic.jndi.internal.ServerNamingNode_813_WLStub.lookup(Unknown Source)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:369)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:357)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.Test.main(Test.java:27)
Caused by: javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException: remaining name: /app/ejb/myejb.jar#CabinLocal/local-home]; Link Remaining Name: 'null'
     at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:98)
     at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:292)
     at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:771)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
     at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Caused by: javax.naming.NameNotFoundException: remaining name: /app/ejb/myejb.jar#CabinLocal/local-home
     at weblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:35)
     at weblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:39)
     at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:57)
     at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:62)
     at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)
     at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)

Hi,
from what I gather, u have two jars
1. EJBClient - this will have remote and home interfaces and will be used by the client
2. myEJB - this iwll have all the classes - remote & home interfaces, the bean class and all the other classes required by the bean.
Now, the question is, who is acting as the client of your EJB ? There are 3 possibilities
1. A servlet
2. Another EJB
3. a simple java program.
In the first 2 cases, you can go for Local Interfaces (more so in the second case than the first). The reason being that the the client and server will be in the same JVM. Thus, in the first case, if the Web container and the ejb container are in the same app server, EJBs can be local.
However, in the third case, it is unlikey that you will have the client runnng and the same jvm as the server, because the server is using the jvm provided by weblogic.
Thus, you cannot use local interfaces in this 3rd case. I have a feeling that this is what you are doing. If so, change the local interfaces to remote.
See if this helps. Else, I will mail you some sample code. But I am afraid, sample code wont be of much help bcoz this seems to be a design problem.
regards

CMR and Local Interfaces

I have a question on setting up CMR in an environment where I want to utilize local
interfaces within a weblogic server instance. In the deployment descriptor, I have
set up the home, remote, local-home, local, and ejb-class entries. I then want to
define the relationships between two CMP entity beans. Here is where I run into
problems.
1) If I define the CMR field using the local interface, I get an error stating that
the type defined by the bean for the field does not match that of the remote interface.
2) If I define the CMR field using the remote interface, I get an error stating that
the bean must use the local interface for the CMR if one exists.
Seems kind of circular to me. What am I missing?

If you want to be able to have mutiple children companies for a parent
company and you want to be able to query for the parent company for a given
comapnay then this is the XML I would do something like the following. In
your xml you had the mutiplicities inverted and also the cmr field was
either in the wrong place or misnamed (ie, if it had to be in the top block
then it should have been "childCompanies" instead of "parentCompany").
Assuming the bean name in the descriptor for the CompanyEJB is Company:
<ejb-relation>
<ejb-relation-name>Company-ParentCompany</ejb-relation-name>
<ejb-relationship-role>
<ejb-relationship-role-name>Company-Has-ChildCompanies</ejb-relationship-rol
e-name>
<multiplicity>one</multiplicity>
<relationship-role-source>
<ejb-name>Company</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>Company-Has-ParentCompany</ejb-relationship-role
-name>
<multiplicity>many</multiplicity>
<relationship-role-source>
<ejb-name>Company</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>parentCompany</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
</ejb-relation>
In the CompanyEJB you would have:
public abstract CompanyLocal getParentCompany();
public abstract void setParentCompany( CompanyLocal parent );
-- Anand
"Steve Ebersole" <[email protected]> wrote in message
news:[email protected]...
>
The jar I am running through ejbc is attached (with source). The EJBobject naming
conventions are as follows:
ejb-class = CompanyEJB
home = CompanyHome
remote = Company
local-home = CompanyLocalHome
local = CompanyLocal
The pertinent ejb-jar snippet:
<ejb-relation>
<ejb-relation-name>Company-ParentCompany</ejb-relation-name>
<ejb-relationship-role>
<ejb-relationship-role-name>Company-Has-ChildCompanies</ejb-relationship-rol
e-name>
<multiplicity>Many</multiplicity>
<relationship-role-source>
<ejb-name>Company</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>parentCompany</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>Company-Has-ParentCompany</ejb-relationship-role
-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
<ejb-name>Company</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>
And the weblogic-cmp-rdbms-jar snippet:
<weblogic-rdbms-relation>
<relation-name>Company-ParentCompany</relation-name>
<weblogic-relationship-role>
<relationship-role-name>Company-Has-ParentCompany</relationship-role-name>
</weblogic-relationship-role>
<weblogic-relationship-role>
<relationship-role-name>Company-Has-ChildCompanies</relationship-role-name>
<column-map>
<foreign-key-column>PRNT_COMP_ID</foreign-key-column>
<key-column>COMP_ID</key-column>
</column-map>
</weblogic-relationship-role>
</weblogic-rdbms-relation>
In the CompanyEJB, these are the two scenarios I tried:
1)
public abstract Company getParentCompany();
public abstract void setParentCompany( Company prnt );
2)
public abstract CompanyLocal getParentCompany();
public abstract void setParentCompany( CompanyLocal prnt );
The only way I have been able to get it to work so far is to use thesyntax in #1
above and then to remove all references to the local interfaces in thedeployment
descriptors.
Thanks for all help

Local Interfaces using CMP

Similar Messages

Maybe you are looking for