From notifications-return-25475-archive-asf-public=cust-asf.ponee.io@ofbiz.apache.org Sat Apr 27 10:23:01 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id A0CCB180630 for ; Sat, 27 Apr 2019 12:23:01 +0200 (CEST) Received: (qmail 42668 invoked by uid 500); 27 Apr 2019 10:23:01 -0000 Mailing-List: contact notifications-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ofbiz.apache.org Delivered-To: mailing list notifications@ofbiz.apache.org Received: (qmail 42657 invoked by uid 99); 27 Apr 2019 10:23:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Apr 2019 10:23:01 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 54E6FE0331 for ; Sat, 27 Apr 2019 10:23:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1195025812 for ; Sat, 27 Apr 2019 10:23:00 +0000 (UTC) Date: Sat, 27 Apr 2019 10:23:00 +0000 (UTC) From: "Jayansh Shinde (JIRA)" To: notifications@ofbiz.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OFBIZ-10966?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayansh Shinde updated OFBIZ-10966: ----------------------------------- Description:=20 *Entity data import/export in JSON format* =C2=A0 Currently, we have support to import/export entity data in XML format. We a= re required to have support for JSON format which looks quite similar to XM= L support. We are summarizing how current data looks and how its done in cu= rrent system and proposing how it should be done. =C2=A0 Just an example the existing xml data may look like: {color:#008080}<{color}{color:#3f7f7f}Party{color} {color:#7f007f}partyId{c= olor}{color:#3c3c3c}=3D{color}{color:#2a00ff}_"_{color}{color:#2a00ff}_1234= 56_{color}{color:#2a00ff}_"_{color} {color:#7f007f}partyTypeId{color}{color= :#3c3c3c}=3D{color}{color:#2a00ff}_"PERSON"_{color} {color:#7f007f}statusId= {color}{color:#3c3c3c}=3D{color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{col= or:#008080}/>{color} same proposed JSON data will look like: =C2=A0 {color:#000000}_{=E2=80=9CParty=E2=80=9D: \{"partyId":"123456","partyTypeId= ":"PERSON","statusId":"PARTY_ENABLED=E2=80=9D}}_{color} =C2=A0 {color:#000000}*Proposal:*{color} _Services=C2=A0can be *entityImportJson* and *entityImportDirJson* for impo= rting json from screen and directory respectively. And *entityExportAllJson= * for exporting entity data in JSON, similar to existing services for xml.= =C2=A0{color:#000000}Our suggestion that Json data must be validated via a = json schema during upload.{color}{color:#000000}R{color}{color:#000000}efer= {color}{color:#000000}[https://json-schema.org/] {color}{color:#000000}for= more information on json schema.{color}_ was: *Entity data import/export in JSON format* =C2=A0 Currently, we have support to import/export entity data in XML format. We a= re required to have support for JSON format which looks quite similar to XM= L support. We are summarizing how current data looks and how its done in cu= rrent system and proposing how it should be done.=20 =C2=A0 Just an example the existing xml data may look like: {color:#008080}<{color}{color:#3f7f7f}Party{color} {color:#7f007f}partyId{c= olor}{color:#3c3c3c}=3D{color}{color:#2a00ff}_"_{color}{color:#2a00ff}_1234= 56_{color}{color:#2a00ff}_"_{color} {color:#7f007f}partyTypeId{color}{color= :#3c3c3c}=3D{color}{color:#2a00ff}_"PERSON"_{color} {color:#7f007f}statusId= {color}{color:#3c3c3c}=3D{color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{col= or:#008080}/>{color} same proposed JSON data will look like: =C2=A0 {color:#000000}_{=E2=80=9CParty=E2=80=9D: \{"partyId":"123456","partyTypeId= ":"PERSON","statusId":"PARTY_ENABLED=E2=80=9D}}_{color} =C2=A0 {color:#000000}_{color:#000000}*Proposal:*{color}_{color} {color:#000000}_{color:#000000}Services=C2=A0can be *entityImportJson* and = *entityImportDirJson* for importing json from screen and directory respecti= vely. And *entityExportAllJson* for exporting entity data in JSON, similar = to existing services for xml.=C2=A0{color}{color:#000000}Our suggestion tha= t Json data must be validated via a json schema during upload.{color}{color= :#000000}R{color}{color:#000000}efer {color}{color:#000000}[https://json-sc= hema.org/] {color}{color:#000000}for more information on json schema.{color= }_{color} > JSON entity data import and export utility > ------------------------------------------ > > Key: OFBIZ-10966 > URL: https://issues.apache.org/jira/browse/OFBIZ-10966 > Project: OFBiz > Issue Type: New Feature > Components: framework > Reporter: Jayansh Shinde > Priority: Minor > > *Entity data import/export in JSON format* > =C2=A0 > Currently, we have support to import/export entity data in XML format. We= are required to have support for JSON format which looks quite similar to = XML support. We are summarizing how current data looks and how its done in = current system and proposing how it should be done. > =C2=A0 > Just an example the existing xml data may look like: > {color:#008080}<{color}{color:#3f7f7f}Party{color} {color:#7f007f}partyId= {color}{color:#3c3c3c}=3D{color}{color:#2a00ff}_"_{color}{color:#2a00ff}_12= 3456_{color}{color:#2a00ff}_"_{color} {color:#7f007f}partyTypeId{color}{col= or:#3c3c3c}=3D{color}{color:#2a00ff}_"PERSON"_{color} {color:#7f007f}status= Id{color}{color:#3c3c3c}=3D{color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{c= olor:#008080}/>{color} > same proposed JSON data will look like: > =C2=A0 > {color:#000000}_{=E2=80=9CParty=E2=80=9D: \{"partyId":"123456","partyType= Id":"PERSON","statusId":"PARTY_ENABLED=E2=80=9D}}_{color} > =C2=A0 > {color:#000000}*Proposal:*{color} > _Services=C2=A0can be *entityImportJson* and *entityImportDirJson* for im= porting json from screen and directory respectively. And *entityExportAllJs= on* for exporting entity data in JSON, similar to existing services for xml= .=C2=A0{color:#000000}Our suggestion that Json data must be validated via a= json schema during upload.{color}{color:#000000}R{color}{color:#000000}efe= r {color}{color:#000000}[https://json-schema.org/] {color}{color:#000000}fo= r more information on json schema.{color}_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)