Matt Hogstrom wrote:
As Aaron said we have made significant progress in testing againnst our
test harnesses but there are lingering issues that need to be
addressed. Aaron (aka the JIRA magnet) has identified several usability
and bug issues. The first release that we put our is stable
Aaron Mulder wrote:
Please do any work in the 1.1 branch. Right now 1.2 is in a very
uncertain state. Though, I suspect the issues will be different in
1.1, so you may want to start by testing the same things there.
IIRC, the hot deployer does not yet check the timestamp of the
deployments
On 5/4/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
I thought 1.1 was done and in testing in prep for release?
No, there are still plenty of serious bugs (including, it would seem,
with the hot deployer). We're close enough that we cut a build so
people don't have to build from SVN, but I
I suggest you start by reading the SingleFileHotDeploy service I
wrote last week. It uses the most recent apis.
-dain
On May 3, 2006, at 10:30 PM, Rakesh Ranjan wrote:
I have seen the same problems with Geronimo-1.1-SNAPSHOT also. So i
will create JIRA ID for these two issues and start
Can anybody please tell me the purpose of SingleFileHotDeploy service. Is it same as the purpose of hot deployment directory?
Rakesh RanjanOn 5/4/06, Dain Sundstrom [EMAIL PROTECTED] wrote:
I suggest you start by reading the SingleFileHotDeploy service Iwrote last week.It uses the most recent
As Aaron said we have made significant progress in testing againnst our test harnesses but there are
lingering issues that need to be addressed. Aaron (aka the JIRA magnet) has identified several
usability and bug issues. The first release that we put our is stable (DayTrader runs in most
SFHD is similar to hot deployer but has these differences:
- It is not an integrated part of the server itself. It is a gbean
itself that must be deployed into the server to use it.
- It only takes action when the SFHD gbean is started (which is
typically during server startup). Hot
Thanks Joe.
Still i have some confusions.
Is SFHD the substitute for the DirectoryHotDeployer ? If it is
substitute, then do we need to disable the hotdeployment GBean for the
working of SFHD?
What is the meaning of It monitors just one directory for one deployable element ?
Rakesh Ranjan
On
For purposes of the hot deployer functionality, forget that the SFHD
even exists. It is a special case feature, and does not at all
replace what the hot deploy directory does.
However, for purposes of updatng the hot deployer implementation, you
may want to refer to the SFHD implementation.
Aaron, Thanks for clarification.
We will work without conflicting. I am going to touch the startup
problem. I mean if a module kept in hot deployment directory is already
deployed, the server should not deploy the module again during the
startup. Currently the server try to deploy the module
When you're working on that, you should be sure to test with several
types of modules -- one module with a fully-specified configId (group,
artifact, version, and type), one module without a configId, and one
module with a configId but no version in the configId -- it ought to
work all ways (and
Exactly. I wrote the SFHD to demonstrate how one does hot deployment
with the new ConfigurationManager apis. I expect this code to be
rolled into a new hot deployer implementation in 1.2 (and deleted).
Below you asked What is the meaning of It monitors just one
directory for one
You're welcome to look at that. Can you list the issues you're going
to attempt to fix? There seems to be a lot of variation in what
people think the problems actually are.
Thanks,
Aaron
On 5/4/06, Rakesh Ranjan [EMAIL PROTECTED] wrote:
Hi all,
I have not seen much activity in hot
Thanks Aaron for the quick response.
Here are two issues with Geronimo-1.2-SNAPSHOT which need to be fixed :
1. When Geronimo starts, it try to deploy the modules in the hot
deployment directory even if that module is already deployed. Since
the application is already deployed, it throws an error
Please do any work in the 1.1 branch. Right now 1.2 is in a very
uncertain state. Though, I suspect the issues will be different in
1.1, so you may want to start by testing the same things there.
IIRC, the hot deployer does not yet check the timestamp of the
deployments in it its directory
I have seen the same problems with Geronimo-1.1-SNAPSHOT also. So i will create JIRA ID for these two issues and start working.
Rakesh RanjanOn 5/4/06, Aaron Mulder [EMAIL PROTECTED] wrote:
Please do any work in the 1.1 branch.Right now 1.2 is in a veryuncertain state.Though, I suspect the issues
16 matches
Mail list logo
