David M. Lloyd wrote:
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.
I think following these steps would do well in figuring out hwo you want
the API to look:
* How hard is it to use within Eclipse?
* How hard is it to use within Intellij?
* How hard is it to use with a unit test for, EJB + JPA + JCA?
Why you create the first prototype. Try it out for all these scenarios.
This should tell you whether or not you're doing the right thing.
I'm probably stating the obvious, but too many times I see people not
actually trying out their own APIs.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com