[
https://issues.apache.org/jira/browse/LOG4NET-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682328#action_12682328
]
Jerome Haltom commented on LOG4NET-196:
---------------------------------------
The main problem is the subject. There is no way I can find to set up
RemoteLoggingAppender to work between AppDomains. The requirement is that I
give the Appender a remote object Url. But when working between AppDomains, I
don't have a remote object Url. I can get references to MarshalByRefObjects,
but not the url of those objects when exposed. Without the url I cannot
configure the appender.
What needs to be changes is there needs to be an alternative way to configure
the appender. My local patch (which is not very well done) adds a property to
RemoteLoggingServerPlugin called Sink, which returns IRemoteLoggingSink. I
think change RemotingAppender.Sink to IRemoteLoggingSink. When configuring the
appender in AppDomain #2 (by hand) I retrieve the Sink from the Plugin in
AppDomain #1, hand the sink to AppDomain #2, and set it on the Appender.
So, something like that.
> Remote Logging Stuff doesn't seem to have anyway to work between AppDomains
> ---------------------------------------------------------------------------
>
> Key: LOG4NET-196
> URL: https://issues.apache.org/jira/browse/LOG4NET-196
> Project: Log4net
> Issue Type: Bug
> Reporter: Jerome Haltom
>
> There's no way to obtain a proper url to a IRemoteLoggignSink that ends up
> being published in the local app domain.
> There needs to be a way to set the IRemoteLoggingSink instance specifically,
> managing the remoting yourself. This would solve it easily.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
