K, I feel like ive had my teeth kicked in and still I cant seem to make any
progress...

Here's a summary of what I am trying to do:
---------------------------
1) I have a WebService (similar to a session) that acts as my controller

2) I have 2 methods, one that returns a string and another that returns a
interface (which is implemented using the Java DynamicProxy - so it is
basically a HashMap with the interface methods wrapped around it)

3) I eventually need to use a .NET client (VB) to attach to these
"controllers" and invoke their methods, in some cases I will want primitives
returned in other cases I need the beanType returned (as well as being able
to send those back too).


Here's what I have so far:
---------------------------
1) No matter what I try - Bean (de)Serializers, Custom (de)Serializers,
Defining the bean in the WSDL, etc. I cannot seem to successfully get the
bean-type methods to work correctly (deserialize) what looks to be on the
client.

2) From the TCPMon, both methods seem to be working fine and returning what
I am looking for (at least at the point I am at right now)

3) The "string" method works fine both server and client side.


Here's my questions:
---------------------------
1) Could this have something to do with defining as a RPC vs. Wrapped?

2) Since I can see the TCPMon and it looks right and since the error is
client-side, does that suggest it might be something there?

3) By defining the "person" bean inside the WSDL will this allow my .NET
client to invoke the method on the WebService and actually recieve a
"Person" object?  If so, would I need proxy's on the .NET side for this or
to do something special?


Once again, appreciate all the responses and suggestions i've been
getting...any more would be great as I am totally banging my head here...

Thanks.

KJQ

Reply via email to