R2D2 wrote:
One last thing the response in the WSDL schema types
is a 'mixed'.
Snippet from the WSDL is as follows:
<s:element name="GetWSResponse">
- <s:complexType>
- <s:sequence>
- <s:element minOccurs="0" maxOccurs="1"
name="GetWSResult">
- <s:complexType mixed="true">
yes - that may be *the* problem - i do not think AXIS actually supports
such thing (for sure not 1.0) - you will need to check with AXIS 1.2 -
quick search of jira turned out few issues possibly fixed din AXIS 1.2 ...
http://issues.apache.org/jira/browse/AXIS-1269
http://issues.apache.org/jira/browse/AXIS-1263
http://issues.apache.org/jira/browse/AXIS-1170
however if it still does not help construct little test case (so it easy
to reproduce) and sent bug report to
http://issues.apache.org/jira/browse/AXIS and/or ask about it in
axis-dev - i think there are many people willing to help with .NET
interop so good chance it is resolved quick.
HTH,
alek
- <s:sequence>
<s:any />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
Thanks.
--- R2D2 <[EMAIL PROTECTED]> wrote:
Alek,
I forgot to add.. I saw a post somewhere which
recommended :
org.apache.wsif.schema.Parser.getTypeMappings(definition,
typeMap);
This loads the definitions into the type map, but
how
can I set it to the service or service factory
object?
--- R2D2 <[EMAIL PROTECTED]> wrote:
What I meant was that the response XML is visible
in
the logs. Will check out using TCP Trace...
Thanks....
--- Aleksander Slominski <[EMAIL PROTECTED]>
wrote:
R2D2 wrote:
Hello Alek,
hi R2D2?!
I am using WSIF 2.0 and the Axis jars which are
packaged with it only. It is Axis 1.0.
if possible try and use the latest WSIF/AXIS and
wee
what happens:
http://cvs.apache.org/dist/wsif-2.0/nightly/
Is there someway in which I can use the
BeanDeserializer
check this thread and try to use mapType
http://www.mail-archive.com/[email protected]/msg00459.html
instead of the SimpleSerializer ?
i think you can access AXIS Call object through
casting WSIFPort to
WSIFPort_ApacheAxis (check mailing list
archives
-
for example
http://article.gmane.org/gmane.comp.apache.webservices.wsif.user/150
http://article.gmane.org/gmane.comp.apache.webservices.wsif.user/6)
and that should allow you to overwrite
serializers
-
also you could try
client side deployment descriptor
BTW, the logs actually show the xml message
coming
back successfully :
i would need to see the actual XML/HTTP message
on
the wire to say
something useful - probably there is some small
mismatch in its
structure triggering the problem - use TCPMon
and
check what *exactly*
is XML on the wire ...
The entire response XMLis available between
these
2
blocks ie, between END1 and START2
i could not see any XML in your email ...
best,
alek
--
The best way to predict the future is to invent
it
-
Alan Kay
___________________________________________________________
How much free photo storage do you get? Store your
holiday
snaps for FREE with Yahoo! Photos
http://uk.photos.yahoo.com
___________________________________________________________
Yahoo! Messenger - NEW crystal clear PC to PC
calling worldwide with voicemail
http://uk.messenger.yahoo.com
___________________________________________________________
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com
--
The best way to predict the future is to invent it - Alan Kay
