[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=7470171
By: bprucha

> I think XML templates, which render a xml information to html, are very private
> to the module which maintains that information. It should never be used by
any
> other module directly, and even more so by another web application

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.

> if there is a need to access that information, an jee service or a content
type
> as proxy site or xmlfeed should be used

The stylesheet-paths.txt file describes where to look for these resources and
by default points to the resource-resolver servlet through an absolute URL.
The templating system translates this into a call to resolve the resource from
the local context to optimize resource lookup.

> Why not fetch it from the we applications context?

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

> Even more worse with c.ad.caching.CacheServlet. It reads the host's name and
> port from a persistent database table

I've never had to change these values so haven't run into this problem.  It's
used to support clustering I suppose.  I haven't ever looking into it since
I've never changed the host name or used clustering.

______________________________________________________________________
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