Hello Versus_Spirit, thanx for your reply!
Yeah - I found the bug in ConstructorTarget too (after some cursing and tracing). There's some "not-very-functional" :-) code that's suppose to determine the actual constructor parameter types... I thought I'd fix it and I partially did, but there were some other problems and I really didn't have the time and the nerve to look for them.... Eventually, the sollution that worked for me was to remove the non-default constructor from the bean (I have a feeling that a proper JavaBean should only have a default constructor) and populate the fields by setters only. So in the end ConstructorTarget won't be involved...and it works fine... Versus_Spirit wrote: > > I just found a solution, > > There is, may be, a bug in org.apache.axis.encoding.ConstructorTarget. > > When axis instanciate a class with a custom constructor (not the default > parameterless), it check if class type from webservice are same as > constructor parameters, here is the code that do this : > > if > (values.get(i).getClass().getName().toLowerCase().indexOf(classes[c].getName().toLowerCase()) > != -1) > > The bean class contructor (for me) take a java.util.calendar and the > webservice return a java.util.gregorianCalendar, indexOf failed. > > To correct it without changed axiscode. I change the bean class contructor > (generated with wsdl2java) to take gregoriancalendar not a calendar. > > -- View this message in context: http://www.nabble.com/No-object-was-found-for-class-type-class-java.util.Calendar-tf2190378.html#a6442204 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
