a workaround could be to use a java pojo, not a declared fact

From: "Edson Tirelli" <ed.tirelli@gmail.com>
To: "Rules Users List" <rules-users@lists.jboss.org>
Sent: Friday, September 7, 2012 3:43:04 PM
Subject: Re: [rules-users] Guvnor Declarative Model

Ouch, more than 255 fields? As of 5.4.x there is no workaround, the engine always tries to generate the constructor.

Can you please open a JIRA and we will fix this for the next release?

Thank you,

Edson

On Fri, Sep 7, 2012 at 9:05 AM, JP Chemali <jshemali@hotmail.com> wrote:

Hi guys,

I just stumbled into the same issue in 5.4.0.Final, I think this is caused
by https://issues.jboss.org/browse/JBRULES-2652
When declaring a type, a constructor with all fields as parameters is
generated automatically, but this causes in our case to hit a barrier of the
Java language because the generated constructor has more than 255 parameters

Anyone knows if this generation can be skipped (annotation or something
else), maybe a safeguard not to generate the constructor when the limit is
reached would be nice too?

--
View this message in context: http://drools.46999.n3.nabble.com/Guvnor-Declarative-Model-tp4019419p4019637.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users