Hi Eddie,
I didn't see any reply to this message you sent a while ago so:
Edde wrote:
> Is it possible to propagate log events to the application layer?
>
The cleanest way to do this is is to provide your own logger by
extending the existing FileLog (as you mention below).
> What I need is a way to propagate low level problems (for example
> connection problems) to the application so that users have a way of
> knowing what's going on. My current solution is to customize QuickFix
> by overriding the onEvent(String message) method in FileLog to capture
> the relevant messages and then passing them on to my application.
> However, in the future I'd rather not have build my own version of
> QuickFix everytime there is a new version so is there a different way
> to do what I want?
> The other option is to create my own subclass of FileLog but from what
> I can understand this also means I need to override the FileLogFactory
> to actually create my own instance of FileLog.
>
Yep. You need to provide your own factory in order to provide your own
logger, but it's no big deal. The required code is dead-simple.
Dale
> Cheers,
> /Eddie
>
|
