[rules-dev] Today's Eleusinian mystery: deserializing a package forchange set monitoring

[Wolfgang Laun]

On 17 June 2011 16:34, Joe White <Joe.White at recondotech.com> wrote:

> Not that it necessarily needs to be fixed but in 5.0.1 you could serialize
> a package just using a regular ObjectOutputStream.
>

No - the code was not writing anything to a file.



> Also the guy
>

Lisa!

-W


> on the user mailing list was getting an exception using the
> DroolsObjectOutputStream.****
>
> ** **
>
> *From:* rules-dev-bounces at lists.jboss.org [mailto:
> rules-dev-bounces at lists.jboss.org] *On Behalf Of *Wolfgang Laun
> *Sent:* Friday, June 17, 2011 2:54 AM
> *To:* Rules Dev List
> *Subject:* [rules-dev] Today's Eleusinian mystery: deserializing a package
> forchange set monitoring****
>
> ** **
>
> Serializing a compiled package seems a rational thing to do - after all,
> there is: <resource source="..." type="PKG" /> and it is recognized by the
> monitor.
>
> However, you can't simply serialize an
> org.drools.definition.KnowledgePackage as it is usually done by writing it
> to an ObjectOutputStream: deserialization in the KnowledgeAgent throws a CCE
> exception.  To make it work, you must use a DroolsObjectOutputStream, which
> is nothing but a rename of ObjectOutputStream. So I have use
> DroolsObjectOutputStream, but it is not part of the public API.
>
> -W****
>
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20110617/048b3da1/attachment.html