Hussein - Thank you for your quick reply.
stephen.deal at myCompany.com wrote: > I'm a newbie with XXE and I have been testing it to see how well it > supports our complex W3C XML Schema before moving on to other requirements. > I have been making good progress in creating a configuration that uses our > schema but have run into a problem with CSS. > > I created a custom configuration (based on example2) and changed only the > references to the for <css> and <template> as follows: > <?xml version='1.0' encoding='ISO-8859-1'?> > <configuration name="GPP" > xmlns="http://www.xmlmind.com/xmleditor/schema/configuration"; > xmlns:cfg="http://www.xmlmind.com/xmleditor/schema/configuration";> > <detect> > > <rootElementNamespace>http://myCompany.com/schemas/content/prod/gpp.xsd</rootElementNamespace> > </detect> > <css name="Style sheet" location="gpp.css" /> > <template name="GPP template" location="gpp.xml" /> > </configuration> > > This enables me to create new docs based on our gpp.xsd schema and that > part works well! > However I am only presented with the XML tree view and no styled view. > > When I start XXE there are no errors and I cannot find any log files that > indicate a problem. > How can I debug my XXE configuration and get the styled view to work? >[1] Start XXE and use "Help|About XMLmind XML Editor". Your gpp.xxe file should be listed there. Yes, it is. Thanks for telling me about this feature. >[2] Open your gpp.xxe in XXE and use the "Tools|Check Validity". There should be no errors at all. There are no errors. [3] Use "File|New". The dialog box should list "GPP > GPP Template". Double-click on "GPP Template" to create a new GPP document. Yep, works just fine. [4] Look at the title bar of the newly created document. It should display "gpp.xml : Style sheet : GPP". Nope. I get=> Untitled.xml: : If it displays anything else it is certainly because your gpp.xml template document is *not* a GPP document. You probably forgot to properly declare the namespace of the root element. Yes, you are correct. As you may have surmised I am not proficient at XML Schema. Originally my gpp.xml template looked like this: <content_root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:noNamespaceSchemaLocation="http://myCompany.com/schemas/content/prod/gpp.xsd"; xmlns:x0="http://www.w3.org/2001/XMLSchema"; > and while it validated against the schema and allowed me to add elements, it failed to display the styled view. I was able to get the styled view to display by changing the namespace declaration of the root element in my gpp.xml template to this: <content_root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://myCompany.com/schemas/content/prod/gpp.xsd"; xmlns="http://myCompany.com/schemas/content/prod"; xmlns:x0="http://www.w3.org/2001/XMLSchema";> however now when I go to add elements the only element I can add is <para> which implies that it is no longer referencing the schema. So then I tried: <content_root xmlns="http://webdev.kodak.com/schemas/content/prod"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:noNamespaceSchemaLocation="http://myCompany.com/schemas/content/prod/gpp.xsd"; xmlns:x0="http://www.w3.org/2001/XMLSchema";> which produces a XXE Information dialog that essentially states: "Under these conditions, you can't do this with Standard, you must use Professional". To me this waas a good sign. I understand completely the need to constrain the Standard product in order to provide a revenue stream through the Professional product. However I am testing XXE to determine whether my company should purchase any licenses and before we spend the money I am trying to understand the following: 1) Can XXE Standard be configured to both validate our W3C schema and provide a styled view? Saying no is acceptable, I just want to know if it is a problem with my configuration. 2) Would XXE Professional both validate our W3C schema and provide a styled view using my configuration? 3) Are there any caveats in XXE Professional that would prevent it from being used in our environment? We would use JavaWebStart and probably take advantage of the DocumentHook interface. I would appreciate it if you could answer the questions 1 and 2. In the meanwhile I am going to see if I can get funding to acquire at least one Professional license to continue investigating your product since it looks very promising. -- XMLmind XML Editor Support List xmleditor-support at xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
