<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Edson applied the pull request and I tweaked it further.<br>
-this.strategyStore was missing from unmarshall, to make it reflect
the patch.<br>
-MarshallerProviderImpl.newMarshaller should not default to
serialized strategy, but instead pass a null strategy. Allowing it
to fallback to what's provided in the ksession/enviornment<br>
<br>
The behaviour now is that if no strategy is provided it will
fallback to what's in the ksession/environment, if one is provided
it will always use that for marshalling and unmarshalling. I updated
the javadocs on the factory class to reflect this.<br>
<br>
Mark<br>
<br>
On 21/04/2011 14:07, Laird Nelson wrote:
<blockquote
cite="mid:BANLkTinm10QtyhGaLJARAkXdChE_yBUFxQ@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Thu, Apr 21, 2011 at 1:56 AM, Wolfgang
Laun <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:wolfgang.laun@gmail.com">wolfgang.laun@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
It seems to me that an environment is not the best place for
an operation that<br>
could depend on the session and/or a client's request. It
could be used additionally,<br>
but not without the direct approach.<br>
</blockquote>
<div><br>
For the record I totally agree.<br>
<br>
Context, in case it helps: I am in the process of migrating
off of a heavily used stateless session bean that--right
now--creates StatefulKnowledgeSessions and serializes them to
the database in between calls. I've enabled equality checking
(vs. identity checking) in the knowledge base, but for some
reason after about 20 serialization/deserialization cycles the
app server runs out of memory.<br>
<br>
I am assuming that JBRULES-2048 is in play here; I was hoping
that by supplying my own marshalling strategy I could control
how the serialization/deserialization happens and avoid the
memory leak.<br>
<br>
Best,<br>
Laird <br>
</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rules-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>