I would assume that you're trying to test out rule writing and see
what works and what doesn't. I don't believe you can use if
statements in the RHS.
Normally, anytime you want to use "if" statements inside the RHS, it's
a sure sign that you should move it to the LHS and create separate
Try changing your BOM_TRANSACTION_DETAILS Display() method access to
public and see if it works.
Currently, you have it as "void Display()" in your
BOM_TRANSACTION_DETAILS method declaration. Change it to "public void
Display()". It might solve your problem.
No need to change method dec
With the new hibernate jars and the migration to the new Javassist,
what hibernate is essentially doing is dynamically generating
hibernate proxy objects that should subclass the original file.
Here's the interesting part.
In groovy, comparing two hibernate objects:
a.a == b.a
works fine
Oh, and a couple other things I forgot to mention.
I believe Hibernate by default will lazily load all association
objects. You have to explicitly set the lazy loading to false in
order to get eager fetching. I don't consider to be ideal as I have a
pricing object that contains many optio
Hi,
I'm testing out some simple codes using Hibernate and Drools 5 and I'm
hitting an issue with hibernate proxy objects.
With the newer version of hibernate, Javassist is used to proxy some
hibernate objects. By doing this, hibernate objects essentially
cannot use == comparisons, which
va
style, not mvel. Am I correct on this one?
Thank you,
CK
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
to
log in, it won't let me.
I'll try again later, but if I can't login, I won't be able to create
a Jira issue. :X
-ck
On Mar 15, 2009, at 6:10 AM, Edson Tirelli wrote:
There were some changes in the latest MVEL release making it more
strict on type resolution.
the class? It's quite strange though.
Considering that I'm following the docs, I should be able to
dynamically create a new type declaration instance without qualifying
it.
The following somehow works:
then
insert(new com.test.abc.Domestic());
end
Why is drools/mvel being so str
Hi,
I'm wondering if I am doing something wrong in my code:
I create dummy type declarations to indicate presence of certain
states (is there possibly a better way of doing this?):
declare Domestic
dummy : boolean
end
declare Multiple
dummy : boolean
end
rule "..."
when
...
Hi all,
Before I ask my question, just wanted to know if others have noticed
that the Hudson docs for Drools 5 is not available online. Or maybe
it's just me?
I'm a little bit of a beginner in this particular area on the Drools
flow and its persistence mechanism. I have a couple questio
If I understand you correctly, this is a Java runtime restriction.
Java classes in the default package can reference any class in a named
package. Other the other hand, classes in a named package cannot
reference any class in a default package. Classes in a default
package can reference o
d one
less API system to learn.
However, based on what I've been seeing so far, ruleflow is a purely
in-memory deal. I have read some discussions that it's possible to
persist the workflow for long-running tasks (ie. days). How would I
go about doing this or learning about this?
12 matches
Mail list logo
