Dain, >Are you trying to use an unknown primary key (java.lang.Object)? If you >are, it is not supported.
Is this really the case? I posted a message regarding this very feature, titled "incorrect SQL generated for findAll() on CMP bean", and I am interested in getting it to work. I just read the relevant parts of the J2EE and EJB 2.0 specs, and found no statement that this feature is optional. I found the following on the JBoss FAQ. >Is JBoss in compliance with the current EJB spec ? >Yes. JBoss is being continuously tested for compliance with the EJB 2.0 specification. Please resolve this discrepancy for me. Does JBoss meet the EJB 2.0 spec or not? If Unknown Primary Keys are not supported, it appears that the answer is "no". If you couls, please clarify this for me. - Matt -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Russell Sent: Thursday, June 06, 2002 11:18 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] CMP Generated SQL Problem Thanks for your response, dain, your comment prodded me to notice my own stupidity. I had managed to leave out the <primkey-field> in the ejb-jar.xml file. I would have expected that to have caused some type of deployment exception. What are the plans to support java.lang.Object primary key types as outlined in the spec.? (Not that I've actually come up with a use for it, just wondering) David >>> [EMAIL PROTECTED] 06/06/02 10:32AM >>> Are you trying to use an unknown primary key (java.lang.Object)? If you are, it is not supported. If you are not you have some funky configuration, and you will need to post a bug report (with only the simple entity and query). -dain David Russell wrote: > OK, so I'm a little impatient and posted this question in a longer form two days ago. Hopefully I won't annoy too many people by adding to the already significant deluge of mail associated with this list. > > Any thoughts on why the generated SQL for an EJB-QL query of the form: > > SELECT OBJECT(o) > FROM EgadGenomeBean AS o > > would end up generating SQL that looks like this: > > SELECT FROM EGAD.GENOME t0_o > > The missing "selected" columns cause a missing element exception when I actually try to use the finder method for this EJB. > > Thanks, > > David > > David P. Russell > Lead Technical Consultant > Idea Integration > [EMAIL PROTECTED] > [EMAIL PROTECTED] > (585) 249-2600 > (585) 273-7728 > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
