Re: BeanShell and Class: x not in namespace

> 
> Through a module all the actions and related functionality are all  
> made magically (I like how Rebel is using this word;) available to  
> the the entire site. A module has his own config and life-cycle. 
>
Will read modules documentation once again. Thanks for the suggestion.

>
> Personally I am not too too happy with the vfs dependencies and the repository  
> syntax definitions but it's ok. 
>
When I first saw VFS in JP3 I thought, hey, this is powerful. Thing is,
after several years, I never took advantage of that feature. I can live
with it, but commons-* is usually a source for dependencies problems.

--Alejandro 
http://jpos.org/blog