Oxygen XML Forum

Hi, I am new to oxygen and its products. I am using an eval license to generate sample xml from UNIFI pacs.004.001.01.xsd and I do not get the proper xml from it. It is valid, but it does not generate the full depth of it as it should. It just gets down to one level and where a "large" chunk of xml structure should be the tag is just empty. It works down to a certain depth then nothing, this happens all over the place. It is a big file to generate, has it something to do with it being an eval version? I have increased the heapsize for all tools to 1 GB of ram, the generator had max 180 MB before.

I select to generate optional elements and attributes. Value of elements and attributes are random, choice strategy is random. ANY namespaces and ANY elements, no custom stuff there.

I have the pacs file open and use the xml generator to generate an XML file and I get the error mentioned. The file called output.log is full of errors, they are the end of this post.

Also, when I click on any tag other than "document" at the top, to genererate xml from that starting point, I get an error sayin that "XXXelement does not longer exist"

What should I do to get rid of this problem? Any help is appreciated.

Here is part of one error:

10:29:37,841 143059 ERROR [ InstanceGenerator ] org.apache.xerces.impl.xpath.regex.RegexpInputGeneratorInternal - Selected |65|
10:29:37,841 143059 ERROR [ InstanceGenerator ] org.apache.xerces.impl.xpath.regex.RegexpInputGeneratorInternal - Processing range: 65-90
10:29:37,841 143059 ERROR [ InstanceGenerator ] org.apache.xerces.impl.xpath.regex.RegexpInputGeneratorInternal - Selected |65|
10:29:37,841 143059 ERROR [ InstanceGenerator ] org.apache.xerces.impl.xpath.regex.RegexpInputGeneratorInternal - Processing range: 65-90

Hello,

What is the value of the option Maximum recursivity level in the dialog Generate Sample XML Files? Try with a larger value for increasing depth of generated XML elements.


Regards,
Sorin

I started with 5 on that value, I increased it to 30 before posting on the forum and that did not help. Should it be even bigger than that?

Actually it gets deeper in some places and shallower in other.

So, the idea you came with should not be the issue. Any other things to look out for?

Thank you so much for the fast reply.

I cannot find a link for downloading the XSD file and generating an XML instance in Oxygen. Please post a download link for the XML Schema that you use.


Regards,
Sorin

Here is the link, I have downloaded it and tested, same error.

http://www.iso20022.org/documents/messa ... 001.01.zip

So click on "Document" at the top of the view, right click and select "Generate sample xml files...".

All the values for the schema and stuff should be filled in, there is just one root tag, document, and then:
Generate optional element and attributes.
Random values of elements and attributes
Pref number of repetitions: I have used 10
Max recurse level: 100
Choice strategy: First

I have tried other settings too with no difference.

Once you have generated the file, look for
MndtRltdInf element, it is empty. Should not be empty with the settins used.

Regards,

Diver

The error was fixed in Oxygen 10.1 beta. I tried with the options that you specified and there are 10 MndtRltdInf elements that look like the following:
You can download a Windows kit of Oxygen 10.1 beta from here and a Linux kit from here. Please let us know if you have other platform or if you find other problems.


Regards,
Sorin

That helps a little bit but the same problem still exists with "AmdmntInfDtls".
It is still empty, should NOT be empty, it is of the type at the end of the post.

So, you get one level deeper, then no more? I'll try the beta anyway but it seems it does not solve the problem still? Or am I misunderstandning something?

Regards,
Diver

<xs:complexType name="AmendmentInformationDetails1">
<xs:sequence>
<xs:element name="OrgnlMndtId" type="Max35Text" minOccurs="0" maxOccurs="1"/>
<xs:element name="OrgnlCdtrSchmeId" type="PartyIdentification8" minOccurs="0" maxOccurs="1"/>
<xs:element name="OrgnlCdtrAgt" type="BranchAndFinancialInstitutionIdentification3" minOccurs="0" maxOccurs="1"/>
<xs:element name="OrgnlCdtrAgtAcct" type="CashAccount7" minOccurs="0" maxOccurs="1"/>
<xs:element name="OrgnlDbtr" type="PartyIdentification8" minOccurs="0" maxOccurs="1"/>
<xs:element name="OrgnlDbtrAcct" type="CashAccount7" minOccurs="0" maxOccurs="1"/>
<xs:element name="OrgnlDbtrAgt" type="BranchAndFinancialInstitutionIdentification3" minOccurs="0" maxOccurs="1"/>
<xs:element name="OrgnlDbtrAgtAcct" type="CashAccount7" minOccurs="0" maxOccurs="1"/>
<xs:element name="OrgnlFnlColltnDt" type="ISODate" minOccurs="0" maxOccurs="1"/>
<xs:element name="OrgnlFrqcy" type="Frequency1Code" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>

I see in the XML Schema that AmdmntInfDtls should not be empty. We will fix the problem.


Thank you for your report,
Sorin

How quick can we expect a fix? Things are in a hurry here and your software showed good promise.

Regards,

Diver.

I need to use Oxygen more often to learn the options In fact it is already fixed. You have to increase the value of the option Discard optional elements after nested level available in Preferences -> XML -> XML Instances Generator. The default value is 6 and that is the level of AmdmntInfDtls. Increase it to 7 or more and the child elements of AmdmntInfDtls will be also generated. The default value is so small because there are large schemas for which the file sizes of the generated XML instances grow exponentially with the value of this option.


Regards,
Sorin

Lovely, that did not exist in the 10.0 version, the beta 10.1 has it and it works.

Now here is a suggestion for a slight improvement.
It would be good if you could have an option to max out all fields, to sett all fields to their max length so to speak. That would be a nice feature I think.

Thank you so much for the speedy help and superb service.

Regards,

Diver

We will consider your suggestion for a future version. I think random values of random length for the XML elements are better for testing an XML Schema. That means it is better to set the option Values of elements and attributes to Random.


Regards,
Sorin

I am using random now, that is useful of course. But, testcases often includes "maxed out" fields, so that would be useful too, minimum would be useful as well. For testing with large schemas that is invaluable, since doing it by hand takes several days pretty much.
Also an option to use more "odd" characters included in UTF8 and UTF16 could be nice too.

Regards, and again many many thanks.

Diver wrote:an option to max out all fields, to sett all fields to their max length

Diver wrote:Also an option to use more "odd" characters included in UTF8 and UTF16 could be nice too.

We will consider your requests for a future version.


Regards,
Sorin