Are you sure you're using 4.1.1? It works here...
On Sat, 07 Oct 2006 00:36:52 +0200, Leo Sakhvoruk
<[EMAIL PROTECTED]> wrote:
Thanks for such a quick response, still no luck though.
Leo
Jesse Kuhnert wrote:
Ahh..Looks like I made it so that you have to use an ognl expression ...
Try deb
Thanks for such a quick response, still no luck though.
Leo
Jesse Kuhnert wrote:
Ahh..Looks like I made it so that you have to use an ognl expression ...
Try debugEnabled="ognl:false" .
On 10/6/06, Leo Sakhvoruk <[EMAIL PROTECTED]> wrote:
Hi Jesse,
I tried disabling the dojo debug message
Ahh..Looks like I made it so that you have to use an ognl expression ...
Try debugEnabled="ognl:false" .
On 10/6/06, Leo Sakhvoruk <[EMAIL PROTECTED]> wrote:
Hi Jesse,
I tried disabling the dojo debug message in the Shell component per your
instructions but I get the following runtime excepti
Hi Jesse,
I tried disabling the dojo debug message in the Shell component per your
instructions but I get the following runtime exception:
Component .shell allows only formal parameters,
binding debugEnabled is not allowed.
This is how I define the Shell component:
Sounds like a sensible default behaviour, I just hadn't seen the
debugEnabled parameter. Thanks.
Martin
On Tue, 03 Oct 2006 23:22:19 +0200, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
Yeah, I thought the most common default behaviour would wanting debug on
-
so that's what I've done...If pe
Yeah, I thought the most common default behaviour would wanting debug on -
so that's what I've done...If people find this to be counter-intuitive I'll
disable it by default.
You can control the log levels, as well as whether it's on at all via the
@Shell component "debugEnabled" parameter.
http:
