Re: Complex type problem

> for the attributes. ) > WMemberInfo > ---|- ID > ---|- Attrbutes [] > -|- Name > -|- Value > > Following complex type works. > WMemberInfo > ----|- ID > |- Attr1Name > |- Attr1 Value &g

Re: Complex type problem

this is a crude workaround till the time problem is fixed.   Hope this helps. Suyog      -Original Message-From: robert lazarski [mailto: [EMAIL PROTECTED]]Sent: Friday, May 26, 2006 9:36 AMTo: axis-user@ws.apache.org Subject: Re: Complex type problem The other thing is make sur

Re: Complex type problem

l the time problem is fixed.   Hope this helps. Suyog      -Original Message-From: robert lazarski [mailto: [EMAIL PROTECTED]]Sent: Friday, May 26, 2006 9:36 AMTo: axis-user@ws.apache.org Subject: Re: Complex type problem The other thing is make sure your vendor supports wsdl2java

Re: Complex type problem

s helps. Suyog      -Original Message-From: robert lazarski [mailto:[EMAIL PROTECTED]]Sent: Friday, May 26, 2006 9:36 AMTo: axis-user@ws.apache.orgSubject: Re: Complex type problem The other thing is make sure your vendor supports wsdl2java -jboss does not, for example (although they run

Re: Complex type problem

e time problem is fixed.   Hope this helps. Suyog      -Original Message-From: robert lazarski [mailto:[EMAIL PROTECTED]]Sent: Friday, May 26, 2006 9:36 AMTo: axis-user@ws.apache.orgSubject: Re: Complex type problem The other thing is make sure your vendor supports wsdl2java - jbos

RE: Complex type problem

workaround till the time problem is fixed.   Hope this helps. Suyog      -Original Message-From: robert lazarski [mailto:[EMAIL PROTECTED]Sent: Friday, May 26, 2006 9:36 AMTo: axis-user@ws.apache.orgSubject: Re: Complex type problem The other thing is make sure your vendor supports wsdl2java

Re: Complex type problem

The other thing is make sure your vendor supports wsdl2java - jboss does not, for example (although they run a modified version of axis 1.2 internally). The problem I had was similair, although IIRC correctly I was getting ser / deser errors, not null. It was working on simple types but failing on

Re: Complex type problem

I think that this is not exactly my problem. I can call normally the service from my client when i use simple types. When i try to pass complex types i face the problem.robert lazarski <[EMAIL PROTECTED]> έγραψε: You're trying to use a non-ejb client to connect to a Web Service that implements impl

Re: Complex type problem

You're trying to use a non-ejb client to connect to a Web Service that implements implements SessionBean, is that correct? The only way I got that to work - using jboss - was something like...  // remote ejb / web service  private CallCentreWebEndpoint endpoint;  String wsdl_loc   = "http://local

Re: Complex type problem

I tried the beanmapping too but it didn't work. This is the the complex type i want to send and the deploy.wsdd file:Deploy.wsdd:                                                                                            ---public class RequestData implements java.io.Serializable{private String x;p

Re: Complex type problem

I think you need to use a beanmapping element rather than a typemapping element.If that doesn't work, please post more information.AnneOn 5/25/06, Roy <[EMAIL PROTECTED]> wrote:Hello all, I have deployed an ejb service with a method that takes as input a complex object (it contains 2 Strings and o