It is not that bad. Start with a few small bugs. You start to get the hang of where things are. I have not gotten to the point where the UML is in my head just yet, but I think I am very close. I am sure castor developers would be glad to give you some small bugs to fix. Also, as far as the core developers leaving, I think there are people who would be able to pick it up. This is very very common in open source products. I think the castor team did a great job at architecting/rearchitecting castor. It is really clean and intuitive.
Dean

tek1 wrote:

do any design diagrams exist? it might be easier for others to help out if we're able to grasp the overall and some detail structure of castor...

without that type of documentation, if the 2-3 core castor people were to leave (knock on wood), it might be a real challenge for others to pick it up...



At 23:19 03/02/12 +0100, you wrote:

Hi Chavan,

There are no UML diagrams available, the only one I am aware of is in my
mind :).
I committed some weeks ago some code that will drive the SourceGenerator
to be extensible: all what you'll have to do is to implement an
interface (org.exolab.castor.builder.BindingComponent) and Castor will
use your implementation to create the classes you need.
Currently the BindingComponent support is limited to support only
XMLBindingComponent since our aim is really to finish the implementation
of the XML Schema to Java binding and to provide a JAXB compatibility
layer before concentrating fully on the extensibility.
On the meantime, feel free to help us in adding the support.

Arnaud

----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev

----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev

Reply via email to