![Red Hat Application Server Manual Download Page 229](http://html.mh-extra.com/html/red-hat/application-server/application-server_manual_1427406229.webp)
Chapter 29. Web Services with JOnAS
221
Ù
!-- The endpoint interface defining methods exposed --
Ú
Ù
!-- for the endpoint
--
Ú
Ù
service-endpoint-interface
Ú
org.objectweb.ws.servlets.wsendpoint.WSEndpointSei
Ù
/service-endpoint-interface
Ú
Ù
!-- Link to the J2EE component (servlet/EJB)
--
Ú
Ù
!-- implementing methods of the SEI
--
Ú
Ù
service-impl-bean
Ú
Ù
!-- name of the servlet defining the JAX-RPC endpoint
--
Ú
Ù
!-- can be ejb-link if SSB is used (only in EjbJar !)
--
Ú
Ù
servlet-link
Ú
WSEndpoint
Ù
/servlet-link
Ú
Ù
/service-impl-bean
Ú
Ù
!-- The list of optional JAX-RPC Handlers --
Ú
Ù
handler
Ú
Ù
handler-name
Ú
MyHandler
Ù
/handler-name
Ú
Ù
handler-class
Ú
org.objectweb.ws.handlers.SimpleHandler
Ù
/handler-class
Ú
Ù
!-- A list of init-param for Handler configuration --
Ú
Ù
init-param
Ú
Ù
param-name
Ú
param1
Ù
/param-name
Ú
Ù
param-value
Ú
value1
Ù
/param-value
Ú
Ù
/init-param
Ú
Ù
init-param
Ú
Ù
param-name
Ú
param2
Ù
/param-name
Ú
Ù
param-value
Ú
value2
Ù
/param-value
Ú
Ù
/init-param
Ú
Ù
/handler
Ú
Ù
/port-component
Ú
Ù
/webservice-description
Ú
Ù
/webservices
Ú
29.2.5. The Optional jonas-webservices.xml
The
jonas-webservices.xml
file is collocated with the
webservices.xml
. It is an optional De-
ployment Descriptor (required only in some cases). Its role is to link a
webservices.xml
to the Web
Application in charge of the SOAP request dispatching. In fact, it is only needed for an EJB-JAR (the
only one that depends on another servlet to be accessible with HTTP/HTTPS) that does not use the
Default Naming Convention used to retrieve a Web Application name from the EJB-JAR name.
Convention:
ejbjar-name
.jar
will have an
ejbjar-name
.war
Web Application.
Example:
Ù
jonas-webservices xmlns="http://www.objectweb.org/jonas/ns"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.objectweb.org/jonas/ns
http://www.objectweb.org/jonas/ns/jonas_j2ee_web_services_4_0.xsd"
Ú
Ù
!-- the name of the webapp in the EAR
--
Ú
Ù
!-- (it is the same as the one in application.xml) --
Ú
Ù
war
Ú
dispatchingWebApp.war
Ù
/war
Ú
Ù
/jonas-webservices
Ú
29.2.6. Changes to jonas-web.xml
JOnAS allows the developer to fully configure an application by setting the hostname, the context-
root, and the port used to access the Web Services. This is done in the
jonas-web.xml
file of the
dispatching Web Application.
Summary of Contents for Application Server
Page 1: ...Red Hat Application Server JOnAS User Guide ...
Page 8: ......
Page 22: ...14 Chapter 1 Java Open Application Server JOnAS a J2EE Platform ...
Page 58: ...50 Chapter 3 JOnAS Configuration ...
Page 66: ...58 Chapter 5 JOnAS Class Loader Hierarchy ...
Page 78: ...70 Chapter 6 JOnAS Command Reference ...
Page 80: ......
Page 86: ...78 Chapter 7 Developing Session Beans ...
Page 136: ...128 Chapter 9 Developing Message Driven Beans ...
Page 142: ...134 Chapter 10 Defining the Deployment Descriptor ...
Page 148: ...140 Chapter 11 Transactional Behavior of EJB Applications ...
Page 158: ...150 Chapter 14 EJB Packaging ...
Page 162: ...154 Chapter 15 Application Deployment and Installation Guide ...
Page 164: ......
Page 176: ...168 Chapter 18 WAR Packaging ...
Page 178: ......
Page 184: ...176 Chapter 20 Defining the Client Deployment Descriptor ...
Page 186: ...178 Chapter 21 Client Packaging ...
Page 188: ......
Page 192: ...184 Chapter 23 EAR Packaging ...
Page 194: ......
Page 200: ...192 Chapter 24 JOnAS Services ...
Page 204: ...196 Chapter 25 JOnAS and the Connector Architecture ...
Page 222: ...214 Chapter 27 Ant EJB Tasks Using EJB JAR ...
Page 234: ...226 Chapter 29 Web Services with JOnAS ...
Page 236: ......
Page 260: ...252 Chapter 34 How to use Axis in JOnAS ...
Page 270: ...262 Chapter 36 Web Service Interoperability between JOnAS and BEA WebLogic ...
Page 296: ......