Re: Local macros [was: RE: quick note on recent changes]

[Daniel Rall]

Jose  Alberto Fernandez <[EMAIL PROTECTED]> writes:

> > From: Daniel Rall [mailto:[EMAIL PROTECTED]]
> > WOW!  Do fill us in on how you successfully skip development 
> > and testing...
> > 
> 
> As Gier notice with the sentence I had just after this one. The issue
> is not on testing individual applications. Which I presume will happen and
> everything will be fine. The problem will occur when you install
> this application on the same environment as others (that have also been
> tested by themselves). Because of the global macros, not the two apps
> may interact in unforseable manners and the problems show up.
> 
> Two different organizations within an enterprise may have bought or develop
> their own thing, and not until they are both installed in the common
> production server, that we will discover these problems.
> 
> The point is that we need to be able to provide some compositional
> guarantees. And the first tenant of that is component isolation.
> Component should only interact thru well defined APIs.

This could only be an issue if you run two Velocity apps with
conflicting macros in the same JVM.  Don't do that.

Daniel