Hi Bruno,
My opinions as below:
For now, I will call the standalone framework as framework project and the
rest of the components as applications project.
1. As the current framework embeds servlet container like Tomcat and Jetty,
codes related to servlet containers stay with the standalone framework.
2. Webtools and Example should be in the framework project.
2. Party application shouldn't be in framework. But it can be decoupled from
the rest of the applications.
3. It is also alrite for Party application to reference other applications
like Order, but
a. links to other application, should be disabled in realtime if the
other application component is not loaded.
b. the framework should inject scripts (like css and js) into the header
(similar to what wicket and click framework is doing) if screens from other
application is used. Likewise, if screens from other application are called
without the applications being loaded, the framework should provide some
useful screen messages when the screen is loaded.
4. The application project should contain the compiled framework without its
source code. In the long run, it should be easy to simply drop the framework
into the applications project, or the applications project into the
framework.
5. Themes can go with the framework with a default theme, and the rest as
adds-on.
6. The framework project can have more frequent releases than the
application project, while keeping the goals for the framework project in
alignment with the applications project as what currently is.
- james
Bruno Busco wrote:
>
> Hi James,
> I did write a wiki page to define how the framework only distribution
> should
> be shaped.
> Following that there was some mail thread in which we discussed about.
> Some
> of us was not on the same page but we did not agree on something different
> that could be written updating the wiki page.
>
> You can find the wiki page here:
> https://cwiki.apache.org/confluence/display/OFBIZ/Framework-only+distribution
>
> Fill free to express your opinion and help on that.
>
> A contribute that will gine IMO a great help on framework independence is
> also:
> https://issues.apache.org/jira/browse/OFBIZ-3373
>
> Scott is working on that and I am looking forward to it.
>
> -Bruno
>
>
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/why-we-should-have-a-10-04-standalone-framework-release-tp1568563p2543514.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
