selecting methods with allowedMethods param

2007-09-21 Thread Dr Janusz Martyniak
Hi All, It looked all simple when reading the docs. My goal was to expose only a few methods from the interface, so I changed allowedMethods="*" to allowedMethods="myMethod" in server-config.wsdd. Restart tomcat, point a browser to the list of services ... and: Exception - org.apache.axis.In

Re: Calling one webservice from another web service

2007-01-11 Thread Dr Janusz Martyniak
Hi, Unless you want to daisy-chain the services (client - > serviceA -> serviceB ), then you serviceA impl method would act as a client of serviceB. Is that what you originally wanted ? cheers JM Nilesh Ghorpade wrote: Hi Amit, As per my understanding what you want to do

Re: AW: ServiceLifecycle

2007-01-11 Thread Dr Janusz Martyniak
Tony Dean wrote: Here's what you need: services.xml yourService.Impl ... Hi, Are you talking about axis2 ? I'm using axis 1.4 . There is no services.xml apparently... server-config.wsdd seems to have a similar role in axis 1.4 but tags are somewhat different there. Have you

Re: AW: ServiceLifecycle

2007-01-11 Thread Dr Janusz Martyniak
Deepal Jayasinghe wrote: Hi Janusz; but, The init() is called every time I invoke the method. That will only happen if you deploy your service in request scope , if you deploy your service in application scope then that will never happen. Well, if I deploy my service as an application

Re: AW: ServiceLifecycle

2007-01-09 Thread Dr Janusz Martyniak
Dies Koper wrote: It depends on what you specify for the deployScope option. If you choose "application", the init method will be called only once. Well, I tried the lifecycle business as well (via skeletons which call imp classes explicitly in their init() method, i.e both skeletons a

redirect a call from a handler

2006-10-13 Thread Dr Janusz Martyniak
Hi All, I'm trying to redirect a call to an end-service in a client-side handler attached to the client. I'm unable to interfere with the client code (it's third party). I'm also left with client's HTTP sender which is custom. The idea is to create an intermediate service which would act as

Re: Accessing operation parameters' _values_ vs getTextContent()

2006-04-19 Thread Dr Janusz Martyniak
Hi all again, Since it is apparently not possible to get a value of an operation variable for a MessageContext without looking into the message itself, I tried the latter... and failed miserably. On Tomcat Apache Tomcat/5.5.15 java 1.5 I'm getting a message when trying to access my favour

Accessing operation parameters' _values_

2006-04-17 Thread Dr Janusz Martyniak
Hi All, I have a little 'message interceptor' deployed as a service-side handler. I can access various parts of a message passed in a 'civilised' way: public void invoke(MessageContext msgContext){ OperationDesc opDesc = msgContext.getOperation();

Re: client side chains question

2006-03-10 Thread Dr Janusz Martyniak
Yes, I want to chain services. I just realised that a axis client ( a proxy service in my case) will try to set itsef up by lookind into the client-config.wsdd file (or specified by the axis.ClientConfigFile property. It might solve my problem, since I can add client side chains w/o modifyin

client side chains question

2006-03-10 Thread Dr Janusz Martyniak
Hi all, I have a following problem. I have a web service which is third party and I can't change it. It is instructed to contact other web services (so it acts as a client here, or a proxy-service) I can deploy it how I wish, in particular with server side chains. Can I put it into the en

RE: soapenc:string rather then xsd:string ?

2005-10-07 Thread Dr Janusz Martyniak
On Fri, 7 Oct 2005, Grossberger, Guenter wrote: Hi! Although Sunil is right about starting from a WSDL you can still use Java2WSDL but you have to select "document" style and "literal" use or even better "wrapped" style instead of rpc/encoding. Best regards, Thanks Guenter, I discovered

soapenc:string rather then xsd:string ?

2005-10-07 Thread Dr Janusz Martyniak
Hi all, In my Java2WSDL generated wsdl (axis 1.2) axis uses soapenc:string as a type. Older version of axis seemed to use xsd:string. Can I revert this behaviour in the generation step? My colleague has problems using my wsdl in his workflow engine. any help will be greatly apprec