Re: One more question on nav-app

Hi Shash,

>I'm not only Texan, but an Aggie as well...so means a lot to me :-)
 
I'm in DFW area too, do you go to javamug or something like that?

>app-nav is an enhanced menu system. It allows each Keel app to 
>contribute pieces of the menu. It then takes the logged-in user's 
>authorization levels into account to display only those items that are 
>permitted for the user. It knows nothing about the particular 
>web-clients, it just hands a series of (menu level, menu title, URL) 
>combinations to a Javascript menu-generator.

thanks for the info, will check it out

>Keel's business objects (models) know nothing about the client 
>framework. Navigation between models are done using generic "Command" 
>objects which contain the next model to navigate to, and the parameters 
>to apply. On the client side, based on the UI framework, use 
>techniques documented on the following pages:

I will have to understand more the way you implement the command pattern.
 
Now, in struts (and ww) there is a mapping file that decides where to go depending on the result of the action executed.  The problem is that both struts and ww have their own little world.  If you intend to create an application in which some actions are executed in struts and other in ww, you need a way to bind them together to form a coherent workflow.  is this what app-workflow does?
 
If there is no support today in keel for the above, I guess we can work towards a keel-server-wide (clustered or non-clustered) navigation (or workflow).  This is why we'd like to use either jbpm or bonita.
 
Anyway, there are some other areas in which we would like to enhance the current keel infrastructure (for example a notification engine).  We'll keep posting questions/suggestions.
 
Thanks