-
1. Re: what to do when EJBQL doesn't cut it.
ben2 Apr 17, 2003 10:59 PM (in response to ben2)Is switching to BMP my only option here?
-
2. Re: what to do when EJBQL doesn't cut it.
juhalindfors Apr 18, 2003 3:06 AM (in response to ben2)you can try JBossQL, declared SQL or just providing your own finder implementation within CMP bean as well, depending what it is that you need to do in SQL
-
3. Re: what to do when EJBQL doesn't cut it.
ben2 Apr 20, 2003 1:54 AM (in response to ben2)I need this to work on a variety of app servers so I would prefer not to use JBossQL, and it is my understanding that declared SQL has the same limitation.
Can you point me to a reference on implementing a custom finder for a CMP bean, and is this a JBoss thing or do all app servers support it?
Thanks,
Ben -
4. Re: what to do when EJBQL doesn't cut it.
juhalindfors Apr 20, 2003 3:49 AM (in response to ben2)All of the above are specific to JBoss.
EJBQL is really quite limited and I don't know how feasible it is to use it to build full scale applications. The only option (in J2EE) besides EJBQL is to revert back to BMP, which is not a very good option.
Quite frankly, I'd rather recommend you use the small additions that are provided by JBOSSQL and then if you actually need to port to another server, worry about converting your beans to BMP or to other app server specific query extensions. -
5. Re: what to do when EJBQL doesn't cut it.
ben2 Apr 24, 2003 3:33 PM (in response to ben2)So, back to my original question. What are the implications of hand writing some JDBC which looks up the primary keys and then doing a findByPK with that key? This would only be used for cases where EJBQL does not work.
I can't see any reason why this would be a problem with the container. -
6. Re: what to do when EJBQL doesn't cut it.
juhalindfors Apr 26, 2003 9:34 AM (in response to ben2)Shouldn't be a problem.