item.\u03CDA is not a function
July 01 2008
- 10 replies.
- This question is not yet resolved.
- This question was started by Thomas Stahl.
- Last post by Laurens.
member 01 July,
14:50 | I have create a schema, a document and a xsl file. But when I try to load it with Xopus using http:/ I get the following error message inside the "Xopus window": An unknown error has occured: item.\03CDA is not a function So I reduced my files to (nearly) the very minimum, but I still get that error. What is wrong with my approach? ======== mini.xml =========== <?xml version="1.0" encoding="UTF-8" standalone="no"?> <?xml-stylesheet href="mb.xsl" type="text/xsl"?> <mb:fall xsi:schemaLocation="urn:de:vfst.mb,2008 mb.xsd" xmlns:xsi="http:/ xmlns:mb="urn:de:vfst.mb,2008" > <mb:titel>My title</mb:titel> </mb:fall> ======== mini.xsd =========== <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http:/ targetNamespace="urn:de:vfst.mb,2008" xmlns="urn:de:vfst.mb,2008" elementFormDefault="qualified"> <xs:element name="fall"> <xs:annotation> <xs:appinfo xmlns:xopus="http:/ <xopus:documentation> <xopus:name xml:lang="en">Case</xopus:name> <xopus:name xml:lang="de">Fall</xopus:name> </xopus:documentation> </xs:appinfo> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element ref="titel"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="titel" type="xs:string"> <xs:annotation> <xs:appinfo xmlns:xopus="http:/ <xopus:documentation> <xopus:name xml:lang="en">Title</xopus:name> <xopus:name xml:lang="de">Überschrift</xopus:name> </xopus:documentation> </xs:appinfo> </xs:annotation> </xs:element> </xs:schema> ======== mini.xsl =========== <?xml version="1.0"?> <xsl:stylesheet xmlns:xsl="http:/ xmlns:mb="urn:de:vfst.mb,2008" exclude-result-prefixes="mb" version="1.0" > <xsl:template match="mb:fall"> <div><xsl:apply-templates select="*"/></div> </xsl:template> <xsl:template match="mb:titel"> <h1><xsl:apply-templates select="node()" /></h1> </xsl:template> </xsl:stylesheet> |
Xopus Team 01 July,
15:26 | Thomas, You load the XML directly into Xopus. This is possible, but I think Xopus has a problem with the location of your XSD. Try creating a simple island, and save it as an HTML file. Load this file into Xopus. An example is the start.html from the Simple Demo. You can also look here: http:/ |
Xopus Team 01 July,
15:29 | If this still does not work, by the way, zip your files and mail them to support@xopus.com We will take a look for you. |
member 01 July,
19:08 | No, I tried the same with a data island html file: ======================================================= <pre> <html> <head> <title>Mini</title> <link rel="stylesheet" type="text/css" href="css/common.css"/> <link rel="stylesheet" type="text/css" href="css/style.css"/> <style> .testdiv { border: 1px solid red; } .xopusdiv { border: 1px solid green; } </style> <!-- Start Xopus --> <script type="text/javascript" src="../../xopus/xopus/xopus.js"></script> </head> <body> <!-- The Xopus Canvas --> <div xopus="true" autostart="true" class="xopusdiv"> <xml> <x:config version="1.0" xmlns:x="http:/ <!-- <x:javascript src="js/save.js"/> --> <x:pipeline xml="mini.xml" xsd="mini.xsd"> <x:view name="WYSIWYG View"> <x:transform xsl="mini.xsl"/> </x:view> <x:view name="Tags On View"> <x:transform xsl="tagson.xsl"/> </x:view> <x:view name="XML View"> <x:treeTransform/> </x:view> </x:pipeline> <x:import src="config.xml"/> </x:config> </xml> </div> </body> </html> </pre> ======================================================= The error remains the same. Furthermore, if I change the name of the xsd file to something like "xxxmini.xsd", I get an alert box, telling me that the file does not exist. What happens, if *you* use those 3 (or 4) files on your xopus system? Do they work for you? |
member 01 July,
19:09 | Sorry, oversaw your last remark. I will send the files as zip. Thank you! |
member 01 July,
19:17 | I have sent the zip file. |
member 01 July,
19:23 | Sorry, forgot to mention: all the above in Firefox 2.x. Discovered a minute ago that the mini files do work in IE 6 !! But shouldn't they work in FF, too? Or is Xopus "IE only"? |
Xopus Team 02 July,
22:21 | Officially Xopus 3.x only supports IE 6 and 7, but most of the functionality also works in FF 2 and 3. Unfortunately you found some that doesn't.
If you open the files in IE and press Ctrl+Alt+R once Xopus is running and explain in the dialog that that case doesn't work in FF, we might be albe to resolve the issue in the next 3.x release. Xopus 4 will be fully compatible with Firefox 3. |
member 02 July,
23:18 | >> open the files in IE and press Ctrl+Alt+R I will do so. >> Xopus 4 will be fully compatible with Firefox 3. That's great news! Can you give me an estimate of when Xopus 4 will be available. And do get Xopus 3 customers that upgrade for free? (I still use the trial download, but we are severly considering to buy some licenses...) |
member 03 July,
12:44 | >> ...open the files in IE and press Ctrl+Alt+R I have done so and sent the "mini" application to you (case number: 137560). But there is no text field in that dialog, so I could not enter any comments. The prospect of Firefox 3 compatibility is nice, but I still cannot understand that my mini application (just a container and a title element) can break Xopus, while the much more complex examples work in IE and FF alike. Sorry to say that, but this is a little disappointing (my boss will not like it). If you could give me a hint about the cause of the problem (and how I can avoid it), my chances to convince my boss of Xopus would greatly increase. ;-) |
Xopus Team 03 July,
20:21 | > Can you give me an estimate of when Xopus
> 4 will be available. We will release Xopus 4 when it is done. We expect will be by the end of the year. > And do get Xopus 3 customers that upgrade > for free? Yes, if they have an update subscription. > I have done so and sent the "mini" application > to you (case number: 137560). Thanks, we have received it and we can reproduce the issue. > I still cannot understand that my mini > application (just a container and a title > element) can break Xopus Our Firefox development is primarily targeted at Xopus 4. We have just fixed this particular bug in Xopus 3. The fix will be shipped with the Xopus 3.2.12 release. |
- support /
- forum /
- General Discussion /
- item.\u03CDA is not a function
React
Write a comment