[jboss-dev] JBoss Bootstrap, Embedded & Reloaded

[Andrew Lee Rubinger]

Bill Burke wrote:
> 
> 
> 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?

The only criteria I'm presently considering is:

* How hard is it to use in POJO Unit Tests?

...what do you think I'm missing that's specific to some particular IDE?

The Unit Testing deployment stuff should start to get addressed when the 
start/stop/deployment API is done, where we build nice VFS deployment 
units to assemble virtual packages.

> I'm probably stating the obvious, but too many times I see people not 
> actually trying out their own APIs.

The Integration Tests for the APIs should cover this, as well as be a 
form of self-documentation.

S<
ALR

-- 
Andrew Lee Rubinger
Sr. Software Engineer
JBoss, a division of Red Hat, Inc.
http://exitcondition.alrubinger.com