[
https://issues.jboss.org/browse/JBIDE-17549?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17549:
-------------------------------------
Adding a comment from max on jbt-dev:
I took a look - still don't know what that "space" means.
Anyways seems only difference is that WTP schemas has
<uri
name="http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd"
uri="dtdsAndSchemas/beans_1_1.xsd"/>
declared and that is what maps that uri to that location hint.
I went and added this and voila entries for that get proper location
hint.
BUT with this two different entries shows up in the xml wizard so its
not of much help ;/
why there is this different between using plugin.xml uri's vs xml
catalog i'm not sure about
but I'm surprised since I thought this was said to working when you did
the whole "move" to xml catalog thing ?
XML file generated from catalog contains absolute paths
-------------------------------------------------------
Key: JBIDE-17549
URL:
https://issues.jboss.org/browse/JBIDE-17549
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta2
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.2.0.Beta3
Copied over from JBIDE-16358.
When I create a xml file from schema, it contains absolute path:
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
jar:file:/Users/rasp/jbossqa/JBDS/8.0.0/jbdevstudio-8.0.0.Beta2-106/studio/plugins/org.jboss.tools.as.catalog_3.0.0.Beta2-v20140528-1139-B52.jar!/schema/xsd/jboss-web_5_1.xsd
"
Also, notice the extra space at the end. Validation seems to work, but shouldn't it
point to the schema online? Or at least using a relative path?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)