- This topic has 4 replies, 2 voices, and was last updated 19 years, 4 months ago by Daniel Serodio.
-
AuthorPosts
-
Daniel SerodioMemberI can’t use Content Assist on a XML file.
The XML declaration is:<p:process-definition xmlns:p="http://jbpm.org/3/jpdl" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jbpm.org/3/jpdl jpdl-3.0.xsd" name="Incluir Documento">
And I added this schema it to the XML Catalog like this:
URI: platform:/resource/excelencia_reloaded/conf/jpdl-3.0.xsd Key Type: Namespace Name Key: http://jbpm.org/3/jpdl jpdl-3.0.xsd
But when I hit Ctrl+Space anywhere on the file, the only suggesttion that pops up is “comment”.
Riyad KallaMemberThe URL you gave: http://jbpm.org/3/jpdl jpdl-3.0.xsd does not resolve to a valid XSD file, I’m getting a file not found error, this is likely why the editor is not giving you autocomplete, because it cannot resolve the file.
Also I tried removing the space toh ave it resolve to: http://jbpm.org/3/jpdl/jpdl-3.0.xsd, and that was invalid as well. Your schema location needs to resolve to a web accessible file for the editor to pull it down, parse it, and provide validation.
Daniel SerodioMemberThe URL has to resolve even if I add it to the XML Catalog? I thought the reason behind the XML Catalog was to avoid the network! What if I’m not connected to the net?
Riyad KallaMemberYou are correct, have you downloaded the xsd file somewhere, and when you made the catalog entry, you pointed at the local file:// somewhere on your file ssytem? If you kept the same location as the one above then the catalog is simply trying to load the file from the invalid URL as well. The bottom line is that if you don’t want to use the catalog, then the location needs to be valid (aka put it in your browser and it opens an XSD file) if you want to use the catalog you need to download the file and store it locally, and then make a mapping in the catalog between the URI and the file, then the catalog will be used for lookups (like it does for all the DTDs and Schemas we ship).
Daniel SerodioMemberFound the problem. The “key” in the XML Catalog was wrong, it should be:
URI: platform:/resource/excelencia_reloaded/conf/jpdl-3.0.xsd Key Type: Namespace Name Key: http://jbpm.org/3/jpdl
-
AuthorPosts