Hi Carole,
This is a known issue, actually it should also be present in 0.9.5.2. To
fix a bug with inheritence, we chose to change the method signature to
Object instead of a specific time. So casting is currently necessary.
Hopefully we'll come up with some better logic for calculating the
correct type for the generated classes. Basically we need to find the
lowest common denominator and use that as the method return type for
inheritence purposes.
Have you tried using your previously generated classes with the newer
castor, there may not be any need for you to regenerate the sources if
you just want to take advantage of bug fixes in the
marshaller/unmarshaller in later versions.
Hopefully we'll try and add some better logic for determining the return
type for Castor 0.9.6.
--Keith
Carole Zieler wrote:
>
> I've just downloaded the new castor jar, as well as the source to try and
> fix a bug I posted about yesterday. When I try to compile my source code,
> any place where I am calling unmarshal on an object is now returning an
> Object, instead of the specific type as it did before. MyClassName myVar =
> MyClassName.unmarshal(somefile) no longer works. I've looked at this for a
> while this morning, about four hours, trying to figure out if there is just
> some switch I need to modify when compiling, and I've also tried downloading
> the JAR file from the site, and neither seems to work with this anymore.
>
> Is there a way to fix this I am not seeing? I know I could go back and just
> cast it everywhere, but I have a ton of code using this.
>
> Thanks for any info.
> Carole Zieler
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
