[
https://issues.apache.org/jira/browse/OFBIZ-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199868#comment-13199868
]
Jacques Le Roux commented on OFBIZ-4602:
----------------------------------------
I finally did not create an issue for JobManager.reloadCrashedJobs() where I
wanted to continue in the loop when a job has maxRetry set to 0.
I believe this case appears (mostly?) when you have multiples instances running
on the same DB. So I think it's better to handle this case using
unique.instanceId in general.properties.
The reason I made this choice is because I'm afraid that else we could prevent
to reload running (ie crashed) jobs and hence miss them completly.
Though I still wonder why I got those issues locally with demo instances
running on their own DBs...
> Null values are not synchronized in http mode
> ---------------------------------------------
>
> Key: OFBIZ-4602
> URL: https://issues.apache.org/jira/browse/OFBIZ-4602
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Release 4.0, Release 09.04, Release 09.04.01, Release
> 10.04, SVN trunk
> Environment: Using entity synchronization over HTTP (not RMI)
> Reporter: Patrick Antivackis
> Assignee: Jacques Le Roux
> Fix For: Release Branch 4.0, Release Branch 09.04, Release Branch
> 10.04, Release Branch 11.04, SVN trunk
>
> Attachments: patch-OFBIZ-4602.txt
>
>
> In order to send over http the values to create, store and remove, Ofbiz is
> Xml serializing the values. GenericValue xml serialization is managed in
> GenericEntity.makeXmlElement, unfortunately this method just don't serialized
> null valued fields.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
