[jboss-cvs] JBossAS SVN: r61589 - trunk/server/src/resources/dtd.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Mar 22 11:43:57 EDT 2007
Author: heiko.braun at jboss.com
Date: 2007-03-22 11:43:56 -0400 (Thu, 22 Mar 2007)
New Revision: 61589
Modified:
trunk/server/src/resources/dtd/jboss_5_0.dtd
Log:
Add webservice and port-component elements to DTD
Modified: trunk/server/src/resources/dtd/jboss_5_0.dtd
===================================================================
--- trunk/server/src/resources/dtd/jboss_5_0.dtd 2007-03-22 15:41:25 UTC (rev 61588)
+++ trunk/server/src/resources/dtd/jboss_5_0.dtd 2007-03-22 15:43:56 UTC (rev 61589)
@@ -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>
@@ -64,6 +71,12 @@
<resource-env-ref>
<clustered />
<cluster-config>
+ <port-component>
+ <port-component-name>
+ <port-component-uri>
+ <auth-method>
+ <transport-guarantee>
+ </port-component>
</session>
<message-driven>
@@ -155,7 +168,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?,
+ webservices?, enterprise-beans?, assembly-descriptor?,
resource-managers?, invoker-proxy-bindings?, container-configurations?)>
<!-- The loader-repository specifies the name of the UnifiedLoaderRepository
@@ -417,11 +430,59 @@
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 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, config-name?, config-file?, 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)*)>
<!--
@@ -456,7 +517,7 @@
security-proxy? , ejb-ref* , ejb-local-ref* , service-ref*, security-identity? ,
resource-ref* , resource-env-ref*, message-destination-ref* , clustered? ,
cluster-config?, method-attributes?, depends*,
- ior-security-config?, ejb-timeout-identity?)>
+ ior-security-config?, port-component*, ejb-timeout-identity?)>
<!-- Allow the session to have a unique id -->
<!ATTLIST session id ID #IMPLIED>
@@ -1532,7 +1593,14 @@
auth-method element describes the authentication method. The only supported value
for as-context is USERNAME_PASSWORD
-Used in: as-context
+For port-component, the auth-method element is used to configure the
+authentication mechanism for the web service. As a prerequisite to gaining
+access to any web service which are protected by an authorization
+constraint, a user must have authenticated using the configured
+mechanism. Legal values for this element are "BASIC", or "CLIENT-CERT".
+
+Used in: as-context, port-component
+
-->
<!ELEMENT auth-method ( #PCDATA )>
@@ -1554,7 +1622,49 @@
-->
<!ELEMENT caller-propagation ( #PCDATA) >
+<!-- The port-component element specifies a mapping from a webservice
+port-component whose service-impl-bean/ejb-link value maps to an ejb.
+
+Used in: session
+-->
+<!ELEMENT port-component (port-component-name, port-component-uri?, auth-method?,
+ transport-guarantee?) >
+
+<!-- Maps to the port-component-name in the webservices.xml descriptor.
+
+Used in: port-component
+-->
+<!ELEMENT port-component-name (#PCDATA) >
+
+<!-- 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.
+
+Used in: port-component
+-->
+<!ELEMENT port-component-uri (#PCDATA) >
+
<!--
+The transport-guarantee element specifies that the communication
+between client and server should be NONE, INTEGRAL, or
+CONFIDENTIAL. NONE means that the application does not require any
+transport guarantees. A value of INTEGRAL means that the application
+requires that the data sent between the client and server be sent in
+such a way that it can't be changed in transit. CONFIDENTIAL means
+that the application requires that the data be transmitted in a
+fashion that prevents other entities from observing the contents of
+the transmission. In most cases, the presence of the INTEGRAL or
+CONFIDENTIAL flag will indicate that the use of SSL is required.
+
+Used in: port-component
+-->
+<!ELEMENT transport-guarantee (#PCDATA)>
+
+<!--
Activation config
used in message-driven and proxy-factory-config
More information about the jboss-cvs-commits
mailing list