I have the same problem!
I have a webservice that receives a class (fillled from a .NET 2.0 client)
which contains some double values. Since 1.2.1 the EJB (JSR-181) receives null
values for these doubles.
I'm currently trying to encircle the error, but at the moment i have no idea
what is happ
I believe I found the bug. It is described here ->
http://support.microsoft.com/kb/925272
In my .Net code I have field names ending with Specified on the object I'm
sending through the web service (e.g. for an Integer field called NumberOfHits
there will be a bool field called NumberOfHitsSpeci
So, do we consider this to be .NET problem?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041383#4041383
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041383
___
jboss-user
JBossWS is standard conforming, and per se this is not a JBossWS problem. But
it means that updating to new JBossWS versions breaks a lot of client code or
requires to put XMLElement on all generated DataStructures for
nillable non-complex Data fields. Thus it is a JBossWS users problem.
Detail:
Heiko, yes it is a .Net problem.
The XMLSerializer class in the .NET Framework 2.0 has a bug with optional
elements.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041748#4041748
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=
