File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes BEA/Weblogic and the fly likes Deployment problem Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Deployment problem" Watch "Deployment problem" New topic

Deployment problem

hash ramakrishnan

Joined: Jul 15, 2002
Posts: 1
I have a new bean that emulates the pattern of another bean in functionality. They both are stateless session beans. One deployed fine and the other just wont. I can see it in the deployment descriptor (generated by JBuilder6). When I try to do a lookup on the other I get:
javax.naming.NameNotFoundException: Unable to resolve FuelDailyLmtEditor. Resolved: '' Unresolved:'FuelDailyLmtEditor' ; remaining name ''
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(
at weblogic.rmi.internal.ProxyStub.invoke(
at $Proxy0.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(
at javax.naming.InitialContext.lookup(
at gptest.FuelDailyLmt.test(
at gptest.FuelDailyLmt.<init>(
at gptest.TestGP.main(
Exception in thread "main"

Could some one please give me some ideas to figure it out?
Michael Pearson
Ranch Hand

Joined: Mar 11, 2001
Posts: 351
hash, Welcome to JavaRanch.
Please change your name to comply with the naming policy to which you agreed when you registered.
You can change your name here:

You can also find the naming policy here:
Thank You!
Graham Thorpe
Ranch Hand

Joined: Mar 25, 2002
Posts: 265
u should create another directory at present current directory it should be valid direcory.then u can get the deployment
Simon Brown
sharp shooter, and author
Ranch Hand

Joined: May 10, 2000
Posts: 1913
Have you checked the JNDI name that you are looking the bean up against the JNDI name specified in the WebLogic-specific EJB deployment descriptor?
I agree. Here's the link:
subject: Deployment problem
It's not a secret anymore!