#1 - I have been able to avoid all the Exception trouble you mention by simply creating a beanMapping for my custom exception.
#2 - Easy. Create a typeMapping for your array and call it whatever you want.
#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.
#4 - Valid. There's only so much time in a day?
Another point: I have been able to use the java2wsdl tool without modifying the wsdl at all. Of course, it depends on your needs. I have been able to easily create a wsdl of my liking by simply creating the neccessary delegate objects. I have yet to run into any trouble with wsdl creating I couldn't get around.
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 a typemapping/beanmapping for 'xyz.myexception'
- 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.
How do I 'tweak' the WSDL to correct these issues?
On the #2 issue below, I eventually found a workaround which is instead of
writing the following:
public class Employer
{
public int employerID;
public Employee [] employees;
}
just write the following:
public class Employer
{
public int employerID;
public Employee [] employees; // could be private
public Employee [] getEmployees()
{
return this.employees;
}
public void setEmployees(Employee [] employees)
{
this.employees = employees;
}
}
This 'hack' solved all my problems to do with having to use ArrayOfEmployee
in boith the Axis server and Axis clients.
On #3, I don't have a solution yet so may have to create an intermediate
class that contains the Booleans and then pass that class to the operation
rather than passing the contained Booleans.
>From: Davanum Srinivas <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: axis-user@ws.apache.org
>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.
>
>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.
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
