Forum Discussion

WilliamX's avatar
WilliamX
Occasional Contributor
17 years ago

soapUI with Adobe Flex

The concept of this tool is awesome!!! The only thing I am disapointed is that the conection between soapUI ( MockServices ) and a Flex Client ( WebService Component ) doesnt work...  It see...
NHU's avatar
NHU
Occasional Contributor
16 years ago
Hi again,

Indeed it is very tricky.

I found the cause of the exception, and it's specific to my configuration.
In blazeDS, I was using a custom BeanProxy that was registered against the Object class.
That's what was causing the exception.

I've registered that BeanProxy against another class and don't have the exception anymore.

But the XML layout of the response is still not as nice to read as the one from the tutorial in the demo.
It looks like this :


 
 
   
      0.75
      12
   
    16
    11
    numericIntegerVersion
   
    numericBigIntegerVersion
   
    numericLongVersion
   
    numericPrimitivelongVersion
   
    dateSampleVersion
   
...

The actual object is in fact of class Envelope and numericIntegerVersion and the others are properties of the object and the null are the values of the properties.

So I was expecting something like :


  null
  null
  ...


This object doesn't go through the BeanProxy anymore, so it shouldn't be the cause of the layout.

Do you have any idea what I could do for that?

Thanks,
Nicolas.