I removed <primkey-field>key</primkey-field> from my deployment
descriptor. Now I get a java.lang.reflect.UndeclaredThrowableException,
and then the original exception.

I understand your concerns about compound primary keys. In this case I
really do need to identify each row by 3 separate fields.

You mention that is difficult to get the code right, as I'm
experiencing. Do you have a sample of one that works that I could model
my scenario after?

I'm perfectly willing to believe that this is a coding error or
deployment descriptor error on my part [that's always easier to fix then
to wait for a new release of the appserver :) ], but what's fishy is
that the first deployment works perfectly. When I restart jboss, it
works perfectly. It is only after subsequent hot deployments that
there's a problem, until of course I restart jboss again.

.peter

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]] On Behalf Of 
> Dain Sundstrom
> Sent: Thursday, June 27, 2002 8:58 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] [JBossCMP2.0] Compound Primary Keys 
> and CMR fields
> 
> 
> Dmitri Colebatch wrote:
> > I could be way off, but...
> >  
> > a)
> > <quote>
> >      <entity>
> >             <ejb-name>MyBean</ejb-name>
> >             <prim-key-class>....MyKey</prim-key-class>
> >             ...
> >             <cmp-field><field-name>key</field-name></cmp-field>
> >             <cmp-field><field-name>year</field-name></cmp-field>
> >             <cmp-field><field-name>month</field-name></cmp-field>
> >             <primkey-field>key</primkey-field>
> >            ...
> >      </entity>
> > </quote>
> >  
> > aren't prim-key-class and primkey-field mutually exclusive?  Could 
> > that
> > be upsetting something? 
> 
> If prim-key-class is not a primitive wrapper, you can't have 
> primkey-field.
> 
> > b) aren't the fields of a pk class suppose to be public?  
> or did that
> > change in ejb2?
> 
> Yes you are right, they must be public.
> 
> I had to look it up myself.  I strongly recommend you don't use a 
> compound primary key as it is very hard to code correctly, 
> and even if 
> you get it correct, the person who has to maintain it can 
> easily break 
> the code.
> 
> -- 
> xxxxxxxxxxxxxxxxxxxxxxxx
> Dain Sundstrom
> Chief Architect JBossCMP
> JBoss Group, LLC
> xxxxxxxxxxxxxxxxxxxxxxxx
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Bringing you mounds of caffeinated joy.
> http://thinkgeek.com/sf 
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED] 
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> 



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Caffeinated soap. No kidding.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to