with 'Log::Contextual::Role::Router';
with 'Object::Remote::Role::LogForwarder';
-#lookup table for package names that should not
-#be forwarded across Object::Remote connections
has _connections => ( is => 'ro', required => 1, default => sub { [] } );
has _remote_metadata => ( is => 'rw' );
sub _invoke_logger {
my ($self, $logger, $level_name, $content, $metadata) = @_;
#Invoking the logger like this gets all available data to the
- #logging object with out losing any information from the structure.
+ #logging object with out losing any information from the datastructure.
#This is not a backwards compatible way to invoke the loggers
#but it enables a lot of flexibility in the logger.
#The l-c router could have this method invoke the logger in
+#During testing of Object::Remote this logger is connected
+#to the router and runs at trace level but does not output anything.
+#This lets the logging codeblocks get executed and included
+#in the testing.
+
package Object::Remote::Logging::TestLogger;
use base qw ( Object::Remote::Logging::Logger );
has enable_forward => ( is => 'rw', default => sub { 1 } );
has _forward_destination => ( is => 'rw' );
+#lookup table for package names that should not
+#be forwarded across Object::Remote connections
has _forward_stop => ( is => 'ro', required => 1, default => sub { {} } );
after _deliver_message => sub {