Hey Alexis -
>> Some considerations:
>> - Need high avail/clustering somehow - I know the clustering is not in v3 - at least the same as it was in v2 - but can use mod_jk to alleviate this. I have also been considering Terracotta or something similar (external hardware cluster/load balancing is not an option).
>
> Make sure you've read those 2 pieces wrt clustering :
> - http://www.theserverside.com/news/thread.tss?thread_id=59317#332067
> - http://blog.eisele.net/2010/02/glassfish-vs-weblogic-10-visions-for.html?showComment=1265316113593#c573858513072567459
Hmm - I have read these - but there are some conflicts in here. Mike Lehmann seems to be saying that since it was in the original roadmap, that there is no reason is should not be in the current roadmap as well - albeit the original poster seems to say he believes it will not.
I have started experimenting with Terracotta to maybe take care of this short coming - but need more time to determine.
>
>> - I like the idea of wrapping our daemons and deploying via osgi modules - and the ability to maybe remove services we don't need in our appliance within glassfish 3
>
> It's probably a good idea to do some proof-of-concept to make sure the granularity and dependencies are as you need them.
I have been working on some of this - but are you implying that the OSGi implementation (being Felix) is not up to par?
Do you have any suggestions with the considerations I had outlined above on which would be a better choice?
Thanks.
--
Robert B. Weeks
rweeks_at_ext-inc.com