|
| Re: org.eclipse.rwt.clientLogLevel - how to use? [message #48384 is a reply to message #48354] |
Wed, 19 September 2007 20:10  |
Eclipse User |
|
|
|
Originally posted by: rsternberg.innoopract.com
Hi Ryan,
Ryan Donnelly schrieb:
> Hi, I am not getting the VM argument "org.eclipse.rwt.clientLogLevel" to
> do anything. I have added -Dorg.eclipse.rap.rwt.clientLogLevel=ALL to
leave out the ".rap" and you'll probably get the the extra window. The
correct parameter is "org.eclipse.rwt.clientLogLevel". If you have
Firebug installed, it could also be that the logging goes directly to
the Firebug console.
> my launch configuration, but I don't see any additional logging to the
> console, nor do I see the extra window described in this bug comment:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=189686, Comment 4.
>
> "Note:
> If you specify -Dorg.eclipse.swt.clientLogLevel=ALL as a VM argument in
> your launch configuration there will be opened a secondary browser
> window that shows debug and error messages."
>
> I have tried both the old (with "swt",
> -Dorg.eclipse.rap.swt.clientLogLevel=ALL) and new (with "rwt",
> -Dorg.eclipse.rap.rwt.clientLogLevel=ALL) arguments (the change of the
> argument is mentioned here:
> http://wiki.eclipse.org/index.php/Rap10M6_News).
>
> Is there any documentation on org.eclipse.rwt.clientLogLevel and the
> other VM arguments? Or at least a list of them?
No, a proper documentation on these parameters is still missing, but
we're currently adding some more articles to the RAP Help. Of course,
the properties should also be covered there.
Anyway, the important properties are:
- org.osgi.service.http.port
- org.eclipse.rwt.clientLogLevel=ALL to enable client logging
- org.eclipse.rwt.clientLibraryVariant=DEBUG for using a
debugging-enabled qx lib instead of the performance-optimized one
Hope that helps so far,
Ralf
|
|
|
Powered by
FUDForum. Page generated in 0.03027 seconds
] 
Search
Help
Register
Login
Home
