Hi Dims, thanks for the feedback. You skipped the most important questions
however ;-)
They were:
1. Is Axis 1.3 suitable for a production environment?
2. Is Axis 1.3 the most suitable version for a production environment?
I ask not only because of the issues raised below but because of numerous
other (not easily reproducible) operational issues that I see periodically
with Axis 1.3. For example socket timeouts, SOAP versions mismatches, and
SAX parsing issues**
** one thing that I will add about all of these situations is that the
diagnostics could be better. If, for example, VersionMismatch is raised
then it should indicate both the received version number and the expected
version number. Similarly a SAXParseException that indicates, for example,
"Content is not allowed in prolog" should indicate what that content was.
If java2wsdl or wsdl2java detect a parsing problem then they should indicate
both the filename and the current line number of the file being processed.
Really basic stuff that will help us all diagnose our own bugs ;-)
From: Davanum Srinivas <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [email protected]
Subject: Re: Axis 1.3 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]> 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 java.rmi.RemoteException (as per the Axis
> sample NoSuchEmployeeFault) cause java2wsdl to report "The class
> java.lang.Throwable is defined in a java or javax package and cannot be
> converted into an xml schema type. An xml schema anyType will be used
to
> define this class in the wsdl file."
>
> 2. you have to jump through hoops to avoid intermediate ArrayOfxxxx
classes.
>
> 3. Boolean parameters to operations appear to be converted to intrinsic
> booleans (note lowercase) in an Axis client so you can only pass
true/false
> when you need to be able to pass true/false/null.
>
> 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).
>
> Don't want to sound negative, just want to know if I'm fighting a losing
> battle using Axis 1.3.
>
> Thanks.
>
> _________________________________________________________________
> Don't just search. Find. Check out the new MSN Search!
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
_________________________________________________________________
Dont just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
