Re: BeanShell and Class: x not in namespace

> >
> >        <property name="perms">login admin</property>
> >        <page-action name="org.jpos.ee.action.CheckAccess" />
> 
> :) Good ideas are always welcomed. I implemented something similar  
> some time ago, except that the permissions were given as action  
> attributes instead of page properties. 
>
Good point.

>
> have you thought in writing a module to encapsulate all the 
> functionality?
> 
While I like the module concept, I was under the impression that
modules where more suitable to deal with stand-alone kind of
components (think a calendar, a captcha generator and things
like that). There has been a long time since I read JP documentation
for the last time, so I'll have to get back to the manual in order to 
see if using a module here is feasible.

> 
> If there is interest we may transform it into a user authentication  
> and permission management module or such. Having it packed as a  
> module will make its usage optional for the users who doesn't need  
> security ;) Anthony?
> 
> > If you've seen Echo and EchoPoint, this could be some kind of
> > JPublish-Point (but we need a better name as this has no sense :)
> 
> I am going to have a look at Echo. I don't know much about it, sorry.
> 
I'm using Echo and EchoPoint as analogy here, being EchoPoint a project
that provides nice (and optional) ready-to-use Echo components. What we 
are doing in particular is not just a user authentication module, it's 
about general purpose components (web based system log, status monitoring, 
web based configuration/property editor) and a some specific to our project
(i.e. merchant/terminal administration, etc.).

>
> Are you guys working with JP3 or JP2? 
>
JP3 - we started with JP2 but moved to JP3 because it was the active
branch at that time. We can get back to JP2 if the fun is there now.

--Alejandro