Keith,
Until
choice will be fully implemented in AXIS, I could suggest two
workarounds:
1. Programmatically in you client code similar to
this:
org.apache.axis.description.ElementDesc
field;
field =
(ElementDesc)requestChoice.getTypeDesc().getFieldByName("hat");
submit it
Quicker than waiting for someone else to fix it.
Sapozhnikov, Michael wrote:
> It looks to me that it's not too hard to fix it (e.g. by
> prefixing member field name with a namespace prefix for the not unique
> field names)
Hi,
In our XSDs we use
elements, which give me a hard time with
AXIS.
In the first case
(similar to what is described in the bug http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13439, opened
a year ago) this XSD fragment:
I think you are getting underscore prefix because package is a reserved word in Java.
Try to change name to something else, like "aPackage" to see if this true.
Mike
-Original Message-
From: Irazabal, Alex [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 2:12 PM
To: '[EMAIL PROTEC
Title: RE: Interim drop of 11-13-2002
Hi,
I have the same problem with 11/14 when I run my client.
What I could see here that HTTPSender.writeToSocket uses StringBuffer.append method which expects as a parameter StringBuffer argument and this is the new method added in JDK 1.4, JDK 1.3 does no
Title: Parent/Child relationship in AXIS
Hi,
I have a general question regarding generated XML in case when xsd extension is used.
I have my types defined as follows:
Title: What happened with nightly drops?
Hi,
I have a nightly drop as of 10/22 but I don't have source for it, which I need.
What happened with nightly drops? The only one available is as of 10/27 and it does not contain binaries, only source. I cannot use release 1.0.
Where can I get la
pec about
this.
Thanks for any help you can give me.
--Alex
-Original Message-From: Sapozhnikov,
Michael [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October
15, 2002 8:20 AMTo: '[EMAIL PROTECTED]'Subject:
RE: Problem with multiple import
Alex,
As far
as I know WSDL's grammar for is similar to xsd
schemas' grammar (only location is used enstead of schemaLocation) and
in xsd schemas you cannot use when you
use target namespace are the same, there is an for
this. AFAIK, there is no in wsdl so try to change
namespaces t
Title: RE: Problems with WSDL2Java and complex import/include hierarchies
This is an existent problem with imports and includes. I reported this some time ago.
See my previous posts about multiple imports problem at
http://marc.theaimsgroup.com/?l=axis-user&m=102260951728371&w=2
and about incl
s note, it falls
apart in certain cases. As I said, I'll look at the import problem as soon
as I get the chance.
Russell Butek
[EMAIL PROTECTED]
"Sapozhnikov, Michael" <[EMAIL PROTECTED]> on 05/29/2002 09:10:39 AM
Please respond to [EMAIL PROTECTED]
To: "'[
Title: Includes
Hi,
We have elaborate set of XSDs generated by our own tool. Some of them "live" in the same namespace,
but they don't have knowledge of content of each other except the file name.
So the most natural way to connect them is not copy and paste one into another, but using
sta
Title: Multiple import problem
Hi,
I am using WSDL2Java tool (beta-2 version), trying to generate Java classes and run into problem when one of my imported xsd was already been imported in another xsd. Generally the structure is similar to this:
MyWSDL. wsdl
|
+-- import comp.
Title: Multiple import problem
Hi,
I am using WSDL2Java tool (beta-2), trying to generate Java classes and run into problem when one of my imported xsd has already been imported in another xsd. Generally, the structure is similar to this:
MyWSDL. wsdl
|
+-- import comp.xsd
14 matches
Mail list logo
