[higgins-dev] Log4J vs JSR47 loggers in Higgins' IdAS code

[Prakash C Mallick <prakash.mallick@xxxxxxxxxx>]

Hi All,
           I
found that higgins' IdAS uses log4j for lgging . As IdAS APIs consumer
will be from different organizations, they will have their only guide lines
for selecting a logging framework , this sort of direct usage of logging
calls from Log4J will have the following limitations.

1. Say an existing software uses JSR47 logging framework and they plan to use IdAS API in one of their component. They will niether prefer to maintain two logging frameworks simultaneously to use IdAS API  nor will they will prefer to move to log4j if they plan to use IdAS API. Admining two logging mechanism in one software will be not a good idea and also if the software is having a large code base , its not possible to move from one existing logging frame work to Log4J.
2. Loggers as choosen based on performance, internationalization flexibility , better features and so on , but this way the user will have no choice but stick to log4j even if its a good logging toolkit.
3. Many roganizations will have their own logging framework or they will have some standard to use a specific logging framework . So using IdAS API based on Log4J may not be possible for them.

Similarly there can
be many such limitation which needs to be identified.

To over come such issues, Is it possible
to implement logging using one of the following ways or any other ways
which can help in avoiding such issues mentioned above.

1. Replace Log4J with JSR47  (preferrable as  in many areas JSR47 is the preferred logger compared to Log4J)
2. Write a wrapper logging framework which can be either configured for Log4J and JSR47

Thanks and Regards,
Prakash
---------------------------------------------------------------------------------------------------
Advisory Software Engineer,
Tivoli Security Products
India Software Lab, IBM Software Group
Ozone, SP Infocity, Saswad Road, Fursungi, Pune 412 308
Ph: +91-20-2690-1013
e-mail: prakash.mallick@xxxxxxxxxx
---------------------------------------------------------------------------------------------------