Lukas and Werner:
Thanks for your comments and I appreciate knowing that you both find
that things work for you in the way that the documentation changes. I'd
be happy if I could pick up my slightly modified castor.properties file
from the classpath because that way I have control over that for
everyone running our Castor-based application.
Let me ask you a follow-up question:
First, castor-1.3.1-xml.jar contains the default castor.properties file
(well, org/exolab/castor/castor.properties, correct)?
If I also include a slightly modified
org/exolab/castor/castor.properties file in part_of_my_application.jar,
then does the "version" of the castor.properties file that I get depend
on the order that part_of_my_application.jar and castor-1.3.1-xml.jar
are listed in the class path?
In my case, I think that I have part_of_my_application.jar listed before
castor-1.3.1-xml.jar. Does that mean that I'm reading the modified
castor.properties file from part_of_my_application.jar .... but then
immediately overwriting it, in effect, when it reads the default
castor.properties file from castor-1.3.1-xml.jar?
Or, if several jar files in the class path contain
org/exolab/castor/castor.properties files .... say the default and one
or two others ...
then does it use the first one that it finds and ignores any that are
included in jar files appear later in the classpath?
Thanks,
John
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
