According to the spec, it looks like prim-key-class is required
in the deployment descriptor for entity beans, and primkey-field is
optional.  This sort of leaves one to wonder what to use for the class
name for a primitive - I guess the name of the primitive, but that's going
to be a beast if we try to load the class for it!  Anyway, we may have
some logic in there that assumes one or the other, but it looks like that
won't work.
        Perhaps we should validate ejb-jar.xml when we load a JAR?

Aaron


Reply via email to