The developerWorks Connections Platform is now in read-only mode and content is only available for viewing. No new wiki pages, posts, or messages may be added. Please see our FAQ for more information. The developerWorks Connections platform will officially shut down on March 31, 2020 and content will no longer be available. More details available on our FAQ. (Read in Japanese.)
Matching: xml X
TheresaRamsey 1100004FVX Tags:  eglcafe xml json egl record rest soap service wsdl 4 Comments 13,608 Views
We want to help you be an EGL rockstar and make your own record...an EGL Record that is. When you combine EGL and Web services is sure to be a hit.
To create EGL Records from the XML or JSON, try this web application written in EGL Rich UI:
http://comm05.haw.ibm.com/EGLRecordConversionServices/transform-en_US.html. The JSON or XML can be loaded from a URL or directly input. You can create EGL Records from XML schema too.
So be a rockstar programmer and make tons of records using EGL!
We looking forward to hearing from you. Login and enter a comment to let us know what you think of this application. Thanks![Read More]
It has happened more than once, more than twice. Someone asked me to define an EGL record from a snippet of xml string. It is not that hard, but I often get it wrong.
If you've used EGL Rich UI 751, and made REST service calls. You probably have found yourself in the same situation. This process can be tricky depending on what the xml looks like. In the EGL Rich UI 751 User's manual, it talks about the rules for defining EGL record from xml string in details.
Wouldn't it be nice if a tool can do this for you?
We've got one for SOAP web service, from a wsdl file, it can produce EGL interfaces and records. That's because WSDL contains all the information a client needs to call a SOAP service on the server. It reads the WSDL to determine what functions are available on the server. Any special datatypes used are embedded in the form of XML schema.
There isn't such a standard for REST web service. REST web services deal with resources by running CRUD operations on them. The resource is often transmitted in the format of xml or json. In the case of xml, in order for EGL to deserialize xml string into EGL record, you would have to define an EGL record according to the XML structure. That's an error prone process like I mentioned in the beginning.
So as a start, I wrote this EGL RUI application, that converts xml string to EGL record definition
The input can be:
Here are some of the rules and assumptions I made:
You can paste the output EGL record definition into any packages.
Here is the project interchange file you can import to your workspace. The RUI handler is RecordConverter