[Aplaws-devel] [aplaws - Developing on APLAWS+] RE: ccm.home and r1919

[Aplaws D. L. <apl...@li...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=7475944
By: bprucha

> Is it really true, that each module should be able to run in its own context?

I don't see modules necessarily as being an extension to the existing functionality.
A module can provide completely new and independent functionality.  Developers
should be able to use the core as a lower level framework for their own applications.
This is what I use the code for.  I tap into the user/group/permission functionality
and dispatcher and templating mechanism to create multiple themable instances
of my applications.  Beyond that, the software I've developed stands on its
own.  Having each module in it's own context also makes it truly modular.  You
don't have to merge the moduals web.xml in with the core web.xml.  This also
allows you to undeploy/redeploy individual moduals without having
to undeploy/redeploy the entire system.  Those are the main benefits I see in
having modules in their own context.  I don't think each module has to be in
its own context but when a module provides new application services that simply
rely on the core for lower level API it's nice of have that capability.

> a theme is very specific to a web application, no one wants to mix themes
between several web applications.

Why not?  In an enterprise environment you want all of you applications to have
the same look and feel.

> As to my knowledge version 5 of APLAWS was a JEE application, were all modules
were installed into one
> context (ccm). Do you know, WHY that had been changed? I suppose I never understood
this design decision.

I'm not sure why.  The code used the c.a.sitenode.SiteNodeDispatcher to locate
the package dispatcher to handle the request.  That was deprecated in favor
of the c.a.web.DispatcherServlet which tries to forward the request to a servlet
defined in c.a.web.Application.  The new dispatcher mechanism is more flexible
and allows the application to reside in a different context.  My guess is that
it makes the moduals more plug and play.

> Just another topic: If each module is dependent from resources in core, I
suppose it is an example of
> (very) strong coupling. So it should not divided into different modules (at
least according to theory :-) )

I see core as being a lower level web framework that should be in a shared jar.
I think much of whats in their can/should be replaced with other competing
technologies that are maintained as independent projects.  What should stay
are the things that make APLAWS+ truly unique like the way it handles
users/groups/permissions and dispatches modules in a way that facilitates multiple
instances of an application.

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=368401