Michael Neale <michael.neale <at> gmail.com> writes:

> 
> there isn't really anything at the moment, we are starting from scratch for
> the new Descr classes.
> 
> On 3/20/06, Jayaram C S <jayaramcs <at> gmail.com> wrote:
> >
> > Mark Proctor <mproctor <at> codehaus.org> writes:
> >
> > >
> > > The descr is a string based intermediate API. Its a rough appoximation
> > > to the classes rule/spi except each field is just a string. The
> > > PackageDescr is then passed to the PackageBuilder which returns a
> > > Package. We have aligned Drools 3.0 with Java - RuleSets no longer
> > > exist, we just call them Packages. It is possible to go direct to
> > > rule/spi - especially if you have no code to compile - but bear in mind
> > > that PackageBuilder has a lot of logic to take care of the building and
> > > you might end up replicating a lot of it anyway.
> > >
> > > Take a look at PackageBuilder and RuleBuilder in drools-compiler.
> > >
> > > I would love to have a RuleML driver - but its complex and is marked for
> > > after 3.0. So a directly aligned XML was a quick answer to those that
> > > still need XML. Also remember that RuleML has some limitations - for
> > > instance you can't have freecode in predicates and consequences -
> > > instead you can only call functions.
> > >
> > > Mark
> >
> >
> >
> >
> > So our first objective is to derieve an XSD for native rule
> > representation, if I
> > have gotten it right.
> > Then we can move on to a conversion logic using a mapping tool.
> >
> > Please let me know of any documents or tutorials to understand the DRL
> > used now
> >
> >
> >
> 



I was doing some research on Java to XSD and XSD to Java conversions and this is
what I have found.

The JAXB spec 2.0 states,


2.1 XML Schema to Java

2.1.1 W3C XML Schema support

The mapping of the following XML Schema components must be specified.
 type substitution (@xsi:type)
 element substitution group (<xs:element @substitutionGroup>)
 wildcard support(xs:any and xs:anyAttribute)
 identity constraints (xs:key, xs:keyref and xs:unique)
 redefinition of declaration (xs:redefine)
 NOTATION
For binding builtin XML Schema datatypes which do not map naturally to Java
datatypes, Java datatypes specified by JAXP 1.3 (JSR 206) must be used.

2.2 Java to XML Schema

2.2.1 Default Mapping
A default mapping Java constructs to XML Schema must be specified. The
default mapping may be overridden by customizations described in
Section 2.2.2, “Customized Mapping”.

2.2.2 Customized Mapping

A customization mechanism to override default mapping of Java constructs to
XML Schema constructs must be specified. Since XML Schema provides a
much richer feature set than Java language for defining data models, the scope
of customizations will be restricted to enable mapping to commonly used XML
Schema constructs.


So once we have the classes ready , then creating the native format and the
mapper shouldnt be a problem.


Reply via email to