Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export + Import name/value pairs #12

Closed
se38 opened this issue Jan 16, 2015 · 6 comments
Closed

Export + Import name/value pairs #12

se38 opened this issue Jan 16, 2015 · 6 comments

Comments

@se38
Copy link
Owner

se38 commented Jan 16, 2015

  • get name/value pairs from JSON string
  • create JSON string from name/value pairs
@se38 se38 added this to the zJSON Version 0.2.28 milestone Jan 16, 2015
@se38 se38 added the fixed label Jan 16, 2015
@se38 se38 closed this as completed Jan 16, 2015
@Kyrodan
Copy link

Kyrodan commented Feb 5, 2015

By implementing this item you now have a dependency to WebDynpro for type wdr_simple_name_value_list (which is not installed on every system). And I don't understand why you use this type and not your own key-value-store?

@se38
Copy link
Owner Author

se38 commented Feb 5, 2015

Hi Daniel,

the main reason was, that I don't want to populate internal data definitions to the outside. The developer should only work with SAP standard structures.

Are there really systems without the Webdynpro framework? Do you have an example?

Uwe

@Kyrodan
Copy link

Kyrodan commented Feb 6, 2015

Hi Uwe,

I don't know whether they exist in production environments. But our policy of our core product forbids this dependency and therefore it is not installed on our core development system. So I have to eliminate this dependency or just use and older version of zJSON.

@se38
Copy link
Owner Author

se38 commented Feb 6, 2015

If I understand you correctly you are not allowed to use SAP standard DDIC structures in your system?

To clarify the reason, why I did it this way:
I've got a second project (Neo4a), which uses zJSON internally. I don't want the developer to see any parts of zJSON outside of Neo4a -> the developer shouldn't know that zJSON is installed. (Probably this is also not allowed in your system, because there is a dependency between zJSON and Neo4a). That's why I've used a component, which should be already pre-installed on every SAP system.

If you see it really as a no-go I'm able to change the code (zJSON + Neo4a). But currently I'm not seeing really a reason to do so.

@Kyrodan
Copy link

Kyrodan commented Feb 6, 2015

My explanation was misleading:

  • I am allowed to use SAP standard DDIC structures
  • I saw that wdr_simple_name_value_list is a WebDynpro component and my colleague just stated "It's not installed on our development system" - so i thought it is a structure from any Add-On package

I just investigated it on my own and it seems that it is indeed a structure of SAP basis, which is not present on our development system. This system is on release 700 (which is our minimum requirement to support systems back to this release). The structure is present in our 731-systems.

@se38
Copy link
Owner Author

se38 commented Feb 6, 2015

Now that's indeed a reason. I'll create a new issue here on Github.

Maybe I'll find another key/value table which is present also on a 7.00 systems. (or can you search for one, I don't have a 7.00 system at hand right now). If we can't find one, I'll use the zJSON table [but under protest ;-) ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants