Menu
▾
▴
[jboss-cvs] jboss/src/resources/dtd ...
|
From: Thomas D. <tho...@jb...> - 2005-06-18 15:45:05
|
User: tdiesler
Date: 05/06/18 11:44:25
Modified: src/resources/dtd jboss_4_0.dtd
Log:
synch web services with jboss-4.0.3beta
Revision Changes Path
1.28 +55 -35 jboss/src/resources/dtd/jboss_4_0.dtd
(In the diff below, changes in quantity of whitespace are not shown.)
Index: jboss_4_0.dtd
===================================================================
RCS file: /cvsroot/jboss/jboss/src/resources/dtd/jboss_4_0.dtd,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- jboss_4_0.dtd 5 Apr 2005 19:49:05 -0000 1.27
+++ jboss_4_0.dtd 18 Jun 2005 15:44:25 -0000 1.28
@@ -4,7 +4,7 @@
This is the XML DTD for the JBoss 4.0 EJB deployment descriptor.
The DOCTYPE is:
-$Id: jboss_4_0.dtd,v 1.27 2005/04/05 19:49:05 ejort Exp $
+$Id: jboss_4_0.dtd,v 1.28 2005/06/18 15:44:25 tdiesler Exp $
<!DOCTYPE jboss PUBLIC
"-//JBoss//DTD JBOSS 4.0//EN"
@@ -17,6 +17,13 @@
<enforce-ejb-restrictions />
<security-domain />
<unauthenticated-principal />
+ <webservices>
+ <context-root>
+ <webservice-description>
+ <webservice-description-name>
+ <wsdl-publish-location>
+ </webservice-description>
+ <webservices>
<enterprise-beans>
@@ -91,10 +98,6 @@
<resource-env-ref>
</message-driven>
- <webservice-description>
- <webservice-description-name>
- <wsdl-publish-location>
- </webservice-description>
</enterprise-beans>
@@ -155,7 +158,7 @@
-->
<!ELEMENT jboss (loader-repository?, jmx-name?, enforce-ejb-restrictions?,
security-domain?, missing-method-permissions-excluded-mode?,
- unauthenticated-principal?, exception-on-rollback? , enterprise-beans?, assembly-descriptor?,
+ unauthenticated-principal?, exception-on-rollback? , webservices?, enterprise-beans?, assembly-descriptor?,
resource-managers?, invoker-proxy-bindings?, container-configurations?)>
<!-- The loader-repository specifies the name of the UnifiedLoaderRepository
@@ -403,7 +406,48 @@
Used in: jboss
-->
-<!ELEMENT enterprise-beans ((session | entity | message-driven)*, webservice-description*)>
+<!ELEMENT webservices (context-root?, webservice-description*)>
+<!-- The context-root element specifies the context root of the web
+application that the EJB service endpoints are deployed to.
+If it is not specified it will be derived from the deployment short name.
+-->
+<!ELEMENT context-root (#PCDATA)>
+<!--
+Runtime information about a web service.
+wsdl-publish-location is optionally used to specify
+where the final wsdl and any dependent files should be stored. This location
+resides on the file system from which deployment is initiated.
+-->
+<!ELEMENT webservice-description ( webservice-description-name, wsdl-publish-location? )>
+<!--
+Unique name of a webservice within a module. It corresponds to the <webservice-description-name>
+element in webservices.xml
+-->
+<!ELEMENT webservice-description-name ( #PCDATA )>
+<!--
+file: URL of a directory to which a web-service-description's wsdl should be
+published during deployment. Any required files will be published to this
+directory, preserving their location relative to the module-specific
+wsdl directory(META-INF/wsdl or WEB-INF/wsdl).
+Example :
+ For an ejb.jar whose webservices.xml wsdl-file element contains
+ META-INF/wsdl/a/Foo.wsdl
+ <wsdl-publish-location>file:/home/user1/publish
+ </wsdl-publish-location>
+ The final wsdl will be stored in /home/user1/publish/a/Foo.wsdl
+-->
+<!ELEMENT wsdl-publish-location ( #PCDATA )>
+<!--
+ The enterprise-beans element contains additional information about
+ the beans. These informations, such as jndi names, resource managers and
+ container configurations, are specific to jboss and not described in
+ ejb-jar.xml.
+ jboss will provide a standard behaviour if no enterprise-beans element
+ is found, see container-configurations, jndi-name and resource-managers
+ for defaults.
+ Used in: jboss
+-->
+<!ELEMENT enterprise-beans ((session | entity | message-driven)*)>
<!--
The entity element holds information specific to jboss and not declared
@@ -1552,13 +1596,13 @@
-->
<!ELEMENT port-component-name (#PCDATA) >
-<!-- Absolute path starting with web context root to form fully qualified
-endpoint address for a web service endpoint. The port component uri, if present
+<!-- Relative path that is appended to the <context-root> element to form fully qualified
+endpoint address for a web service endpoint.
+For backwards compatibility, it may also be the absolute path starting with web context root
+to form fully qualified endpoint address for a web service endpoint. In this case, the port component uri
must contain at least two token seperated by '/'. The first token is the web context root,
which must be identical among all port component uris in a given deployment.
-If this element is not present, the web context root will be derived from the
-deployment canonical name.
Used in: port-component
-->
@@ -1580,19 +1624,8 @@
-->
<!ELEMENT transport-guarantee (#PCDATA)>
-<!--
-Runtime information about a web service.
-wsdl-publish-location is optionally used to specify
-where the final wsdl and any dependent files should be stored. This location
-resides on the file system from which deployment is initiated.
--->
-<!ELEMENT webservice-description ( webservice-description-name, wsdl-publish-location? )>
-<!--
-Unique name of a webservice within a module
--->
-<!ELEMENT webservice-description-name ( #PCDATA )>
<!--
This is a valid URL pointing to a final WSDL document. It is optional.
@@ -1611,24 +1644,11 @@
-->
<!ELEMENT wsdl-override ( #PCDATA )>
-<!--
-file: URL of a directory to which a web-service-description's wsdl should be
-published during deployment. Any required files will be published to this
-directory, preserving their location relative to the module-specific
-wsdl directory(META-INF/wsdl or WEB-INF/wsdl).
-Example :
- For an ejb.jar whose webservices.xml wsdl-file element contains
- META-INF/wsdl/a/Foo.wsdl
- <wsdl-publish-location>file:/home/user1/publish
- </wsdl-publish-location>
- The final wsdl will be stored in /home/user1/publish/a/Foo.wsdl
--->
-<!ELEMENT wsdl-publish-location ( #PCDATA )>
<!--
Activation config
|