I'm not sure I understand your problem. The field is spelled wrong in the
hasIdentity() method? What about the regular value object? It should be
excactly the same there.

My guess if there's something wrong with the value objects, is that
there's a bug in xdoclet. The template for value objects is in the ejb
module of xdoclet, but I haven't made any changes to this..

Check out the XxBean class of your table, see if there's anything in there
that could lead to the error in the value object.

.eivind

On Tue, 27 May 2003 [EMAIL PROTECTED] wrote:

> Eivind,
> 
> OK, I have another issue.
> 
> in the light value objects, there's a method "hasIdentity()": it's got the 
> value of the boolean field it's checking spelled wrong (lowercase first 
> letter hard-coded) -- I have my own DbNameConverter, and my table names 
> don't get converted the way Middlegen might expect them to (because they 
> already look like Java class names and the stock DbNameConverter just 
> screws them up: APClientCode would become ApclientCode which messes up the 
> pneumonic and makes the classes too hard to find). It seems like whatever 
> generates the variable name in "hasIdentity()" doesn't use the same scheme 
> as the rest of the methods (the others which return the same field spell 
> it right).
> 
> Where can I find the code that generates this: it's in your customized 
> xdoclet-ejb-module, no? Is the source for that in CVS, or just the jar?
> 
> Dave



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
middlegen-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/middlegen-user

Reply via email to