You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by "Tudor, Liviu @Cimage" <Li...@cimage.com> on 2002/07/02 15:28:31 UTC
Possible problem with IBM WebSphere Developer Studio 4.0.3
Hi everyone!
Rather new to the WebServices/SOAP area. We've just finished
implementing our webservices on .NET (yeah, I know I know, but there are
commercial reasons for doing it this way beyond my control) and we need to
deliver a set of "basic consumers" for them on WebSphere.
I've generated a basic skeleton using the Wizzards in WebSphere and it
didn't work, as it complained when reading an Array of items. The error was
something like "cannot find PropertyDescriptor for property XXX". At first I
suspected that the generated classes do not respect the JavaBeans patterns,
but they actually do (i.e. there's a setXXX and getXXX for each property
etc.). There was nothing wrong with the XML passed in between, so I had to
get around this problem by writing a BeanInfo (extend SimpleBeanInfo) for
each of my beans and exposing the properties through getPropertyDescriptors.
Once I did that it worked fine, still, I can't understand why it wouldn't
detect through introspection the properties of the Bean!
Has anyone come across this problem so far? Writing a bean descriptor
for each of the beans involved in the project would be a bit of an overkill
-- surely I can automate this through a little tool that can generate them
for me, but again, why the need for that when all the classes actually DO
respect the JavaBeans pattern?
Thanks!
Liviu Tudor
Liviu Tudor <?XML:NAMESPACE PREFIX = O />
Cimage Novasoft Limited
: www.cimagenovasoft.com <http://www.cimagenovasoft.com/>
+ liviut@cimage.com <ma...@cimage.com>
(Fax: +44 (0)1344 767701
(Direct Line: +44 (0)1344 767759
*Centennial Court, Easthampstead Road, Bracknell, BERKS, RG12 1JZ
Sun Java Certified Programmer
"C makes it easy to shoot yourself in the foot; C++ makes it harder, but
when you do, it blows away your whole leg." Bjarne Stroustrup
RE: Possible problem with IBM WebSphere Developer Studio 4.0.3
Posted by Erich Izdepski <ei...@cysive.com>.
All I can say is I've seen the problem and done the same thing to fix it. I
was using tomcat, so it is not just a websphere issue- it is something
deeper. I found that not all beans required the bean info class, just some.
No idea why, but my guess is how automated tools using WSDL to generate the
beans is not quite right per the bean spec.
Erich Izdepski
Senior Software Engineer
Cysive, Inc.
-----Original Message-----
From: Tudor, Liviu @Cimage [mailto:LiviuT@cimage.com]
Sent: Tuesday, July 02, 2002 9:29 AM
To: 'soap-user@xml.apache.org'
Subject: Possible problem with IBM WebSphere Developer Studio 4.0.3
Hi everyone!
Rather new to the WebServices/SOAP area. We've just finished
implementing our webservices on .NET (yeah, I know I know, but there are
commercial reasons for doing it this way beyond my control) and we need to
deliver a set of "basic consumers" for them on WebSphere.
I've generated a basic skeleton using the Wizzards in WebSphere and it
didn't work, as it complained when reading an Array of items. The error was
something like "cannot find PropertyDescriptor for property XXX". At first I
suspected that the generated classes do not respect the JavaBeans patterns,
but they actually do (i.e. there's a setXXX and getXXX for each property
etc.). There was nothing wrong with the XML passed in between, so I had to
get around this problem by writing a BeanInfo (extend SimpleBeanInfo) for
each of my beans and exposing the properties through getPropertyDescriptors.
Once I did that it worked fine, still, I can't understand why it wouldn't
detect through introspection the properties of the Bean!
Has anyone come across this problem so far? Writing a bean descriptor
for each of the beans involved in the project would be a bit of an
overkill -- surely I can automate this through a little tool that can
generate them for me, but again, why the need for that when all the classes
actually DO respect the JavaBeans pattern?
Thanks!
Liviu Tudor
Liviu Tudor
Cimage Novasoft Limited
:www.cimagenovasoft.com
+liviut@cimage.com
(Fax: +44 (0)1344 767701
(Direct Line: +44 (0)1344 767759
*Centennial Court, Easthampstead Road, Bracknell, BERKS, RG12 1JZ
"C makes it easy to shoot yourself in the foot; C++ makes it harder,
but when you do, it blows away your whole leg." Bjarne Stroustrup
RE: Possible problem with IBM WebSphere Developer Studio 4.0.3
Posted by Erich Izdepski <ei...@cysive.com>.
All I can say is I've seen the problem and done the same thing to fix it. I
was using tomcat, so it is not just a websphere issue- it is something
deeper. I found that not all beans required the bean info class, just some.
No idea why, but my guess is how automated tools using WSDL to generate the
beans is not quite right per the bean spec.
Erich Izdepski
Senior Software Engineer
Cysive, Inc.
-----Original Message-----
From: Tudor, Liviu @Cimage [mailto:LiviuT@cimage.com]
Sent: Tuesday, July 02, 2002 9:29 AM
To: 'soap-user@xml.apache.org'
Subject: Possible problem with IBM WebSphere Developer Studio 4.0.3
Hi everyone!
Rather new to the WebServices/SOAP area. We've just finished
implementing our webservices on .NET (yeah, I know I know, but there are
commercial reasons for doing it this way beyond my control) and we need to
deliver a set of "basic consumers" for them on WebSphere.
I've generated a basic skeleton using the Wizzards in WebSphere and it
didn't work, as it complained when reading an Array of items. The error was
something like "cannot find PropertyDescriptor for property XXX". At first I
suspected that the generated classes do not respect the JavaBeans patterns,
but they actually do (i.e. there's a setXXX and getXXX for each property
etc.). There was nothing wrong with the XML passed in between, so I had to
get around this problem by writing a BeanInfo (extend SimpleBeanInfo) for
each of my beans and exposing the properties through getPropertyDescriptors.
Once I did that it worked fine, still, I can't understand why it wouldn't
detect through introspection the properties of the Bean!
Has anyone come across this problem so far? Writing a bean descriptor
for each of the beans involved in the project would be a bit of an
overkill -- surely I can automate this through a little tool that can
generate them for me, but again, why the need for that when all the classes
actually DO respect the JavaBeans pattern?
Thanks!
Liviu Tudor
Liviu Tudor
Cimage Novasoft Limited
:www.cimagenovasoft.com
+liviut@cimage.com
(Fax: +44 (0)1344 767701
(Direct Line: +44 (0)1344 767759
*Centennial Court, Easthampstead Road, Bracknell, BERKS, RG12 1JZ
"C makes it easy to shoot yourself in the foot; C++ makes it harder,
but when you do, it blows away your whole leg." Bjarne Stroustrup