click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CLK-347) Module support
Date Sat, 03 Jul 2010 04:44:50 GMT

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

Bob Schellink edited comment on CLK-347 at 7/3/10 12:44 AM:
------------------------------------------------------------

> 1) Click should have modularity support. Where developers can write their own click modules
and use the same module on different applications.

Are you saying you want to build a full blown stand-alone application which can then be dropped
into another Click application? There are many question that pop into my head at this stage:

- How do you expect the module to become aware of the main application BorderPage?
- How will the module plug into the main application menu system?
- How will the module third-party jar dependencies and configurations be handled?
- What about the module's DataSource?
- What about the entities of the module and how will the main application ORM filter influence
the module ORM settings? By this I mean the Open Session In View Filter which is the most
common for web apps.

I also think we need to differentiate between modules and the way to manage a big project.
One can certainly break a big app into smaller modules (Eclipse subprojects), but they are
still part of the same application and are tested as a whole. However creating stand-alone
application modules which are dropped into a main application is not a simple task.

      was (Author: sabob):
    > 1) Click should have modularity support. Where developers can write their own click
modules and use the same module on different applications.

Are you saying you want to build a full blown stand-alone application which can then be dropped
into another Click application? There are many question that pop into my head at this stage:

- How do you expect the module to become aware of the main application BorderPage?
- How will the module plug into the main application menu system?
- How will the module third-party jar dependencies and configurations be handled?
- What about the module's DataSource?
- How will the module fit into the main app menus?
- What about the entities of the module and how will the main application ORM filter influence
the module ORM settings?

I also think we need to differentiate between modules and the way to manage a big project.
One can certainly break a big app into smaller modules (Eclipse subprojects), but they are
still part of the same application and are tested as a whole. However creating stand-alone
application modules which are dropped into a main application is not a simple task.
  
> 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.


Mime
View raw message