Hi dms
I am sorry for my late reply , if you deploy service as archive file there
has to be a services.xml describing the service then only that would be a
valid service, second in current impl you need to list all the operation
that you need to publish in services.xml (if you have 4 ops in wsdl and if
you list only 3 ops in services.xml then only those 3 will be available to
invoke.) , but I don't know this is right or wrong.
But as I can see some user want to use third party wsdl and want only to
publish few functionally of them , in that case we can write his
services.xml including the operation that he need to publish.
???????????
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Davanum Srinivas" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, January 06, 2006 3:12 AM
Subject: Re: [Axis2] New feature - making java class a web service
Deepal,
If i run w2j on the WSDL for AXIS2-243
(http://issues.apache.org/jira/secure/attachment/12321416/DLDataService.wsdl)
and run the server as per my prev instructions, i don't see the
operations *IF* i don't drop my wsdl. If i drop my wsdl in resources
all's well. So basically there is a problem filling up the operations
of the AxisServer IF the wsdl is missing.
thanks,
dims
On 1/4/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Hi all;
Sanjiva and I came up with the idea of providing a way to make a java
class
into AxisService , so I implemented that last night and it work as we
wanted. I feel that a very cool feature so if some one does not like to
write services.xml or wsdl and in the mean while he wants to make java
class
into web service now he can do that.
the only requirement is the corresponding java file should be there in the
class path , any way I will improve this to take actual java class not the
name of the java class , in the mean while if I have time I will modify
web
admin guide to support this.
Note : To support any (not all) data types I made operation message
receiver
as RPCMessageReciver.
any comments ...... ?
Thanks,
Deepal
................................................................
~Future is Open~
--
Davanum Srinivas : http://wso2.com/blogs/
