Synergy with OpenXava

Hi all,
 
I'm Javier Paniza, project lead of OpenXava project,
http://www.openxava.org/ 
and I have a proposal for Trails team and community.
 
OpenXava and Trails are very alike products,
in fact, OpenXava competes against Trails.
Even though, I think that Trails and OpenXava  
can cooperate in some way, and this can be profitable
for both, this can help us to gain ground against  
MVC frameworks.
 
But, How ?
 
We can concentrate in portability. The idea is that a  
develeper develops an application for OpenXava, and in
any moment he could migrate it with a minimun effort
to Trails. The same application, different engine
for running it. Even, if we will achieve a high level
of portability, the developer can have the application
on OpenXava (to use it inside a Java Portal) or in Trails
to use it as a Java Web Application.
 
How we can obtain this portability ?
We can agree to use standard Java API as JPA for persistence,
and bean validation (JSR-303) for validation. Removing
from our frameworks all propietary annotations about these  
issues.
Then, we can try to create a "common" specification for
layout, currently OX does it in this way:
http://openxava.wikispaces.com/view_en 
and controller, OX does it in this way:
http://openxava.wikispaces.com/controllers_en 
 
 
Maybe, this proposal is technically impossible,
or it's outside of the Trails strategy.
But, maybe not.
 
This offer can include other model driven frameworks
as Naked Objects, RomaFrameworks or JMatters.
 
What think about this the Trails team ?
What think about this the Trails community ?
 
Regards,
Javier Paniza


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email