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!
Uhm.. it seems that this proplem happens to each new class I migrate to ejb quartz job
so any solution will be highly appreciated :)
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.