10:48 a.m.
http://jira.jboss.com/jira/browse/JBAS-4252
----------------------------------------------------------------------------------
Line 15 of jboss-web_4_2.dtd seems to be invalid:
<!ENTITY % service-ref SYSTEM "./docs/dtd/service-ref_4_2.dtd">
The relative path causes problems, e.g. Eclipse cannot evaluate the DTD and so it cannot
validate a jboss-web.xml file or provide content assist. Shouldn't the URL point to
http://www.jboss.org/j2ee/dtd/ either ?
Same problem for jboss-client_4_2.dtd, jboss-app_4_2.dtd and jboss_4_2.dtd.
----------------------------------------------------------------------------------
Is there a better way to make those inclusions?
<!ENTITY % service-ref SYSTEM "./docs/dtd/service-ref_4_2.dtd">
%service-ref;
Also, have we documented the process for updating the www.jboss.org/j2ee site with the
dtds/schemas stored in dtds.war?
12:17 p.m.
Dimitris Andreadis wrote:
http://jira.jboss.com/jira/browse/JBAS-4252
----------------------------------------------------------------------------------
Line 15 of jboss-web_4_2.dtd seems to be invalid:
<!ENTITY % service-ref SYSTEM "./docs/dtd/service-ref_4_2.dtd">
The relative path causes problems, e.g. Eclipse cannot evaluate the DTD
and so it cannot validate a jboss-web.xml file or provide content
assist. Shouldn't the URL point to http://www.jboss.org/j2ee/dtd/ either ?
Same problem for jboss-client_4_2.dtd, jboss-app_4_2.dtd and jboss_4_2.dtd.
----------------------------------------------------------------------------------
Is there a better way to make those inclusions?
This should be handled by the
entity resolver at runtime. Without an xml
catalog configuration for each env (server, ide, ...) resolution is just
a pain. What does eclipse have in this area?
<!ENTITY % service-ref SYSTEM "./docs/dtd/service-ref_4_2.dtd">
%service-ref;
Also, have we documented the process for updating the www.jboss.org/j2ee
site with the dtds/schemas stored in dtds.war?
No. We really should have dtd/schema
projects that can be released so
qa/engineering can maintain this better.
1:31 p.m.
Scott M Stark wrote:
Dimitris Andreadis wrote:
> http://jira.jboss.com/jira/browse/JBAS-4252
I added public ids in the JBossEntityResolver for service-ref 4.0, 4.2, 5.0, like:
registerEntity("-//JBoss//DTD Web Service Reference 4.0//EN",
"service-ref_4_0.dtd");
...
And updated the inclusions to be:
<!ENTITY % service-ref PUBLIC
"-//JBoss//DTD Web Service Reference 4.2//EN"
"http://www.jboss.org/j2ee/dtd/service-ref_4_2.dtd">
%service-ref;
> Also, have we documented the process for updating the
www.jboss.org/j2ee
> site with the dtds/schemas stored in dtds.war?
No. We really should have dtd/schema projects that can be released so
qa/engineering can maintain this better.
Made a new tasks for publishing the updated dtds.
http://jira.jboss.com/jira/browse/JBAS-4280
Ryan may want to streamline this process with QA.
2:13 p.m.
On Tue, 2007-03-27 at 18:48 +0300, Dimitris Andreadis wrote:
http://jira.jboss.com/jira/browse/JBAS-4252
----------------------------------------------------------------------------------
Line 15 of jboss-web_4_2.dtd seems to be invalid:
<!ENTITY % service-ref SYSTEM "./docs/dtd/service-ref_4_2.dtd">
The relative path causes problems, e.g. Eclipse cannot evaluate the DTD and so it cannot
validate a jboss-web.xml file or provide content assist. Shouldn't the URL point to
http://www.jboss.org/j2ee/dtd/ either ?
+1
Same problem for jboss-client_4_2.dtd, jboss-app_4_2.dtd and
jboss_4_2.dtd.
Also, have we documented the process for updating the www.jboss.org/j2ee site with the
dtds/schemas stored in dtds.war?
I can take care of that if you let me know how to access
www.jboss.org/j2ee
/Heiko
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
6551
days inactive
6556
days old
jboss-development@lists.jboss.org
3 comments
3 participants
participants (3)
-
Dimitris Andreadis -
Heiko Braun -
Scott M Stark