that make sence is to use XMLBean with is open source
and seem to be the most uptodate on XML Schema.
-Original Message-
From: Eric Chijioke [mailto:[EMAIL PROTECTED]
Sent: Friday, November 19, 2004 10:52 AM
To: [EMAIL PROTECTED]
Subject: Axis and JAXB
Has anybody tried to integrate JAXB
Has anybody tried to integrate JAXB into Axis' serialization framework?
Does anyone know of any discussions/resources that address this?
- Eric
Running the WSDL2Java tool on a class that implements multiple
interfaces (or a base class and 1+ interfaces), results in a WSDL schema
that (randomly?) selects only one of the interfaces (or base class) as
the of the implementing class.
Is there a way to express multiple interface implementati
Hi,
Version: Axis 1.2 beta
Config: Document/literal
Does anyone know if there is a way to force the Axis server to include
the xsi:type attribute for a *single element* during serialization.
Details:
I am serializing a bean which contains another bean. The contained bean
is referred to by a
pecified in any schema.
I think this is one of the reasons the Basic Profile advises against
using encoded forms.
Jeff
- Original Message -----
From: "Eric Chijioke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Tami Wright" <[EMAIL PROTECTED]>
Se
rrect xml results since it added
extra wrapper and used item.
NOTE: I have discovered also that by removing the field type description
for the array property from the helper class causes the serializer to
output correctly, with the wrapping element. (although the Axis client
is unable to correctly
ay of Objects in Axis and .NET interop
Hi,
I wondered what the status was with the message thread originally posted
by Eric Chijioke entitled "Axis and .NET interoperability - Arrays".
Any interim solution that can be posted until the bug is resolved would
be appreciated.
Best Regards,
tami
ow it will create a wrapper
> element with sub elements all named "item" this matches what happens
> during the rpc/encoded processing but I don't believe it is valid for
> the wrapped/literal processing.
>
> marcus
>
>
>
> -Original Message-
nitions are generated. Can you provide us with the generated XML
Schema definitions of the nested arrays?
[1]
http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#soapenc_Ar
ray
- Anne
-----Original Message-
From: Eric Chijioke [mailto:[EMAIL PROTECTED]
Sent: Wednesday, Septembe
On Tue, 14 Sep 2004 09:54:30 -0400, Eric Chijioke <[EMAIL PROTECTED]>
wrote:
> Thanks Michael,
> This is very useful.
>
> You found that .NET 1.1 doc/literal doesn't work with Axis 1.2 Beta 3
> for complex objects, object arrays etc..
> How did they fail to interop
t: Tuesday, September 14, 2004 3:33 AM
To: [EMAIL PROTECTED]
Cc: Eric Chijioke
Subject: AW: Axis and .NET interoperability - Arrays
Eric,
we could not find sufficient information about interoperability in
detail and checked out those issues with Axis and .NET on our own. Here
is a list of out _
appropriate WSDL schema)?
Thanks,
Eric Chijioke
[EMAIL PROTECTED]
one make this work with a .NET client which seems to expect a
container element (to provide to the XmlArrayAttribute if your familiar
with .NET webservices)?
Thanks
Eric Chijioke
[EMAIL PROTECTED]
) using the WSDL I described above, it assumes (rightly
so?) that the top level element of the response SOAP body will be named
as you name it in your WSDL.
PLease let me know if this is an issue with Axis or if there is a spec
somewhere that requires the top level element to be named
getFactorReturn (in this case).
Thank you for taking the time.
Eric Chijioke
ERisk
[EMAIL PROTECTED]
14 matches
Mail list logo
