9 AM
Subject: Re: [JBoss-dev] Deployers lifecycle/logging question
>
> Scott,
>
> What does this mean? Log4j appenders will output events in the order
> it receives them. Do you have something else in mind?
>
> > There is no guarentee of log m
Scott,
What does this mean? Log4j appenders will output events in the order
it receives them. Do you have something else in mind?
> There is no guarentee of log message ordering in the standard log4j
> appenders.
>
>
> Scott Stark
> Chief Technology Officer
> JBo
>
Sent: Friday, May 24, 2002 3:55 AM
Subject: Re: [JBoss-dev] Deployers lifecycle/logging question
> Hi Alex!
> Does log4j guarantee to display the log messages in the order they
> timely occured ?
>
> With the old logging that wasn't the case (it was NOT guaranteed). It d
Hi David
> The FoeDeployer should register with MainDeployer as the last thing it
does
> in startService(), when it is in fact usable. So at least you should move
> super.startService() to the end.
Done.
> I just looked at the code and think that a simpler design would be to
> simply have the
Hello David,
Friday, May 24, 2002, 5:17:19 PM, you wrote:
DJ> The FoeDeployer should register with MainDeployer as the last thing it does
DJ> in startService(), when it is in fact usable. So at least you should move
DJ> super.startService() to the end.
Yes, it even caused problem determining c
On 2002.05.24 10:02:08 -0400 Alex Loubyansky wrote:
> Hello David,
>
> Friday, May 24, 2002, 4:20:33 PM, you wrote:
>
> DJ> From your description below I think FoeDeployer depends on
> DJ> WebLogicConverter. If you explicitly state this dependency with a
> depends
> DJ> tag the deployment syste
The FoeDeployer should register with MainDeployer as the last thing it does
in startService(), when it is in fact usable. So at least you should move
super.startService() to the end.
I just looked at the code and think that a simpler design would be to
simply have the WLC be a SubDeployer. You
Hello Alex,
I've got it.
[FoeDeployer] Starting - the beginning of the method
FoeDeployer.startService()
[FoeDeployer] Started - the end of it.
But it looks messy in case of deploying (actually any) deployer when
there are waiting deployable units.
alex
Friday, May 24, 2002, 4:53:33 PM, you w
Hello David,
Friday, May 24, 2002, 4:20:33 PM, you wrote:
DJ> From your description below I think FoeDeployer depends on
DJ> WebLogicConverter. If you explicitly state this dependency with a depends
DJ> tag the deployment system will create WLC before FD and start WLC before
DJ> FD. If FD is d
Hello David,
I asked that because I found it strange that the deployer not being
started already deploys some units, if the log is right. So, the log
is like:
[FoeDeployer] Starting
[MainDeployer] Adding deployer:
[MainDeployer] Starting deployment of package:
[FoeDeployer] create()
...
>From your description below I think FoeDeployer depends on
WebLogicConverter. If you explicitly state this dependency with a depends
tag the deployment system will create WLC before FD and start WLC before
FD. If FD is designed to accept lots of converters you can use a
depends-list element.
H
Hello Tobias,
good question. I'd like to know too.
Friday, May 24, 2002, 1:55:26 PM, you wrote:
TF> Hi Alex!
TF> Does log4j guarantee to display the log messages in the order they
TF> timely occured ?
TF> With the old logging that wasn't the case (it was NOT guaranteed). It do
TF> not know f
Hi Alex!
Does log4j guarantee to display the log messages in the order they
timely occured ?
With the old logging that wasn't the case (it was NOT guaranteed). It do
not know for log4j.
Just a thought,
Tobias
Alex Loubyansky wrote:
>
> Hello,
>
> I am now testing FoeDeployer and have a que
Hello,
I am now testing FoeDeployer and have a question that, probably, affects
behaviour of other deployers too.
Suppose we have deployment units in the deploy dir waiting for the
deployer. And the deployer is at last deployed. I expect the following
sequence of calls on the deployer: createS
14 matches
Mail list logo
