RE: [JBoss-dev] Deployer Message

2002-02-25 Thread Georg Schmid
] [mailto:[EMAIL PROTECTED]]On Behalf Of danch Sent: Monday, February 25, 2002 04:46 To: Jason Dillon Cc: Hunter Hillegas; JBoss Dev Subject: Re: [JBoss-dev] Deployer Message There's a big difference in granularity between the code in the component being deployed and the component itself: do you

Re: [JBoss-dev] Deployer Message

2002-02-25 Thread David Jencks
looked very hard at it however. david jencks Georg -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of danch Sent: Monday, February 25, 2002 04:46 To: Jason Dillon Cc: Hunter Hillegas; JBoss Dev Subject: Re: [JBoss-dev] Deployer Message There's

Re: [JBoss-dev] Deployer Message

2002-02-24 Thread Jason Dillon
I probably changed it from info to debug, in that this information is only useful when debugging a deployer problem. Other info level messages should be provided by the component that has been deployed. --jason Hunter Hillegas wrote: Maybe this should be marked as INFO, not DEBUG:

Re: [JBoss-dev] Deployer Message

2002-02-24 Thread danch
There's a big difference in granularity between the code in the component being deployed and the component itself: do you suggest that I have a static initializer in all of my beans that logs 'hey, i've been loaded'?. Even picking an arbitrary component (from those that _do_ get their class

Re: [JBoss-dev] Deployer Message

2002-02-24 Thread Jason Dillon
In the case of a bean, the bean's container will log creating/created starting/started as INFO. Take a plain .jar file (which is deployed with jboss3), there is nothing here to say. If it does not load then an exception is thrown. Yes notifications. --jason danch wrote: There's a big