jakarta.servlet.resources.jakartaee_web_services_2_0.xsd Maven / Gradle / Ivy
The newest version!
Copyright (c) 2009, 2021 Oracle and/or its affiliates. All rights reserved.
This program and the accompanying materials are made available under the
terms of the Eclipse Public License v. 2.0, which is available at
http://www.eclipse.org/legal/epl-2.0.
This Source Code may also be made available under the following Secondary
Licenses when the conditions for such availability set forth in the
Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
version 2 with the GNU Classpath Exception, which is available at
https://www.gnu.org/software/classpath/license.html.
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
(C) Copyright International Business Machines Corporation 2002
...
The instance documents may indicate the published version of the
schema using the xsi:schemaLocation attribute for the Jakarta EE
namespace with the following location:
https://jakarta.ee/xml/ns/jakartaee/jakartaee_web_services_2_0.xsd
]]>
The following conventions apply to all Jakarta EE
deployment descriptor elements unless indicated otherwise.
- In elements that specify a pathname to a file within the
same JAR file, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
the JAR file's namespace. Absolute filenames (i.e., those
starting with "/") also specify names in the root of the
JAR file's namespace. In general, relative names are
preferred. The exception is .war files where absolute
names are preferred for consistency with the Servlet API.
The webservices element is the root element for the web services
deployment descriptor. It specifies the set of web service
descriptions that are to be deployed into the Jakarta EE Application Server
and the dependencies they have on container resources and services.
Used in: webservices.xml
The webservice-description-name identifies the collection of
port-components associated with a WSDL file and Jakarta XML RPC mapping.
The name must be unique within the deployment descriptor.
The port-component element associates a WSDL port with a web service
interface and implementation. It defines the name of the port as a
component, optional description, optional display name, optional iconic
representations, WSDL port QName, Service Endpoint Interface, Service
Implementation Bean.
This element also associates a WSDL service with a Jakarta XML Web Services
Provider implementation.
EmployeeService
]]>
Defines the name space and local name part of the WSDL
service QName. This is required to be specified for
port components that are Jakarta XML Web Services
Provider implementations.
Defines the name space and local name part of the WSDL
port QName. This is not required to be specified for port
components that are Jakarta XML Web Services Provider
implementations
Used to enable or disable SOAP MTOM/XOP mechanism for an
endpoint implementation.
Not to be specified for Jakarta XML RPC runtime
When MTOM is enabled, binary data above this size in bytes
will be XOP encoded or sent as attachment. Default value is 0.
Not to be specified for Jakarta XML RPC runtime
This specifies the WS-Addressing requirements for a Jakarta XML
web service. It corresponds to jakarta.xml.ws.soap.Addressing
annotation or its feature jakarta.xml.ws.soap.AddressingFeature.
See the addressingType for more information.
Not to be specified for Jakarta XML RPC runtime
Corresponds to the jakarta.xml.ws.RespectBinding annotation
or its corresponding jakarta.xml.ws.RespectBindingFeature web
service feature. This is used to control whether a Jakarta XML Web
Services implementation must respect/honor the contents of the
wsdl:binding in the WSDL that is associated with the service.
Not to be specified for Jakarta XML RPC runtime
Used to specify the protocol binding used by the port-component.
If this element is not specified, then the default binding is
used (SOAP 1.1 over HTTP)
com.wombat.empl.EmployeeService
This may not be specified in case there is no Service
Enpoint Interface as is the case with directly using an
implementation class with the @WebService annotation.
When the port component is a Provider implementation
this is not specified.
]]>
To be used with Jakarta XML RPC based runtime only.
To be used with Jakarta XML Web Services based runtime only.
The service-impl-bean element defines the web service implementation.
A service implementation can be an enterprise bean class or Jakarta
XML RPC web component. Existing enterprise bean implementations
are exposed as a web service using an ejb-link.
Used in: port-component
StockQuoteService
]]>
The webservice-description element defines a WSDL document file
and the set of Port components associated with the WSDL ports
defined in the WSDL document. There may be multiple
webservice-descriptions defined within a module.
All WSDL file ports must have a corresponding port-component element
defined.
Used in: webservices
The webservice-description-name identifies the collection of
port-components associated with a WSDL file and Jakarta XML RPC
mapping. The name must be unique within the deployment descriptor.
The wsdl-file element contains the name of a WSDL file in the
module. The file name is a relative path within the module.
The jaxrpc-mapping-file element contains the name of a file that
describes the Jakarta XML RPC mapping between the Java interaces used by
the application and the WSDL description in the wsdl-file. The
file name is a relative path within the module.
This is not required when JAX-Jakarta Enterprise Web Services based
runtime is used.
Defines the name of the handler. The name must be unique
within the module.
EmployeeService
]]>
The required value for the version is 2.0.
© 2015 - 2024 Weber Informatics LLC | Privacy Policy