Sachith, your task is to come up with a solution that adds certain functionality to Castor to make it (or parts thereof) JAXB compliant. In the context of this statement, JAXB compliance refers to the specification.
Clearly, it cannot be as simple as taking parts of the JAXB reference implementation and integrate it with Castor. There's plenty of issues with this approach, which I should not have to explain to you, one of them being licensing. Yes, nobody wants to re-invent the wheel, but simply pulling parts of the JAXB RI into Castor is not an option. Regards Werner Sachith Dhanushka wrote: > Hi Werner and all, > > This is what I am trying to do now. As I commented in the JIRA also, now > I am using the java.net <http://java.net> jaxb2 reflection library > instead of annongen Jam. So I am working on that now. > > In addition to that please let me know the feasibility of the following > approach as well. When I looked in to JAXB2 schema generation, I can use > the existing JAXB2 RI to get a DOM model of the schema. In other words, > we can give set of JAXB annotated classes and get the schema as a DOM > model. Then we can create our Castor schema model by looking at the DOM > model. The problem with this approach is that we get an intermediate DOM > object model. But the advantage is this approach is that this is less > error-prone and standard as we can use the implementation from the JAXB > RI itself. > > Please let me know what you think about this approach. > > Thanks, > SD --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
