I have few questions about sample-portal and how the services are started. What concerns
me the most is that currently services seems to be started separately for each container.
This means that we end up with two HibernateServices and OrganizationService instances.
Obviously it may be desired to have separate identity realm per container but I believe
that there may be some situations in which single OrganizationService would also be
expected. So for the more specific questions:
1) Is it possible to have both containers use same service instances? Some configuration
way to mark services as shared and bootstrapped only once.
2) I'm a bit confused by the way the service configuration is separated. AFAIK one
benefit of the separate container config is to push configuration out of gatein.ear. That
way things can be configured in sample-portal.ear/sample-portal.war. However most of
services configuration currently remain in gatein.ear/portal.war/WEB-INF/conf and rely on
the ${container.name.suffix} replaced by the kernel. One example is HibernateService which
creates separate DB instances this way. Now if I want to plug LDAP the natural way is to
provide several xml files with names following ${container.name.suffix} pattern. But those
are defined in config remaining in gatein.ear - then portal admin need to mess with config
in both ears. Wouldn't it make sense to duplicate more service configuration in
sample-portal.ear?
My use case is PicketLink IDM integration with LDAP enabled. As it is natural to provide
separate LDAP DNs for different portal containers I can either put additional config file
in sample-portal.war or have two different ones in gatein.ear/portal.war. So it is either
configuring sample-portal.war inside gatein.ear/portal.war or having part of identity
config in portal.war and part in sample-portal.war... I think it would make sense to
duplicate at least HibernateService and OrganizationService config in both war files.
3) Current behavior is to replace the ${container.name.suffix} by:
- empty string in tomcat deployment
- "_portal" and "_sample-portal" in jboss deployment
It works fine when the suffix is used to create the HSQLDB file name on the fly but when
used to refer to different configuration files it means that there need to be 3 xml
files.. where 2 are duplicated ones to serve main portal container in tomcat and jboss.
Could we have ${container.name.suffix} be replaced by "portal" in both jboss and
tomcat? Also is there any other property that could be used as a prefix? Like to have the
choice between "portal_", "portal" and "_portal" for
flexibility in nice config files naming.
Bolek.