« Return to Thread: Synergy with OpenXava

Re: Synergy with OpenXava

by Alejandro Scandroli :: Rate this Message:

Reply to Author | View in Thread

Hola Javier

Trails 1.2 is comming out, but generally speaking these are uncertain
times for Trails, we still don't know excalty how the next version of
Trails will look like.
http://docs.codehaus.org/display/TRAILS/2008/01/24/Full+Steam+ahead+with+Trails+2.0!
But what's interesting is that even though Trails activity has
declained a lot in the last months I'm getting a lot of questions
similar to your requests.
What's even more interesting, at least for me, is that most of them
come form the Spanish speaking world. :) (BTW, I think there is a
majority of Spanish speakers on this list)
On May 10th I'm going to meet with the guys from the NexOpen framework
(http://www.nexopen.org/) to talk about web development in general and
we will try to see if there is an oportunity for some kind
integration/colaboration between Trails and NexOpen
http://bcurtu.com/?p=362
http://bcurtu.com/?p=376

I'm also will be talking about Trails in the OpenJavaDay 2008 in
Madrid. Are you going?

Your proposal isn't technically impossible and IMO it's not outside of
the Trails scope (I like the View annotation for layout
specification).
But to give you a more concrete and complete answer first we need to
figure out at least a draft of Trails 2.0


Saludos.
Alejandro.

--
Alejandro Scandroli - http://weblog.amneris.es/
Amneris: We build process-driven web applications.
http://www.amneris.es



On Tue, Apr 29, 2008 at 9:33 AM, Javier Paniza Lucas
<javierpaniza@...> wrote:

> 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
>
>
>

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

    http://xircles.codehaus.org/manage_email


 « Return to Thread: Synergy with OpenXava