Hi, Here are two ways to accomplish this, one using the "xsl:for-each-group" construction from XSLT 2.0: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"> <xsl:output indent="y...

Hi,

Just wanted to say that the release of Java Virtual Machine 1.6 available now for downwload fixes the last reported exception (there were problems with that release candidate).
We tested Oxygen with it and did not encounter any problems.

Best regards,
Radu

Hi, We just fixed such an issue a couple of days ago. It happened when editing an XSL file which had associated a scenario specifying an external transform like MSXML. We implemented the feature of using the transformer specified in the scenario for validation because we thought it was useful for th...

Hi Klaus,

Just wanted to let you know we fixed the bug and the fix will probably be available in the next maintainance version.

Regards,
Radu

Hi, There are a couple of ways to accomplish that: 1)Change the default java used on your computer: You can issue a "java -version" command to find out which java is used by default on your computer. If it is not the java from sun, you can issue "which java" to see whether there ...

Dear Cladio, In order to accomplish this you need to use catalog support. Just create a file called for example "testCatalog.xml" and save in it the content below. Of course you have to modify the value of the "rewritePrefix" attribute to the real path on your system. <?xml versi...

Hi, Here's a stylesheet that transforms from the old format to the new one: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:output indent="yes"/> <xsl:template match="/t...

Hi,

Indeed the code templates export file format has changed from 7 to 8 and there seem to be problems importing the old style format.
We will fix them.
I will get back with either a workaround or a stylesheet to transform from old style to new style format.

Thanks,
Regards, Radu

Hi, oXygen requires a Java from Sun and you have GNU Java, see on the download page, under requirements: http://www.oxygenxml.com/download.html *** Sun Microsystems Java VM version 1.4.2 or later (available at http://java.sun.com) in case you use the installation kit without Java VM. *** Eventually ...

Dear Darren, This is indeed a delicate problem. We use different class/library loaders for each transformation but there is a problem disposing them on demand at the end of the transformation (and thus releasing the dll) I added a bug request for this, we will study it further and notify you when we...

Oh, and you also have some workarounds For issue 2 you can right click the response text area and then choose Open in editor so that you can format and indent the content there. For issue 3 you can save a snapshot of the current request + selected ports, actions in a WSSC file and then open it when ...

Dear Andrzej, Your requests seem very appropiate. 1) The WSDL SOAP Analyser is already presented as a view on Eclipse so I think there would be no problem doing this in the standalone version. 2) I see no problem in implementing this 3) Yes, this indeed could be useful I placed your requests in our ...

Hello, The place where to add extensions has changed starting with version 7.2. Now extensions are scenario dependent, so you can configure different extensions for each scenario. You just have to edit the current scenario, press the "Extensions" button located in the first tab and add you...

Hi Adam,

I updated the filed improvement request with your suggestions.
Opening the server response in the editor is possible.
Just right click the in the response text are and choose Open in Editor.

Regards, Radu

Hi Adam, XML-RPC is not supported directly in Oxygen (standalone or eclipse) right now but I think you can use a workaround. Just open in Eclipse the WSDL SOAP Analyser View which comes with oXygen, fill the URL with the destination URL, then go to the request tab and fill the XML request then go ba...

Hi, About the first problem, having 2 schemas in the <wsdl:types> and refering from an element in the first one to a complex type in the other, there seems to be a problem in how Oxygen handles the situation and I'll place a bug report. We'll keep you up to date with the progress. About the second i...

Hi Christian, Maybe the following stylesheet would be useful: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:template match="node() | @*"> <xsl:copy> <xsl:apply-templates se...

Hi Mitch, Hmm, that's strange. So you have the XHTML radio button checked, you create or open a stylesheet and do not have the XHTML elements in the content completion when inside a xsl:template? Can you try clicking the "Formatting objects" radio button, press OK and then check if you hav...

Hi Mitch, The preferences page you are searching for can be found in the Options menu -> Preferences -> Editor -> Content Completion -> XSL/XPath. The page lets you configure additional elements that should be included in the content completion when editing stylesheets. XHTML transitional comes buil...

Hi, As George said, you have to change the xsl:stylesheet 's version attribute to 2.0 in order for it to validate a version 2.0 XPath "if() then else" expression. This is also true for running a transformation on the stylesheet (you have to run it using the Saxon 8B transformer). Indeed, i...

Hi,

The problem is that you have a in the stylesheet fragment which outputs the numeric version of the month. Remove that line and everything seems to work OK.

Regards,
Radu.

Hi,

Here is an interesting link describing translating from HTML to FO (also describes how row and colspans are translated in FO) :http://www-128.ibm.com/developerworks/l ... app/#table

Regards,
Radu

Hi, Please contact us at support at oxygenxml.com with more details like: Does the commit problem happen also when using the HTTP protocol? What is the exact message of the error? Does it seem to originate from the operating system? We will provide you with a log file to enable SVN client logging. R...

Hi Mike, As I see it, you have an omission in the xpath used in the "xsl:apply-templates". It should be like: <xsl:apply-templates select="$generic-common-xsd/xs:schema/xs:simpleType[@name='$TypeVal']" Notice the additional "xs:schema" in the path. Here is your styleshe...

Hi, The error you encountered comes from the server side of the IBM WebSphere Application Server: WSWS3084E: Error: {0} encountered a child element, which is NOT expected, in something it was trying to deserialize. Explanation: This message normally indicates that the soap message is invalid. The en...

Hi Igor, I opened the WSDL file you specified in Oxygen and tried to validate it. There are indeed problems reported. WSDL files are validated in Oxygen using the XML Schemas available at http://schemas.xmlsoap.org/wsdl/ and http://schemas.xmlsoap.org/wsdl/soap/ . Among the problems found (you can c...

Hi Eric, We made another patch for this problem. Please download the new patch from http://www.oxygenxml.com/update/patchEric/oxygen.jar and place it in the 'lib' directory of your <oXygen/> installation. Then, set the theme that originally generated the exception, start Oxygen and let us know if th...

Hi, Peter Here's a way: <?xml version="1.0" encoding="windows-1250"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="text" omit-xml-declaration="yes" encoding="ascii"/> <xsl:pre...

Hi, Just wanted to let you know that we are now using the Saxon output serializer which also respects the parameters set in the XQuery file. We also improved the performance when the output is produced on a single line. The fix will most probably be available in the 7.2 maintainance version. Regards...

Hi,

We already have a bug request for the "Move beyound next tag" action which I think is exactly what you suggest.
I'll enhance it's priority.

Regards,
Radu