On Tue, 27 Mar 2007, [EMAIL PROTECTED] wrote:
The issue was actually to do
with there being two setter methods on my object - both with the same
name but taking parameters of different types - one 'Date' and one
'String'. My local environment was using the correct setter method. The
service provider's environment was using the incorrect 'String' setting
method, which caused the parse exception. I have no idea why one used
the correct one and one not - perhaps someone can enlighten me about
that?
Are you breaking the JavaBean spec?
void setDate(Date)
void setDate(String)
Date getDate()
I'm no reflection expert but according to the API docs the methods
found in a class aren't returned in any particular order.
Were both JVM versions were the same?
--
Graeme -
