Issue deploying ejb

[naov]

Hi, Im working with Eclipse and JBOSS 4.2.2GA.

I have a Quartz job class that is a MessageDrivenBean, I once deployed a VERY similar class with no problems, but now, when I try to deploy this one, i get the following errors:

WARN [verifier] EJB spec violation:
Bean : MyJob
Section: 15.7.2
Warning: A message driven bean must implement, directly or indirectly, the javax.ejb.MessageDrivenBean interface.

11:12:19,834 WARN [verifier] EJB spec violation:
Bean : MyJob
Section: 15.7.3
Warning: The message driven bean must declare one ejbCreate() method.

11:12:19,834 WARN [verifier] EJB spec violation:
Bean : MyJob
Section: 15.7.5
Warning: The message driven bean must declare one ejbRemove() method.

The class is like this:

public class MyJob implements Job, MessageDrivenBean, MessageListener {

// Business Methods


 public void ejbRemove() throws EJBException {
 }



 public void setMessageDrivenContext(MessageDrivenContext context) throws EJBException {
 }


 public void onMessage(Message message) {
 }


 public void ejbCreate() {
 System.out.println("Quartz Job created");
 }

}

The issue is, first I forgot to add the methods so the violations appeared, but then I added the methods and still there was the violation message. I tried erasing the Temp and Work folders, the output classes so they recompile again, and also cleaned the project but the error still happens.

I'm sure it is not a jboss config problem, or that it has not to do with the ejb-jar.xml or jboss.xml because I still have this other jar in which the class is almost the same (just a previous version) and it continues to deploy correctly. [the jars only contain the class, both xmls and manifest file]


I think it has something to do with cache or something like that but I don't know elsewhere to look.

any ideas? :(

thanks in advance
best regards

[naov]

Well... Whenever someone has the answer that will be usefull

In the meanwhile I just changed the package name (that in fact I needed to change to a more appropiate name), and with that it worked now :)


That's just a clear note that it's a temp file issue


anyways, thank you!

[naov]

Hello

Uhm.. it seems that this proplem happens to each new class I migrate to ejb quartz job

so any solution will be highly appreciated :)

[naov]

Solved!

Well it was not really a temp issue, it was a business jar that also had that class in it, but was not actualized.

As this jar was in lib folder, this class had precedence. The jar in fact doesn't have to have that class in it hah.


Thank you anyways, this is so human error but may be of help to someone.