No, java does not support changing the value of parameters to methods. You
need to wrap in/outs in a holder object. While the value of the holder
cannot be changed, its attributes can be.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 1
I doubt if you can do anything through configuration. The last time I
checked if an exception is sent to a log4j file logger, the stack trace is
automatically logged. You could write your own custom appender that did not
log the exceptions.
> -Original Message-
> From: Josh Emmons [mailto:
If you expect help you'll need to more specfic about what does not work.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 04, 2003 3:28 PM
> To: [EMAIL PROTECTED]
> Subject: How to map java.sql.Timestamp in deploy.wsdd?
>
>
> Hi,
>
Then I think you need to subclass AxisFault so you can set the fault code.
> -Original Message-
> From: Marco Spinetti [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 29, 2003 7:43 AM
> To: [EMAIL PROTECTED]
> Subject: Fault Code
>
>
> I've a question about axis fault management.
>
> I
ent side whereas with the .NET platform, I parse it out of
> the detail element returned in the fault.
>
> All that said, I am using the nightly builds as opposed to
> the 1.0 release.
>
> Cory
>
>
> -Original Message-
> From: Hansen, Richard [mailto:[EMAIL
> > specific exception. I'm successfully catching my specific
> > exception on the client side with both Axis and .NET
> > platforms -- Axis manages to throw my exception type on the
> > client side whereas with the .NET platform, I parse it out of
> > the de
If you define the exceptions in your WSDL as "faults" in the appropriate
pacles. Then wsdl2Java will generate your exception classes and create the
required config setup in the stubs and skeletons it generates.
My notes of axis fault handling:
Faults
- For all practical purposes a client programme
Is axis configured to handle you custom exceptions? If you look at
samples.faults in the wsdd it defines the exceptions like below. When I
define faults in my wsdl, then wsdl2Java puts configuration code in the
stubs and skeleton classes.
...
http://localhost:8080/ch09/services/Employee";
Other than the effort required to configure Axis, I don't see why it would
make much difference.
> If I have a Java interface that I am going to be turning into
> a web service (with AXIS and the Java2WSDL and WSDL2Java tools).
>
> Should I define a hierarchy of exception classes that could be
>
I suppose it does that because Call.invoke() only throws AxisFaults. If you
throw an exception without defining it to axis then axis wraps it in a
AxisFault. If you define application specific exceptions they seem to need
descend from AxisFault so they get serialized. If you don't want to see any
"
Title: Message
It can
only come in on the port the web server accepts HTTP requests
on.
-Original Message-From: Fabien Guillaume
[mailto:[EMAIL PROTECTED]Sent: Monday, August 18, 2003 9:22
AMTo: [EMAIL PROTECTED]Subject: Get Client
Port
Hello,
I am trying to
coll
What do you mean by "create"? Generating code and compiling it into a class
or just constructing using new. This is all just Java. You can call any
object you create, just like usual.
> -Original Message-
> From: Frank Schoenau [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 15, 2003 11:0
Are the web services classes on the Axis classpath?
> -Original Message-
> From: Jorge Alberto Rodriguez Suarez [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 12, 2003 3:16 PM
> To: [EMAIL PROTECTED]
> Subject: AdminClient Exception...
>
>
> Hi there!
>
> When iam making:
>
> java -
I have not tested this, but I would have expected some sort of Fault on the
client side. I am not exactly sure what you mean by not running though. It
seems to me that there are several types of "not running". Assuming HTTP:
1) The web server is down
2) Axis servlet unreachable
3) Axis can't find
Separate WSDL files proabably. Unless you can get away which
services are valid for which client type.
-Original Message-From: Doss Markus
[mailto:[EMAIL PROTECTED]Sent: Monday, August 11, 2003
10:03 AMTo: [EMAIL PROTECTED]Subject: WSDL
generation
Hi
all,
we pr
(vertical solution developer) I should not
> have to know the intricacies of interface defn. That is why
> CORBA is dead. Because it is disgusting to use.
>
> What is the point of a web services toolkit if it doesnt
> understand WSDL?
>
> But then of course I could just dig ou
Title: Message
http://schemas.xmlsoap.org/wsdl/
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Sent: Friday, August 08, 2003 2:38
PMTo: [EMAIL PROTECTED];
[EMAIL PROTECTED]Subject: WSDL SchemaDTD
Hi
folks,
Is there a WSDL schema or
-crafting.
>
> In any case, for the moment I definitely recommend using one
> of the tools
> listed below to help you create and validate WSDL files.
>
> Anne
>
> - Original Message -
> From: "Hansen, Richard" <[EMAIL PROTECTED]>
> To: <[EMAIL
Is it
doc/literal? There is a bug in Axis with doc/literal services with no
params.
-Original Message-From: Kareem Ghazal
[mailto:[EMAIL PROTECTED]Sent: Friday, August 08, 2003 5:13
AMTo: [EMAIL PROTECTED]Subject: Re: (500)Internal
Server Error
Hello,
I checked the
Here are my steps.
1. Create WSDL
2. Run WSDL2Java to generate client and server classes.
3. Implement service using generated server skeleton.
I am convinced that starting with WSDL is best. WSDL is the public interface
for you service. Starting with a WSDL file as the definition avoids problems
Too
bad the wsdl2java ant task does not support the noWrapped param (at least in
v1.1).
-Original Message-From: Anne Thomas Manes
[mailto:[EMAIL PROTECTED]Sent: Monday, August 04, 2003 8:15
PMTo: [EMAIL PROTECTED]Subject: Re:
encoding.ser.castor
As I think I mentioned bef
Or you could start with the wsdl. Create valid wsdl then generate the java
classes from it. I have come to the conclusion that starting with wsdl is a
"best practice" just to avoiud conversion error and differences.
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
>
Title: Need WSDL for this SOAP message
Here
is a wsdl I used to create a doc/literal service. The WSDL is defined as usual,
with all the standard parts, no matter what style.
name="demo"
targetNamespace="http://www.tlr.bis.com/rating.wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmln
Posting the same problem multiple times won't help.
Why
did you do this, it is not needed and generally considered bad form for web
applications?
> I have copied all the jar files in the
axis/web-inf/lib directory to TOMCAT_HOME/common/lib.
You don't provide much information that woul
Constants? If they are constants why would they be parameterized. If you
mean "default", then yes, you can do that with xml schema. You should be
able to sue anything in your type definitions that you can do with XML
schema. Whether any WSDL tool would use the information or not is
questionable.
The
number one thing that I see is that the WS-I basic profile does not allow the
use of RPC-encoded format. I think this pretty much means using
document/literal. There are other things but a lot of the requirements seem to
have to do with the wsdl for your service.
Rick Hansen
-Orig
Maybe I am missing something? But the deployment descriptors for the bug
example and and your example are different. Wouldn't this make a
difference. I have experienced the exact same "bug" using document/literal
message style using axis 1.1 from june 13th.
Rick Hansen
> -Original Message
Subject: RE: Possible bug in Axis while creation of stub classes from
> WSDL2Java for Document style Web Service
>
>
> No my method is not taking any input parameters.
>
> regards,
> Naresh Agarwal
>
> -Original Message-
> From: Hansen, Richard [mailto:[E
Are there any input parameters to the method? I noticed that when I did
doc/literal call that took no parameters then the response was not extracted
correctly. But when I added input params everything worked. Though I can't
imagine why/how this should affect the response.
Rick Hansen
> -Origi
xception;
>
> but, I am also expecting the Folder class to be generated in
> order to make
> it easier for the consumer to play with.
>
> I want to be able to do: port.add( new Folder(...));
>
> Sylvain.
>
>
>
>
> -Original Message-
> From: Han
Maybe I am missing something? Given that the input param is
type="types:Object" I would not have any reason to expect the Java code to
be generated with a Folder. Folder maybe in the types section but it
certainly does not appear as the message type.
Rick Hansen
> -Original Message-
> Fr
31 matches
Mail list logo
