IntelliJ Java IDE
The moose likes JBoss and the fly likes deployment problem Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Products » JBoss
Reply Bookmark "deployment problem" Watch "deployment problem" New topic
Author

deployment problem

Ankit Doshi
Ranch Hand

Joined: Dec 04, 2002
Posts: 222
Hello,

I am facing a strange problem while deploying my application on jboss 3.2.3. I have around 10 CMP entity beans and around 4 stateless session beans. Session beans are internally calling entity beans. So, to deploy the session bean, I will need classes of the home and remote interfaces of the entity beans in the server's classpath. To so this, I have created following structure :
I have created the classes folder, under the jboss home directory /usr/local/jboss323 and there I have copied the classes of the home & remote interfaces of the entity beans. I've added the /usr/local/jboss323/classes folder in jboss's classpath. Now, if I try to deploy the entity beans, it gives me the following error :

13:04:26,424 WARN [verifier] EJB spec violation: Bean : OperatorMst Section: 22.2 Warning: The bean provider must specify the fully-qualified name of the enterprise bean's remote home interface, if any, in the element.

Now, if I remove the classes folder from server's classpath and deploy again, it gets deployed correctly.

What is the problem in having the home/remote interfaces in the classpath this way?
 
 
subject: deployment problem
 
Threads others viewed
WSAD access beans
Remote EJB deployment needs a Local Home Interface too?
Fallen at the first hurdle!
problems with JNDI name lookup
DeploymentException encountered when trying to deploy an Enterprise Bean in WebSphere
MyEclipse, The Clear Choice

cast iron skillet 49er

more from paul wheaton's glorious empire of web junk: cast iron skillet diatomaceous earth rocket mass heater sepp holzer raised garden beds raising chickens lawn care CFL flea control missoula heat permaculture