Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

error deploying portlet

 
lubna kausar
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hello i m getting the following error while deploying my portlet can you suggest me what can be wrong?


Build failed due to An exception occurred while running the command. The exception message is: Deployment Error -- Error while running ejbc -- Fatal Error from EJB Compiler -- -- Failed to load deployment descriptor for: ipsp-tiptAmc-ejb
[ipsp-deploy] cause: Error creating sun specific cmp-mappings xml graph
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dude, that's pretty clearly an EJB error?

What the heck are EJBs doing in your Portlet project?

My assumption is that you have an EAR that contains a web module (your portlet) and an EJB module(something else), and they're somehow getting deployed together.

A special process is run on EJBs to generate container specific bindings. That's what's kicking out the error. Can't see how that is portlet related.

Let me know!

-Cameron McKenzie
 
lubna kausar
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hey its my 1st project including ejb n portlet n all so obviously i would not b able to figure out the error!!!
i got that the error is related to cmp-mappings.xml or sun-ejb-jar.xml but could not get what exactly is the error!!!as cmp-mappings contains database related mappings only!!
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sorry, I didn't mean to come off as being curt or snide. Message posts can so lack the appropriate emotion.

I don't do JBoss development, so I can't speak to any packaging best practices in JBoss, but in WebSphere, I tend to develop and package EJB and Portlet applications separately. If there's no really compelling reason to have EJBs and a Portlet application in the same EAR, then I'd separate them and develop/troubleshoot them independently. This will help isolate problems from one another.

Good luck.

-Cameron
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic