Hi Maxime,
thanks for the clarification! It was not clear to me whether there are
any channels established to write log messages to the server. I restored
the original logging mechanism now. All the log messages are written to
the screensharing.log (located in the download directory (the one the
underlying public_9.jnlp is written to) as stated. Great!
Maxime (or someone else with expertise in logging), if you let me know
the different "contexts" steering where the messages are written to
(error/openmeetings/red5 log), I can compile and summarize this
information for future reference.
Here's the template which needs to be completed (did I miss an option?):
------------------------------------------
*How to write to server logs?*
Init:
-----
import org.slf4j.Logger;
import org.red5.logging.Red5LoggerFactory;
(import org.apache.openmeetings.OpenmeetingsVariables;)
private static final Logger logger = Red5LoggerFactory.getLogger(*.class,
webAppRootKey); // you might need OpenmeetingsVariables.webAppRootKey
Openmeetings.log: webAppRootKey= ??? (default)
error.log: webAppRootKey= ???
red5.log: webAppRootKey= ???
Call:
------
-> logger.warn("log msg");
-> logger.debug("log msg");
*How to write to client log (Screensharing servlet)?*
Init:
-----
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
private static final Logger logger =
LoggerFactory.getLogger(ScreenSharerFrame.class);
screensharing.log (located in download directory)
Call:
------
-> logger.warn("log msg");
-> logger.debug("log msg");
-----------------------------------------------------------------
~~~~~~~
*Dr.-Ing. Rene' Rosenbaum
meeCoda^IT * - Consulting and Services
~: Neue Reihe 15, 18182 Goorstorf, Germany
#: ++49-(0)-1781408041
@:[email protected] <mailto:[email protected]>
//:www.meecoda.de <http://www.meecoda.de>
~~~~~~~~~~~~~~ +++ ~~~~~~~~~~~~~~~~
On 2/10/2014 6:54 PM, Maxim Solodovnik wrote:
Screensharing applet is client application and is unable to write into
server log.
It has loggers already (please search through its code)
The logs goes into console (can be enabled in javaws settings on the
client) and in the file screensharing.log (please search on the client
machine)
On Feb 10, 2014 8:33 PM, "Rene' Rosenbaum" <[email protected]> wrote:
Dear Maxime,
sorry, was unclear and incomplete in my statements! What I meant with
"dialog" is the screensharing dialog that doesn't come up when I integrate
the logger as descibed (in the constructor):
/private static final Logger logger =
Red5LoggerFactory.getLogger(ScreenSharerFrame.class,
OpenmeetingsVariables.webAppRootKey);//
//
//...//
////
//public ScreenSharerFrame(final CoreScreenShare m_core, String[]
textLabels) throws AWTException { //
//
//...//
//logger.warn("test");//
//logger.debug("test");//
//logger.trace("test");//
//}//
/
Not a single log (error/openmeetings/red5) shows the "test" entry. Any
ideas? Maybe its JAVA not accessed the right way.
Cheers,
Rene'
~~~~~~~
*Dr.-Ing. Rene' Rosenbaum
meeCoda^IT * - Consulting and Services
~: Neue Reihe 15, 18182 Goorstorf, Germany
#: ++49-(0)-1781408041
@:[email protected] <mailto:[email protected]>
//:www.meecoda.de <http://www.meecoda.de>
~~~~~~~~~~~~~~ +++ ~~~~~~~~~~~~~~~~
On 2/8/2014 6:16 AM, Maxim Solodovnik wrote:
no dialog will pop up
all messages will go to the log (openmeetings.log)
On Sat, Feb 8, 2014 at 4:06 AM, Rene' Rosenbaum <[email protected]> wrote:
Hi Maxim,
thanks for your quick reply! Tried it, but without success. Maybe its the
class?
=> private static final Logger logger = Red5LoggerFactory.getLogger(
ScreenSharerFrame.class,
OpenmeetingsVariables.webAppRootKey);
Compiles well, but dialog doesn't come up ... probably crashes before :(
Any idea what I'm doing wrong? Debugging is pretty though without the
option to log :)
Cheers,
Rene'
~~~~~~~
*Dr.-Ing. Rene' Rosenbaum
meeCoda^IT * - Consulting and Services
~: Neue Reihe 15, 18182 Goorstorf, Germany
#: ++49-(0)-1781408041
@:[email protected] <mailto:[email protected]>
//:www.meecoda.de <http://www.meecoda.de>
~~~~~~~~~~~~~~ +++ ~~~~~~~~~~~~~~~~
On 2/7/2014 4:56 PM, Maxim Solodovnik wrote:
Here is the example:
https://svn.apache.org/viewvc/openmeetings/branches/2.x/src/
org/apache/openmeetings/data/flvrecord/listener/
StreamListener.java?view=
markup&pathrev=1548014
the code will be:
private static final Logger log =
Red5LoggerFactory.getLogger(StreamListener.class, webAppRootKey);
webAppRootKey will be set to the current context (openmeetings by
default)
On Fri, Feb 7, 2014 at 9:34 PM, Rene' Rosenbaum <[email protected]>
wrote:
Hi all,
may someone tell me how I get any events logged in the openmeetings.log
or
red5.log?
I tried "LoggerFactory.getLogger(*.class);", but this didn't do the
job.
Any suggestions?
best regards,
Rene'
--
~~~~~~~
*Dr.-Ing. Rene' Rosenbaum
meeCoda^IT * - Consulting and Services
~: Neue Reihe 15, 18182 Goorstorf, Germany
#: ++49-(0)-1781408041
@:[email protected] <mailto:[email protected]>
//:www.meecoda.de <http://www.meecoda.de>
~~~~~~~~~~~~~~ +++ ~~~~~~~~~~~~~~~~
