• Post Reply Bookmark Topic Watch Topic
  • New Topic

Error deploying EJB - auto generated Entity class  RSS feed

 
Stefan Mohr
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi guys,

First time poster - have been looking for a good Java forum community and the atmosphere here seems great!

I've spent a couple days trying to deploy my application and have hit a wall. Here are the details:

The project is an Enterprise Application Project with an EJB project and a Web project.
I'm developing in MyEclipse 6.0.1-GA.
The project itself was originally built in NetBeans and Sun Java Application Server but I've finished migrating it to MyEclipse and jBoss (at least to the point where we're compiling) due to a myriad of issues.
The jBoss server is running locally (Windows XP box).

The DB connections are being handled through Persistence. Netbeans has a great wizard for generating Entity classes from a DB. On moving to MyEclipse, however, Netbeans' entities wouldn't compile at all, so I opted to run MyEclipse's wizard to build my entities. All went well and I finished refactoring the original Bean code to work with the new entities.

Now I'm at the point where I want to deploy and start building the Web project and jBoss is none too pleased with me.
(Mods: please move this post to the jBoss forum if you feel it's more appropriate there)

My deployment fails, ultimately with:


This facade class was auto generated by the MyEclipse wizard, but I did a refactor (rename only) to fix the terrible default names.

Here's a chopped copy of the code in AccountFacade.java:


I'm still quite new to Enterprise development so if there if something glaringly wrong here or my refactor may broken something in an XML config file, please point me the right way! I don't even know what the Facade classes are (nor did some searching provide me much in the way of a clear explanation) so this one really has me stumped.

Thanks for any advice!
 
Edvins Reisons
Ranch Hand
Posts: 364
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Stefan,
welcome to JavaRanch.

As the exception message says, the bean class has to implement an interface that its clients will call. There are examples that you may consult, for example from this JBoss tutorial.
 
Stefan Mohr
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Edvins!

Ugh, I think I had convinced myself that the wizard would have created the interfaces I would need as well - I'll create the interfaces and see how it goes!
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!