[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997875#comment-16997875
]
Jayansh Shinde edited comment on OFBIZ-10966 at 12/17/19 6:13 AM:
--
Hi Mathieu, I tried the test cases this weekend and they worked without any
issue. As you suggested earlier, I will try replacing reflection code by next
weekend.
was (Author: jayansh):
Hi Mathieu, I tried the test cases this weekend and they worked without an
issue. As per your suggestion, I will replace reflection code and will provide
new patch.
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch, OFBiz-10966.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997875#comment-16997875
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Mathieu, I tried the test cases this weekend and they worked without an
issue. As per your suggestion, I will replace reflection code and will provide
new patch.
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch, OFBiz-10966.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16991144#comment-16991144
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Mathieu,
I will check it by this week-end and will try to update it.
Meanwhile I find I am not able to reply from email, I replied earlier as well
but it was bounced. Well from next time will comment directly here.
Thanks,
Jayansh
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch, OFBiz-10966.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: OFBiz-10966.patch
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch, OFBiz-10966.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: (was: OFBiz-10966.patch)
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch, OFBiz-10966.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918369#comment-16918369
]
Jayansh Shinde edited comment on OFBIZ-10966 at 8/29/19 9:33 AM:
-
Hi Mathieu,
Please review patch I uploaded.
In this patch:[^OFBiz-10966.patch]
Simplified source code for easy understanding.
Added test cases as requested.
Added missing java doc.
Please let me know if you see anything missing.
Thanks,
Jay
was (Author: jayansh):
Hi Mathieu,
Please review patch I uploaded.
In this patch:
Simplified source code for easy understanding.
Added test cases as requested.
Added missing java doc.
Please let me know if you see anything missing.
Thanks,
Jay
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch, OFBiz-10966.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918369#comment-16918369
]
Jayansh Shinde edited comment on OFBIZ-10966 at 8/29/19 9:32 AM:
-
Hi Mathieu,
Please review patch I uploaded.
In this
patch:https://issues.apache.org/jira/secure/attachment/12978859/OFBiz-10966.patch
Simplified source code for easy understanding.
Added test cases as requested.
Added missing java doc.
Please let me know if you see anything missing.
Thanks,
Jay
was (Author: jayansh):
Hi Mathieu,
Please review patch I uploaded.
In this patch:
Simplified source code for easy understanding.
Added test cases as requested.
Added missing java doc.
Please let me know if you see anything missing.
Thanks,
Jay
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-10966.patch, OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918369#comment-16918369
]
Jayansh Shinde edited comment on OFBIZ-10966 at 8/29/19 9:32 AM:
-
Hi Mathieu,
Please review patch I uploaded.
In this patch:
Simplified source code for easy understanding.
Added test cases as requested.
Added missing java doc.
Please let me know if you see anything missing.
Thanks,
Jay
was (Author: jayansh):
Hi Mathieu,
Please review patch I uploaded.
In this
patch:https://issues.apache.org/jira/secure/attachment/12978859/OFBiz-10966.patch
Simplified source code for easy understanding.
Added test cases as requested.
Added missing java doc.
Please let me know if you see anything missing.
Thanks,
Jay
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-10966.patch, OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918369#comment-16918369
]
Jayansh Shinde edited comment on OFBIZ-10966 at 8/29/19 7:57 AM:
-
Hi Mathieu,
Please review patch I uploaded.
In this patch:
Simplified source code for easy understanding.
Added test cases as requested.
Added missing java doc.
Please let me know if you see anything missing.
Thanks,
Jay
was (Author: jayansh):
Hi Mathieu,
Please review patch I uploaded.
In this patch:
Supplified source code for easy understanding.
Added test cases as requested.
Added missing java doc.
Please let me know if you see anything missing.
Thanks,
Jay
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-10966.patch, OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: OFBiz-10966.patch
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-10966.patch, OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: OFBiz-10966.patch
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-10966.patch, OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913887#comment-16913887
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Pierre, Thank you very much for your inputs, this is blessings of community,
we have wonderful software as a result, as we keep enhancing things. I will
definitely going to fix this once we are done with backend, we will do it as
separate task.
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911436#comment-16911436
]
Jayansh Shinde edited comment on OFBIZ-10966 at 8/22/19 9:10 AM:
-
Hi, I will start soon on pending things, and will try to provide you necessary
stuff by this month end.
was (Author: jayansh):
Hi Matheiu, I will start back on same, and will try to provide you necessary
stuff by this weekend.
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911436#comment-16911436
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Matheiu, I will start back on same, and will try to provide you necessary
stuff by this weekend.
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905387#comment-16905387
]
Jayansh Shinde commented on OFBIZ-10966:
Yes no problem. Go ahead and revert...
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905094#comment-16905094
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Mathieu,
I will pick it and complete it, asap. I am currently occupied with so many
high priority production tasks, thus not able to check it.
Thanks,
Jay
On Mon, Aug 12, 2019 at 3:27 PM Mathieu Lirzin (JIRA)
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884838#comment-16884838
]
Jayansh Shinde commented on OFBIZ-10966:
Yes sure, I will fix it as per you suggestion!!!
Thanks,
Jayansh
Sahaja Yoga The Ultimate Yoga
www.sahajayoga.org
On Sat, Jul 13, 2019 at 8:52 PM Mathieu Lirzin (JIRA)
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: OFBIZ-10966.patch
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884340#comment-16884340
]
Jayansh Shinde commented on OFBIZ-10966:
I am almost done, except few more testing, enclosing patch, but its not
ready!![^OFBIZ-10966.patch]
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884295#comment-16884295
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Mathieu,
I have made some progress, hopefully this will be ready soon. Meanwhile I
noticed that this is assigned to you, hope it doesn't matter.
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879805#comment-16879805
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Mathieu,
I already started this, but I got something more urgent, thus was not able
to finish it. Please allow me some more time, I will be back with a patch.
Thanks,
Jay
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874851#comment-16874851
]
Jayansh Shinde edited comment on OFBIZ-10966 at 6/28/19 11:48 AM:
--
Hi Jacques/Mathieu,
Thank you for pointing this out, I will change it to jackson, and remove
the dependency. This is a mistake, as library is there already I should have
implemented same. This is what we practice, but don't know how I missed it.
was (Author: jayansh):
Hi Jacques/Mathieu,
Thank you for pointing this out, I will change it to jackson, and remove
the dependency. I will keep posted.
On Fri, Jun 28, 2019 at 3:00 PM Jacques Le Roux (JIRA)
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874851#comment-16874851
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Jacques/Mathieu,
Thank you for pointing this out, I will change it to jackson, and remove
the dependency. I will keep posted.
On Fri, Jun 28, 2019 at 3:00 PM Jacques Le Roux (JIRA)
> 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
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-11125) No proper error message displayed if user misses to select entities
[ https://issues.apache.org/jira/browse/OFBIZ-11125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874059#comment-16874059 ] Jayansh Shinde commented on OFBIZ-11125: Thanks again Jacques!!! On Thu, Jun 27, 2019 at 5:35 PM Jacques Le Roux (JIRA) > No proper error message displayed if user misses to select entities > > > Key: OFBIZ-11125 > URL: https://issues.apache.org/jira/browse/OFBIZ-11125 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Reporter: Jayansh Shinde >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 16.11.06, 18.12.01 > > Attachments: OFBiz-11125.patch, > OFBiz-Web-Tools-XML-Data-Export_no_proper_error_msg.png > > > No Proper error message is displayed if user misses to select entities from > the list, and throw error message as shown in attached image -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874056#comment-16874056
]
Jayansh Shinde commented on OFBIZ-10966:
Thanks Jacques, will take care of it...
Thanks,
Jayansh
On Thu, Jun 27, 2019 at 5:32 PM Jacques Le Roux (JIRA)
> 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
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874053#comment-16874053
]
Jayansh Shinde commented on OFBIZ-10966:
Thank you very much Jacques, for fixing issues and putting patch in trunk.
> 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
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-11125) No proper error message displayed if user misses to select entities
[ https://issues.apache.org/jira/browse/OFBIZ-11125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873829#comment-16873829 ] Jayansh Shinde edited comment on OFBIZ-11125 at 6/27/19 5:29 AM: - Patch is enclosed here to resolve this error [^OFBiz-11125.patch]. was (Author: jayansh): Patch is enclosed here to resolve this error.[^OFBiz-11125.patch] > No proper error message displayed if user misses to select entities > > > Key: OFBIZ-11125 > URL: https://issues.apache.org/jira/browse/OFBIZ-11125 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Reporter: Jayansh Shinde >Assignee: Jayansh Shinde >Priority: Major > Attachments: OFBiz-11125.patch, > OFBiz-Web-Tools-XML-Data-Export_no_proper_error_msg.png > > > No Proper error message is displayed if user misses to select entities from > the list, and throw error message as shown in attached image -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-11125) No proper error message displayed if user misses to select entities
[ https://issues.apache.org/jira/browse/OFBIZ-11125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayansh Shinde updated OFBIZ-11125: --- Attachment: OFBiz-11125.patch > No proper error message displayed if user misses to select entities > > > Key: OFBIZ-11125 > URL: https://issues.apache.org/jira/browse/OFBIZ-11125 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Reporter: Jayansh Shinde >Assignee: Jayansh Shinde >Priority: Major > Attachments: OFBiz-11125.patch, > OFBiz-Web-Tools-XML-Data-Export_no_proper_error_msg.png > > > No Proper error message is displayed if user misses to select entities from > the list, and throw error message as shown in attached image -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-11125) No proper error message displayed if user misses to select entities
[ https://issues.apache.org/jira/browse/OFBIZ-11125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873829#comment-16873829 ] Jayansh Shinde commented on OFBIZ-11125: Patch is enclosed here to resolve this error.[^OFBiz-11125.patch] > No proper error message displayed if user misses to select entities > > > Key: OFBIZ-11125 > URL: https://issues.apache.org/jira/browse/OFBIZ-11125 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Reporter: Jayansh Shinde >Assignee: Jayansh Shinde >Priority: Major > Attachments: OFBiz-11125.patch, > OFBiz-Web-Tools-XML-Data-Export_no_proper_error_msg.png > > > No Proper error message is displayed if user misses to select entities from > the list, and throw error message as shown in attached image -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OFBIZ-11125) No proper error message displayed if user misses to select entities
[ https://issues.apache.org/jira/browse/OFBIZ-11125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayansh Shinde reassigned OFBIZ-11125: -- Assignee: Jayansh Shinde > No proper error message displayed if user misses to select entities > > > Key: OFBIZ-11125 > URL: https://issues.apache.org/jira/browse/OFBIZ-11125 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Reporter: Jayansh Shinde >Assignee: Jayansh Shinde >Priority: Major > Attachments: OFBiz-Web-Tools-XML-Data-Export_no_proper_error_msg.png > > > No Proper error message is displayed if user misses to select entities from > the list, and throw error message as shown in attached image -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873821#comment-16873821
]
Jayansh Shinde commented on OFBIZ-10966:
All known issues has been resolved. Thus I am attaching new patch for same.
[^OFBIZ-10966_27062019.patch]
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: (was: OFBIZ-10966_24062019.patch)
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: OFBIZ-10966_27062019.patch
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: (was: OFBIZ-10966.patch)
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966_27062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-11124) Allow to create single file if both directory and filename is provided by user
[
https://issues.apache.org/jira/browse/OFBIZ-11124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872199#comment-16872199
]
Jayansh Shinde commented on OFBIZ-11124:
Hi Jacques,
I also had attached a patch, when I created this issue, this is similar we do
in JSON, please have a look.
Thanks,
Jay
> Allow to create single file if both directory and filename is provided by user
> --
>
> Key: OFBIZ-11124
> URL: https://issues.apache.org/jira/browse/OFBIZ-11124
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/webtools
>Reporter: Jayansh Shinde
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: OFBIZ-11124.patch,
> OFBiz-Web-Tools-XML-Data-Export_BothFilenameAndDir.png
>
>
> As reported by Jacques
> "Actually the path is missing in line 191 (same for XML, line 190) for
> Windows to work:
> {{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
> FileOutputStream(outpath + "/" + filename), "UTF-8")))}}
> I also think it should be used for *nix OS, else the file is always written
> at OFBiz root"
>
> If user provided file name and output directory in that case the entity xml
> files are generated at both locations.
> As in attached image we have files created at both locations, i.e. at root we
> have test.xml and in user provided output directory we have multiple files
> with _[entityname]_.xml.
> The expected change would be if user provided both output directory and
> filename then file should be created in given directory with given filename.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-11124) Allow to create single file if both directory and filename is provided by user
[
https://issues.apache.org/jira/browse/OFBIZ-11124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-11124:
---
Attachment: OFBIZ-11124.patch
> Allow to create single file if both directory and filename is provided by user
> --
>
> Key: OFBIZ-11124
> URL: https://issues.apache.org/jira/browse/OFBIZ-11124
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/webtools
>Reporter: Jayansh Shinde
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-11124.patch,
> OFBiz-Web-Tools-XML-Data-Export_BothFilenameAndDir.png
>
>
> As reported by Jacques
> "Actually the path is missing in line 191 (same for XML, line 190) for
> Windows to work:
> {{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
> FileOutputStream(outpath + "/" + filename), "UTF-8")))}}
> I also think it should be used for *nix OS, else the file is always written
> at OFBiz root"
>
> If user provided file name and output directory in that case the entity xml
> files are generated at both locations.
> As in attached image we have files created at both locations, i.e. at root we
> have test.xml and in user provided output directory we have multiple files
> with _[entityname]_.xml.
> The expected change would be if user provided both output directory and
> filename then file should be created in given directory with given filename.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-11124) Allow to create single file if both directory and filename is provided by user
[
https://issues.apache.org/jira/browse/OFBIZ-11124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-11124:
---
Description:
As reported by Jacques
"Actually the path is missing in line 191 (same for XML, line 190) for Windows
to work:
{{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
FileOutputStream(outpath + "/" + filename), "UTF-8")))}}
I also think it should be used for *nix OS, else the file is always written at
OFBiz root"
If user provided file name and output directory in that case the entity xml
files are generated at both locations.
As in attached image we have files created at both locations, i.e. at root we
have test.xml and in user provided output directory we have multiple files with
_[entityname]_.xml.
The expected change would be if user provided both output directory and
filename then file should be created in given directory with given filename.
was:
As reported by Jacques
"Actually the path is missing in line 191 (same for XML, line 190) for Windows
to work:
{{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
FileOutputStream(outpath + "/" + filename), "UTF-8")))}}
I also think it should be used for *nix OS, else the file is always written at
OFBiz root"
If user provided file name and output directory in that case the entity xml
files are generated at both locations
!OFBiz-Web-Tools-XML-Data-Export_BothFilenameAndDir.png!
In this case we have files created at both locations, i.e. at root we have
test.xml and in user provided output directory we have multiple files with
_[entityname]_.xml.
The expected change would be if user provided both output directory and
filename then file should be created in given directory with given filename.
> Allow to create single file if both directory and filename is provided by user
> --
>
> Key: OFBIZ-11124
> URL: https://issues.apache.org/jira/browse/OFBIZ-11124
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/webtools
>Reporter: Jayansh Shinde
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBiz-Web-Tools-XML-Data-Export_BothFilenameAndDir.png
>
>
> As reported by Jacques
> "Actually the path is missing in line 191 (same for XML, line 190) for
> Windows to work:
> {{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
> FileOutputStream(outpath + "/" + filename), "UTF-8")))}}
> I also think it should be used for *nix OS, else the file is always written
> at OFBiz root"
>
> If user provided file name and output directory in that case the entity xml
> files are generated at both locations.
> As in attached image we have files created at both locations, i.e. at root we
> have test.xml and in user provided output directory we have multiple files
> with _[entityname]_.xml.
> The expected change would be if user provided both output directory and
> filename then file should be created in given directory with given filename.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-11125) No proper error message displayed if user misses to select entities
[ https://issues.apache.org/jira/browse/OFBIZ-11125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayansh Shinde updated OFBIZ-11125: --- Description: No Proper error message is displayed if user misses to select entities from the list, and throw error message as shown in attached image (was: No Proper error message is displayed if user misses to select entities from the list: !OFBiz-Web-Tools-XML-Data-Export_no_proper_error_msg.png!) > No proper error message displayed if user misses to select entities > > > Key: OFBIZ-11125 > URL: https://issues.apache.org/jira/browse/OFBIZ-11125 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Reporter: Jayansh Shinde >Priority: Major > Attachments: OFBiz-Web-Tools-XML-Data-Export_no_proper_error_msg.png > > > No Proper error message is displayed if user misses to select entities from > the list, and throw error message as shown in attached image -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871964#comment-16871964
]
Jayansh Shinde commented on OFBIZ-10966:
I found one more bug, created one more ticket here:
https://issues.apache.org/jira/browse/OFBIZ-11125
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_24062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OFBIZ-11125) No proper error message displayed if user misses to select entities
Jayansh Shinde created OFBIZ-11125: -- Summary: No proper error message displayed if user misses to select entities Key: OFBIZ-11125 URL: https://issues.apache.org/jira/browse/OFBIZ-11125 Project: OFBiz Issue Type: Bug Components: framework/webtools Reporter: Jayansh Shinde Attachments: OFBiz-Web-Tools-XML-Data-Export_no_proper_error_msg.png No Proper error message is displayed if user misses to select entities from the list: !OFBiz-Web-Tools-XML-Data-Export_no_proper_error_msg.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871963#comment-16871963
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Jacques
I created ticket for xml issue as per your suggestion. I have fixed same with
json, I will upload patch by this week for xml as well.
https://issues.apache.org/jira/browse/OFBIZ-11124
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_24062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-11124) Allow to create single file if both directory and filename is provided by user
[
https://issues.apache.org/jira/browse/OFBIZ-11124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-11124:
---
Description:
As reported by Jacques
"Actually the path is missing in line 191 (same for XML, line 190) for Windows
to work:
{{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
FileOutputStream(outpath + "/" + filename), "UTF-8")))}}
I also think it should be used for *nix OS, else the file is always written at
OFBiz root"
If user provided file name and output directory in that case the entity xml
files are generated at both locations
!OFBiz-Web-Tools-XML-Data-Export_BothFilenameAndDir.png!
In this case we have files created at both locations, i.e. at root we have
test.xml and in user provided output directory we have multiple files with
_[entityname]_.xml.
The expected change would be if user provided both output directory and
filename then file should be created in given directory with given filename.
was:
As reported by Jacques
"Actually the path is missing in line 191 (same for XML, line 190) for Windows
to work:
{{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
FileOutputStream(outpath + "/" + filename), "UTF-8")))}}
I also think it should be used for *nix OS, else the file is always written at
OFBiz root"
If user provided only file name and output directory in that case the entity
xml files are generated at both locations
!OFBiz-Web-Tools-XML-Data-Export_BothFilenameAndDir.png!
In this case we have files created at both locations, i.e. at root we have
test.xml and in user provided output directory we have multiple files with
_[entityname]_.xml.
The expected change would be if user provided both output directory and
filename then file should be created in given directory with given filename.
> Allow to create single file if both directory and filename is provided by user
> --
>
> Key: OFBIZ-11124
> URL: https://issues.apache.org/jira/browse/OFBIZ-11124
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/webtools
>Reporter: Jayansh Shinde
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBiz-Web-Tools-XML-Data-Export_BothFilenameAndDir.png
>
>
> As reported by Jacques
> "Actually the path is missing in line 191 (same for XML, line 190) for
> Windows to work:
> {{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
> FileOutputStream(outpath + "/" + filename), "UTF-8")))}}
> I also think it should be used for *nix OS, else the file is always written
> at OFBiz root"
>
> If user provided file name and output directory in that case the entity xml
> files are generated at both locations
> !OFBiz-Web-Tools-XML-Data-Export_BothFilenameAndDir.png!
>
>
> In this case we have files created at both locations, i.e. at root we have
> test.xml and in user provided output directory we have multiple files with
> _[entityname]_.xml.
> The expected change would be if user provided both output directory and
> filename then file should be created in given directory with given filename.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OFBIZ-11124) Allow to create single file if both directory and filename is provided by user
Jayansh Shinde created OFBIZ-11124:
--
Summary: Allow to create single file if both directory and
filename is provided by user
Key: OFBIZ-11124
URL: https://issues.apache.org/jira/browse/OFBIZ-11124
Project: OFBiz
Issue Type: Improvement
Components: framework/webtools
Reporter: Jayansh Shinde
Assignee: Jayansh Shinde
Attachments: OFBiz-Web-Tools-XML-Data-Export_BothFilenameAndDir.png
As reported by Jacques
"Actually the path is missing in line 191 (same for XML, line 190) for Windows
to work:
{{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
FileOutputStream(outpath + "/" + filename), "UTF-8")))}}
I also think it should be used for *nix OS, else the file is always written at
OFBiz root"
If user provided only file name and output directory in that case the entity
xml files are generated at both locations
!OFBiz-Web-Tools-XML-Data-Export_BothFilenameAndDir.png!
In this case we have files created at both locations, i.e. at root we have
test.xml and in user provided output directory we have multiple files with
_[entityname]_.xml.
The expected change would be if user provided both output directory and
filename then file should be created in given directory with given filename.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: (was: OFBIZ-10966_24062019.patch)
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_24062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: OFBIZ-10966_24062019.patch
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_24062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871209#comment-16871209
]
Jayansh Shinde edited comment on OFBIZ-10966 at 6/24/19 1:42 PM:
-
Hi Jacques,
I am attaching new patch, this includes Import from Directory and Export All
entities as well.
But there is know bug in parsing, I working on same. This is regarding
special/escape charters in JSON, entities like ElectronicText has html text and
it has character like new line, tab, quote etc, which are giving me issue
during import.
I also removed bigger image and put smaller one ;).
I will open new Jira ticket tomorrow.
Thanks again!!
[^OFBIZ-10966_24062019.patch]
was (Author: jayansh):
Hi Jacques,
I am attaching new patch, this also include Import from Directory and Export
All entities as well.
But there is know bug in parsing, I working on same. This is regarding
special/escape charters in JSON, entities like ElectronicText has html text and
it has character like new line, tab, quote etc, which are giving me issue
during import.
I also removed bigger image and put smaller one ;).
I will open new Jira ticket tomorrow.
Thanks again!!
[^OFBIZ-10966_24062019.patch]
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_24062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: OFBiz-Web-Tools-JSON-Data-Import-Dir.png
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_24062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png,
> OFBiz-Web-Tools-JSON-Data-Import-Dir.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: OFBiz-Web-Tools-JSON-Data-Export-All.png
exportJson.png
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_24062019.patch,
> OFBiz-Web-Tools-JSON-Data-Export-All.png, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: OFBIZ-10966_24062019.patch
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_24062019.patch,
> importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871209#comment-16871209
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Jacques,
I am attaching new patch, this also include Import from Directory and Export
All entities as well.
But there is know bug in parsing, I working on same. This is regarding
special/escape charters in JSON, entities like ElectronicText has html text and
it has character like new line, tab, quote etc, which are giving me issue
during import.
I also removed bigger image and put smaller one ;).
I will open new Jira ticket tomorrow.
Thanks again!!
[^OFBIZ-10966_24062019.patch]
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, OFBIZ-10966_24062019.patch,
> importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: (was: exportJson.png)
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870800#comment-16870800
]
Jayansh Shinde commented on OFBIZ-10966:
Agreed with you
_"Actually the path is missing in line 191 (same for XML, line 190) for Windows
to work:_
_{{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
FileOutputStream(outpath + "/" + filename), "UTF-8")))}}_
_I also think it should be used for *nix OS, else the file is always written at
OFBiz root"_
Currently we put full path in filename to get it work otherwise its created at
OFBiz root.
There may be one more bug, if you provide both Filename and out directory it
may be written at both locations :).
So here its summarise as:
_filename_ is name with _Output directory =_ generate it in Ouput directory
with given name.
_filename_ only: No change in current behaviour.
Let me know can I fix this in XML data export as well, or should create
separate ticket for same.
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870796#comment-16870796
]
Jayansh Shinde commented on OFBIZ-10966:
Agreed with you
_"Actually the path is missing in line 191 (same for XML, line 190) for Windows
to work:_
_{{writer = new PrintWriter(new BufferedWriter(new OutputStreamWriter(new
FileOutputStream(outpath + "/" + filename), "UTF-8")))}}_
_I also think it should be used for *nix OS, else the file is always written at
OFBiz root"_
Currently we put full path in filename to get it work otherwise its created at
OFBiz root.
I will put support for this:
_filename_ is name with _Output directory =_ generate it in Ouput directory
with given name.
Let me know can I fix this in XML data export as well, or should create
separate ticket for same.
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870752#comment-16870752
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Jacques,
This is my mistake, I should have uploaded screenshots, what's included in this
patch, currently we have only 2 pages Import Json and Export Json as we have
for xml, I will try to complete "JSON Data Export All" and "JSON Data Import
Dir" by this week. what else is missing, do you thing its worth adding "JSON
Data Import Readers".
I am on ubuntu, I will check this on windows today. There we can use
File.separator instead of "/" or "\\" to avoid platform specific issues.
!importJson.png!
!exportJson.png!
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: importJson.png
exportJson.png
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch, exportJson.png, importJson.png
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870569#comment-16870569
]
Jayansh Shinde commented on OFBIZ-10966:
Hi Jacques,
Thank you very much for review and trying this...I will check all issues
reported by you and upload new patch.
Thank you again!!!
On Sun, Jun 23, 2019, 2:10 PM Jacques Le Roux (JIRA)
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870213#comment-16870213
]
Jayansh Shinde commented on OFBIZ-10966:
I have attached a patch for same!!!
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Attachment: OFBIZ-10966.patch
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
> Attachments: OFBIZ-10966.patch
>
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde reassigned OFBIZ-10966:
--
Assignee: Jayansh Shinde
> 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
>Assignee: Jayansh Shinde
>Priority: Minor
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830289#comment-16830289
]
Jayansh Shinde edited comment on OFBIZ-10966 at 5/1/19 4:42 AM:
Thanks Nicolas!
I think just adding tags create/create-update/create-replace/delete as root
element, absent of this root tags will be treated as "create-update"
by-default. Handling would be similar to current implementation.
{code:java}
{"create-replace": {“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
,{"Product": {"productId": "10001", "productName":"Round Hat", "InternalName":
"RoundHat" }}}
{code}
Please help me out if you have any better idea!
was (Author: jayansh):
Thanks Nicolas!
I think just adding tags create/create-update/create-replace/delete as root
element, absent of this root tags will be treated as "create" by-default.
Handling would be similar to current implementation.
{code}
{"create-replace": {“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
,{"Product": {"productId": "10001", "productName":"Round Hat", "InternalName":
"RoundHat" }}}
{code}
Please help me out if you have any better idea!
> 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
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830289#comment-16830289
]
Jayansh Shinde edited comment on OFBIZ-10966 at 5/1/19 4:42 AM:
Thanks Nicolas!
I think just adding tags create/create-update/create-replace/delete as root
element, absent of this root tags will be treated as "create-update"
by-default. Handling would be similar to current implementation.
{code:java}
{"create-replace": {“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
,{"Product": {"productId": "10001", "productName":"Round Hat", "InternalName":
"RoundHat" }}}
{code}
Please help me out if you have any better idea!
Reference:
[https://cwiki.apache.org/confluence/display/OFBIZ/Handling+of+External+data]
was (Author: jayansh):
Thanks Nicolas!
I think just adding tags create/create-update/create-replace/delete as root
element, absent of this root tags will be treated as "create-update"
by-default. Handling would be similar to current implementation.
{code:java}
{"create-replace": {“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
,{"Product": {"productId": "10001", "productName":"Round Hat", "InternalName":
"RoundHat" }}}
{code}
Please help me out if you have any better idea!
> 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
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830289#comment-16830289
]
Jayansh Shinde commented on OFBIZ-10966:
Thanks Nicolas!
I think just adding tags create/create-update/create-replace/delete as root
element, absent of this root tags will be treated as "create" by-default.
Handling would be similar to current implementation.
{code}
{"create-replace": {“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
,{"Product": {"productId": "10001", "productName":"Round Hat", "InternalName":
"RoundHat" }}}
{code}
Please help me out if you have any better idea!
> 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
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Comment: was deleted
(was: Reference [https://www.jsonschemavalidator.net/] for json validation
against json schema.
Tried data:
{"Party":
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED"},
"Product": {"productId":"654321", "productName": "Round Hat"}}
)
> 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
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Description:
Currently, we support import/export entity data in XML format.
Nowadays JSON is widely used in industry, we can have support for JSON format
which looks quite similar to XML support.
Here is example of XML data and it's JSON version
{code:java}
{code}
{code:java}
{“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
{code}
*Design Proposal*
We can write *entityImportJson* and *entityImportDirJson* services for
importing JSON from screen and directory respectively.
And the *entityExportAllJson* service for exporting entity data in JSON.
*Import Design*
The import service will perform following operations:
1.) Validate the input JSON data (I am in process of exploring the way for
this)
2.) On successful validation, convert JSON to OFBiz's entity model
(GenericValue)
3.) The GenericValue will be inserted in database by some handler class for
e.g we can write JsonDataHandler, it will convert given JSON to
List, and finally write it to database (Similar pattern is used
in XML import).
*Export Design*
Based on existing XML pattern the writeXmlText method of GenericEntity class
write the exported data in XML format.
In the similar way, we can implement writeJsonText to export data in JSON
format.
Please free feel to share your thought.
was:
Currently, we support import/export entity data in XML format.
Nowadays JSON is widely used in industry, we can have support for JSON format
which looks quite similar to XML support.
Here is example of XML data and it's JSON version
{code:java}
{code}
will look like this in JSON format
{code:json}
{“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
{code}
Here is design proposal
We can write entityImportJson and entityImportDirJson services for importing
JSON from screen and directory respectively. And entityExportAllJson for
exporting entity data in XML.
*Import Design*
We may validate the JSON schema during upload (I am in process of exploring it)
The import service will read the JSON data, validate it, then convert it to
OFBiz's entity data model (GenericEntity) and finally commit to database using
some handler class.
Like, we can write JsonDataHandler, this convert given JSON data to
List and write it to database.
{code:java}
private void writeValues(List valuesToWrite) throws
GenericEntityException {
if (this.checkDataOnly) {
EntityDataAssert.checkValueList(valuesToWrite, delegator,
this.getMessageList());
} else {
delegator.storeAll(valuesToWrite, new
EntityStoreOptions(createDummyFks));
}
}
{code}
*Export Design*
> 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
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Comment: was deleted
(was: The import service will read the json data and validate it and then
convert same to ofbiz’s entity data(GenericEntity) and commit to database using
some handler class. e.g. JsonDataHandler convert given json data to
List and write it to DB. Similar to:
private void writeValues(List valuesToWrite) throws
GenericEntityException {
if (this.checkDataOnly) {
EntityDataAssert.checkValueList(valuesToWrite, delegator,
this.getMessageList());
} else {
delegator.storeAll(valuesToWrite, new
EntityStoreOptions(createDummyFks));
}
}
Export service may require new method
(org.apache.ofbiz.entity.GenericEntity#writeJsonText) similar to existing
org.apache.ofbiz.entity.GenericEntity#writeXmlText )
> 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
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Comment: was deleted
(was: Lets have a look at main services used during Xml data import:
entityImport[WebtoolsServices.java]
entityImportDir[WebtoolsServices.java]
parseEntityXmlFile[WebtoolsServices.java]
Above services are responsible for importing parsing and validating xml data
using SAX XML parser class org.apache.ofbiz.entity.util.EntitySaxReader
Similarly export is done by entityExportAll service.
org.apache.ofbiz.entity.GenericEntity#writeXmlText is ultimately responsible
for converting entity data to xml data.
Please refer service definition file for more
details:../framework/webtools/servicedef/services.xml)
> 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
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON
> format which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> {code:java}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
>
> *Design Proposal*
> We can write *entityImportJson* and *entityImportDirJson* services for
> importing JSON from screen and directory respectively.
> And the *entityExportAllJson* service for exporting entity data in JSON.
>
> *Import Design*
> The import service will perform following operations:
> 1.) Validate the input JSON data (I am in process of exploring the way for
> this)
> 2.) On successful validation, convert JSON to OFBiz's entity model
> (GenericValue)
> 3.) The GenericValue will be inserted in database by some handler class for
> e.g we can write JsonDataHandler, it will convert given JSON to
> List, and finally write it to database (Similar pattern is used
> in XML import).
>
> *Export Design*
> Based on existing XML pattern the writeXmlText method of GenericEntity class
> write the exported data in XML format.
> In the similar way, we can implement writeJsonText to export data in JSON
> format.
> Please free feel to share your thought.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Description:
Currently, we support import/export entity data in XML format.
Nowadays JSON is widely used in industry, we can have support for JSON format
which looks quite similar to XML support.
Here is example of XML data and it's JSON version
{code:java}
{code}
will look like this in JSON format
{code:json}
{“Party”:
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
{code}
Here is design proposal
We can write entityImportJson and entityImportDirJson services for importing
JSON from screen and directory respectively. And entityExportAllJson for
exporting entity data in XML.
*Import Design*
We may validate the JSON schema during upload (I am in process of exploring it)
The import service will read the JSON data, validate it, then convert it to
OFBiz's entity data model (GenericEntity) and finally commit to database using
some handler class.
Like, we can write JsonDataHandler, this convert given JSON data to
List and write it to database.
{code:java}
private void writeValues(List valuesToWrite) throws
GenericEntityException {
if (this.checkDataOnly) {
EntityDataAssert.checkValueList(valuesToWrite, delegator,
this.getMessageList());
} else {
delegator.storeAll(valuesToWrite, new
EntityStoreOptions(createDummyFks));
}
}
{code}
*Export Design*
was:
*Entity data import/export in JSON format*
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. I am summarising how current data looks and how its done in current
system and proposing how it should be done.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}My suggestion that Json data must be validated via a json schema
during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{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
>
> Currently, we support import/export entity data in XML format.
> Nowadays JSON is widely used in industry, we can have support for JSON format
> which looks quite similar to XML support.
> Here is example of XML data and it's JSON version
> {code:java}
>
> {code}
> will look like this in JSON format
> {code:json}
> {“Party”:
> {"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}
> {code}
> Here is design proposal
> We can write entityImportJson and entityImportDirJson services for importing
> JSON from screen and directory respectively. And entityExportAllJson for
> exporting entity data in XML.
> *Import Design*
> We may validate the JSON schema during upload (I am in process of exploring
> it)
> The import service will read the JSON data, validate it, then convert it to
> OFBiz's entity data model (GenericEntity) and finally commit to database
> using some handler class.
> Like, we can write JsonDataHandler, this convert given JSON data to
> List and write it to database.
> {code:java}
> private void writeValues(List valuesToWrite) throws
> GenericEntityException {
> if (this.checkDataOnly) {
> EntityDataAssert.checkValueList(valuesToWrite, delegator,
> this.getMessageList());
> } else {
> delegator.storeAll(valuesToWrite, new
> EntityStoreOptions(createDummyFks));
> }
> }
> {code}
> *Export Design*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Description:
*Entity data import/export in JSON format*
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. I am summarising how current data looks and how its done in current
system and proposing how it should be done.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}My suggestion that Json data must be validated via a json schema
during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{color}_
was:
*Entity data import/export in JSON format*
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.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}My suggestion that Json data must be validated via a json schema
during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{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*
>
> 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. I am summarising how current data looks and how its done in current
> system and proposing how it should be done.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}My suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Description:
*Entity data import/export in JSON format*
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.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}My suggestion that Json data must be validated via a json schema
during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{color}_
was:
*Entity data import/export in JSON format*
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.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}Our suggestion that Json data must be validated via a json
schema during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{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*
>
> 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.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}My suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827555#comment-16827555
]
Jayansh Shinde edited comment on OFBIZ-10966 at 4/27/19 1:17 PM:
-
Reference [https://www.jsonschemavalidator.net/] for json validation against
json schema.
Tried data:
{"Party":
{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED"},
"Product": {"productId":"654321", "productName": "Round Hat"}}
was (Author: jayansh):
Reference [https://www.jsonschemavalidator.net/] for json validation against
json schema
> 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*
>
> 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.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}Our suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json schema.{color}_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827555#comment-16827555
]
Jayansh Shinde edited comment on OFBIZ-10966 at 4/27/19 1:15 PM:
-
Reference [https://www.jsonschemavalidator.net/] for json validation against
json schema
was (Author: jayansh):
Reference [https://jsonschema.net/] for json validation against json schema
> 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*
>
> 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.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}Our suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json schema.{color}_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827555#comment-16827555
]
Jayansh Shinde commented on OFBIZ-10966:
Reference [https://jsonschema.net/] for json validation against json schema
> 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*
>
> 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.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}Our suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json schema.{color}_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827552#comment-16827552
]
Jayansh Shinde edited comment on OFBIZ-10966 at 4/27/19 10:32 AM:
--
The import service will read the json data and validate it and then convert
same to ofbiz’s entity data(GenericEntity) and commit to database using some
handler class. e.g. JsonDataHandler convert given json data to
List and write it to DB. Similar to:
private void writeValues(List valuesToWrite) throws
GenericEntityException {
if (this.checkDataOnly) {
EntityDataAssert.checkValueList(valuesToWrite, delegator,
this.getMessageList());
} else {
delegator.storeAll(valuesToWrite, new
EntityStoreOptions(createDummyFks));
}
}
Export service may require new method
(org.apache.ofbiz.entity.GenericEntity#writeJsonText) similar to existing
org.apache.ofbiz.entity.GenericEntity#writeXmlText
was (Author: jayansh):
The import service will read the json data and validate it and then convert
same to ofbiz’s entity data(GenericEntity) and commit to database using some
handler class. e.g. JsonDataHandler convert given json data to
List and write it to DB. Similar to:
private void writeValues(List valuesToWrite) throws
GenericEntityException {
if (this.checkDataOnly) {
EntityDataAssert.checkValueList(valuesToWrite, delegator,
this.getMessageList());
} else {
delegator.storeAll(valuesToWrite, new
EntityStoreOptions(createDummyFks));
}
}
Export service may require new method
(org.apache.ofbiz.entity.GenericEntity#writeJsonText) similar to existing
org.apache.ofbiz.entity.GenericEntity#writeXmlTex
> 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*
>
> 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.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}Our suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json schema.{color}_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827548#comment-16827548
]
Jayansh Shinde edited comment on OFBIZ-10966 at 4/27/19 10:30 AM:
--
Lets have a look at main services used during Xml data import:
entityImport[WebtoolsServices.java]
entityImportDir[WebtoolsServices.java]
parseEntityXmlFile[WebtoolsServices.java]
Above services are responsible for importing parsing and validating xml data
using SAX XML parser class org.apache.ofbiz.entity.util.EntitySaxReader
Similarly export is done by entityExportAll service.
org.apache.ofbiz.entity.GenericEntity#writeXmlText is ultimately responsible
for converting entity data to xml data.
Please refer service definition file for more
details:../framework/webtools/servicedef/services.xml
was (Author: jayansh):
Lets have a look at main services used during Xml data import:
{color:#00}entityImport[WebtoolsServices.java]{color}
{color:#00}entityImportDir[WebtoolsServices.java] {color}
{color:#33}parseEntityXmlFile[WebtoolsServices.java]{color}
{color:#00}Above services are responsible for importing parsing and
validating xml data using SAX XML parser class
org.apache.ofbiz.entity.util.EntitySaxReader{color}{color:#008000}{color:#00}Similarly
export is done by {color}{color:#00}*entityExportAll*
{color}{color:#00}*service.*{color} **
{color:#00}_org.apache.ofbiz.entity.GenericEntity#writeXmlText_{color}{color:#00}
is ultimately responsible for converting entity data to xml data.
{color}{color}{color:#008000}{color:#00}Please refer service definition
file for more
details:{color}{color:#00}../framework/webtools/servicedef/services.xml{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*
>
> 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.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}Our suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json schema.{color}_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827552#comment-16827552
]
Jayansh Shinde commented on OFBIZ-10966:
The import service will read the json data and validate it and then convert
same to ofbiz’s entity data(GenericEntity) and commit to database using some
handler class. e.g. JsonDataHandler convert given json data to
List and write it to DB. Similar to:
private void writeValues(List valuesToWrite) throws
GenericEntityException {
if (this.checkDataOnly) {
EntityDataAssert.checkValueList(valuesToWrite, delegator,
this.getMessageList());
} else {
delegator.storeAll(valuesToWrite, new
EntityStoreOptions(createDummyFks));
}
}
Export service may require new method
(org.apache.ofbiz.entity.GenericEntity#writeJsonText) similar to existing
org.apache.ofbiz.entity.GenericEntity#writeXmlTex
> 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*
>
> 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.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}Our suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json schema.{color}_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827548#comment-16827548
]
Jayansh Shinde commented on OFBIZ-10966:
Lets have a look at main services used during Xml data import:
{color:#00}entityImport[WebtoolsServices.java]{color}
{color:#00}entityImportDir[WebtoolsServices.java] {color}
{color:#33}parseEntityXmlFile[WebtoolsServices.java]{color}
{color:#00}Above services are responsible for importing parsing and
validating xml data using SAX XML parser class
org.apache.ofbiz.entity.util.EntitySaxReader{color}{color:#008000}{color:#00}Similarly
export is done by {color}{color:#00}*entityExportAll*
{color}{color:#00}*service.*{color} **
{color:#00}_org.apache.ofbiz.entity.GenericEntity#writeXmlText_{color}{color:#00}
is ultimately responsible for converting entity data to xml data.
{color}{color}{color:#008000}{color:#00}Please refer service definition
file for more
details:{color}{color:#00}../framework/webtools/servicedef/services.xml{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*
>
> 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.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}Our suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json schema.{color}_
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Description:
*Entity data import/export in JSON format*
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.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}*Proposal:*{color}
_Services can be *entityImportJson* and *entityImportDirJson* for importing
json from screen and directory respectively. And *entityExportAllJson* for
exporting entity data in JSON, similar to existing services for xml.
{color:#00}Our suggestion that Json data must be validated via a json
schema during upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{color}_
was:
*Entity data import/export in JSON format*
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.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}_{color:#00}*Proposal:*{color}_{color}
{color:#00}_{color:#00}Services can be *entityImportJson* and
*entityImportDirJson* for importing json from screen and directory
respectively. And *entityExportAllJson* for exporting entity data in JSON,
similar to existing services for xml. {color}{color:#00}Our suggestion that
Json data must be validated via a json schema during
upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}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*
>
> 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.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}*Proposal:*{color}
> _Services can be *entityImportJson* and *entityImportDirJson* for importing
> json from screen and directory respectively. And *entityExportAllJson* for
> exporting entity data in JSON, similar to existing services for xml.
> {color:#00}Our suggestion that Json data must be validated via a json
> schema during upload.{color}{color:#00}R{color}{color:#00}efer
>
[jira] [Updated] (OFBIZ-10966) JSON entity data import and export utility
[
https://issues.apache.org/jira/browse/OFBIZ-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayansh Shinde updated OFBIZ-10966:
---
Description:
*Entity data import/export in JSON format*
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.
Just an example the existing xml data may look like:
{color:#008080}<{color}{color:#3f7f7f}Party{color}
{color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
{color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
{color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
same proposed JSON data will look like:
{color:#00}_{“Party”:
\{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
{color:#00}_{color:#00}*Proposal:*{color}_{color}
{color:#00}_{color:#00}Services can be *entityImportJson* and
*entityImportDirJson* for importing json from screen and directory
respectively. And *entityExportAllJson* for exporting entity data in JSON,
similar to existing services for xml. {color}{color:#00}Our suggestion that
Json data must be validated via a json schema during
upload.{color}{color:#00}R{color}{color:#00}efer
{color}{color:#00}[https://json-schema.org/] {color}{color:#00}for more
information on json schema.{color}_{color}
was:Adding support in OFBiz to import and export JSON data similar to XML
entity import/export.
> 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*
>
> 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.
>
> Just an example the existing xml data may look like:
> {color:#008080}<{color}{color:#3f7f7f}Party{color}
> {color:#7f007f}partyId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"_{color}{color:#2a00ff}_123456_{color}{color:#2a00ff}_"_{color}
>
> {color:#7f007f}partyTypeId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PERSON"_{color}
>
> {color:#7f007f}statusId{color}{color:#3c3c3c}={color}{color:#2a00ff}_"PARTY_ENABLED"_{color}{color:#008080}/>{color}
> same proposed JSON data will look like:
>
> {color:#00}_{“Party”:
> \{"partyId":"123456","partyTypeId":"PERSON","statusId":"PARTY_ENABLED”}}_{color}
>
> {color:#00}_{color:#00}*Proposal:*{color}_{color}
> {color:#00}_{color:#00}Services can be *entityImportJson* and
> *entityImportDirJson* for importing json from screen and directory
> respectively. And *entityExportAllJson* for exporting entity data in JSON,
> similar to existing services for xml. {color}{color:#00}Our suggestion
> that Json data must be validated via a json schema during
> upload.{color}{color:#00}R{color}{color:#00}efer
> {color}{color:#00}[https://json-schema.org/] {color}{color:#00}for
> more information on json schema.{color}_{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OFBIZ-10966) JSON entity data import and export utility
Jayansh Shinde created OFBIZ-10966: -- Summary: 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 Adding support in OFBiz to import and export JSON data similar to XML entity import/export. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
