Incorrect code generated by weblogic.appc

Question

Hi,
My application has an ejb module which has entities with some CMR relationships. One instance of which is an n-m bi-directional relationship between an entity with a java.lang.Long primary key, and an entity with a composite primary key of types java.lang.Long, java.lang.Integer and java.util.Locale.
At the command line I'm invoking weblogic.appc for the application. The deployment descriptors are validated as okay. However, the compilation is falling over on the above relation in that the appc generated java is incorrect. Looking at the generated source code I believe the generated class was intended to test that the join table for the relation existed. The compilation errors are all of the form:
[appc] Compiling EAR module 'core-ejb'
[VersionHelper] : Recompiling because no previous hashes found
[EJBCompiler] : Compliance Checker said bean was compliant
c:\weblogic-epix-compile\core-ejb\com\formicary\epix\module\content\ContentElement_fvoisg__WebLogic_CMP_RDBMS_contentDocuments_Set.java:291: setBytes(int,byte[]) in java.sql.PreparedStatement cannot be applied to (int,java.util.Locale)__WL_stmt.setBytes(2,((com.formicary.epix.module.content.ContentDocumentPK)__WL_pk2).language);
So the generated Weblogic class won't compile, since it's trying to apply language (a java.util.Locale object and part of the primary key as detailed above) to a byte[] argument field. Obviously java.sql.PreparedStatement doesn't have the capability to set a Locale field as an parameter to a SQL statement.
Is there any way to inform Weblogic to treat this field as a String parameter? Or a way to map custom classes to Strings for EJBs? (I already have the application successfully deployed on Orion server, where the field is persisted in a varchar field). If none of this is possible then I will have to change the ejb property to a String rather than continue to use a Locale. Is there a reason why I shouldn't be using a Locale object as a primary key involved in a relation?
Any thoughts, ideas or solutions would be greatly appreciated.
Many thanks,
Steven

Answer 1

The SQL is quite complex as there seems to be several multiple tables and inheritance involved, but the AND portion seems correct.
For any joins (1-1, 1-m, get/anyOf) the AND of the join criteria must be applied to the entire expression, this is correct. If you require OR semantics to include 1-1 being null or 1-m being empty you must use an outerjoin, getAllowingNull or anyOfAllowingNone. You seem to be correctly doing this for the 1-1, but not for the 1-m.
To outerjoin the 1-m to account for allowing an empty collection you must use the anyOfAllowingNone method in your expression.
i.e.
Expression isDefectScheduled = builder.anyOfAllowingNone("storyCards").getAllowingNull("iteration").notNull();
Now this is a very complex expression and model, so there may be other issues, but if you desire to allow an empty 1-m anyOfAllowingNone is this correct way to specify this.