Just to exclude some causes:

is it possible for you to run this transformation outside of uniface without these problems?
just launch this XML-Transformation and check the results.

Uli

Hi

Well, the euro symbol, nor any symbol, should be a problem with a valid unicode file (UTF-8 encoded for example), processed by a valid unicode stylesheet file.

This seems to be more a file encoding problem than a XSL processor one (or Xalan is not really scalable, what I doubt)

Kind regards,
Richard

Good to know -- always trouble with this euro

Good morning. We resolved the problem. It was the euro character, in our version xmltransform function is not able to transform it. Regards.

"preceeding" the root node may point to some unbalanced quotes or so:

The EOF is encountered before a root node is recognised.

This is exactly the message error: "XSLT: The markup in the document preceding the root element must be well-formed. Xalan: was not successful". Regards.

Hi, character unicode 0x19 is an end of file, if you cut and paste the xml file or the content inside from Word to uniface it´s normal that this character appears.

Regards,Rafa.

Hi mates! I got a problem again but now I got a -3 code error with a descripcion about "An Invalidad xml character unicode 0x19. Xalan was not successfully". Does anyone know something about Xalan version, updating and his caracteristics? PS: We are using Uniface 8.02. Thanks in advance! Kind Regarsd.

Hi Rafa,

thanks for your detailed analysis; it is very positive that we do not have a fundamental problem launching XML transformation out of Uniface.

And the "all-in-one-node" should not occur too often in the real world.

Have a nice weekend (warm and sunny here in Regensburg/Germany), Uli

Ok, i´ve been talking with Antonio and I tested his xml files in a similar enviroment, i think that it´s not a problem of memory, jvm or file size, i tested similar xml files and works fine, but in his xml file, there is a node that content all the information, if this node is separated in two nodes works fine, it´s a possible solution, but someone knows the limit of a xml node? or a parameter to change the limit?

Regards, Rafa.

The control is returned to uniface and Altova takes much more time to convert it. It seems like uniface get an unclassified error before finishing the process. Regards

Does the control returns to uniface in +/- the same amount of time it took using the Altova way?

Or is it faster (which may point to a problem during conversion) w/o proper error reporting?

And using the pragmatic way: would it be possible to do the transformation via Altova and just load the output in Uniface?

I already did using Altova to check the xml_input and the xsl. It took a lot of time but it worked.

Finally I got the solution for Unifave 8.2.03 updating the Java Virtual Machine and changing the environment variable $PATH with the lastest installed version.

Well, I am really confusing. Firstly, thank you for help me to everyone. The problem is I have no idea about what kind of problem is happening because when I am executing xmltransform operation I get a null value in status parameter and the output is empty. At the beggining we got an error, -5, java runtime error and we resolved changing the java virtual machine version. After that, we got our new strange error and I thought changing the JVM memory size using something like "JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=1024m" but it didn?t work. Any idea!? Best regards.

Hi rafa,

what we need to find out is if there is something in HIS very special environment
stopping the processing of THIS special file regardless if inside or outside of uniface.

May be memory, processor, disk space, ...you-name-it....

If it's only a problem when started inside uniface, (synchronous) launching processing outside with a script may help.

With uniface I don´t know, I don´t tried it; with java or C++ it´s possible.
I´working with Uniface 9.4 if this weekend I have time I´ll test it and I tell you.

Regards,Rafa.

let me be more specifc: is it possible ... FOR Antmartinr in his environment?

Yes, it´s possible, a larger file could take a lot of minutes (maybe hours).
PD: always appears some problems, but it´s our work to solve them :) .
 

Regards, Rafa.

is it possible to run the XML transformation of that big file outside of uniface w/o problems?

Hi, you upgraded the JVM, maybe a possible solution it´s upgrade the xalan libraries.

Regards, Rafa.

Hello, I got a new problem using XMLTRANSFORM. This operation is not working when I try to convert a file around 13M in Uniface 8.2.03.01. Thanks in advance. PS:I didn?t get any error in the status parameter

At the beginning I tried to do it using this options but it didn?t work with Uniface 8.2.03. Thanks, anyway.

Some additional information regarding this topic.

Instead of changing the PATH you can also tell Uniface where to locate the jvm DLL.
I think this is more solid.
 

Like:

[USER_3GL]

;D:\\USYS94\\common\\jre\\bin\\client\\jvm.dll(JNI_CreateJavaVM)

C:\\Progra~1\\Java\\jre1.5.0_12\\bin\\client\\jvm.dll(JNI_CreateJavaVM)

 And also you can overrule default options for JVM, e.g. heap size:

 [LOGICALS]

JVM_OPTIONS = -Xss4m -Xnoclassgc -Xmx90000000

 Sjaak

Exactly. At least it is a possible solution.