Hello Aaron!
FA> - Currently you need to use a roles file (WEB-INF/system.roles).
FA> Technically it's optional, but I can't seem to get Fortress to find all my
FA> services using just the meta approach, so for now, you'll need to use roles
FA> configuration.
That sounds really intriguing :-)
ServiceMetaManager class seems to be able to
load just all. It goes like
public void initialize() throws Exception
{
...
final Enumeration enum = getLoader().getResources( "services.list" );
where getLoader is implemented in AbstractMetaInfoManager
and there it is set up as
public AbstractMetaInfoManager( final MetaInfoManager parent,
final ClassLoader loader )
{
ClassLoader thisLoader = loader;
if ( null == thisLoader )
{
thisLoader = Thread.currentThread().getContextClassLoader();
}
m_loader = thisLoader;
m_parent = parent;
}
so either way it is I believe that the context classloader _should_
get into this way or other. (BTW, do you set the classloader in
your listener on FortressConfig? technically cleaner it would be to
_do_ it, but it _should_ work either way)
So, for all the jars that are visible via context class loader and
those that have services.list in their
/service.list
/META-INF/services/role.Name
/impl.Class.meta
in proper shape should get fetched up okay.
Isn't this happening for you?
-Anton
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
