I don't believe that JBoss parses the EJB-QL if JBossQL is present, but I would not recommend putting invalid EJB-QL in the compliant ejb-jar.xml file. You should just leave the ejb-ql element empty, which will signify to the application deployer that this query requires non-complient ejb-ql (and will need to port it).
In my experience, developers just want to know what they are up against when porting an application. BTW how would your application be portable if you are using non-complient EJB-QL? -dain Patrick Golec wrote: > JBoss complains about the following finder EJB-QL query: > > SELECT DISTINCT OBJECT(o) FROM Customer o WHERE o.searchName LIKE ?1 > > I understand that JBoss doesn't accept the parameters in the LIKE > operator, so I have overridden it with the JBossQL (same query), which > is cool. > > However, I want to maintain the portability of the application, so I > would like to have both: EJB-QL in the ejb-jar.xml and JBossQL in the > jbosscmp-jdbc.xml. > > My question is: is there any way to turn off EJB-QL query parsing when > JBossQL query is present? So that the app deploys with the EJB-QL > unmodified? > > Thanks! > > ------- > > Patrick Golec > Software Architect > Arachne Prime Inc. > ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
