You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Christofer Dutz <c....@upw.de> on 2009/03/27 09:37:52 UTC

Anoying problems with string2stringMap and Aegis databinding

Hi,

 

I am having a little problems with the automatically generated
string2stringMap type.

All of the types generated by CXF have names starting with capital letters.
All but string2stringMap.

This causes the Flex builder to have problems automatically generating
clients for Webservices using this datatype.

This is because the SOAPEncoder takes the class-name of the object and tries
to resolve a type . of course it won't find a type String2stringMap.

 

I currently solved the problem by creating my own CxfSoapEncoder, which
simply returns "string2stringMap" when getting a String2stringMap object,
but I can't think of it any more than a hack.

 

Would it be a great problem to make CXF and Aegis generate types with names
starting with capital letters?

 

Chris

AW: Anoying problems with string2stringMap and Aegis databinding

Posted by Christofer Dutz <c....@upw.de>.
Also I am getting strange errors on the CXF side, when sending messages
containing string2stringMaps:

65469 [btpool0-1] WARN  org.apache.cxf.aegis.type.TypeUtil  -
xsi:type="{http://service.pgm.tiller.upw.de/}string2stringMap" was
specified, but no corresponding Type was registered; no default.

But as the data is correctly processed, I think I can live with that ;-)

Chris 




-----Ursprüngliche Nachricht-----
Von: Christofer Dutz [mailto:c.dutz@upw.de] 
Gesendet: Freitag, 27. März 2009 09:38
An: users@cxf.apache.org
Betreff: Anoying problems with string2stringMap and Aegis databinding

Hi,

 

I am having a little problems with the automatically generated
string2stringMap type.

All of the types generated by CXF have names starting with capital letters.
All but string2stringMap.

This causes the Flex builder to have problems automatically generating
clients for Webservices using this datatype.

This is because the SOAPEncoder takes the class-name of the object and tries
to resolve a type . of course it won't find a type String2stringMap.

 

I currently solved the problem by creating my own CxfSoapEncoder, which
simply returns "string2stringMap" when getting a String2stringMap object,
but I can't think of it any more than a hack.

 

Would it be a great problem to make CXF and Aegis generate types with names
starting with capital letters?

 

Chris

 

__________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 3968
(20090327) __________

E-Mail wurde geprüft mit ESET NOD32 Antivirus.

http://www.eset.com
 
 

__________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 3968
(20090327) __________

E-Mail wurde geprüft mit ESET NOD32 Antivirus.

http://www.eset.com