Hi Joyce,
Doing some clean-up of our error messages is definitely on our to-do
list, it is a great idea to provide better messages.
However I am not sure of the i18n process, it will make Castor rely on
external files and can introduce newbie problems with the CLASSPATH or
whatever but since Cast
Hi Rick and Krishna,
Once again I will remind the bug is from XML Spy and not from Castor.
Taken from the XML Schema specification:
"2 If the alternative is chosen, the type definition
.resolved. to by the .actual value. of the base [attribute] must be
either a complex type definition whose {co
we
have had the same problem with a combination of castor and poolman (we
don't use tomcat, but i can c that u r using poolman from the stack
trace).
i am
not sure if it is a poolman or a castor problem yet, haven't had time to
investigate it thoroughly. to get around it, u can comment o
I have a similar issue. I am using BeanUtils from Apache Jakarta project. Its
an util to introspect the Java bean and get the attribute names and values
etc.
That should probably help you instead of hard coding.
-Suresh
On Wednesday 02 January 2002 22:57, [EMAIL PROTECTED] wrote:
> hi all,
