[ 
https://issues.apache.org/jira/browse/CLK-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883303#action_12883303
 ] 

Md. Jahid Shohel commented on CLK-347:
--------------------------------------

Couple of questions pooped up while I was looking into the old 
implementation[1] of module support for click. I will point out those questions 
and would like to have thoughts from everyone -

1) Since each module is doing to be stand alone and independently pluggable, 
does that mean that each module will have their own configurations. By 
configurations I mean automapping, autobinding, etc (but not log service, 
config service,etc). If any configuration is not mentioned on module, then it 
will use base application's configuration (here by base application I mean the 
web application).

2) If each module can have their own configuration(mentioned on on #1 above), 
then should we impose for each module to have "click-module.xml" to be in their 
class path (inside META-INF)?

3) Who will load the modules? Potential candidates are ClickServlet or any 
config service. I think it should be ClickServlet. So that we do not depend on 
different config services. Because config services can change, but ClickServlet 
will not change.

4) What will be the loading sequence? I mean load all modules first, then base 
application(by base application I mean, the main application as it is today, 
which is a war and contains web.xml)? Or other way around. Also what is the 
reason of loading sequence?




[1] http://click.svn.sourceforge.net/viewvc/click/trunk/sandbox/sabob/plugin/

> Module support
> --------------
>
>                 Key: CLK-347
>                 URL: https://issues.apache.org/jira/browse/CLK-347
>             Project: Click
>          Issue Type: Improvement
>          Components: core
>            Reporter: Bob Schellink
>
> Add module support to Click core. Some code has been committed here: 
>   http://click.svn.sourceforge.net/viewvc/click/trunk/sandbox/sabob/plugin/
> Note that with the recent work done on CLK-343 the module code wont compile 
> anymore.
> A related issue is: CLK-328

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to