I've finally solved my client connection problems with axis, and the problem
ended up being an issue with the naming of the bean property. Essentially,
I had a message:
false
and a class to handle this response (I'm simplifying the message structure).
I finally figured out that the wsdlToJav
- Original Message -
From: "Mitch Gitman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Sunday, November 10, 2002 15:01
Subject: RE: running Java2WSDL via reflection
> Explanation and suggestion.Apparently, Java2WSDL is quitting for the most
The logging configuration file is in axis.jar, called log4j.properties or
something similar. If you make a copy of it, tweak it to turn on debug
logging, and put the copy ahead of axis.jar in your class path, you'll get
what you need. This information is somewhere in the Axis docs, but I can't
re
On Sun, 2002-11-10 at 22:39, Tom Schuring wrote:
> One way is by using RPC-Soap that implements an RPC call like:
>
> sendMyXML( String serialisedXMLDocument )
>
> it's pretty simple to implement and does the job.
This works for me as well.
-k.
> -Original Message-
> From: Amit Khuran
Hi Mike,
So far I have only limited experience, so the following may be
"inaccurate". Hopefully someone else will correct me though!
It seems to me untidy and dangerous (from a maintenance point of view)
to be using both your "original" and "WSDL2Java generated" classes. The
development process
looks
like it works by just adding the entry to the server-config.wsdd
-Original Message-From: Tom Schuring
Sent: Monday, November 11, 2002 9:41 AMTo:
[EMAIL PROTECTED]Subject: deploying
hello,
when i deploy my
webservice with
java
org.apache.axis.client.
Someone mentioned there was an Ant task for Java2WSDL. I'll check this out, but if it calls main(), it's still going to exit.One easy workaround. Subclass Java2WSDL and call directly the run() method called by main(). Both the constructor and run() are protected.--- On Sun 11/10, Mitch Gitman < [E
Explanation and suggestion.Apparently, Java2WSDL is quitting for the most obvious reason. It's calling System.exit(): /** * Main * Run the Java2WSDL emitter with the specified command-line arguments * @param args String[] command-line arguments */public static void main(Strin
hello,
when i deploy my
webservice with
java
org.apache.axis.client.AdminClient -lhttp://localhost/axis/services/AdminService
deploy.wsdd
i notice that it
adds an entry to the:
server-config.wsdd
file for my
service.
Can i automatically
deploy my service by adding this ent
I"m having client side serialization issues and I'd like to enable debug
logging. How can I turn it on?
Hello,
I'm working through deploying my web service.
However, there's this one problem that won't
leave me alone.
I have a folder (a package) named
groceryWebService1. Within this package, I have a folder (and
hence
another package) named groceryWebService1.ws.
Note that the files wit
hello Mohammed,
what i have done is to use a startup parameter that specifies the path name to a
configuration file.. this way i can change the configuration file (i used an xml
document that loads itself as a "properties" object ) without changing the parameter.
in other words i only use the
One way is by using RPC-Soap that implements an RPC call like:
sendMyXML( String serialisedXMLDocument )
it's pretty simple to implement and does the job.
-Original Message-
From: Amit Khurana [mailto:amit.khurana@;vichara.com]
Sent: Sat 11/9/2002 1:21 AM
To: [EMAIL PROTECTED]
Cc
Forgive me -- or just ignore me -- if this question isnt totally on-topic. I manage to run Java2WSDL successfully to generate the WSDL for my web service. I manage to run it successfully whether its invoked directly or from within another Java application. But when its invoked by another appli
14 matches
Mail list logo
