axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepal Jayasinghe <dee...@opensource.lk>
Subject Re: services.xml
Date Mon, 01 Jan 2007 16:37:18 GMT
Hi Vasil ;

We have a schema file for services.xml in the xdoc directory in the svn
(xdocs\1_1\resources\schemas) , but it is not up to date with the recent
changes. I will make those changes and commit them.

Thanks
Deepal

> Hi Yamini,
>
> Thank You for the reply.
>
> What I am looking for is a really complete services.xml spec or a
> schema definition.
>
> Best regards,
>   Vasil
>
> On 12/28/06, * Hemanth, Yamini (MSAS Sys Dev IBD)*
> <Yamini.Hemanth@morganstanley.com
> <mailto:Yamini.Hemanth@morganstanley.com>> wrote:
>
>
>         Hi Vasil,
>
>
>         Please find below the description of services.xml file.
>
>
>          
>
>         * Writing services.xml
>
>     The description of services are specified using services.xml. Each
>     service archive file needs to have a services.xml in order to be a
>     valid service and it should be available in the META-INF directory
>     of the archive file. A very simple services.xml is shown below:
>
><service name="name of the service" scope="name of the scope" class="full qualifide
name the service lifecycle class"   targetNamespace="target namespase for the service">
>
>    <description> The description of the service  </description>  
>
>    <transports> 
>       <transport>HTTP</transport>
>    </transports>
>    
>    <schema schemaNamespace="schema namespace"/> 
>
>     
>    <messageReceivers>
>            <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out
> <http://www.w3.org/2004/08/wsdl/in-out>"
>                             class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
>    </messageReceivers>
>     
>     <parameter name="ServiceClass" locked="xsd:false">
>org.apache.axis2.sample.echo.EchoImpl</parameter>
>    
>    <operation name="echoString" mep="operation MEP"> 
>        <actionMapping>Mapping to action</actionMapping>
>
>        <module ref=" a module name "/>
>        <messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
>    </operation>
>  </service>
>
>     *name*: The service name will be the name of the archive file, if
>     the .aar file contains only one service, or else the name of the
>     service will be the name given by the name attribute.
>
>     *scope*: (Optional Attribute) The time period in which runtime
>     information of deployed services will be available. Scope is of
>     several types- "Application", "SOAPSession", "TransportSession",
>     "Request". The default value (if you dont put any value) will be
>     "Request"
>
>     *class*: (Optional attribute) To specify the full qualified name
>     of the service lifecycle implementation class. ServiceLifeCycle
>     class is usefull when you want to do some tasks when the system
>     start and when it shutdowns.
>
>     *targetNamespace*: (Optional Attribute) Target name space of the
>     service, and this value will be used when generating the wsdl , if
>     you do not specify this value , then the value will be calculated
>     from the package name of the service impl class
>
>     *description*: This is an optional element if you want to display
>     any description about the service via Axis2 web-admin module, then
>     the description can be specified here.
>
>     *transports* : The transports that the service is going to be
>     exposed to. This is an optional element. If the transport element
>     is not present then the service will be exposed in all the
>     transports available in the system. The transport child element is
>     there to specify the transport prefix (the name of the transport
>     specified in axis2.xml).
>
>     *parameters:* A services.xml can have any number of top level
>     parameters and all the specified parameters will be transformed
>     into service properties in the corresponding AxisService. There is
>     a compulsory parameter in a services.xml called ServiceClass which
>     specifies the java class which really does the job and the class
>     will be loaded by the MessageReceiver.
>
>     *operations :* If the service impl class is java, then all the
>     public methods in that service will be exposed and if the user
>     wants to override it then he has to add the "operation" tag and
>     override it. In the case of non-Java or if you do not have a
>     service class, then all the operations the user wants to expose by
>     the service has to be indicated in the services.xml and the
>     correct way of specifying is as follows:
>
>    <operation name="echoString">
>        <module ref=" a module name "/>
>        <messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver
>"/>
>    </operation>
>
>     The only compulsory attribute here is "name", which represents the
>     operation name that is going to be exposed. Any operation can
>     contain module references as well as any number of parameters. The
>     most interesting thing is that one can register custom message
>     receivers per operation, then the registered message receiver will
>     be the message receiver for the corresponding operation. If one
>     does not specify the message receiver, then the default message
>     receiver will do the job.
>
>      
>     Regards,
>     ** 
>     *Yamini Hemanth *
>     <mailto:yamini.hemanth@morganstanley.com>
>      
>
>     ------------------------------------------------------------------------
>     *From:* Vasil Benov [mailto:benovv@gmail.com
>     <mailto:benovv@gmail.com>]
>     *Sent:* Wednesday, December 27, 2006 2:41 PM
>     *To:* axis-user@ws.apache.org <mailto:axis-user@ws.apache.org>
>     *Subject:* services.xml
>
>     Hello,
>
>     is there a thorough description of the <services.xml> file.
>
>     Best regards
>
>     -- 
>     Vasil Benov,
>     Mobile: +359(0)889/202682
>     @-mail: benovv at gmail dot com
>     ICQ: 140269988
>
>     GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259  DE12 ACF3 177C 8906 0908
>     Public Key URL:
>       1) http://www.student-zw.fh-kl.de/~vabe0001/misc/key.asc
>     <http://www.student-zw.fh-kl.de/%7Evabe0001/misc/key.asc>
>       2) http://sks.keyserver.penguin.de/
>     ------------------------------------------------------------------------
>
>     NOTICE: If received in error, please destroy and notify sender.
>     Sender does not intend to waive confidentiality or privilege. Use
>     of this email is prohibited when received in error.
>
>
>
>
> -- 
> Vasil Benov,
> Mobile: +359(0)889/202682
> @-mail: benovv at gmail dot com
> ICQ: 140269988
>
> GPG Fingerprint: 2CDC 5DA0 4C0A 7C06 5259  DE12 ACF3 177C 8906 0908
> Public Key URL:
>   1) http://www.student-zw.fh-kl.de/~vabe0001/misc/key.asc
> <http://www.student-zw.fh-kl.de/%7Evabe0001/misc/key.asc>
>   2) http://sks.keyserver.penguin.de/ <http://sks.keyserver.penguin.de/> 




---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Mime
View raw message