My preferred process is to create a standalone Maven project which contains nothing but
the XSD and the JAXB config which will generate the POJO classes from it.
That way, every time I run the build, a .jar is generated containing all the fact classes.
So it's basically zero effort to keep the Java model in sync with the XSD.
Steve
On 29 May 2013, at 10:13, ashish6276 <ashishkumarec010(a)gmail.com> wrote:
Hi Thanks for the reply. If I follow as you suggested, then if there
is any
small change in the XSD in future , I will have to convert it into a POJO
again if I am not wrong. So is this the best solution available for this
problem..?
--
View this message in context:
http://drools.46999.n3.nabble.com/Importing-XSD-in-Drools-guvnor-5-2-1-tp...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users