Local versus remote interface

Hello
i'm working with Bea weblogic 8.1 sp1. We are now looking to change our remote
interface into locale interface to avoid serialization. But someone tell me that
bea weblogic already manage remote interface as local interface if we are inside
a ear application deploy on one server !
I look in Bea documentation but i was not able to find anything that confirm this.
Do someone know abou this!!!!!

If by serialization you mean call-by-value, then take a look at
enable-call-by-reference. You can avoid the cost of copying by setting this
to true. Otherwise, the default value is false.
"Benjamin Léonard" <[email protected]> wrote in message
news:[email protected]..
>
Hello
i'm working with Bea weblogic 8.1 sp1. We are now looking to change ourremote
interface into locale interface to avoid serialization. But someone tellme that
bea weblogic already manage remote interface as local interface if we areinside
a ear application deploy on one server !
I look in Bea documentation but i was not able to find anything thatconfirm this.
Do someone know abou this!!!!!

Similar Messages

Configure webapp to use local or remote interface based on environment

Hi,
I have the following problem I am trying to solve (app server is Weblogic 10g by the way).
I have a webapp (war-project) and an ear project containing stateless session beans.
In our development environment I would like to deploy the war and ear separately, because that is easier for development (war-project can then be deployed as a directory, so changes to jsp's and such have immediate effect).
Deploying the war and ear separately means that the war-project can only call the session beans through their remote interfaces. For development this is not a problem.
In a production environment however we would like to package the war INSIDE the ear, so that the webapp can use the local interfaces to call the session beans, as this will improve performance.
So I am looking for a solution where I can configure the way beans are called. Local if the war is inside the ear, remote if the war is separate from the ear. I was thinking along the lines of packaging a properties file with the war that determines the mode (local or remote). Or maybe packaging a different deployment descriptor, if that is a possibility.
This is what I have so far:
Business Interface_
package be.cegeka.test.ejb3.service;
public interface TestService {
     public void doSomething();
Remote Interface_
package be.cegeka.test.ejb3.service;
public interface TestServiceRemote extends TestService {
Local Interface_
package be.cegeka.test.ejb3.service;
public interface TestServiceLocal extends TestService {
Bean implementation_
package be.cegeka.test.ejb3.service;
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateless;
@Stateless(mappedName="ejb/TestService")
@Local(TestServiceLocal.class)
@Remote(TestServiceRemote.class)
public class TestServiceBean implements TestService {
     @Override
     public void doSomething() {
          System.out.println("I'm doing something");
     @Override
     public void doSomethingLocal() {
          System.out.println("I'm doing something local");
JSF backing bean_
package be.cegeka.test.ui;
public class MyWebAppBackingBean {
     @EJB(mappedName="ejb/TestService", beanInterface=TestServiceRemote.class)
     private TestService testService;
     public String doSmth() {
          testService.doSomething();
          return "success";
}The part that I would like to be configurable is the "+beanInterface=TestServiceRemote.class+" part in the JSF backing bean. Depending on the environment (development vs. production), this should be "+beanInterface=TestServiceRemote.class+" for development and "+beanInterface=TestServiceLocal.class+" for production.
Is something like this possible?
I would like to avoid having to fill my web.xml with ejb-refs and having to do the JNDI-lookups myself if at all possible, to keep things as easy and clean as possible.
Any ideas are welcome!
Steven

Hey Manish,
comments inline.
"manish kumar" <[email protected]> wrote in message
news:1794338.1102557677925.JavaMail.root@jserv5...
So If they are supposed to be in the same JVM -
then
1. the cluster of 3 weblogic servers are three JVMs. So does that meanLOCAL INTERFACES CAN'T BE USED IN CLUSTERED ENVIORONMENT ?
Sure they can, but the calling component in an enterprise app will not call
an intance of the local bean on another node in the cluster. It will make a
by-reference call to the local component in the same EAR. Local interfaces
are not Remote, so they cannot be used with by-value RMI semantics.
>
2. ARE YOU SURE ABOUT THIS FACT THAT THAT LOCAL INTERFACES CAN BE USEDONLY INSIDE THE SAME APPLICATION, I THOUGHT IT CAN BE USED AS LONG AS CLINET
IS IN THE SAME JVM?
PLEASE CONFIRM.........!!!!!!!!!!!!!Dead sure:
http://e-docs.bea.com/wls/docs81/programming/classloading.html#1073506
http://e-docs.bea.com/wls/docs81/ejb/understanding.html#1126831
http://e-docs.bea.com/wls/docs61/ejb/cmp.html#1085452
http://www.theserverside.com/discussions/thread.tss?thread_id=14628
Also, search the ejb newsgroups. I know Rob Woollen has addressed this in
here somewhere. And, if Rob says it's so, trust me, it's so.
Bill

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

How to deside weather to write local interface or remote interface

Hi All.
in Ejb 2.0 the concept of local and remote interface is introduced.then how to deside weather to wrire local interface or to write remote interface.
thanks

Here in lies the problem. That decision shouldn't be up to a developer, it should be the role of the deployer who decides this. I think they got this wrong in 2.0, its been put at the wrong level. You as the coder need to make scalability decisions about the deployment, which you shouldn't need to. One of the big stengths of the EJB's is that anyone can code them because the container does the hard work for you. That paradigm has been broken now, IMHO.
Having said that, I was at a SUN developer day just the other day and they suggested that the local interface was mainly for fine grained entity beans and that the course grained entity beans would access the fine grained over local interfaces thus allowing a 'cheaper' implementation of relationship modeling in the entity bean layer. In this scheme of things you would then use the remote interface from session beans to access the course grain entity beans.
Cheers,
Peter.

Get a remote interface from a local instance

hi,
I want to construct a bean locally on a server and then I want to pass the remote interface for that constructed bean back to a client. Is this possible?
Thanks

Yes. Take a look at SessionContext class. You can't construct a bean yourself, as its life is managed by container.
     * Obtain an object that can be used to invoke the current bean through
     * the given business interface.
     * @param businessInterface One of the local business interfaces
     *        or remote business interfaces for this session bean.
     * @return The business object corresponding to the given business
     *         interface.
     * @exception IllegalStateException Thrown if this method is invoked
     *         with an invalid business interface for the current bean.
    <T> T getBusinessObject(Class<T> businessInterface) throws IllegalStateException;

Convert a local interface to the remote interface

Hello *
Is it possible to convert a local interface to the same bean's remote interface?
Regards,
Lukas

Thanks for the reply.
I have simpliefied the lookup to the following:
Context ctx = new InitialContext();
spiHome = (ServiceProviderBeanLocalHome) ctx.lookup ("ServiceProviderBeanEJB");
I still get the following exception:
javax.naming.NameNotFoundException: ServiceProviderBeanEJB not found
at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:174)
I looked up the deployment descriptor from J2EE RI and took the name
to lookup from the ejb-name:
<ejb-jar>
<display-name>localSPIJAR</display-name>
<enterprise-beans>
     <entity>
          <display-name>ServiceProviderBeanEJB</display-name>
          <ejb-name>ServiceProviderBeanEJB</ejb-name>
I presume that this is the correct name to use.

Remote interface / Local interface

Hi
I would like to if its possible to avoid using remote interfaces completely and improve performance by using - JSP -> Servlet -> (local interface) Session bean -> Entity bean ???
Let the client call from JSP which is sent to control servlet which uses local-interface to send the request to a session bean that may in turn interact with Entity bean ?
Is there any specific guidelines regarding that ?
Thanks
Ramesh

building thru ANT is much more helpful, fast and efficient(I personally haven't tried any tools for builing EARs...:-)....Check out the EAR task in the ANT documentation...it describes each of its option and you will also find the EXAMPLES which you can download and tweak according to your beans....

Super interfaces on EJB 3.0 Remote interface in OC4J 10.1.3

We are implementing (on OC4J 10.1.3) an EJB 3.0 Stateless Session Bean with 2 business interfaces (remote and local) both of which extend an inteface we have defined in our system.
When we look up the local interface we see our interface in the bean.
When we look up the remote interface we do not see our interface in the bean.
Any ideas?
Thanks,
Ed Dirago
Computer Sciences Corp.
FAA TFMS System

The EJB 3.0 Remote Business references are not directly stored in CosNaming. EJB 3.0 Remote references do not have the cross-vendor interoperability requirements that the EJB 2.x Remote view had.
You can still access Remote EJB references from a different JVM as long as the client has access to SJSAS naming provider. Please see our EJB FAQ for more details :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html

Using local session bean interface from web container using EJB 3.0

Hi,
How can you use a local session bean interface from Java (rather than data controls) in a web container using EJB 3.0?
I can use a remote interface by looking up InitialContext, but I can't find a local interface this way (even from another session EJB). I can use a local interface from an EJB using annotation "EJB", but as I understand, this is not available in the web container.
If I try to add an ejb-jar.xml file, these seems to mess up by project...
Hope you can help.
Roger

The portable way to retrieve an EJB reference in Java EE is to either inject it or look it up via the
component's private naming environment. The simplest way is :
@EJB
private DocumentManager dm;
The global JNDI name is only used as an implementation specific way to uniquely assign an
identifier to a specific Remote EJB. It's best for this not to appear directly in the source code.
There's more on global JNDI names in our EJB FAQ :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
The alternative to annotations is to use an ejb-ref to declare the ejb dependency. The ejb-ref
is declared in the standard deployment descriptor corresponding to the component doing the
lookup. Each ejb-ref has an ejb-ref-name, e.g. <ejb-ref-name>DM_ref</ejb-ref-name>
The code looks up the ejb-ref-name relative to the java:comp/env namespace to retrieve the
EJB reference.
DocumentManager dm = (DocumentManager)
new InitialContext().lookup("java:comp/env/DM_ref");

Remote interface distribution

Hi,
I am just learning to use RMI, have a typical setup, Server and Client and everything works fine, BUT.......
I have compiled my remote classes, ie RmtServer, RmtServerImpl, then run the rmiregistry
and then started the service, so far so good.
I then compile etc the Client class and run
My question is this, I am currently working from the same directory for all classes, I would like to truly
distribute the client and server. Do I need to put a copy of the RmtServer interface on the client?
Currently in my client I have the line:
RmtServer server = (RmtServer)Naming.lookup("rmi://" + serverHost + "/ProjectServer");
I have been reading about dynamic class loading but I am slightly confused!!!
It says that the stubs created by running "rmic" on the server classes can be loaded dynamically, thats great, but the stubs created and the RmtServer interface are not the same thing. If I have to have a "local" copy of every interface I want to use then it seems a bit limited.
My impression was that I could specify a location for a class repositry on a remote machine and then
instantiate classes from the server on the local machine! So then I would only need to have one interface on the client to enable me to connect to the server for the first time!!!
Im really confused as people can probably tell. Any help would be really appreciated

The purpose of dynamic loading is really so that you don't have to distribute the stub, or the implementation classes of any interfaces.
You can certainly load the remote interface dynamically from the codebase in the client, e.g. with URLClassLoader, but you will also have to have already loaded all the classes that use the remote interface the same way, rather than via the system class loader. Otherwise they won't load (NoClassDefFoundError). You can download the entire client actually, and this is not a bad way to go: see the the RMI 1.1 Specification, 'Bootstrapping the client', for details (if you can find it: try http://java.sun.com/products/archive/jdk/1.1/index.html), and the RMI-USERS archives of about five-six years ago for discussions (see http://archives.java.sun.com/archives/rmi-users.html). The description of this was removed from the 1.2 specification for some reason, and I did encounter problems migrating a 1.1 bootstrap client to 1.2, so beware.

Remote Interface problem using Sun ONE App & web server

HI,
1) I am using an S'less SB. I have local & remote interfaces. I am using the sun one appserver7 & the sun ones's htttp server. By default it doesnt pick up the remote interfaces is it ? How do i make my remote interfaces work ? what are the changes required in config/xml ?
2) However i changed my client code (i.e my action class which is called by the struts action servlet ) to access the localhome rather than the remote home, but then i get java.lang.classcastexception.
pls help !
sanjay

Hi parsuram,
Thanks for the tip. After looking at the sample source code, I did finally figure out the solution - so I'll post it in case anyone else happens to be working with websphere studio has the same issue deploying on sun one.
To access local interface ejb, you must have the following
1. ejb-local-ref tag in the ejb-jar.xml like so underneath the <session> or <entity> tag of the bean which you plan to access the local ejb with.
<ejb-local-ref>
<ejb-ref-name>TestL</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>memory.simple.TestLLocalHome</local-home>
<local>memory.tool.simple.TestLLocal</local>
<ejb-link>TestL</ejb-link>
</ejb-local-ref>
2. similar ejb-ref tag in sun-ejb-jar.xml
<ejb-ref>
<ejb-ref-name>TestL</ejb-ref-name>
<jndi-name>localejbs/module_memory.betaEJB/TestL68640023372300293</jndi-name>
</ejb-ref>
note: sun generates the <jndi-name> and overwrites whatever you put in that tag no matter what you put in there.
3. here is the code to access
Context initial = new InitialContext();
TestLLocalHome tlHome=(TestLLocalHome) Initial.lookup
("TestL");
//the string must match <ejb-ref-name> underneath <ejb-local-ref>
4. note that the jndi name for the local interface bean becomes irrelevant. only the <ejb-ref-name> in the ejb-jar and sun-ejb-jar matter. furthermore, both <ejb-ref-name> must be the same or you won't be able to deploy.
5. This is completely my fault for not checking the "proper" way to access local interfaces. in websphere, they let you get away without the ejb-ref tags and just use the string "local:/TestL"!
-matt

TraderService Remote Interface

Why is the TraderService back end stateless session EJB implemented with remote
interfaces instead of local interfaces. If I'm not mistaken, upon reaching this
service, all processing will be co-located on one server, therefore, wouldn't
it be more performant to implement this EJB with local interfaces?

Hello,
The examples are simply starting points to assist your own development
work.
You might want to take a look at the web service design guide [1] in the
docs. If you are deploying to a cluster of WebLogic Server instances,
by default the deployment targets all server instances in the cluster.
This corresponds to homogenous module deployment, which is recommended
in most clusters. See [2].
Regards,
Bruce
[1]
http://edocs.bea.com/wls/docs81/webserv/design.html
[2]
http://edocs.bea.com/wls/docs81/deployment/overview.html
Sean Cohan wrote:
>
Why is the TraderService back end stateless session EJB implemented with remote
interfaces instead of local interfaces. If I'm not mistaken, upon reaching this
service, all processing will be co-located on one server, therefore, wouldn't
it be more performant to implement this EJB with local interfaces?

How to lookup the remote interface in JNDI of the cluster (glassfish)

I have write a simple sessionbean:
package authority;
import javax.ejb.Stateless;
* Session Bean implementation class LoginSessionBean
@Stateless
public class LoginSessionBean implements LoginSessionBeanRemote, LoginSessionBeanLocal {
     * Default constructor.
    public LoginSessionBean() {
        // TODO Auto-generated constructor stub
    @Override
    public boolean login(String name, String password)
        boolean result = false;
        System.out.println("User: " + name + " is login with password: " + password);
        return result;
    @Override
    public LoginSessionBeanRemote create()
        // TODO Auto-generated method stub
        return this;
}And I write a simple client to test it.
package test;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.rmi.PortableRemoteObject;
import authority.LoginSessionBean;
import authority.LoginSessionBeanRemote;
public class SessionBeanTestClient
    public static void main(String[] args)
        try
            InitialContext context = new InitialContext();
            Object obj = context.lookup(LoginSessionBean.class.getName());
            LoginSessionBeanRemote loginService = (LoginSessionBeanRemote)PortableRemoteObject.narrow(obj, LoginSessionBeanRemote.class);
            loginService.login("Jason", "password");
        catch (NamingException e)
            // TODO Auto-generated catch block
            e.printStackTrace();
}And it is OK, but after I deploy the sessionbean into a cluster with two instances on local host, it can not find the remote interface:
javax.naming.NameNotFoundException: authority.LoginSessionBean not found
     at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)Is it different for cluster (for IIOP port?), I want to test the HA solution, how could I start it?

Please look at http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-how-to.html. There is a How-To on local interface.
thanks
Debu

SRP521W - Local and Remote Traffic Cannot be the Same Subnet Address

I support an existing VPN infrastructure with PIX, Juniper NS5GT, and Netopia devices used as VPN endpoints. In all cases, I can create a VPN where the location's internal subnet, 10.x.y.0/24 sends traffic to 10.0.0.0/8 out the VPN tunnel. In the case of this 521W that we are evaluating, it appears that I cannot do this. Insteadm when creating the IPSEC policy I get this error "Local and Remote Traffic Cannot be the Same Subnet Address." Which, while strictly true, has never been an issue with all the above devices. Is there a workaround or other methodology to support this?
Thanks.

We have extactly the same problem with the SRP527W. Other Cisco small business products work like.
Cisco RV 120W
http://www.cisco.com/en/US/products/ps10852/index.html
Cisco WRV210
http://www.cisco.com/en/US/products/ps9929/index.html
We need a device with that supports one IPSec VPN and one ADSL interface and is easy to use like these devices.

What is @Local and @Remote

I use to think that @Local interfaces are those interfaces that could be called within the same app server JVM and @Remote calls are inter-JVM calls.
I have a code that doesn't support this. I write my ejb module and deployed it under ejb module of SUn application server. I also wrote a web application module deployed under web application module of the same server but because I did not specify any @Remote interface, the web application will not deploy becuase of a null ejb-ref problem.
When I added the @Remote Interface, it work.
This just conflicts my understanding of @Remote and @Local.
Can anyone throw light on this.
Regards.
Michael

to clarify issues on this --
I just completed another test on both @Local and @Remote - all in the same JVM
@Remote
works fine
@Local
*exception*
javax.servlet.ServletException: com.login.service.LoginService#com.login.service.LoginService not found
*root cause*
javax.naming.NameNotFoundException: com.login.service.LoginService#com.login.service.LoginService not found the exception message is from the web page while the server log says
[#|2008-02-21T00:17:30.332-0800|WARNING|sun-appserver-pe9.0|javax.enterprise.resource.webcontainer.jsf.lifecycle|_ThreadID=20;_ThreadName=httpWorkerThread-8085-0;_RequestID=b04cb6db-8a16-463e-ba4f-f2a8aed4d9c7;|executePhase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@57737a) threw exception
javax.faces.FacesException: javax.faces.FacesException: com.sun.enterprise.InjectionException: Exception attempting to inject Unresolved Ejb-Ref com.login.web.LoginBean/loginService@jndi: com.login.service.LoginService@[email protected]@Session@null into class com.login.web.LoginBean
     at com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:521)
     at com.sun.faces.el.ManagedBeanELResolver.getValue(ManagedBeanELResolver.java:82)
     at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143)
     at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:62)
     at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:65)
     at com.sun.el.parser.AstValue.getValue(AstValue.java:106)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: javax.faces.FacesException: com.sun.enterprise.InjectionException: Exception attempting to inject Unresolved Ejb-Ref com.login.web.LoginBean/loginService@jndi: com.login.service.LoginService@[email protected]@Session@null into class com.login.web.LoginBean
     at com.sun.faces.config.ManagedBeanFactoryImpl.newInstance(ManagedBeanFactoryImpl.java:325)
     at com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:510)
     ... 55 more
Caused by: com.sun.enterprise.InjectionException: Exception attempting to inject Unresolved Ejb-Ref com.login.web.LoginBean/loginService@jndi: com.login.service.LoginService@[email protected]@Session@null into class com.login.web.LoginBean
     at com.sun.enterprise.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:373)
     at com.sun.enterprise.util.InjectionManagerImpl.inject(InjectionManagerImpl.java:193)
     at com.sun.enterprise.util.InjectionManagerImpl.injectInstance(InjectionManagerImpl.java:87)
     at com.sun.faces.vendor.GlassFishInjectionProvider.inject(GlassFishInjectionProvider.java:65)
     at com.sun.faces.config.ManagedBeanFactoryImpl.newInstance(ManagedBeanFactoryImpl.java:312)
     ... 56 more
Caused by: javax.naming.NameNotFoundException: com.login.service.LoginService#com.login.service.LoginService not found
     at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:203)
     at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:175)
     at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
     at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
     at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:833)
     at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:156)
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:307)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.sun.enterprise.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:274)
     ... 60 more
|#]
[#|2008-02-21T00:17:30.332-0800|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.container.web|_ThreadID=20;_ThreadName=httpWorkerThread-8085-0;_RequestID=b04cb6db-8a16-463e-ba4f-f2a8aed4d9c7;|StandardWrapperValve[Faces Servlet]: Servlet.service() for servlet Faces Servlet threw exception
javax.naming.NameNotFoundException: com.login.service.LoginService#com.login.service.LoginService not found
     at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:203)
     at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:175)
     at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
     at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
     at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:833)
     at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:156)
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:307)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.sun.enterprise.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:274)
     at com.sun.enterprise.util.InjectionManagerImpl.inject(InjectionManagerImpl.java:193)
     at com.sun.enterprise.util.InjectionManagerImpl.injectInstance(InjectionManagerImpl.java:87)so I am still confused as what @Local is.

Local versus remote interface

Similar Messages

Maybe you are looking for