Dinesh Premalal [EMAIL PROTECTED] writes:
Manoj Rao [EMAIL PROTECTED] writes:
Hi all,
Can anyone please explain how different is the addition of the following
line under operation name helpful?
parameter name=wsamapping Calculator#add/parameter
BTW this parameter value should be a URL
Hi Manoj,
Manoj Rao [EMAIL PROTECTED] writes:
Hi Dinesh,
Thanks for the reply. I was using axis2c 0.90 till recently and now
migrated to 1.0 the same services.xml doesn't work here is there
anything I need to change in axis2.xml before using it? Sample of my
working services.xml is the
Did you copy axis2.xml file form 0.90 to 1.0.0? They are not compatible,
there are minor changes. You have to use axis2.xml that comes with 1.0.0.
However, we did not change services.xml as far as I can recall.
It helps to have a look into the services.xml file to get an idea on
what is going
Looking at the back trace, the problem is most probably with the service
library.
Please try to re-compile the service. Also make sure the old libs form
0.90 are not in the library path, when you compile and run the service
and client.
Samisa...
Manoj Rao wrote:
Ok Maybe I was not clear in
Hi Samisa,
Yes I am using axis2.xml from 1.0.0 version. If you want to have a look
into my services.xml this is how it looks
===
service name=MyService
parameter name=ServiceClass
locked=xsd:falseMyService/parameter
description
This is
Hi Sharada,
Could you pls send us the generated client code?
Then we can see what's wrong with it. Reading the log it's clear that
Rampart is not in the outgoing path for the generated client. So there
is no way of adding security headers.
Also we believe that you have specified AXIS2C_HOME
