Re: BeanShell and Class: x not in namespace

> 
> I subscribe to Lateef's question. If you're not using JP3 in a very  
> specific way I may send you a new JP2 (I hope I'll commit it soon to  
> the 2-0 branch in the CVS) which is cleaned a bit, some errors are  
> fixed, the access to the page components are cached through a  
> pluggable mechanism and all the libraries are updated to their latest  
> versions; bsh, groovy, RHINO, etc.
> 
Do you have plans to upgrade these libraries in JP3 (HEAD) too?

>
> JPublish is a very reliable piece of software (I am biased, of  
> course:) and the version I am using (based on 2.0 and I am still  
> working on it) is very reliable and efficient, here are my old notes:  
> http://weblog.flop.ca/2005/03/12/1110656258000.html, since then I  
> added few more changes, such as: groovy support. Currently I am  
> working to finalize the DWR support for AJAX and the support for page  
> localization based on properties files, a very common i18n specific  
> practice.
> 
For the records, I'm using some AJAX (OpenRico's LiveGrid) with JP3
and it was something amazingly simple to do after getting some
directions from Anthony, I just had to add this line to my jpublish.xml:

   <mime-mapping ext="x" mimetype="text/xml" />

I make all my AJAX calls to pages ending in .x (i.e. list.x) and that's
it, I can produce whatever XML is required as a response, with the full
scripting support courtesy of JPublish (I can understand that you may
require a more deep hack to support DWR, though).

BTW, I'm using JPublish and Hibernate and have some standard actions 
(written in Java) to Open an Hibernate connection, Close it, then standard 
modules for user administracion with 'remember-me' features, permission
validation and redirection to the login page, so you can write page
configurations like:

       <property name="perms">login admin</property>
       <page-action name="org.jpos.ee.action.CheckAccess" />

and that check access would verify that a given user has the proper
permissions. We are having this under our project's umbrella, but
I wonder if there's enough quorum here to run it under JPublish's 
umbrella. I believe these basic general purpose components are good to 
jump-start new applications. You can see what I'm talking about in
action here: http://jpos.org/jposee (user 'admin' password 'test').
(BTW, login page and password change uses MD5 to send the new password,
and change password uses MD5 xored with the old password which make it
impossible for the server's operator to get the cleartext password after
it has been changed). 

If there's interest I'm ready to contribute that code to a sister project 
under JP's umbrella and to actively help in further development. 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 :)

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