its implemented . So if the service impl class is implement in Java then it is not require to have any operation tag in services.xml unless user want to override something.

But I think we need to improve that , meaning user should be able to control the operation that he need to expose , currently user dose not have any control over that and all the public methods in service impl class will be exposed.

Thanks,
Deepal
................................................................
~Future is Open~

----- Original Message ----- From: "Davanum Srinivas" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, January 18, 2006 9:51 AM
Subject: Re: Axis2-0.94 deployment and client usage


Deepal,

Is the "Service Operations" behavior already implemented in SVN? do we
need to track it via a JIRA issue?

thanks,
dims

On 1/17/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Hi all;

sorry for late reply :(

Service name :
  well , if the services.xml (irrespective of archive file or directory)
contains <service> </service> as its root element in that case the name of
the service will be the name of the aar (or name of the directory) , if
there is name attribute then that will be ignored.
 if the services.xml contains
<serviceGroup>
   <service name="foo">
  </service>
  <service name="baa">
  </service>
</serviceGroup>
in this case name of the service group will be the name of the archive file
, and name of the services will be the name attribute of each service.

Service Operations
There was a mail thread in the mailing list about that topic and we came to
conclusion that , we are going to display all the public method in the
service impl class. And using services.xml user can override or add
parameters to those operation. IF there is a wsdl in META-INF then all the
operations in the portType will be published and user can override them
using services.xml.


Thanks,
 Deepal
................................................................
~Future is Open~

----- Original Message -----
From: "Davanum Srinivas" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Saturday, January 14, 2006 8:53 PM
Subject: Re: Axis2-0.94 deployment and client usage


Ajith,

i think IF the name is NOT present then we should use the directory
name...what do you think?

Actually i think it is the %USERPROFILE%\.axis2. i could be wrong.

-- dims

On 1/14/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
> Hi steve,
>  Here's an attempt to anwer your issues :)
>
>
> > 1) service name
> >    - if the .aar file has not the same name as the attribute 'name' of
> > the
> > 'service' element in the 'services.xml', the name of the .aar > > file
> will
> >      be the service name the service is deployed with, e.g.:
>
>  For the single service case the serviceName attribute is ignored
>>>>>>>
>>>>>>>>>>>>>
>
> > 2) service operations
> >
> >    independet of the operations i "mount" in the ' services.xml', ALL
> opeations
> >    of the service class will be shown on the service list
>
>  Hmm.. This could be a bug :(. the default behavior is to expose all the
> public methods but if the user specifies any then only those methods > need
> to
> be exposed. We'll check it out further.
>
> > another point ..
> >
> > i want to use the 'EchoBlockingDualClient' from the userguide, but i > > get
> an
> > exception: 'module.xml not found  for the module :   addressing;'
> >
> > on the axis2 homepage users are advised to remove the .axis2 dir and
> create a
> > new one. my question:
> > where do i have to place this dir using windows? i tried several > > places
> (root of
> > my hdd, dir the client runs in, ..) and it didn't worked out.
> > what about the 'module.xml'?
>
> The .axis directory is created in the users home. it's usually > something
> like C:\Documents and Settings\${user} but if you've set a custom home
> check
> the values of the HOMEPATH and HOMEDRIVE environmental variables just to
> make sure
>
> > thanks in advance,
> > steven
> >
>
>
>
> --
>  Ajith Ranabahu


--
Davanum Srinivas : http://wso2.com/blogs/





--
Davanum Srinivas : http://wso2.com/blogs/


Reply via email to