| mwSteidl |
| Member |
| Michael+Steidl |
| AT |
| + |
|
| Female |
|
| Wednesday, March 23, 2005 |
| Thursday, February 20, 2014 4:55:45 PM |
20
[0.11% of all post / 0.00 posts per day] |
|
We are using an XML Schema which has parent element with many child elements as multiple choices, see the diagram below.
Using the Generate Sample XML File function creates the parent element but only with the first child element as single child.
Is there any parameter for the Generate ... function to add all choices to the parent element?
|
Agreed: files should be accessed by the rules of RFC1738 - but why does XMLspy accept href="C:\aPath\aFile.xslt", that's confusing. By the XSLT 1.0 specs the @href of xsl:import is a uri-reference, therefore using a local file path is actually an implicit use of the file URI scheme and as a result also C:\aPath\aFile.xslt should throw an error.
|
I've been using a line like this one in my XSLT documents:
<xsl:import href="file:///C:\aPathOnMyHarddisk\file.xslt" />
Opening such an XSLT with XMLspy 2012 SP1 throws an error: "The syntax for the file name, ... is wrong"
When removing the "file:///" string XMLspy is happy.
Apparently there is something wrong as I did not change the file name, I only removed the URL schema identifier.
Altova, please make XMLspy compliant with the file scheme from the IANA Scheme registry - http://www.iana.org/assignments/uri-schemes.html - again.
thanks
Michael
|
We have a workflow for wrapping multiple XML documents by a wrapper instance, the resulting XML looks like this:
<newsMessage xmlns="http://iptc.org/std/nar/2006-10-01/" xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/ NAR_1.8-spec-All-Power.xsd">
<itemSet>
<conceptItem xmlns="http://iptc.org/std/nar/2006-10-01/" xsi:schemaLocation="http://iptc.org/std/nar/2006-10-01/ NAR_1.8-spec-All-Power.xsd" >
...
</conceptItem>
</itemSet>
</newsMessage>
But this throws an error in XML Spy 2010 rel 3: "The 'schemaLocation'attribute references a schema whose target namespace was already used for validation".
1. Which W3C recommendation does not allow assigning the same XML Schema to the same XML Namespace multiple times.
2. Can anybody explain what ".. namespace was already used for validation" means - we always thought XML Schemas are used for validation, the namespace is used only for scoping.
Interesting enough this XML does not throw an error in XML Spy 2006...., ok, times are changing.
Thanks.
|
Hm, actually I can't remember exactly if I've run XML Spy on my Win7 64-bit machine, and it is very likely that I used XML spy on the Vista 32-bit PC. But this is the typical use case: I start XML Spy, get the message that an update is available, download it and install it - possibly later that day but usually not in the morning right after starting up. And I never experienced such errors ever before.
Ok, will check if I've used an Altova application at the time of the next update.
|
I've installed Altova Mission Kit 2010 rel 3 for Enterprise on Windows Vista 32-bit and Windows 7 64-bit and got the same error on both systems:
after some installation activities a pop-up opens claiming "Files in Use" and that an application is "using a file which needs to be updated by this setup". This application is: Windows Explorer.
I can only continue with the installation after shutting down the Explorer by the Task Manager. Then I have to restart my computer. Very inconvenient.
As the same issue happened on both computers this cannot only be a bad coincidence.
|
The "Show Macros..." dialog shows a "Debug" button and the script text windows of the XMLSpyFormEditor allow to set a Breakpoint for specific code lines.
If I click on this "Debug" button only the default debugger of my PC is launched - but that's all.
This worries me - is there a debugger in the scripting environment at all? Also the help file is mute on this topic.
Any hints welcome
|
Hi Vlad
looking forward to see this feature. When to expect this version?
Michael
|
I'm using: XML Spy version 2008 rel 2 sp1
Apparently there is an internal fight over the XSLT output format between the xslt:output@method and the setting of the file name extension of the XmlSpy Options - and the Option wins:
- I set <xsl:output method="text" ...
- The output filename extension is set to ".html"
- The output windows launches the html browser module and not the plain text module.
I feel the xsl:output@method should come first and then the file name extension. The result is that for switching between XSLTs using method "text" and "html" I always have to align the file name extension in the options - kind of boring if you have to do this 10 times an hour.
Michael
|
Excellent guess: it is an 0x0 character. Ok, then I'll turn to the Altova support.
Thanks for pointing this out.
Michael
|
|
