Guys,
I think it would be a good idea to extend the use of components.xml to
include parameters (same way as interceptors accept parameters).
<component>
<scope>application</scope>
<class>com.intrasoft.search.lucene.LuceneIndexer</class>
<enabler>com.intrasoft.search.IndexerAware</enabler>
<param name="indexDir">lucene-index</param>
</component>
Or in a new format:
<component name="indexer" scope="application">
<class>com.intrasoft.search.lucene.LuceneIndexer</class>
<enabler>com.intrasoft.search.IndexerAware</enabler>
<param name="indexDir">lucene-index</param>
</component>
This will call setIndexDir on LuceneIndexer using Jakarta BeanUtils.
Giving each component a unique name also has another advantage:
ComponentManager cm = (ComponentManager)
ServletActionContext.getRequest().getAttribute("DefaultComponentManager");
Indexer indexer = (Indexer) cm.getComponent("indexer");
Good idea?
Cheers,
Mathias
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
