>From a pure JavaBean perspective, a class like:
package com.dotech;
import java.io.Serializable;
import java.util.Date;
public class ConfusedBean implements Serializable {
public void setDate(String s) {}
public Date getDate() { return null; }
}
is seen by Introspector as (Sun JDK 1.4.2_05-b04):
Dumping Properties for: com.dotech.ConfusedBean
class
propertyType: class java.lang.Class
readMethod: public final native java.lang.Class java.lang.Object.getClass()
writeMethod: null
date
propertyType: class java.util.Date
readMethod: public java.util.Date com.dotech.ConfusedBean.getDate()
writeMethod: null
In other words, it has two properties: "class" and "date". The "date" property
is read-only and is accessed through the "getDate" method. How are you trying
to set the "expirationDate" property on your bean?
Quoting "Slattery, Tim - BLS" <[EMAIL PROTECTED]>:
> > You wouldn't happen to have another setter method that
> > accepts a different type (e.g. Date) would you?
> >
> > for example:
> >
> > ...
> > ...
> >
> > public void setExpirationDate(Date expirationDate){
> >
> > ...
> > ...
>
> No, only what I posted.
>
>
> --
> Tim Slattery
> [EMAIL PROTECTED]
--
Kris Schneider <mailto:[EMAIL PROTECTED]>
D.O.Tech <http://www.dotech.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
