Believe me, I understand
the difference between attribute, element and text. I am myself a co-author of
the XML framework developed by our company. It was written 4 years back. Due to
lack of resources, we couldn't add extensive support for Schema. Hence looking
at Castor or Toplink to substitue our framework.
-----Original
Message-----
From: Sudhendra Seshachala
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 09, 2004
10:33 AM
To: [EMAIL PROTECTED]
Subject: Re: [castor-user] Date:
Wed, 9 Jun 2004 10:10:19 -0700
It is not a bug. You have
to understand the difference between 'attribute| element| text'
accordingly map. In your case that is an issue looks like. After careful
investigation of the mapping file you sent.
In your case your objects
are not same as the xml representation. Please review both closely and
peacefully. I have done the most complex mapping with castor and it rocks. You
need to poke and probe a bit more. Please visit the castor.org and wiki,
and various mailing lists on google. You can find lot resources which can be of
immense help. The errors you are getting are pretty basic and standard stuff
which I have encountered during implementation. But a close and patient look at
xml, objects will relieve you of all you issues. Do you have a test case?
I used to follow this
method initially when I started using castor
Start with One class with
basic objects (Only java.lang.Object and primitives) and continue onto add more
complex structure.
Hope this helps.
Thanks
Sudhi
.
-----Original Message-----
From: Gawde, Kiran
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 09, 2004
10:12 AM
To: '[EMAIL PROTECTED]'
Subject: [castor-user] Date: Wed,
9 Jun 2004 10:10:19 -0700
I am getting following error
during unmarshalling:
java.lang.IllegalArgumentException:
Type conversion error: could not set value of issuer(java.lang.String) with
value of type java.lang.String
The complete stack trace is in the
attached log file. The sample xml is in the attachment, too.
I found out that the problem is
caused due to the NameID field being under two elements (Issuer, Subject). If I
take out one of the elements, it works fine. Is it a bug/limitation?
Thanks,
Kiran