I had seen something similar long time ago when measuring the memory footprint of an
MBean,
it was quite significant.
It would be interesting to measure the memory overhead of a POJO (metadata and all), but
as
Bill suggest, having more coarse grained POJOs is better than many fine grained ones.
Bill Burke wrote:
Brian Stansberry wrote:
>> * How about making our bean.xml files more coarse grain? Meaning *A
>> LOT* less implementation details exposed through XML. You can do IoC in
>> Java you know. The vast majority of details within all our beans.xml
>> files will never ever change, nor will we want to support users changing
>> this stuff. If our beans.xml file are reduced to a few bean definitions
>> and classes, would make parsing and creating bean metadata much much faster.
>>
> Semi-related, the ServiceBindingManager config needs a schema and a
> parser. I create a lot of MC beans for SBM, most of which the MC has no
> need to know anything about.
>
EJB and Webservices create an insane amount of beans that can probably
be collapsed into a few beans.