Hi Fred, The configuration you have to modify is in environment.xml. Because a while ago Phoenix was using its own mechanism to configure the logging hierarchy there are two logging configuration versions (for backward compatibility). You are interested in version 1.1 which uses DefaultLogkitManager. An example of how to use DefaultLogkitManager configuration you can find here: http://cvs.apache.org/viewcvs/jakarta-avalon-excalibur/src/test/org/apache/a valon/excalibur/logger/test/LogKitManagementTest.xtest?rev=1.3&content-type= text/vnd.viewcvs-markup
Now to enable DefaultLogkitManager usage you have to add a version attribute to the logging configuration in environment.xml : <logs version="1.1"> ....</logs>. Once you did that you can use JMSLogTarget-s, here is the configuration example : http://jakarta.apache.org/avalon/excalibur/api/org/apache/avalon/excalibur/l ogger/factory/JMSTargetFactory.html Maybe I should add that the choice of *text* message formatters are: 'extended', 'raw', and 'xml' (I will try to update the docs). Mircea > In order to have better centralized logging, I would > like to use JMS Log targets to set up a JMS Topic (or a hierarchy of > them) and have all blocks log to these topics. > > I cannot see however how to configure a JMS log target with phoenix, either > through the server.xml file (which I guess is now the environment.xml file), > or through any other mechanism. > > Can anyone point me in the right direction? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
