==>Hi, Matt is your bean really correct? I mean, do you have a getter and a setter for every variable member in the bean? This is very important, in fact, even though .NET doesn't throw any error if you don't specify a getter or a setter for a variable, you don't get the corresponding type in .NET. Maybe it is better if you post your bean and the WSDD. Ah, download the service pack 2 for .NET. if you didn't before; I did, and lots of eerie errors magically disappeared.
:P: > Hi again, > > At this point, I am able to get a Bean-based ws to work, but not the one I am currently working on. I am fairly certain, at this point, that my wsdd is correct. What else could be the problem? I believe that this issue has come up before on this list. Does anyone have any useful ideas on the subject? > > - Matt Munz ([EMAIL PROTECTED]) > > -----Original Message----- > From: Matt Munz > Sent: Fri 2/21/2003 2:29 PM > To: [EMAIL PROTECTED] > Cc: > Subject: .Net Interop: JavaBean -> WSDL -> c# proxy > > > Hi all, > > I am having trouble using the C# proxy I generated from the WSDL I got from Axis 1.0 for my JavaBean-based web service. On the wiki, it is stated that JavaBeans can be accessed via .Net. Does anyone have an example of this? When I try to access the web service using the generated proxy, the request works just fine, but the response cannot be parsed correctly by the proxy, which throws a System.InvalidOperationException. > > After searching the mailing list, I see that this is perhaps a common problem, but I am unable to find a solution. If anyone has an example laying around, or even any good ideas on where the problem may lie, I'd love to hear it. > > Thanks, > Matt ([EMAIL PROTECTED]) > > >
