Problem resolved. Some other piece of code was overriding the web.xml
timeout by explicitly setting the AxisHttpSession timeout.
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: AxisHttpSession not timing out
Date: Tue, 05 Dec 2006 05
I have just found soapui at http://www.soapui.org/. It seems to be able to
do both types of testing and initially looks very, very good.
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Recommended script-driven or GUI tester?
Date: Fri
I'd like to test an Axis web service, doing both ad hoc testing (ideally
using a GUI) and doing larger-scale script-based testing.
The Eclipse WSUnit plug-in allows me to do ad hoc testing but it does not
appear to support cookies -- my application uses cookies for session
management but
-
From: Jarmo Doc [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Thursday, November 02, 2006 3:28 PM
Subject: Backwards compatibility, versioning
I'm having an issue with enhancing a Web Service operation to return
some
additional information. The problem is that back-level clients
I have a Java method such as:
public MyObject [] myOperation(int param);
Now Axis 1.3 java2wsdl for this yields a response signature as follows:
element name=myOperationResponse
complexType
sequence
element maxOccurs=unbounded name=myOperationReturn
type=impl:MyObject/
See if this article helps:
http://www.nabble.com/Re%3A-%3Citem%3E-in-Arrays-tf1254632.html#a3341799
From: Venkatesh Jayaraman (jvenky) [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Array is different moving from Axis 1.2 to Axis 1.4 Date: Wed,
Axis 1.3 java2wsdl generates 'schema' tags but most WSDL that I see contains
'xsd:schema' tags. The WSDL spec. also seems to suggest that 'xsd:schema'
is the only legal option.
What is the difference between these two tags and why does Axis generate the
former?
Thanks.
.
rantIs there actually anyone out there successfully using this technology
with multiple client types (Axis, gSOAP, WebSphere, .NET)? I don't see how
it's possible for anything more complex than a stock quote lookup
service./rant
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user
Thanks very much guys (Simon, Ian, Paul). Much appreciate the help. I'm
finding that I'm frequently having to debug WSDL that works fine with Axis
but not necessarily with other client tools and it's quite a challenge to
determine a) who's at fault and b) what's the lowest common denominator
I'm using java2wsdl -px.y.z z.x.y to map Java packages to a urn: namespace.
This works fine.
Now I want to generate urn: namespaces so am using java2wsdl -px.y.z
urn:z.x.y. This does *not* work fine. Specifically, in the
wsdl:definitions section of the generated WSDL it produces both
try if you post the whole WSDL before I go home tonight.
Regards,
Dies
Jarmo Doc wrote:
My WSDL document, generated directly from Java via Axis 1.3 java2wsdl,
is structured something like this:
01. wsdl:definitions targetNamespace=a.b.c xmlns:tns2=x.y.z
02. wsdl:types
03. schema
/
05. /schema
06. schema elementFormDefault=qualified targetNamespace=x.y.z
07. complexType name=MyFault
08. ... definition here ...
09. /complexType
10. /schema
11. /wsdl:types
On 3/30/06, Jarmo Doc [EMAIL PROTECTED] wrote:
Can you recommend an easily-downloadable validator? The WSDL's
]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: Axis java2wsdl fails WebSphere validator
Date: Thu, 30 Mar 2006 08:56:38 -0500
Please provide the complete WSDL so that we can help you identify the
problem.
On 3/30/06, Jarmo Doc [EMAIL PROTECTED] wrote:
Hi Anne, my
Try doing this:
catch (AxisFault ex)
{
if (ex instanceof InvalidDateException)
{
InvalidDateException myex = (InvalidDateException)ex;
// deal with myex here
}
// deal with others here
}
From: Jack Lund [EMAIL PROTECTED]
Reply-To:
isn't a subclass of
InvalidDateException.
-Jack
Jarmo Doc wrote:
Try doing this:
catch (AxisFault ex)
{
if (ex instanceof InvalidDateException)
{
InvalidDateException myex = (InvalidDateException)ex;
// deal with myex here
}
// deal with others here
}
From: Jack Lund [EMAIL PROTECTED]
Reply
Ah, seems to be a known bug:
http://issues.apache.org/jira/browse/AXIS-1642
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: axis.development.system
Date: Sat, 28 Jan 2006 13:49:25 -0800
I have switched off axis.development.system in my
-9NM1_dk/soap12WSDL.htm
I don't know how to tell Axis to use SOAP 1.2, but I assume there's a
parameter in java2wsdl and in the WSDD.
Anne
Anne
On 1/26/06, Jarmo Doc [EMAIL PROTECTED] wrote:
I believe that it's all in the transport binding:
- transport=http://schemas.xmlsoap.org/soap/http; (SOAP
When I run wsdl2java with the -s option to generate server-side code, it
generates MyServiceSoapBindingStub.java. Why? I can see the client-side
use of this stub code but what use should one make of it server-side?
Or is it a bug in wsdl2java?
Thanks.
, Jarmo Doc [EMAIL PROTECTED] wrote:
When I run wsdl2java with the -s option to generate server-side code, it
generates MyServiceSoapBindingStub.java. Why? I can see the
client-side
use of this stub code but what use should one make of it server-side?
Or is it a bug in wsdl2java?
Thanks
I have switched off axis.development.system in my server-config.wsdd file
yet Axis 1.3 continues to attach server-side stack trace to every fault. Is
there another setting that takes precedence?
globalConfiguration
parameter name=axis.development.system value=false/
/globalConfiguration
Not sure about that but I believe that you can force service?wsdl to return
a specific file by adding the following to your service definition in the
WSDD file:
wsdlFilemy.wsdl/wsdlFile
It locates the file from the classpath.
From: Rutherford, Matthew [EMAIL PROTECTED]
Reply-To:
You'd think that it would be obvious, or at least clearly and explicitly
stated in the WSDL, wouldn't you? Like version=1.1/ But no! In the
best SOAP traditions, it's as clear as mud.
I believe that it's all in the transport binding:
- transport=http://schemas.xmlsoap.org/soap/http; (SOAP
http://svn.apache.org/viewcvs.cgi/webservices/axis/branches/AXIS_1_4_FINAL/
From: françois françois [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: RE: problems to migrate from AXIS 1.2.1 to AXIS 1.3 array
serialization BUGS OR NOT?
Date: Fri, 20 Jan
For those people like me using Axis 1.3 from the regular downloads page, how
do we find out what's changed since the last official release of Axis 1.3
and how do we download and build the very latest 1.3 code including all
fixes?
Thanks.
I should have read the Wiki first.
It looks like http://ws.apache.org/axis/interim.html
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Getting fixes to released Axis 1.3?
Date: Thu, 19 Jan 2006 04:19:33 -0800
For those people like me
:
log4j.rootCategory=DEBUG, CONSOLE, LOGFILE
Any other ideas?
Thanks for your response,
Sarel
-Original Message-
From: Jarmo Doc [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 8:38 PM
To: axis-user@ws.apache.org
Subject: RE: Debugging Service
Do the samples
Guys, what's the expected schedule for the release of Axis 1.4 final? And
is there a high-level view of the changes from 1.3?
Thanks.
_
Dont just search. Find. Check out the new MSN Search!
Here are a few very basic things that I do upfront to diagnose whether or
not an Axis service is correctly deployed:
1. Is Apache alive? http://hostname
2. Is Tomcat alive? http://hostname:8080
3. Is Axis alive? http://hostname:8080/axis
4. Is Axis happy? http://hostname:8080/axis/happyaxis.jsp
Do the samples such as the echo or stock quote services run? And do they
generate server-side log4j output?
From: Sarel Botha [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: RE: Debugging Service
Date: Wed, 18 Jan 2006 10:02:33 -0500
Thank you very
-
Von: Jarmo Doc [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 17. Januar 2006 02:44
An: axis-user@ws.apache.org
Betreff: RE: bean-problem
I get the impression that you're better off using arrays rather than Java
collections, perhaps something like this (and I've not compiled or tested
this):
public
Releases are at http://ws.apache.org/axis/java/releases.html.
From: Lance Semmens [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Axis java download
Date: Tue, 17 Jan 2006 14:36:11 -
Where do I download axis from for java?
The C++ downloads are
) mentions about
QNames with '' in them. Not sure if that is what Axis is following
here, though.
Regards,
Dies
Jarmo Doc wrote:
Why does Axis wsdl2java generate the in the following? What does it
mean?
- typeDesc.setXmlType(new javax.xml.namespace.QName(a.b.c,
myexception));
This also
Why does Axis wsdl2java generate the in the following? What does it
mean?
- typeDesc.setXmlType(new javax.xml.namespace.QName(a.b.c,
myexception));
This also results in gt;myexception in the server WSDD file after I deploy
the service, for example:
- typeMapping
I get the impression that you're better off using arrays rather than Java
collections, perhaps something like this (and I've not compiled or tested
this):
public class PersonBean
{
private ArrayList telefon; // collection of TelefonBean
public TelefonBean [] getTelefon()
{
return
Note that gSOAP 2.7.6c doesn't like test/wsdl/faults2/FaultService.wsdl. In
particular it complains that:
Warning: part 'msg' uses literal style and must refer to an element rather
than a type
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: [EMAIL PROTECTED], axis
it) then run the gSOAP's
wsdl-to-code generator.
thanks,
dims
On 1/13/06, Jarmo Doc [EMAIL PROTECTED] wrote:
Note that gSOAP 2.7.6c doesn't like test/wsdl/faults2/FaultService.wsdl.
In
particular it complains that:
Warning: part 'msg' uses literal style and must refer to an element
rather
than
/axis/java/reference.html) for interop with other
stacks.
thanks,
dims
On 1/12/06, Jarmo Doc [EMAIL PROTECTED] wrote:
Apologies, I attached the wrong serialization -- that one was from an
exception that derived from Exception rather thanAxisFault (I've tried
both
and neither works unless you
My Axis 1.3 server operations throw MyException which is defined something
like this (though in reality it's more complex):
public class MyException extends AxisFault implements Serializable
{
private String mytext;
public String getMytext() {return mytext;}
public void setMytext(String
=MyException
How do I correct this behavior?
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Exceptions are killing me
Date: Thu, 12 Jan 2006 11:16:15 -0800
My Axis 1.3 server operations throw MyException which is defined something
like
It's many thousands of lines of text so let me work on a minimal sample that
also exhibits the problem and I'll get back to you. Thanks for the offer of
help dims.
From: Davanum Srinivas [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Subject: Re: Exceptions are
Thanks very much for the good idea. If I understand you, every object that
your operations return would be derived from (or explicilty include)
TestServiceResponse. If so then that would have a big impact on my WSDL
(which right now has operations that return arrays of objects, single
[Re-sending]
OK Dims, here's the XML from the standard Axis 1.3 test/wsdl/faults2 (which
is a doc/lit testcase, thus relevant to my situation).
I'd say that it's substantially similar to the XML that I personally see
with my custom exceptions, and therefore I would venture to say that it's
.
if you set minOccurs=1 maxOccurs=1 then is setting the base type
boolean instead of object Boolean.
Kind of makes sense but I was expecting the same behavior when I set
nillable.
On Jan 10, 2006, at 6:32 PM, Jarmo Doc wrote:
If I manually add nillable=true to the WSDL for these Boolean
suitable for production env?
Date: Tue, 10 Jan 2006 11:58:31 -0500
for 1/2/3. You need to use java2wsdl ONLY once, then tweak it. Make
sure u use document/literal and not rpc/encoded.
for 4, which specific JIRA issues bother you? id's please?
thanks,
dims
On 1/10/06, Jarmo Doc [EMAIL PROTECTED
Hi Anne, no criticism of your response intended here at all but it's
absolutely maddening how these things came to be. What could have possessed
anyone to do something like this (base the invocation of operation purely on
the operation's parameters and not on the combination of the operation
Hi Dims, how would you categorize 0.94 (beta? functionally complete except
for xyz?) and what's the tentative schedule for a production-quality release
of Axis 2?
Thanks to you and your team and keep up the good work.
From: Davanum Srinivas [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To:
Raised bug: http://issues.apache.org/jira/browse/AXIS-2366
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: Axis 1.3 suitable for production env?
Date: Wed, 11 Jan 2006 04:49:12 -0800
Thanks Alin. Your suggested workaround is a good
You need a file named log4j.properties.
See http://wiki.apache.org/ws/FrontPage/Axis/ViewSOAPMessages
From: Mike Hammer [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: AXIS log4j warning message when deploying Service through
AdminClient Date: Wed,
Is Axis 1.3 suitable for a production environment? And is it the most
suitable Axis version for a production environment?
I ask because some very, very basic things appear to cause major headaches:
1. exceptions descending from java.rmi.RemoteException (as per the Axis
sample
, Jarmo Doc [EMAIL PROTECTED] wrote:
4. major bugs raised in Jira over a year before the release of Axis 1.3
final have not yet been fixed (e.g. the bug in
AxisHTTPSessionListener::destroySession whereby *no* Axis sessions are
being
destroyed correctly
.
thanks,
dims
On 1/10/06, Jarmo Doc [EMAIL PROTECTED] wrote:
Is Axis 1.3 suitable for a production environment? And is it the most
suitable Axis version for a production environment?
I ask because some very, very basic things appear to cause major
headaches:
1. exceptions descending from
@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: Axis 1.3 suitable for production env?
Date: Tue, 10 Jan 2006 10:25:43 -0800
#3 - This just isn't true. I have many Boolean fields defined. Watching the
debugger I can plainly see that they come in as null if not provided.
On 1/10/06, Jarmo Doc [EMAIL
-0800
#1 - I have been able to avoid all the Exception trouble you mention by
simply creating a beanMapping for my custom exception.
On 1/10/06, Jarmo Doc [EMAIL PROTECTED] wrote:
I do use document/literal.
On the #1 issue below, I see the following from java2wsdl:
- Please register
It always worked fine for attributes of user-defined classes. It doesn't
appear to work at all (or maybe it's illegal?) for parameters to service
operations.
From: Todd Orr [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: Axis 1.3 suitable for
Regardless of whether I throw a user-defined exception (derived from
java.lang.Exception) or an AxisFault, there appear to be two fatal problems
with Axis server-side processing of faults.
My investigation indicates that when a custom exception is thrown:
1. the Axis server returns a 500
nillable=true for 'sacked' when it should,
and
2. even if you manually add nillable=true for 'sacked', wsdl2java does not
generate Boolean, instead it generates boolean
So that's not very good.
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
if
uploading
org.apache.axis.attachments.AttachmentPart.getContentId(ID); // in service
if uploading
You can set/get the filename as a content ID.
Tao
-Original Message-
From: Jarmo Doc [mailto:[EMAIL PROTECTED]
Sent: Friday, January 06, 2006 8:06 AM
To: axis-user@ws.apache.org
Subject: RE
But AttachmentPart::setAttachmentFile(String path) is protected, not public.
I'm getting the impression that I need to pass the original filenames of the
attachments independently of the attachments themselves.
From: Tootell, James [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To:
Last time I investigated this (with Axis 1.2), I came to the conclusion that
you need to use the org.apache.axis.transport.http.CommonsHTTPSender class
in conjunction with the Jakarta Commons HttpClient package.
See http://issues.apache.org/bugzilla/show_bug.cgi?id=16522
From: Mahesh Seshan
I can happily send Mime attached files to my web service but cannot see how
to indicate the names of those attached files.
I could, I suppose, indicate them explicitly via a String [] parameter on
the operation but that seems wrong to me:
1. I'm not sure that the order in which attachments
Apologies, have a look at
http://www.nabble.com/Setting-cookie-with-apache-axis-t494860.html.
From: Keith [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: RE: AXIS, SOAP and cookie based routing
Date: Thu, 5 Jan 2006 20:37:37 -0600
I am not trying to
My Axis 1.3-based server throws user-defined exceptions to indicate errors
(rather than returning specific values to denote errors). When it throws an
exception, Axis appears to tear down the HTTP connection to the client.
Can this behavior be changed? Or am I wrong to be using exceptions to
Most of the posts that I've seen here that contain code excerpts show
call.invoke(). I've written a web service and client and have never had
to issue call.invoke() directly. I can see that it's part of the
auto-generated binding stub so is essential but why do all these code
excerpts use it
I recommend Ethereal (general network sniffer) or Fiddler (Windows-only HTTP
proxy).
Fiddler is simpler to configure for HTTP (because you don't have to
configure anything!)
To get your Java client to use Fiddler as a proxy, run:
java -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=
Typically SOAPMonitor shows all of my service requests with matching
responses and a status of 'Complete'. If, however, an operation throws a
user-defined exception then SOAPMonitor does not show any response and it
shows a status that is permanently 'Active', even if subsequent operations
Thanks for the comprehensive answer Pete.
Having switched to using wrapped arrays (and changing server code, client
code, and WSDL!) my code now works. I was surprised to find that I had to
change the server-side code so that each class contained an ArrayOfXXX
rather than XXX []. Without
Any good hints on how to go about debugging SAX exceptions? For example,
how to at least decide if the problem is:
a) a bug in Axis
b) a bug in SAX
c) malformed WSDL
d) malformed XML data
For example my Axis 1.3 client is currently reporting:
org.xml.sax.SAXException: Invalid element in
I'm using Axis 1.3. My doc/literal WS sends back an array of things, each
of whch can contain an array of other_things.
class OtherThing
{
public String name;
public int value;
}
class Thing
{
public String id;
public OtherThing [] other_things;
}
If my web service returns one thing that
/
On 10/24/05, Jarmo Doc [EMAIL PROTECTED] wrote:
OK, I've come to the conclusion that you cannot write Java classes that
hope
to refer to Mime-attached files and expect java2wsdl to generate
anything
useful.
So it looks like I'll have to write that part of the WSDL manually to
indicate
Glad for the support :-)
And, by the way, I'm *not* knocking the Axis team one bit. Their jobs, and
lives, must have been made a lot less fun having to support all this
craziness.
From: Guy Rixon [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re:
OK, I've come to the conclusion that you cannot write Java classes that hope
to refer to Mime-attached files and expect java2wsdl to generate anything
useful.
So it looks like I'll have to write that part of the WSDL manually to
indicate that member X of class Y is actually a Mime-attached
My WS needs to send attachments to clients. An individual response may
contain more than one attachment. All attachments can be treated as untyped
binary files.
Is it possible to indicate this in my service code so that (Axis 1.2)
java2wsdl will produce something that will work? I can see
A number of my WS operations do not need to return any value. They throw an
exception if they fail so the client can infer success from the lack of a
thrown exception. I have toyed with returning some nominal value such as
ok or zero but it doesn't seem to be all that valuable (and
The Axis (1.2) User's Guide says about exceptions: This is an area which
causes plenty of confusion, and indeed, the author of this section is not
entirely sure how everything works, especially from an interop perspective.
So, should my Axis web service throw Exception, RemoteException,
Does the Axis (1.2/1.3) client work like a browser (open HTTP connection,
send SOAP message, get response, close connection) or are its connections
persistent? Thanks.
_
Express yourself instantly with MSN Messenger! Download
Let's say that I have a complex type such as:
complexType name=Employee
sequence
element name=name type=xsd:string/
element name=fone type=xsd:string/
element name=male type=xsd:boolean/
/sequence
/complexType
And let's say that 'fone' and 'male' are optional. How do I get java2wsdl
My WS clents can request an employee record, update it, and then return it
to me. Because each record contains dozens of fields and I prefer to limit
the number of service operations, I've specified one operation
updateEmployee(employeeRecord) rather than dozens of individual operations
such
@ws.apache.org
Subject: RE: Session handling, do it yourself?
Date: Wed, 21 Sep 2005 14:43:14 -0500
Jarmo, I didn't follow your comment about needing a special WSDD at all
clients - can you explain that?
--Austin
-Original Message-
From: Jarmo Doc [mailto:[EMAIL PROTECTED]
Sent: den 20
I intend to implement session management via SOAP headers and am under the
impression that my WSDL should be as self-describing as possible hence it
would need to describe the session management interface.
Let's say that my WS exposes the following methods:
- login(name, password)
-
Let's say that I have a WS method like so:
deleteEmployee(int empid) throws SOAPException
{
}
Is it sensible for this method to have a void return type or should it
always return something, for example the empid just deleted (for client
correlation purposes, amongst other things)?
I ask
@ws.apache.org
Subject: Re: Explicit response required from WS methods?
Date: Wed, 31 Aug 2005 12:43:41 -0300
I think it would be a good practice return at least a boolean to ensure
your
deleteEmployee method really deleted an employee.
On 8/31/05, Jarmo Doc [EMAIL PROTECTED] wrote:
Let's say that I
scenario.
If you don't care (known as a fire and forget message) then use the
one way scenario.
-Original Message-
From: Jarmo Doc [mailto:[EMAIL PROTECTED]
Sent: 31 August 2005 16:39
To: axis-user@ws.apache.org
Subject: Explicit response required from WS methods?
Let's say that I have a WS
whether the operation really happened, or you want to
be able to receive a fault if anything went wrong, then use the
synchronous request/response scenario.
If you don't care (known as a fire and forget message) then use the
one way scenario.
-Original Message-
From: Jarmo Doc [mailto:[EMAIL
be involved. No, in the sense that the 200 might come back
before the service had processed the request; i.e. the work would be
asynchronous. An asynchronous request to a service is not a good match to a
method returning void.
On Wed, 31 Aug 2005, Jarmo Doc wrote:
Let's say that I have a WS method like so
I already do session management for multiple clients using HTTP cookies and
that allows me to easily distinguish one client from another. But is there
a simple, architected way to manage multiple sessions from the same client?
My clients are application servers and their clients are end
I'm building a web service on Linux using Axis 1.2.1 final. My clients will
typically be gSOAP/C++ but may subsequently be Axis/Java and .NET/C#. I'd
expect to move to Axis 2.x within a year. What style/use would be the most
sensible? Axis's defaults or wrapped/literal? Thanks very much.
is pretty
easy to understand and easy to get other systems to use. Axis likes it,
certainly.
Chris
-Original Message-
From: Jarmo Doc [mailto:[EMAIL PROTECTED]
Sent: Monday, August 29, 2005 09:41
To: axis-user@ws.apache.org
Subject: Recommended style/use
I'm building a web service
A design question: I plan to have 3 instances of my web service, each
logically residing in a different resource domain and none of which has
direct access to the resources in the other 2 domains. Clients can connect
to any of the 3 domains and get the majority of the information that they
they decided this kind of scenario
was out of scope for WS-A.
Cheers
Simon
-Original Message-
From: Jarmo Doc [mailto:[EMAIL PROTECTED]
Sent: Monday, August 29, 2005 1:22 PM
To: axis-user@ws.apache.org
Subject: WS design question, redirection
A design question: I plan to have 3 instances
I've written a simple web service (JWS) that includes a method that returns
a complex type (well hardly complex, just a couple of strings and
booleans). The auto-generated WSDL (using Axis 1_2_1 final) for this web
service makes no sense to me. For example, I have two booleans in my complex
new email changed from [EMAIL PROTECTED]
-Original Message-
From: Jarmo Doc [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 7:29 AM
To: axis-user@ws.apache.org
Subject: 1.2.1 autogen WSDL seems to be wrong
I've written a simple web service (JWS) that includes a method
Given the other problems I've been having with Axis 1.2.1 final on Tomcat
5.5.9, I decided to go back to basics and test the sample calculator
program. It fails to run, as follows:
SAXException: Deserializing parameter 'op1': could not find deserializer
for type
PROTECTED]
To: 'Jarmo Doc' [EMAIL PROTECTED]
Subject: RE: 1.2.1 autogen WSDL seems to be wrong
Date: Wed, 24 Aug 2005 09:40:43 -0700
Wow, it looks like a bug. Make one small change to your class and add a
new
member variable
String any and the accessors getAny() and setAny() and see what happens
invalid WSDD file, but what exactly?)
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Sample calculator cannot deserialize int
Date: Wed, 24 Aug 2005 09:16:48 -0700
Given the other problems I've been having with Axis 1.2.1 final on Tomcat
I've moved my web services from Tomcat/Windows to Tomcat/Linux and the
samples now work fine. I have no idea yet why they didn't work on Windows
though no doubt someone will helpfully respond with a diatribe about Windows
;-)
From: Jarmo Doc [EMAIL PROTECTED]
Reply-To: axis-user
95 matches
Mail list logo
