==>I solved the problem this way: DOWNLOADING AND INSTALLING .NET FRAMEWORK SP2
What before wasn't working, now works fine on Windows2000 just as in Windows XP does. (SAME apps, SAME software). Notice that on the machine I have where XP is installed I didn't install SP2, and everything works fine too! I really don't know the deep motivations of this, but i think this is an important topic to take into considerations when developing .NET, Axis webservices. (God bless the moment when it came into my mind the idea to check for .NET updates!) Paolo > > Hi, > > I've developed, by following in part the precious guidelines of someone of > > you (Mattia Dongili, Mahindra, Brian Ward who I thank very much) an app > that > > at client side (.NET aspx) packages two arrays of strings and send them to > > the server (Axis1.0/Tomcat 4.1.12) that parses the two arrays, makes a SQL > > query to an Access DB and returns a complex type; > > this type is arranged as a java bean, and represents ONE ROW of the query > > resultset. The type returned to the client is an ARRAY of this complex > type. > > > > The point is: the same classes, the same releases of the software > involved, > > the same applications WORK in Windows XP BUT NOT in Windows 2000. > > > > In XP an array of one element (that is to say one row) is correctly > returned > > with the correct string fileds, while in Windows 2000 is returned just > only > > the array with one row but WITHOUT the fields, that is to say with NULL > > fields elements. > > > > I'm sure that everything should work, since in Windows XP it does! And > does > > it well, I have to say. > > > > Someone knows what's going on? > > > > Thank you very much, > > > > Paolo Paganotto > > > ==>I forgot to say that NO error messages raise neither at client nor at > server side. The web service is deployed by using a deploy.wsdd file in > which I specify a serializer for the ROW complex type, complex type that is > correctly interpreted by .NET. > > > >
