Dear Buster In the debugger perspective there is a toolbar containing the Transformation XML and XSL combos, the Transformation engine combo, and the last button on the toolbar is called "Enable XHTML output". Just press it and the next time the debugging session will start the XHTML tab w...

Dear Michael, You can select the desired text(or word), right click, in the contextual menu go to Refactoring->Surround with tag. A dialog will appear allowing you to select any allowed tag in that context. There are also keyboard shortcuts available for the Surround actions which can also be custom...

Hi, In the Mime headers sent along with the request we set the "Content-Type" header with the value : "text/xml; charset=utf-8". This is possibly why the server reports the exception. Setting the header to this value is the default way of posting XML fragments and all servers sho...

Hi,

Can you post a small WSDL sample to reproduce the exact situation on our side?

Regards,
Radu

Dear Hans,

Unfortunately this is the w3c way:
http://www.w3.org/TR/REC-xml-names/#defaulting

Here is an interesting discussion though:
http://lists.xml.org/archives/xml-dev/2 ... 00161.html

Regards,
Radu

Hi, Sorry for the delay Indeed there were problems correctly interpreting the value of the parameter on MarkLogic. We fixed the problem, letting the MarkLogic query processor decide the type of the passed parameter. The fix will be included in the 8.1 maintenance release which will be released proba...

Hi, The difference is that all the elements in your second XML fragment are in the "http://www.filenaker.com/fmpxmlresult" namespace so one way to access the attribute value is to bind the namespace to a prefix and use the prefix in the XPath like: <xsl:value-of select="/FS:FMPXMLRESU...

Hi, You have two mistakes in the select. First of all, everything in XSL (and XML in general) is case sensitive so the attribute name must be written "name" and not "NAME". Then, if you begin an XPath with a "/" it means it's absolute which in your case is not true. So ...

Hi, So, to make things clear, in order to generate this XML in the grid: <elem attr="value"/> in the cell corresponding to the "attr" attribute column you just need to type value and save. On the other hand, if you need to use quotation characters (like simple or double quotes) i...

See this reply: http://www.oxygenxml.com/forum/viewtopic.php?p=7130

Hi, Thank you for contacting us. For problem 1: As I see it you want some kind of format and indent when passing from grid to text. There is a check box in Oxygen Options->Preferences->Editor->Grid : "Format and indent when passing from grid to text or on save". If it does not work as you ...

Dear Jon, Unfortunately the current release of Oxygen does not have the Exist collections or the resources in them sorted in alphabetical order. We fixed this in the current stream both for the eclipse and the standalone version and the fix will probably be available in the upcoming Oxygen minor ver...

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...