Re: What do we need for a 2.1 final release?

Carlos,

I'll answer the ones I can.

>  
> Anyway,  I noticed that 2.1 was planned to be out sometime around 
> May.  I was wondering what the status of this is and if I can help to 
> take the 2.1 out.

We are lacking updates to the docs, which we had considered as the most 
important issue for Keel users.  Other than that, 2.1-dev is quite stable.

>  
> The reason for this is that I want to use keel for our application at 
> work.  So, in the absence of 2.1 final what codebase should I use? 
> 2.1-dev ? HEAD?  Please advice
>  

If you can use HEAD, go for it (for development), it is stable.  For 
production, if your process calls for a stable, released framework, then 
wait for 2.1-final, or we can make another 2.1-dev snapshot release.

> Also, I'd like to know the status in keel to use JSF.  I know it's 
> limited, not so stable implementations and all, but I am betting (not 
> the farm ;-) on it.
>  

This is a question for Mike to answer.  I know there is a JSF/Cocoon 
combo that works.

> Also a question.  I can use Struts/JSF/WW2 and so all at the same 
> time, right?  do I need separate web-contexts (diff WARs) for this?
>  

I think you are better off using the JMS-distributed version of Keel 
(even on a single machine), and then doing multiple webapps, one for 
each client type.  This will allow you to use the build system without 
changes.  In theory, you should be able to specify a custom web.xml that 
has the servlet-mappings for all the controller servlets for the UI 
(Struts/WW2/etc) frameworks you want to use under a single web 
context...but I have never tried that, and I am sure it will require 
some build system changes or another.  But, to be clear, this is not a 
Keel limitation, only of the build process.

> One more question.  How is the status of supporting JDO in keel?  is 
> 1.0.1 supported?
>  

There is a JDO implementation using TJDO, but I have never used it.

> One more, is there any integration done/planned with a workflow engine 
> like jbpm.org and/or bonita.objectweb.org?

There is workflow support using a custom workflow engine, which is like 
WW action chains on steroids (app-workflow).  But it is not a true 
persistent workflow used for BPM.  This would be a welcome add for 
Keel.  I would be willing to help on this if you or someone wants to get 
started on it.  I'd think a good starting point would be to study the 
capabilities of a couple of these tools and distilling a common service 
interface for the workflow service.  Wan'na take a shot :-) ?

Shash