On Friday, October 10, 2003, at 10:52 AM, Alexey Loubyansky wrote:
Jason Essington wrote:
On Thursday, October 9, 2003, at 01:03 PM, Alexey Loubyansky wrote:Jason Essington wrote:Is there some limit on the complexity of ejb's now, or is this just a growing pain on the way to a faster more efficient server (which the 3.2.2 rc's seem to be)?
I don't see anything immediately obvious about what I am doing different here than with my other entities. All of the others seem happy enough (not pitching exceptions).
The only thing I can think that may be causing a problem would be that this entity has 111 persistent fields 6 container managed relationships and 7 non-persistent fields. perhaps the sheer complexity of this entity is causing confusion in the CMP engine?
Yes, it is. Now, I know the reason. Thanks.
Yes, at the moment, the limit is 64 columns.
Kinda reminds me of a famous quote that went something like, "640k ought to be enough for anybody" :-)
If necessary I could possibly whittle this guy down a bit.
The necessity should be dictated by project's domain model and common sense.
Ya, this one kinda grew out of control.
I can't suggest anything, therefore, am working on the fix.
Thanks, I'll keep an eye out for it.
Sorry,
NP, it seems like a reasonable limit, some of us just have unreasonable apps :-/
Thanks
-jason
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
