Thanks Nicko,
I can understand where you are coming from with keeping the XMLLayout
generating only the fragments. However, imagine the following:
http://log4net.sourceforge.net/";>
"/>
Rich,
There is a mapping from Assembly instance to domain. If the Assembly has a
DomainAttribute then it will be to that domain, otherwise it will be to the
default domain. The LogManager.GetLogger(string) method passes
Assembly.GetCallingAssembly() to the
LoggerManager.GetLogger(Assembly,string)
Rich,
There is a one-to-one mapping between domains (which are just names) and
repositories. However domains can also be aliased which means that multiple
domains may point to the same repository.
Nicko
> -Original Message-
> From: Denis, Rich [mailto:[EMAIL PROTECTED]
> Sent: 07 June 2
I was developing a component library that I
thought I would create its own repository for. I have added the necessary
Domain attribute to create it. What I want to know is if I call
LogManager.GetLogger() does the fact that the Logger is
getting created in the context of the assembly that
Nicko,
Getting back to a question that I had long ago Concerning
Repositories and "Domains", is there only one repository per domain? Your
email says if I want to create a repository I add a new domain attribute.
This leads me to believe that there is a one to one mapping between the t
The XmlLayout generates XML Fragments for each message. XML does not lend
itself too well to a streaming format.
When using the XmlLayout with the FileAppender or RollingFileAppender the
file written will not be a valid XML document. It is a valid XML fragment.
However it can be included in a docu
The SmtpAppender works fine with any SMTP mail server (it uses the
System.Web.Mail classes). It works great with my Exchange 5.5 server, but
that's because it is configured to accept SMTP mail.
IIS includes an SMTP server so you may be able to set that up to send mail
for you.
Alternatively you m