Make the current XML-to-Java conversion process more simple and cleanup the error messages to be much more descriptive about the error that has occurred.
The ability to create CIlib simulations using XML should be more robust in the syntax that can be used within the XML to define the required algorithms.
The Java objects created should be able to be introspected with the JavaBeans API and have the needed properties set with minimal effort.
Logged In: YES
user_id=975307
Originator: YES
Currently busy on this. Have investigated the use of Digester, Betwixt and BeanUtils.
BeanUtils is very promising, however, the other two projects are a little complex for the current needs of CIlib.
Going to start converting the current implementation this week.
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
Logged In: YES
user_id=975307
Originator: YES
I've reopened the issue. I've been busy with a small refactor at the moment. This issue is still high priority and I'll get onto it this weekend.