Hello All,
Is it a bug in Axis1.3 that WSDL with nillable="false" and
minOccurs="0", still genrates a nilable="true" string on serialisation?
Is there somewhere I can log this bug or enhancement?
I may be able to do this in work time. Where would I start with Axis1.3
to add/alter the code to
odeName().equals(name)))
{
node.getParentNode().removeChild(node);
}
else
{
// Visit the children
NodeList list = node.getChildNodes();
for (int i=0; i {
removeAll(list.item(i), nodeType, name);
}
}
}
From: Tim R J Langford [mailto:[EMAIL PRO
Kasi, Anand wrote:
Write up a response flow handler that gets the response message from the
MessageContext object and removes the xsi:nil = true elements.
-Original Message-
From: Tim R J Langford [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 15, 2006 9:42 AM
To: axis-user
PS: I am generating the axis code form the wsdl using the following ant
task configuration :
url="eurostar_hack2.wsdl">
Rodrigo Ruiz wrote:
By what you describe, I think you should add minOccurs='0' and remove
nilla
Thanks Rod,
I agree with you and will handle it this way.
Thankyou everyone for your help and advice,
Tim
Rodrigo Ruiz wrote:
By what you describe, I think you should add minOccurs='0' and remove
nillable='true'
Regards,
Rodrigo Ruiz
Tim R J Langford wrote:
Thanks
w
minOccurs="0"? If not, then there's no valid way to send no element
instead of xsi:nil="true".
Anne
On 2/14/06, *Tim R J Langford* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi Jeff,
Thanks for your response.
Sorry for being un
wrote:
Just to be sure, you're sending xsi:nil="true", not xsd:nillable="true", right?
The latter is used only in the schema, and means that the element is
allowed to have no content. The former means that this particular use
of the element has no content.
Jeff
On 2/
Hello All,
I am writing a client interface into a provider SOAP web service, and
their system fails and returns a null pointer exception when I send them
a 'nillable="true"' element in my request. I think the reason for this
is that they are using an older version of axis than we are using (1.
() ?
iksrazal
Em Terça 06 Dezembro 2005 10:20, o Tim R J Langford escreveu:
Greetings All,
1) I am having a problem with the WSDL2Java code generated from the
current schema element :
2) This schema represents (among
Thank you Iksrazal,
Unfortunately, I am only writing the client to attach to this service
and have no control over the WSDL. I could theoretically download the
WSDL and apply some kind of filter to transform the schema into
something else (that hopefully genrates the correct beans) and generat
Greetings All,
1) I am having a problem with the WSDL2Java code generated from the
current schema element :
type="s1:FormattedTextTextType"/>
type="s:string"/>
type="s:anyURI"/>
2) This schema represents (among other things)
Hi Markus,
Did you manage to find a solution to your problem? I had to do something
similar once with a test system to get it to accept non certified sites
across ssl. I could not work out how to do do it correctly in Axis; so I
ended up creating a custom HTTPSender and setting it up as my piv
Try the
--wrapArrays (-w) option when generating the sources.
Regards,
Christian
Tim R J Langford schrieb:
Hello All,
I am upgrading some SOAP clients from Axis 1.2 to Axis 1.3 Final. One
of them upgraded with little effort, just some changes to the code
that processed the new bean
Hello All,
I am upgrading some SOAP clients from Axis 1.2 to Axis 1.3 Final. One of
them upgraded with little effort, just some changes to the code that
processed the new bean convention style generate by WSDL2Java. The other
project is proving very troublesome however.
#1 : Firstly the sc
14 matches
Mail list logo
