We would need to know which ones apply to EAP.
When I say apply I mean the ones that actually manage subsystems
that will be deployed on AS7. Excluding those that manage external resources like Apache,
etc.
Would it be possible to get list of plugins with a brief description?
Maybe such a list already exists somewhere?
In order to do a fair judgement, we would need to know how much porting effort
we actually speak about.
A second interesting question address the abstraction between the plugin (or container)
and the managed runtime components. I would expect an adaptor layer that mediates
changes between target runtimes (i.e. AS4, AS5) and the actually plugin container
versions.
If such a layer exists, can it accommodate the changes required to run on the new domain
model,
so that the plugin doesn't need to be changed?
Ike
On Jan 12, 2011, at 1:28 PM, Heiko W.Rupp wrote:
Am 12.01.2011 um 09:41 schrieb Heiko Braun:
> [Plugin re-use]
> It would be interesting to know about how many plugins we actually speak about.
> The smaller the number, the the more reasonable it becomes to simply rewrite them.
We (= RHQ project have ~50 plugins, where not all apply) and then there are
external ones like HornetQ, Infinispan, SOA-P, Dataservices, ...
--
Reg. Adresse: Red Hat GmbH, Otto-Hahn-Strasse 20, 85609 Dornach bei München
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles Cachera
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev