Hi Russel. Yes that would be the exact problem that Steven and Edson chased
down and will be in 3.0.5, so it should go away.
eval() will work as it generates classes ahead of time, whereas the field
accessors generate them lazily, on demand, first access or deserialization
etc.. (and were not inheriting perms correctly - but that should be OK now).
Its possible we will one day have a version that has no
classworking/generation, but its probably not likely, as we (along with
other frameworks like hibernate) will always do some class generation (via
ASM or otherwise) for dynamic proxying, performance related etc etc.. (its
the way of the future ! especially with javax.compiler in java 6).
Any one want to volunteer some specific instructions on how to config
security for WAS 5/6 and we can put it up on the wiki? (either mail it
around, or add it to the wiki directly) as this will no doubt help others.
THanks to EVERYONE that replied with their details, good to know that many
have had success on websphere.
Michael.
On 11/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Environment: WAS 5.11 (along with various service packs), drools 2.1, 2.5and
3.04
Hi,
We had major issues with drools running with J2EE security turned on. With
security turned off everything worked fine. The issue seemed to similar for
drools version 2.1, 2.5 and 3.04--basically at startup, when compiling the
rules file, drools will blow up.
We tried to get around it by changing the version of drools (particular as
v3 was such a major change). It didn't help. We then tried serialising the
rules separately and loading the serialised rules at start up--different
error, but no luck. We eventually realised that if we wrote the rules using
the statement eval() only (along with serialised rules), we could get things
to work.
ie instead of
account : AccountRequestItem (bankId != null)
write:
account : AccountRequestItem ()
eval ( account.getBankId() != null)
Of course this isn't ideal, but at least it works.
Thanks,
Russell
---- [EMAIL PROTECTED] wrote:
>
> Sorry for late reply... we didn't do anything specific that I know of...
> we had some memory leak issues with an older version of drools, but
> everything got sorted out once we installed 3.0.4 (If I recall well it
> was a 3.0RC that we were using) ...
>
>
> Other than that I do not recall having any specific issues on the
> matter...Feel free to ask anyway (just send directly to my email so I do
> not overlook it as this mail)
>
>
>
> ________________________________
>
> From: Michael Neale [mailto:[EMAIL PROTECTED]
>
> Sent: 16 November 2006 15:54
> To: [email protected]
> Subject: Re: [drools-dev] Anyone using websphere & drools
>
>
> and no issues with permission of accessing classes from generated code
> or anything? did you have to flick any magic switches (now I am *really*
> showing my ignorance of websphere).
>
>
> On 11/16/06, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
>
>
> We are...
>
>
>
> Drools 3.0.4
> WS 5.1.1.1 & Portal 5.1
>
>
> Brgrds,
> Matias
>
>
>
> ________________________________
>
> From: Michael Neale [mailto:[EMAIL PROTECTED]
>
> Sent: 15 November 2006 12:42
> To: Drools User List; [email protected]
> Subject: [drools-dev] Anyone using websphere & drools
>
>
>
>
>
>
> Any version of drools? (and let me know what version of WS and
> rules).
>
>
> (if needs to be confidential, feel free to email me directly).
>
>
> Michael.
>
>
> **** DISCLAIMER ****
> http://www.belgacom.be/maildisclaimer
>
>
>
>
>
>
> **** DISCLAIMER ****
> http://www.belgacom.be/maildisclaimer
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
