[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Slow startup, deploying "transitively complete" applications, custom deployer howto
- From: Dmitry Sklyut <dmitry@xxxxxxxxxxx>
- Date: Wed, 2 Jun 2010 14:25:16 -0400
- Delivered-to: email@example.com
I just realized that forum is not notifying me when there are new replies, only new threads.
To give a quick update. I did not get the time to do what I wanted with profiling of the application. I will pick up your pom and give it a try later this week. This is a much simpler set-up than the 5 plan thing that I have :)
On question 3 - it is possible right now to create new deployment artifact types. I will have to dig out my research on this subject and will follow to the list. There was one thing that scared me along the way, is that some transformers cast to an Abstract implementation of DeploymentArtifact (or something like that) and that class was in an internal package. My impression was that any new deployment artifact type must be created as a fragment bundle. I will find details and post them here.
2010/6/2 Peter Gardfjäll <peter.gardfjell@xxxxxxxxx>
I've made a couple of posts on the forum thread
without receiving a reply.
Maybe my posts have passed unnoticed (or could the poor response be
due to lack of interest?).
Anyhow, I thought I'd try my luck on the mailing list instead.
Basically I have three questions:
(1) Has there been any progress in investigating the "slow startup issue"?
(2) Also, Glyn, in the original forum thread (at Spring dm,
you mentioned ideas about providing support for deploying
"transitively complete" applications/subsystems. Is this on Virgo's
(3) Finally, I assume that it is possible to hook in additional
deployers (handling new types of deployment artifacts) in Virgo. If
this is the case, I'd appreciate any pointers on how to get started
(what interfaces need to be implemented, what design guidelines should
be adhered to, etc)?
virgo-dev mailing list