Semantic Web Drools Module, Request for Feedbak
by Xavier Breton
Hi,
I'm looking for feedback, I'll develop a Semantic Web Drools Module that
will be the subject of my Master Degree Tesis.
The idea is to use Eclipse Modelling Framework (EMF) for prototyping and
follow a Model Driven Architecture (MDA) where the source language is
Semantic of Business Vocabularies and Business Rules (SBVR) and the target
language is Drools DRL.
The mapping could be (PIM level):
- Semantic Web Rule Language (SWRL)
- Ontology Web Language (OWL)
- RuleML
- Rule Interchange Format (RIF)
- REWERSE Rule Markup Language (R2ML)
It could be added to the module at the source UML or Entity Relationship
like models to transform the models into SBVR.
Regards
Xavier Breton
10 years, 10 months
Attach custom editor on guided decision table cell
by c3310082
Hi,
We would like to render a custom editor when a user double-clicks on a cell
that is present in web guided decision table in Guvnor 5.1 (or later). The
custom editor needs to be invoked for cells that represent a particular fact
model attribute only.
This is somewhat similar to WS custom forms functionality available for
guided business rules.
So far we have seen the
org.drools.guvnor.client.decisiontable.GuidedDecisionTableWidget class that
contains implementation for:
public void onCellDblClick(GridPanel grid,
int rowIndex,
int colIndex,
EventObject e)
in the GridCellListenerAdapter class that opens up text editor or drop down
editor.
We're new to GWT and Guvnor so would appreciate it if anyone can provide the
high level steps.
Thanks
--
View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Attach-custom-editor-...
Sent from the Drools - Dev mailing list archive at Nabble.com.
12 years, 2 months
Evil bug in 5.4.0: wrong fact selected by simple constraint due to window:length()
by Wolfgang Laun
It should be pretty obvious that the rule should not fire after the
insertion of a single fact.
declare MyEvent
@role(event)
end
rule FaultsCoincide
when
f1 : MyEvent( key == "type1" ) over window:length( 1 )
f2 : MyEvent( key == "type2" ) over window:length( 1 )
then
System.out.println( ">>> f1=" + f1 + " f2=" + f2 );
if( f2.getKey().equals( "type1" ) ) System.out.println( "*** BUG ***" );
end
insert MyEvent<type1,ALARM>
>>> f1=MyEvent<type1,ALARM> f2=MyEvent<type1,ALARM>
*** BUG ***
insert MyEvent<type2,ALARM>
>>> f1=MyEvent<type2,ALARM> f2=MyEvent<type2,ALARM>
>>> f1=MyEvent<type2,ALARM> f2=MyEvent<type1,ALARM>
*** BUG ***
12 years, 6 months
Bugs
by Wolfgang Laun
Lately, I have occasionally tried to raise an alert for something I
consider a bug, but there was no comment.
Here's another one.
rule "Faults coincide"
when
f1 : MyEvent( key == "faultType1", value == "ALARM" ) over
window:length( 1 )
f2 : MyEvent( key == "faultType2", value == "ALARM" ) over
window:length( 1 )
then
System.out.println( "************ both faults are active! f1.key =
" + f1.getKey() + " f2.key = " + f2.getKey() );
end
This rule fires after the insertion of a single fact matching the
event bound to f1.
Detailed code can be found on the user's list.
-W
12 years, 6 months
GUVNOR-1809 and assembly issue
by Mikael Lönneberg
Hi all,
Thought I would get your input before I go any further on the task of
creating the separate builds for the different target platforms.
In switching to RESTeasy as the jax-rs framework this causes an issue
RESTEASY-586 <https://issues.jboss.org/browse/RESTEASY-586> when we deploy
to AS7 as RESTeasy is already bundled/provided in AS7. So for all other
platforms we need to include the resteasy-*.jar and for as7 they need to be
removed. This is pretty straight forward.
However we also need to add or remove this section
<context-param>
<param-name>resteasy.injector.factory</param-name>
<param-value>org.jboss.resteasy.cdi.CdiInjectorFactory</param-value>
</context-param>
to guvnor-webapp-drools web.xml depending on the target platform, this is
were it becomes a little tricky.
What version should be checked in? Running in hosted mode requires the
section to exist, running Arquillian integration-tests requires it to be
removed, since integration-tests are run on as7.
I'm leaning towards having the section included by default and remove it in
GuvnorIntegrationTest or having the build process filter and create a new
version per platform which can then be copied into the WebArchive in
GuvnorIntegrationTest.
What are your thoughts?
Kind Regards
Mikael Lönneberg (gwendo)
12 years, 6 months
