wood burning stoves 2.0*
The moose likes JBoss/WildFly 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 Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
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?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: deployment problem
 
Similar Threads
Remote EJB deployment needs a Local Home Interface too?
DeploymentException encountered when trying to deploy an Enterprise Bean in WebSphere
WSAD access beans
problems with JNDI name lookup
Fallen at the first hurdle!