-
1. Re: Query method not found:
triathlon98 Jun 9, 2004 6:54 PM (in response to caesarkim)Open the server.log file (in the log directory, at the same level as your deploy directoy), and look for the "error" messages which are logged from the top down. This should give you the right clues.
Joachim -
2. Re: Query method not found:
millerm1 Jun 10, 2004 11:04 AM (in response to caesarkim)Are the two methods:
and here is my local object.
public MainProjectLocal findByPrimaryKey(Integer pk)throws FinderException;
public Collection findByProjectNames(String project_name) throws FinderException;
on your loacl object like you said or did you mena on your local home object, because they need to be on the local home object.
Mark -
3. Re: Query method not found:
robdaemon Jun 10, 2004 6:38 PM (in response to caesarkim)I have the same problem in 3.2.4. My EAR would deploy (and work) great in 3.2.2, but now that I've upgraded to 3.2.4, I have this problem.
I've even tried copying an existing finder in that bean and renaming it, and I have the same results! -
4. Re: Query method not found:
darranl Jun 11, 2004 6:08 AM (in response to caesarkim)What are the earlier errors that you are getting?
-
5. Re: Query method not found:
mkotsbak Jul 15, 2004 5:25 AM (in response to caesarkim)I have the same problem with a .jar-file that deploys without any warnings or errors on jboss 3.0.8....
-
6. Re: Query method not found:
mkotsbak Jul 21, 2004 7:25 AM (in response to caesarkim)I've reported this as a bug to sourceforge project page, bug # 994547 (https://sourceforge.net/tracker/index.php?func=detail&aid=994547&group_id=22866&atid=376685)
Please continue discussing this issue there. -
7. Re: Query method not found:
mkotsbak Jul 21, 2004 1:00 PM (in response to caesarkim)FYI (see bug), this bug seems to be fixed in JBoss 3.2.5 :-)
-
8. Re: Query method not found:
mkotsbak Jul 21, 2004 1:29 PM (in response to caesarkim)Posted to the bug:
Actually, this cause of this problem seems to be duplicate, different classes deployed, and jboss using the wrong version of the class (outside the jar it is deploying).
It probably would work in 3.2.4 too if the old version of the classes were removed.