[Daniel
Shriver]
You don't even have to
do that. If Castor can't automatically do the right thing (a
class isn't a psuedo bean xor one with all public vars) you can easily make
it do the right thing with a mapping file. The docs on mapping files
specify how you lable getters and
setters:
example: I have a field
badGetStr which is a string and has a get method named "getMungey" and a set
method named "fungusEater" then my mapping file would have a
line:
<field name = "badGetStr" type =
"java.lang.String[Daniel Shriver] "
get-method="getMungey"
set-method="fungusEater">
set-method="fungusEater">
I'd
advise AGAINST creating getters and setters just for Castor... just use the
maping to fix things.
-----Original Message-----
From: Techeira, Vincent X -ND [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 14, 2003 1:42 PM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] FW: Specifying get and set methods in an external classAfter giving the problem even more thought, the solution to my problem is so simple I could kick myself. I could just simply but both types of get/set methods in the class. Castor would use the well defined set, and the developers can use the other.
