Hi Tony,
There is a problem with your client code.. You have sent the
return type as Param and your type casting the result to a ArrayList..
So, modify your Client.java file and you need to modify the statement
call.setReturnClass(Param.class)...
regards
Venkatesh
On Thu, 5 Feb 2004, To
I am attempting to execute two distinct web services calls to two separate systems
that perform different tasks. I took the wsdl for each web service, and using the Axis
wsdl2java tool, generated proxy code to connect to each.
I was successful! I was able to make a SOAP call to and receive the
Anne Thomas Manes wrote:
I'm not sure that I understand your error, but I did notice that you
haven't defined a type for the "lang", "name", and "path" element
definitions.
Yes. They should be xs:string.
When using Document style services (which you are), you must reference
an element definiti
Valerie -
Place an onFault method in the handler to intercept faults. The
signature is ' public void onFault(MessageContext msgContext)'
/Chris
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 05, 2004 4:08 AM
To: [EMAIL PROTECTED]
Subject:
Hi Tony Blair,
Please take a look at the attached classes,
WSDD file, request, response etc…
There is nothing wrong with the axis
neither any bug. The issue was with your WSDD file. I wrote it little different
way. Method signature etc are same just added the package name and serial
I'm not sure that I understand your error, but I did notice that you
haven't defined a type for the "lang", "name", and "path" element definitions.
When using Document style services (which you are), you must reference an
element definition in the definition (which you did). When using RPC
sty
I modified classes in the ora.apache.axis.encoding.ser
package that deal with bean and array serialization so that I can specify an
interface in my wsdd that is implemented by a corresponding JavaBean. A few
places expect to deal with a concrete class (e.g., creating new instances, the
"ab
Title: RE: Logging incoming and outgoing messages ?
Hello Benjamin,
Of course you will have to your own interface and Impl classes together
with your handler classes also. Please make sure all these classes are in your classpath,
usually putting then in classes folder in ../webapps/axi
HI Naveen,
I am very new to this. I am not sure if I am following your instructions. I am hoping there is a simpler solution to this.
Thanks,
Tony.Navneet Joneja <[EMAIL PROTECTED]> wrote:
Sounds like bug #17017 to me. If it is: it's a bug in the code-generator. Tweaking the generated code fo
For obscure reasons, I am interposing a adaptor web service between a client
and the target web service, in order to manipulate the SOAP envelopes sent
by the client and returned by the target service.
Presumably this could be done better using handlers, but I have to defer
that approach until it
Matt -
You need to specify a custom WSDL port type in the WSDD.
For example,
http://www.oreilly.com/axis/MessageService"/>
Axis will generate a service with a /definitions/[EMAIL PROTECTED] of
'MessageService' and a /definitions/service/[EMAIL PROTECTED] of 'MessagePort'
and a /definit
Valerie --
Throwing an AxisFault is the correct methodology to use.. maybe you
need to post some code snippets, wire dump, and configuration
information.
To start isolating the issue, use tcpmon to determine if the custom
fault is returning over the wire
/Chris
-Original Mess
Hi Bill,
I found the WebServiceTester from Optimyz Software is great Web Services
Testing Tool. I used their 2.1 version at HP and it works really well
for our services. It is the "OUT OF BOX" tool I ever encountered. No
programming at all. Not even a single line of scripts. You can specify
the te
Sounds like bug #17017 to me. If it is: it's a bug in the code-generator.
Tweaking the generated code for the containing bean should
help.
Or
use 1.1 RC2, that's the only version of Axis that I saw actually do the right
thing, for a brief while before 1.1 was released.
-
Navneet.
-
Title: RE: Logging incoming and outgoing messages ?
Hi,
No just read up on handlers, you can have them
configured in the server wsdd file or
the client wsdd file. The loghandler examples in
the axis samples directory is a good
starting point as mentioned
earlier.
Greetz
Leo
- Origin
Title: [newbie] How can I create a servlet which just listen for SOAP message?
In the JAXM spec, there is a class JAXMServlet for listening SOAP message, but I can't find something equivalent in Axis?
Could someone please tell me if there is a similar class for that purpose?
On the related s
Hi Venkatesh,
Thanks for the suggestion. I slightly modified my code from yesterday where my bean takes a Collection and my service also returns a Collection. Based on the error I get I am not sure if the ser/deser are the problem. Here is the error and thanks for all the help you can give me.
Thanks, I think what you're doing makes sense. My customer is specifically interested
in using an off-the-shelf tool, so I would have to work at convincing them to go the
JMeter approach. I proposed this, but an in-house programmer had bad experience with
JMeter, so I think I'm out of luck unt
Have you tried setting some of the AxisFault fields explicitely?
AxisFault myFault = AxisFault.makeFault(e);
myFault.setFaultReason("some reason...");
myFault.setFaultDetailString("some info...");
throw myFault;
I'm not sure if it'l
Title: RE: Logging incoming and outgoing messages ?
Hi,
so for
my application I`m just implementing the SoapBindingImpl. Do I have to change
the axis.jar to create thes logs ?
Or is
there some other way ?
greets
benjamin
-Ursprüngliche Nachricht-Von: Leo de Blaauw
[mailto:[
Hi Benjamin,
Look at org/apache/axis/handlers/LogHandler.java source code. It
logs the request and response in axis.log file. You can modify this to
write the messages into two files.
regards Venkatesh
On Thu, 5 Feb 2004, Benjamin Marcel Flohr wrote:
> Sorry, I`m a nwebie here. I dont kn
Title: RE: Logging incoming and outgoing messages ?
Hi,
Just log them in handlers on the incoming and outgoing requests.
Greetz
Leo
-Oorspronkelijk bericht-
Van: Benjamin Marcel Flohr [mailto:[EMAIL PROTECTED]]
Verzonden: donderdag, februari 2004 14:41
Aan: [EMAIL PROTECTED]
Onde
Sorry, I`m a nwebie here. I dont know now if my last Mail comes to you, but I hope
this one will and please dont worry if its already the second one ...
So, I`m in the need for logging all outgoing and incoming SOAP-Messages from Axis into
two different logs.
for example outgoing.log, incoming.l
Hi,
I would just turn on SSL
debug in the system property, seems like an SSL related
problem.
Leo
-Oorspronkelijk bericht-Van: Safdar Ali
[mailto:[EMAIL PROTECTED]Verzonden: donderdag, februari 2004
14:32Aan: Axis UserOnderwerp: Socket write
error
Hi all,
why does the
Hi all,
why does the following error
occurs
java.net.SocketException: Software caused
connection abort: socket write
error at
org.apache.axis.AxisFault.makeFault(AxisFault.java:129)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:131)
at
org.a
Peter,
Yes, tcpdump was very easy to use. Thanks very much for the reply.
Thanks to everyone else who replied too. I am going to try out ethereal too
and post the results for the group.
Since I already have tcpdump available to use, this was much quicker. I did
download ethereal but did not tr
> Hello,
>
> could somebody explain me how I can manage that I can log all outgoing and incoming
> soaprequests will be logged in one or two seperate logfiles ?
>
> Thank you for your help
> Benjamin
>
Title: bug in latest nightly build ?
Hi,
Because of the fact that we experienced timeouts on attachments(DIME) trough the managedmemorydatasource
we tried yesterday to have our aplication use an axis.jar constructed from the latest nightly build. The timeouts
are now gone however now we are
On Wed, 4 Feb 2004, Christopher Blunck wrote:
> On Wed, Feb 04, 2004 at 12:27:27PM -0800, Navneet Joneja wrote:
> > Try something like ethereal ( http://www.ethereal.com)
>
> yes!
>
> i say this time and time again -
>
>
> linux users - you will find it *far easier* to sniff the network via ethe
The wssd for the service looks like this :
and here is the handler :
(See attached file: handler1.java)
this handler works very well except for error handling.
Another important thing is I also h
30 matches
Mail list logo
