[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=7470649
By: pboy

Hi Brett,


>  The problem is that the presentation layer depends upon Bebop XSLT in ccm-core.
>  Each module should be able to run in its own context but it also needs to
access the core XSLT
>  components of Bebop. I don't think each individual module should have it's
own copy of the core resources.

Is it really true, that each module should be able to run in its own context?
I asked on the forum and tried hard to find a reason for it.

E.g. why should ccm-ldn-theme run in its own context? By design (i.e. the xml
include mechanism) it provides services for just one web application, that one
that is running in ROOT. Nothing else. It used to store all the themes in its
own context, but a theme is very specific to a web application, no one wants
to mix themes between several web applications.

Of course, several web applications might use the services, the module ccm-ldn-themes
provides. Therefore, the jar files might be / should be stored in the containers
shared lib directory so it can be used by any web application. But each web
application will store the themes in its ówn context (xsl but also logo, images
and other private or specific things the webapp might not be willing to share).
And it will store the theme of the admin interface in its own context and might
whish to modify or redesign it.

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.


Currently, the development system had been changed so that all modules are installed
into one context which is specified in project.xml. If there is a requirement,
that a module should run in its own context, I have to adjust the
build-template.xsl.

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 :-)  )


>   It is fetched from the applications context. Using the ::webapps:: variable
in stylesheet-paths.txt the resource
>   can be lookup up in multiple contexts

That works very well for the core dispatcher, but does not work inside of xml
files (include directive, a mechansim which is widely used in APLAWS). Therefore,
if we decide that every module must be able to run in its own context, we have
to find a solution.

Therefore the question is: Is it essential for your usage of APLAWS / CCM that
each module is able to run in its own context,
or is it sufficient that jar files are stored in a shared directory
or can we determine specific circumstances for the requirement to run in ist
own context (some sort of special kind or types of modules) for which we can
develope a solution for the include directive in xsl files (of make them
unneccessary).


Peter



______________________________________________________________________
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