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
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 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()
...
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
