I've just developed my application using an Ejb-based web service and
a plain axis client.
I've followed the axis user guide on the website and all went well.
The only problems i had was related to the mapping of custom datatypes.
But here, in this mailing list, i found all the answers!
On
]
[EMAIL PROTECTED] wrote:
If your custom class is not a plain bean, you need to provide
serialization/deserialization
mechanism for this class and let Axis know of that by registering a type
mapping.
Jai
-Original Message-
From: fabrizio picca [mailto:[EMAIL PROTECTED]
Sent
representation of your bean.
Jai
-Original Message-
From: fabrizio picca [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 03, 2005 10:30 AM
To: axis-user@ws.apache.org
Subject: Re: axis client consuming an ejb service
the class is jb-compliant.
i'm using the bean(de)serializer bundled
, fabrizio picca
[EMAIL PROTECTED] wrote:
thanks a lot jai
i'll try te way you told me.
On Thu, 3 Mar 2005 10:36:22 -0600, THOMAS, JAI [AG-Contractor/1000]
[EMAIL PROTECTED] wrote:
Well, then it would be pretty straight forward.
You can use java2wsdl tool to generate the wsdl.
This generated
will be opening a new can of worms. There
were lots of discussions in the past in this group on hash table
serialization and interop issues.
Jai
-Original Message-
From: fabrizio picca [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 03, 2005 10:49 AM
To: axis-user@ws.apache.org
Subject: Re
This is my first post, i'm new to axis, so excuse the eventual oddness
of this question.
i wanna call a remote service like this
setTrigger(hashtable triggerMap,String urlRef,String ipRef)
The hashtable triggerMap contains Trigger custom objects.
Those Triggers are made of String and another
