> -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED] > Sent: mardi 25 octobre 2005 00:46 > To: Maven Developers List > Subject: Re: [M2][Proposal] J2EE builds best practices and conventions
[snip] > > Cool. I wonder if there could be synergies with Cargo... It seems there > is > > potentially some overlap. > > > > Cargo could even possibly be used internally by Smartfrog to > > start/stop/deploy to containers as it already supports a big number of > > containers... The opposite could be true so that Cargo could have an EL > for > > generating container configurations (ATM we have either a default config > for > > which users can configure important parameters such as ports, log > levels, > > security, etc) or a config provided by the user). > > > If it works in a world of signed jars, then yes, we could use it. I'm not sure whether this affects Cargo or not. The only jars manipulated by Cargo are the J2EE modules (WAR, EAR, RAR, etc) that need to be copied/deployed into the containers and those are not created by Cargo so they're pretty transparent (one exception though: Cargo can do some introspection to look for container-specific deployment descriptor in those J2EE modules but that's optional). > Another thing we like to add is liveness; that is every component > supports a health check that can be triggered in a walk down the graph > of deployed components. Some components do nothing but liveness, such as > one that probes for a web page and fails if the response is out of > range, the size too small or the content type wrong. Cool. This is useful. Cargo is not a monitoring tool. It's just a wrapper that provides a common Java API to configure, start, stop containers and deploy J2EE archives into them. So I guess it could be used by a higher level framework such as smartfrog for at least container start/stop. WRT the configuration, we have something very basic that I'd like to improve but as Cargo supports existing configuration too it should be easy to integrate with any tool that generates the config itself. In any case thanks for pointing out smartfrog. This gives me a new perspective. I'll need to understand it better but it gives me a new perspective for cargo to see how it fits into this ecosystem of J2EE management in general. I've started a wiki page on http://cargo.codehaus.org/Comparisons+with+other+tools?refresh=1 I'd be interested to get your feedback on it. [snip] > Grab the latest release off the site -http://smartfrog.org/ . Start with > the tutorial. I dont think we have any out the box demo apps, but maybe > we should. Ok. I'll try to find some time to play with it... Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
