First you have to write a services.xml , in your case it may like below;
<service name="FooService" scope="application"
targetNamespace="urn:FooService">
<parameter name="ServiceClass"
locked="xsd:false">net.foo.SchedulerServiceWs</parameter>
<schema schemaNamespace="urn:FooService"/> [optionla]
<messageReceivers>
<messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out";
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
</messageReceivers>
<service>
Next create a service archive file , then you are done :)
Stuart Robertson wrote:
> We're currently using Axis 1.2 to expose a java web service directly,
> with the WSDL generated at runtime (yes, I know "wsdl first" is the
> best practice :-). I'm trying to find out how this would be done with
> Axis 2. I've found plenty of docs about data binding using AXIOM and
> XmlBeans, but haven't seen anything describing this sort of
> transparent binding. Here's how we're setting up Axis 1.2 to do what
> I'm hoping to also do using Axis 2 (this is from our server-config.wsdd):
>
> <service name="SchedulerService" style="wrapped">
> <parameter name="className" value=" net.foo.SchedulerServiceWs"/>
> <parameter name="allowedMethods" value="*"/>
> <parameter name="scope" value="Application"/>
> <parameter name="alias" value="FooService"/>
> <namespace>urn:FooService</namespace>
> <beanMapping qname="impl:ScheduleInfoTO" xmlns:impl="urn:FooService"
> languageSpecificType="java:net.foo.ScheduleInfoTO"/>
> </service>
--
Thanks,
Deepal
................................................................
~Future is Open~
