OK, I take it back, this problem is not solved.
Dain's CMP docs say that an empty <ejb-ql> element is all that's required for the ejb-jar.xml, and that the query in jboss-jdbc.xml will override that.
Well, I've got an empty <ejb-ql> element in the <query> element for the bean in ejb-jar.xml, I've got <dynamic-ql/> in jboss-jdbc.xml w/ the same signature as in ejb-jar.xml, but I'm still getting the spec warning.
Is the only solution to set StrictVerifier to "false"?
Dave
| [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED] 06/10/2003 10:19 AM
|
To: [EMAIL PROTECTED] cc: Subject: [JBoss-user] Getting rid of "spec violation" warning w/ finder w/ no EJB-QL |
Hi all,
I'm getting an EJB spec violation warning on deployment:
"2003-06-09 19:23:44,734 WARN [org.jboss.ejb.EJBDeployer.verifier] EJB spec violation:
Bean : MyBean
Method : public abstract Collection findDynamically(String, Object;) throws FinderException
Section: 10.5.6
Warning: Every finder method except findByPrimaryKey(key) must be associated with a query element in the deployment descriptor."
I'm using dynamic JBossQL in the query for findDynamically(), so I don't have an EBJ-QL query defined.
What is the correct way to use JBossQL w/ finder rather than EJB-QL. Should the finder not even be declared in ejb-jar.xml (the XDoclet docs say for @jboss.query to work, @ejb.finder MUST be defined as well).
Does one just set the verifier strictness for the EJBDeployer to false in jboss-service.xml?
Dave
