The reason why drools-core is a single jar is because we inline
dependencies like ASM. We will inline MVEL in a week or so.
Mark
Shai Bentin wrote:
I saw you already put the fix in, however I think that within the
MvelDataProvider you have a "DroolsMVELFactory" which is also not serializable.
I'm working with MR2 and fixed it there, I wanted to add it to MR3 but I see it has
different code so I guess so other fixes were done there.
BTW. On earlier versions of drools I only needed the drools-core jar in runtime. Now it
seems I will also need to add the mvel jar as well. It was nice not having to care about
such dependencies.
Shai
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On
Behalf Of Mark Proctor
Sent: Thursday, June 14, 2007 9:34 PM
To: Rules Users List
Subject: Re: [rules-users] org.drools.base.dataproviders.MVELDataProvider not
Serializable
oops, I'll open a jira for this and fix in 4.0 now.
Mark
bentins wrote:
> When trying to serialize a Package I get the message that
> org.drools.base.dataproviders.MVELDataProvider is not serializable. I only
> get this problem when I have the "from" word inmy rules.
>
> Looking at the code is does seem that this class is not serializable, and
> also one of its including memebers.
>
>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users