It looks to me that it is a bug because if you want a java.lang.Object
you don't need to cast and no code change is needed. This change breaks
the compatiability without gaining anything.
Bill
Neil Taylor wrote:
Hi Bill,
I have run in to this too. Specifically, I have seen this when my schema is
using stuff from xml.xsd and xlink.xsd. An example is xml:lang and xlink:href.
I think it might be a bug - it is certainly a change in behaviour - but haven't
had time to investigate it nor file a bug report yet.
Regards,
Neil
On Wednesday, June 22, 2005, at 02:44PM, Bill Leng <[EMAIL PROTECTED]> wrote:
Hi
We are currently using castor 0.9.5.3 to generate Java source files from
XML schema. When I try to upgrade to the latest castor, I found the
signature of unmarsha method has been changed. It used to return the
specific class type but now it returns java.lang.Object. I am not sure
if this is a bug or not. If it is not a bug, we have to make many
changes to our code to do the cast. Does anyone have the same problem?
thanks
Bill
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
