This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
Hi there, is there any specific problem that you have, or any error messages you've seen? Moving this to the WebLogic forum since you're having problems with WLS 6... Also, thanks for joining JavaRanch, but could you just take a quick look at the naming policy and edit your profile accordingly. Thanks! Simon Bartender (moderator) of "J2EE and EJB" forum
PappuPager is not a valid name at all. Please re-register before your name gets blocked. As simon stated if you can state the error message you are getting that will be helpful.
Joined: Oct 01, 2002
When i do ejbc this is what i get. C:\project>java weblogic.ejbc cabin.jar Cabin1.jar <Oct 1, 1998 9:08:05 PM EDT> <Error> <EJB> <EJB Deployment: CabinEJB has a class com.titan.cabin.CabinBean which is in the classpath. This class should only be located in the ejb-jar file.> <Oct 1, 1998 9:08:05 PM EDT> <Error> <EJB> <EJB Deployment: CabinEJB has a class com.titan.cabin.CabinHomeRemote which is in the classpath. This class should only be located in the ejb-jar file.> <Oct 1, 1998 9:08:05 PM EDT> <Error> <EJB> <EJB Deployment: CabinEJB has a class com.titan.cabin.CabinRemote which is in the classpath. This class should only be located in the ejb-jar file.>
Joined: Jul 28, 2000
What I would recommend is that you check up your classpath. It looks like you already have the bean in the server classpath and this is causing the problem you are encountering. Check up you setenv.bat file or do a search "containing text" for your package structure com.titan.cabin in the c:\bea folder.
This message is usually just a warning, and should not cause a deployment failure. It means exactly what it says - you are deploying an ejb jar but the same classes are also in CLASSPATH. One reason this might be a problem is maybe the version in CLASSPATH is different and so the ejb would not work correctly. But usually, the only effect is that you will not be able to redeploy ("hot deploy") the bean because weblogic will be unable to replace classes when they are "anchored" in the system classpath.