On 14/09/2010 21:17, Leonardo Gomes wrote:
The thing is that, afaik, the DrlParser in itself doesn't give you something that you can use to generate the BRL XML, even for a well-behaved DRL. You would have to do some sort of model-to-model transformation that would have RuleModel as an outcome. With the RuleModel at hand you can easily marshal it to BRL XML.

There are visitors for the RuleModel that generate BRL XML (quite simple with XStream) and pure DRL, and when you want to compile a BRL rule package today, it uses the DRL visitor to generate the DRL that can be used to compile.

BRL XML: hasn't evolved lately mainly because Mark and the others are waiting for RuleML to become the canonical XML representation. I think that the BRL Schema misses a lot of things that you have today in a DRL and that's why nobody wanted to make the effort to have a DRL -> BRL parser. This part risk to be completely rewritten the day they decide to use RuleML.
Exactly, we don't want to mature and promote a proprietary XML and waste the time and create the confusion from not following a standard.

I think people working on the guided editor are just doing hacks to limp the current xml along for the purposes of the guided editor until we can move to something more long term.

Mark

Having said that, I still thing that I might be wrong since I haven't looked much at the 5.x code except for the parts that I already knew from 4.0.7 :)

Cheers,
Leo.

On Tue, Sep 14, 2010 at 2:00 PM, Wolfgang Laun <wolfgang.l...@gmail.com <mailto:wolfgang.l...@gmail.com>> wrote:

    You are right, of course.  The BRL editor has its own XML format.

    I just wonder whether going through a DrlParser - DrlDumper cycle
    might produce a sufficiently "well-behaved" DRL text that could be
    easily enough transformed to the BRL XML. But nothing of this is
    in the "stable" API, so it would be wobbly in more than one way.

    -W


    2010/9/14 Leonardo Gomes <leonardo.f.go...@gmail.com
    <mailto:leonardo.f.go...@gmail.com>>

        I might be wrong, but I think DRL -> BRL is still not possible.


        Just had a look at
        org.drools.ide.common.server.util.BRDRLPersistence, and we
        have the following:

                public RuleModel unmarshal(String str) {
                    throw new UnsupportedOperationException(
                            "Still not possible to convert pure DRL to
            RuleModel");
                }


        Leo.

        2010/9/14 Wolfgang Laun <wolfgang.l...@gmail.com
        <mailto:wolfgang.l...@gmail.com>>

            There is a short hint in the Expert Manual, subsection
            4.11.3, where conversion between DRL and XML using classes
            such as DrlParser and XmlDumper is discussed. A .brk is
            just the "native" Drools XML format.

            -W


            On 14 September 2010 01:17, Leonardo Gomes
            <leonardo.f.go...@gmail.com
            <mailto:leonardo.f.go...@gmail.com>> wrote:

                Hi Amisha,

                You should use the user's list:
                <rules-users@lists.jboss.org
                <mailto:rules-users@lists.jboss.org>> for this sort of
                question.

                AFAIK, no you can't convert technical rules (manually
                written drl) to business rules (.brl) generated with
                the graphical editor using Guvnor.

                Cheers,
                Leo.


                On Mon, Sep 13, 2010 at 10:42 PM, apatel
                <apa...@ondeckcapital.com
                <mailto:apa...@ondeckcapital.com>> wrote:


                    Hi,

                    Is it possible to port Technical Rules in Drools
                    to Business Rules? Is the
                    procedure posted somewhere?

                    Also is it possible to apply Drools Categories to
                    Technical Rules?

                    Thanks for your help,
                    Amisha
                    --
                    View this message in context:
                    
http://drools-java-rules-engine.46999.n3.nabble.com/Technical-Rules-tp1468563p1468563.html
                    Sent from the Drools - Dev mailing list archive at
                    Nabble.com.
                    _______________________________________________
                    rules-dev mailing list
                    rules-...@lists.jboss.org
                    <mailto:rules-...@lists.jboss.org>
                    https://lists.jboss.org/mailman/listinfo/rules-dev



                _______________________________________________
                rules-dev mailing list
                rules-...@lists.jboss.org
                <mailto:rules-...@lists.jboss.org>
                https://lists.jboss.org/mailman/listinfo/rules-dev



            _______________________________________________
            rules-users mailing list
            rules-users@lists.jboss.org
            <mailto:rules-users@lists.jboss.org>
            https://lists.jboss.org/mailman/listinfo/rules-users



        _______________________________________________
        rules-users mailing list
        rules-users@lists.jboss.org <mailto:rules-users@lists.jboss.org>
        https://lists.jboss.org/mailman/listinfo/rules-users




_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

Reply via email to