CTED]
> [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
> compone
inal 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 a big difference in granularity between the code in the
component being de
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 d
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 lo
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:
>
>12:11
Maybe this should be marked as INFO, not DEBUG:
12:11:58,396 DEBUG [MainDeployer] Done deploying someear.ear
Seems like useful information that the server is done deploying the ear...
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists
