logo       

FYI: Logging in Enhydra 5.1 vs Enhydra5.0: msg#00078

java.enhydra.general

Subject: FYI: Logging in Enhydra 5.1 vs Enhydra5.0

Hi,

1)
I'm currently getting a look at enhydra5.1 which have a more
powerfull logging system but take note that old construct such as

Enhydra.getLogChannel().write(Logger.INFO,msg);
Enhydra.getLogChannel().write(Logger.DEBUG,msg);
Enhydra.getLogChannel().write(Logger.ERROR,msg);

are now all logged under the same level: INFO

2) and take also note that construct such as

exception.printStackTrace(Enhydra.getLogChannel().getLogWriter(Logger.ERROR));

will now throw a NullPointerException because Enhydra.getLogChannel()
return a null pointer.


3)
Also the default setting I used to take (INFO) now receives
a lot informative messages from the classes MultiClassLoader, ClassPath
and ClassPathEntry everytime a class is loaded, but it is probably
just a matter of configuration to get rid of them by default
(in my to do list)

4) Note also that the generated classes from the new DODS now
have two constructs in private void runQuery()
that are using System.out.println
System.out.println("DocumentDO"+" Read from Database");
System.out.println("DocumentDO"+" Read from Cache");
Should not they be removed?

5) BTW I recently talk about a problem I had
with using comma separated string in the configuration.
I solve my problem, it was the quote.
I should not have used
Server.ClassPath[] = "path1/classe1.jar, path2/classe2.jar"
but
Server.ClassPath[] = "path1/classe1.jar" , "path2/classe2.jar"

Daniel

_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise