Community
Participate
Working Groups
Hi A java logging view would be interesting in java perspective and to offer message filtering, coloring, etc. Best regards piri
What do you mean by "Java logging view". Which log should the view show ?
I mean the logger from JDK (java.util.logging); something like LogFactor for log4j. br piri
This would be an excelent thrid party opportunity.
I have started working on a console for the J2SE logger. It is quite basic at the moment (just a proof of concept). So far it just starts a server thread to process the log events and prints them as text to a console. It would be possible to add filtering of logging events and colouring based off severity. It would also be possible to have custom formatting of the events. Basically when a console page is opened it will spawn off a thread that opens a server socket and starts listening (with a set port number). Server control actions would be exposed as actions on the console page (stop and start). Before I waste too much more time on this, is this something JDT really wants to add to the SDK? It would be possible to distribute it as a standalone plugin, but it could be quite powerful if it was a part of the SDK. For instance, a new server could be automatically started when a Java program is debugged (and logging options turned on). I have a patch to expose logging options in bug 86749 but I don't know it will be added to the SDK. If the two functions were combined it could be quite useful.
A console for J2SE logging should IMO be integrated into the console view framework. We shouldn't come up with a separate view part for this. Moving to Debug since a J2SE logging view should be hosted there. Darin, can you please comment on this.
Created attachment 26821 [details] Basic implementation of a logging console A *very* basic implementation of a logging console. Creating a console will start a server on port 9999 which will only accept one connection at a time. The implementation uses MessageConsole but should be changed to use its own console page and source viewer (and associated document). I will make the implementation more robust and add new features if there is enough interest (haven't seen much so far).
Just updating to say we still have not had time to review this contribution.
Deferred for post 3.2 (limited resources)
any chance this will be looked at in 3.3?
Currently, this is not on our radar. If you would like to update the patch to ensure it is 3.2 compatible (for 3.3) and of high quality, we can likely review it as a contribution.
reopening
