[jira] [Commented] (OFBIZ-4602) Null values are not synchronized in http mode

["Jacques Le Roux (Commented) (JIRA)" <ji...@apache.org>]

    [ 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

        

Re: [jira] [Commented] (OFBIZ-4602) Null values are not synchronized in http mode

[Jacques Le Roux <ja...@les7arts.com>]

Thanks Paul,

But once again, please put directly your comments in the Jiras issues.
It's  much easier to follow the convo later than to have this, either in OFBiz dev ML, or as it seems you did in the nabble forum, 
which is actually nothing else than an "easier to use" duplicate of the OFBiz dev ML (I put quote because most of us actually prefer 
to use an email client which has much features, like folders filters, etc.

I put myself your comment in the Jira for this time (did already for another one) and will continue the convo there.

HTH

Jacques

From: "Paul Foxworthy" <pa...@cohsoft.com.au>
> Hi all,
>
> There is a canonical way from the XML standards to express that an XML
> element is null. Rather than reserving a special value for the data within
> the element, there's a special *attribute* xsi:nil. Schemas can define a
> corresponding nillable attribute to say it is possible for an element to use
> the xsi:nil attribute.
>
> Given the problems we've been having with this Jira issue, would using
> xsi:nil be a good idea? The only disadvantage I can see is that this
> solution only works when we are serializing and deserializing to and from
> XML. We would need to solve the problem all over again for other
> serialization formats.
>
> See http://www.w3.org/TR/xmlschema-0/#Nils and
> http://docstore.mik.ua/orelly/xml/schema/ch11_03.htm .
>
> Cheers
>
> Paul Foxworthy
>
> --
> View this message in context: 
> http://ofbiz.135035.n4.nabble.com/jira-Created-OFBIZ-4602-Null-values-are-not-synchronized-in-http-mode-tp4145573p4356519.html
> Sent from the OFBiz - Dev mailing list archive at Nabble.com. 

Re: [jira] [Commented] (OFBIZ-4602) Null values are not synchronized in http mode

[Paul Foxworthy <pa...@cohsoft.com.au>]

Hi all,

There is a canonical way from the XML standards to express that an XML
element is null. Rather than reserving a special value for the data within
the element, there's a special *attribute* xsi:nil. Schemas can define a
corresponding nillable attribute to say it is possible for an element to use
the xsi:nil attribute.

Given the problems we've been having with this Jira issue, would using
xsi:nil be a good idea? The only disadvantage I can see is that this
solution only works when we are serializing and deserializing to and from
XML. We would need to solve the problem all over again for other
serialization formats.

See http://www.w3.org/TR/xmlschema-0/#Nils and
http://docstore.mik.ua/orelly/xml/schema/ch11_03.htm .

Cheers

Paul Foxworthy

--
View this message in context: http://ofbiz.135035.n4.nabble.com/jira-Created-OFBIZ-4602-Null-values-are-not-synchronized-in-http-mode-tp4145573p4356519.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.