joshua,
I think this would be no good idea. this small step is not much work
and I'm flexible: if working with eclipse 3.4 milestones I can easy
use the 3.4 jdt.core jar
...and the error msg is clear enough: jdt.core.jar is missing
ekke
Joshua Jackson-3 wrote:
>
> Too bad Mark don't want to add
Too bad Mark don't want to add eclipse JDT library into the plugin :(
On 10/11/07, ekke <[EMAIL PROTECTED]> wrote:
>
> hi,
> I'm running drools with eclipse 3.3 - there are some minor problems, but it
> works
> just confirmed:
> create a new rules project with hello world example
> then go to proj
hi,
I'm running drools with eclipse 3.3 - there are some minor problems, but it
works
just confirmed:
create a new rules project with hello world example
then go to project - properties - java build path - added external jar: my
jdt.core from my eclipse 33 installation
run hello world - all is ok
I owe you one more beer.
turns out Phonenumber is not a String but a JaxBElement obj.
I should not be allowed to code for more then 32 hrs. straight.
On 10/10/07, Edson Tirelli <[EMAIL PROTECTED]> wrote:
>
>Is phoneNumber1 a String attribute?
>Drools makes a compile time analysis to chec
Is phoneNumber1 a String attribute?
Drools makes a compile time analysis to check whether an operator can or
can not be used... matches can only be used on String attributes.
Maybe, for objects, we could defer that to runtime... any suggestion?
[]s
Edson
2007/10/10, Karl Trout <[
hi,
the error message gives you the answer:
...
Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in
the classpath
...
put this jar into your classpath and it works
(and much better and faster for you to get results: read the docs and search
in the list before asking ;-)
e
That did it Thanks.
Upgrading though did not fix my original problem.
I am trying to use "not Matches" in a rule and I get the following error:
(this is even after upgrading to 4.0.2)
*
java.lang.RuntimeException*: Operator 'Operator = 'not matches'' does not
exist for ObjectEvaluator
here is t
Karl,
Seems you are getting an MVEL JIT related error... did you upgraded the
dependencies jars too (specially MVEL jar)?
[]s
Edson
2007/10/10, Karl Trout <[EMAIL PROTECTED]>:
>
> All I was trying to upgrade my application to use the latest 4.0.2
> release but I seem to be getting
All I was trying to upgrade my application to use the latest 4.0.2
release but I seem to be getting errors
when my application is calling
import org.drools.compiler.DroolsParserException;
import org.drools.compiler.PackageBuilder;
import org.drools.rule.Package;
import org.drools.rule.Rule;
Pack
Manukyan, Sergey wrote:
You should be able to serialise a Package without having to first add
it to PackageBuilder, we have numerous tests for this.
Mark, I looked at the test in PackageBuilderTest.testSerializable(),
but it is too syntetic, f.e. it doesn't use insert(...) function as I
d
Yes I've tried increasing it to 256mb. It didn't help. The memory continued
to grow at a rapid rate till it reached the 256 limit.
On 10/10/07, Andrew Thompson <[EMAIL PROTECTED]> wrote:
>
> Have you tried just increasing the size of your PERM generation? Maybe it
> is not a leak but simply that
Have you tried just increasing the size of your PERM generation? Maybe it is
not a leak but simply that you need just a little more than the JVM's default
limit?
--
Andrew Thompson
- Original Message
From: s erel <[EMAIL PROTECTED]>
To: Rules Users List
Sent: Wednesday, October 10, 2
Markus,
Yes, eval code block will pass through DRL compiler into the java
compiler. So you need to write the regexp as it is written in standard java
code.
Now, this must work:
Item( title matches "^Test\s*" )
Does not matter what characters title contains. If it is not working, i
You'll have to provide your own classloader which can read resources
both from your .jar file and from where you keep your .drl files.
See java.net.URLClassLoader for how to do that. (Include two URLs: one
to your .jar, one where you keep the .drl files.) You can pass the
loader to the package bui
Hi,
I've finished my first small application using JBoss Rules. My current
deployment "strategy" is that I want to have a single executable .jar file
containing my application and an external (not included in the .jar) folder
that contains the rules that should be used.
Unfortunately, this seems
rule "PatternTest"
when
$pli:Item( eval(title.matches("^Test\s*")) )
then
#
end
Having a second look i realize that the DroolsParser should not parse
the pattern string because it's java code ... and i can't use title
matches "^Test\s*" becau
I've tried it with trunk and the OOM error still happens.
In our project working memories/facts are not shared between threads. One
thread does not interfere with another thread rule evaluation.
Do we need shadow proxies for such a scenario?
The document says:
*IMPORTANT: disabling shadow facts
You should be able to serialise a Package without having to first add it
to PackageBuilder, we have numerous tests for this.
Mark, I looked at the test in PackageBuilderTest.testSerializable(), but
it is too syntetic, f.e. it doesn't use insert(...) function as I do in
my scenario. Please try cr
Markus,
Can you please show me your rule?
[]s
Edson
2007/10/10, Markus Helbig <[EMAIL PROTECTED]>:
>
> Hi,
>
> no same exception when i use "\\s". JDK didn't change when i switched
> from 3.x to 4.x
>
> Cheers
>
> Markus
>
> 2007/10/10, DELBART Vincent <[EMAIL PROTECTED]>:
> > Hi,
>
Hi,
no same exception when i use "\\s". JDK didn't change when i switched
from 3.x to 4.x
Cheers
Markus
2007/10/10, DELBART Vincent <[EMAIL PROTECTED]>:
> Hi,
>
> I think you have to use "Test\\s+".
>
> I don't think it's a DROOLS problem (maybe jdk).
>
> V.
>
>
> -Message d'origine-
>
Hi,
I think you have to use "Test\\s+".
I don't think it's a DROOLS problem (maybe jdk).
V.
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Markus Helbig
Envoyé : mercredi 10 octobre 2007 11:12
À : rules-users@lists.jboss.org
Objet : [rules-users] pa
Drools Documentation says:
Matches a field against any valid Java Regular Expression. Typically
that regexp is a String, but variables that resolve to a valid regexp
are also allowed. It is important to note that different from java, if
you write a String regexp directly on the source file, you do
22 matches
Mail list logo
