rstacy@... wrote:
> Dirk,
>
> Thanks for the help. The following endpoint is what is the job being
> persisted:
>
> <quartz:inbound-endpoint jobName="pollModemServiceJob"
> cronExpression="${poll.modems.cron.expression}">
> <property key="method" value="findAll"/>
> <quartz:event-generator-job />
> </quartz:inbound-endpoint>
Where exactly does the serialization happen? This is the crucial info to
find out and then decide how to proceed from there.
> So far I have had to add Serialization to a number of classes. I am not
> sure why these classes are being persisted to be honest with you. I have
> had to Serialize DefaultMuleContext obviously, but I have also had to add
> Serialization to a number of ExpressionEvaluators such as
> org.mule.expression.MuleExpressionEvaluator. Why are these being persisted?
That's the root question. I would not go down the route adding
serialization until the persistence works. I'm pretty sure e.g. that if
you persist a MuleContext and it's de-seiralized somewhere else in the
cluster all kinds of havoc will happen.
-dirk
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
