Werner and the rest of the Castor community:
We are in the process of upgrading our use of Castor from version 1.0 to
1.3.
We believe that we have been running into two issues that have (we think)
been resolved after the release of castor-1.3:
1. We think that we have been running into the problem reported in the
Jira as CASTOR-1236 related to handling of unqualified values of
QName-typed attributes:
http://jira.codehaus.org/browse/CASTOR-1236
2. Also, because we run castor from a server, a local client (that could
be started in many different local directories), and as a Java Web Start
application (where I'm not even sure what "local directory" means), we'd
like to take advantage of the ability to define the location of the
castor.properties file as described in the Jira as CASTOR-2613:
http://jira.codehaus.org/browse/CASTOR-2613
If I am reading things correctly, the ability to define where the
castor.properties file is located is located in the recent castor 1.3.1
snapshots. It appears, however, if the problem described in CASTOR-1236
related to handling of unqualified values of QName-typed attributes is
slated for inclusion in castor 1.3.2.
Am I correct in thinking that there is not yet a snapshot release of
castor 1.3.2? To get and use the fix to CASTOR-1236, would I use the
HEAD of svn and build my own jars?
Finally, is there an example of how to define the location of the
castor.properties file if I am using that post-1.3 feature of castor?
Thanks for your consideration,
John
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
