ws-wsif-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Elder" <ant.el...@uk.ibm.com>
Subject bug 16485
Date Tue, 18 Feb 2003 12:04:43 GMT
A while ago a user reported a problem with WSIF using the AXIS bean
serializer when the schema used names which start with a capital letter:

http://marc.theaimsgroup.com/?l=axis-user&m=104203857924370&w=2.

I raised an AXIS  bugzilla about it:

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16485

which has now been closed as working as designed. I guess Glen is right in
what he says about the reasons for closing this, but as the original user
pointed out, it seems wrong for WSIF to be dependent on the AXIS specific
TypeDesc info:

> I would have expected WSIF not to be AXIS dependant for the complex
> type mapping, as it makes the client code dependant upon the chosen
> binding. From the code - but I'm really new to WSIF so there may be
> better ways - it seemed to me that the AXIS provider would have to
> generate the TypeDesc at runtime (i.e., doing WSDL2Java job) and
> use it to create the proper BeanDeserializers.

I'm not sure how easy it would be for WSIF to generate the TypeDesc on the
fly. What does anyone else think about this?

       ...ant

Anthony Elder
ant.elder@uk.ibm.com
Web Services Development
IBM UK Laboratories,  Hursley Park
(+44) 01962 818320, x248320, MP208.


Mime
View raw message