This content has been marked as final. Show 5 replies
abhi_shek wrote:Your "java logging" is being mixed with the handlers for the platform ADF Logging - the way to seperate the two is to create seperate log handlers, and perhaps use ADF Logging (which is a simple extension of the java logging utilities) across your application.
kindly help on below issue...
i am using java util logging....
i come to know that my util logging messages are included in respective file and adf_diagnostic log also which i dont want..
A good primer with an introduction to the logging tools available in JDeveloper is available here:
… it's a multipart article covering ADF logging in JDeveloper 11.1.2.* - you might find it useful.
abhi_shek wrote:Yes - it would be your best choice in developing an ADF app. You'll have to tackle the task of setting up 'log handlers' and the like, but you'll get a lot of benefit out of doing so.
Thanks for the reply its really helpful....
just want to confirm that as per you post i should go for adf logger in whole code ???
i will go through the adf logger as suggested ...Good luck!
abhi_shek wrote:The best idea is the original one - using the ADF Logger. The problem you'll have with "updated messages on top" is that the logging packages and log handler file appenders will append output to the end of the file rather than the beginning. What you'll end up doing is using some kind of database log handler or some other custom type of log handling, when you could start with the ADF Logger and have the immediate ability to search and sort log messages - in your case the 'timestamp' of the log entry.
for release this plan is cancelled but only task i have is to print the java util logs in updated first manner i.e. i have to see the updated messages on top ... i went through some links but could not get the solution.
The requirement you stated will actually be more difficult to implement (in my opinion) than using the ADF Logging classes.