I kinda disagree. I think supporting the EJB3 programming model (by
leveraging an existing EJB container such as OpenEJB) and allow easy
deployment inside ServiceMix, along with exposing those EJB3 directly
as NMR/JBI endpoints would be really nice. Kinda like what
servicemix-cxf-se provides, but with full support for EJB3.
We could also directly allow EJB3 to be exposed as web services, as we
already integrate CXF ...
If we talk about integrate an existing EJB container into SMX, I'm
totally agree. Exposing directly EJB3 as endpoints it's a overkill feature.
My comment was more to avoid to reinvent the wheel by implementing a
kind of minimal EJB container inside SMX, it's better to use an existing
implementation.
- Provide web admin interface,
I'm agree, I will try to begin a proto soon.
There is a GsoC project for that, see
http://cwiki.apache.org/confluence/display/SM/Google+Summer+Of+Code+2009
I'd like not to step on our students work if possible ;-)
As I said, I think reusing the felix web console would allow us to not
rewrite the full thing.
I would have loved a gwt based console, but not sure it's worth
spending time to rewrite it from scratch ...
No problem, sounds good for me.
Regards
JB
