Something we discuss in EJB3 (related to the Plugin installer) is the
notion of a central installation/update mechanism, where each profile
(ie. EJB3, JPA, JMS, etc) has a set of imports/exports with proper
dependency chain and conflict resolution. Carlo draws an analogy to
yum/aptitude package managers.
So from an AS base you could do:
install ejb3 rails
...which would resolve dependencies upon metadata, jpa, rails-deployer,
etc, bring them in if necessary, and then install.
Currently the EJB3 Plugin overwrites whatever is there.
Big feature, useful for incremental upgrades to AS. Worth the
investment...another issue. ;)
S,
ALR
Dimitris Andreadis wrote:
Which should be the top JBossAS priorities going forward?
http://www.jboss.org/community/wiki/JBossASTop10
Feel free to propose areas and/or priority changes.
Cheers
/D
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Andrew Lee Rubinger
Sr. Software Engineer
JBoss, a division of Red Hat, Inc.
http://exitcondition.alrubinger.com