Which MC deployer API ugliness are you talking about?
Deployer::deploy?
That's all there is to it.
Sent from my iPhone
On Apr 7, 2009, at 18:47, "David M. Lloyd" <david.lloyd(a)redhat.com>
wrote:
On 04/07/2009 11:37 AM, Carlo de Wolf wrote:
> So to rephrase:
> A functional requirement of Embedded is that we want to be able to
> easily configure a data source as per given pseudo code. (Other
> deployable elements to follow.)
> This would require changes in jboss-deployers and jboss-metadata.
> No change is needed in jboss-embedded, jboss-reloaded and/or jboss-
> bootstrap.
I don't think it would (or should) require changes to these modules
at all. It should be an additional Embedded configuration API which
*consumes* the various underlying metadata. This would have the
added advantage of being able to configure lots of unrelated things
using one simple API like Emmanuel's original suggestion. There's
no reason that the users of Embedded should have to know all about
the different metadata layouts of the various components, any more
than the average AS user should have to know.
Guys, modularization is one thing but it's critical that we think
about the API that the end-user will actually end up using. If it's
not easy to use, nobody will use it, period. That equals failure in
my book. I for one would rather use an API like Emmanuel suggested
than all the dozens of different metadata classes and the ugly MC
deployer API.
- DML
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development