Trails activity

[Pablo Gra\~na]

Hi everybody. I've taken a look at the site and the fisheye view of svn, and I
noticed that there is not much activity in there. How far are we from seeing a
new release?

Thanks a lot

--
Pablo Gra\~na
Chief Architect
Globant
Arg Office: [phone]
UK  Office: [phone] int 8043
US  Office: [phone] int 8043


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

    http://xircles.codehaus.org/manage_email

[Kalle Korhonen-2]

On 1/17/08, Pablo Gra~na <pablo.grana@...> wrote:

Hi everybody. I've taken a look at the site and the fisheye view of svn, and I
noticed that there is not much activity in there. How far are we from seeing a
new release?

My contribution for 1.2 has been close to zero; I've actually been happily using Trails for some time. The earlier plan was to have the release sometime early Spring (see http://trailsframework.org/Roadmap ) and it still holds. The biggest new feature is the support for multiple windows and I'm sure Alejandro will have more insight on where we are with it. Beyond that, I'm at least personally waiting for T4.1.4 release that has a fice niceties added, and I'd gladly include it into Trails 1.2. The session-per-conversation is out for 1.2 and there's been a lot of discussiong around making Trails 2.0 an integration with T5 and Seam. Is there anything specific you are looking for in the new release? It's always possible to consider cutting a point release with some specific fixes in it.

Kalle

[Toby78]

Sorry, for digging out old problems ;-)

I circumvented the problem for the time being by eager fetches...now it'
s time to finally get rid of them and replace them by lazy fetches.

I did not quite get the last answer to this.

If I extend HibernatePersistenceService, what would I need to do exactly and where? And what does the spring configuration look like to make it work?

Or is it already fixed in the latest version?

Thanks in advance!

Tobias

>Hi Tobias
>
>This is bug in Trails 1.1.1 (http://jira.codehaus.org/browse/TRAILS-116)
>To workaround it you need to create your own transactional method and
>then implement your logic inside that method.
>You can extend from HibernatePersistenceService, or you can create
>your own service class. As long as you mark your service method as
>@Transactional and inject your service class into the page via Spring
>you shouldn't have any problems making it work.
>
>--
>Alejandro Scandroli
>Amneris: We build process-driven web applications.
>http://www.amneris.es

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

    http://xircles.codehaus.org/manage_email

[Kalle Korhonen-2]

What Alejandro was saying is that you need to have a a Spring bean with an operation marked @Transactional (org.springframework.transaction.annotation.Transactional) for your loading logic and call that operation from your page. It doesn't matter which bean it is, so you can either extend HibernatePersistenceService (already a Spring bean) or create a different service class that typically uses HibernatePersistenceService via composition; the latter option is often better from a design perspective. For example, I have multiple different persistence service for different entity types, e.g UserPersistenceService that has convenience and transactional operations for that element type.

Kalle

On 1/18/08, Tobias Marx <superoverdrive@...> wrote:

Sorry, for digging out old problems ;-)

I circumvented the problem for the time being by eager fetches...now it'
s time to finally get rid of them and replace them by lazy fetches.

I did not quite get the last answer to this.

If I extend HibernatePersistenceService, what would I need to do exactly and where? And what does the spring configuration look like to make it work?

Or is it already fixed in the latest version?

Thanks in advance!

Tobias

>Hi Tobias
>
>This is bug in Trails 1.1.1 (http://jira.codehaus.org/browse/TRAILS-116 )
>To workaround it you need to create your own transactional method and
>then implement your logic inside that method.
>You can extend from HibernatePersistenceService, or you can create
>your own service class. As long as you mark your service method as
>@Transactional and inject your service class into the page via Spring
>you shouldn't have any problems making it work.
>
>--
>Alejandro Scandroli
>Amneris: We build process-driven web applications.
>http://www.amneris.es

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

     http://xircles.codehaus.org/manage_email

[Alejandro Scandroli]

Hola Pablo,

Yes, there was not much activity. I had my projects on hold until recently.
My coding involvement in Trails is driven by need (my own selfish
needs) and my free time, and I haven't had much of either lately.
Thankfully that's look like is starting to change.
One of my old projects has a new requirement: "to use Amazon S3 to
store binary data", so I will be working on persisting blobs to S3 and
revisiting the "blob component" (TRAILS-41) in the next few days.
As Kalle points out the 1.2 release plan still holds. I want/plan to
fix most of the jira issues by March  (April?) and it will be nice to
release 1.2 with Tapestry 4.1.4 so we also depend on the new Tapestry
release.
As for the "support for multiple windows", yes it is there, but its
not for the faint of heart. :) 1.2-SNAPHOT also includes several minor
bug fixes and a new page lifecycle management (but that's wayyyy under
the hood).

Trails 1.2 will the the last major release in the Trails 1.x and
Tapestry 4 era. We are still trying to figure out how we are going to
continue beyond 1.2. I personally want to continue working with Kalle
in some Tapestry5 related project, but It looks like all our ideas are
already being implemented. :(

BTW, There is 1.2 snaphosts in Trails repo and  I desperately DO need
feedback about the them.

Saludos.
Alejandro.

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






On Jan 18, 2008 5:56 AM, Kalle Korhonen <kalle.o.korhonen@...> wrote:

> On 1/17/08, Pablo Gra~na <pablo.grana@...> wrote:
> > Hi everybody. I've taken a look at the site and the fisheye view of svn,
> and I
> > noticed that there is not much activity in there. How far are we from
> seeing a
> > new release?
> >
>
> My contribution for 1.2 has been close to zero; I've actually been happily
> using Trails for some time. The earlier plan was to have the release
> sometime early Spring (see http://trailsframework.org/Roadmap ) and it still
> holds. The biggest new feature is the support for multiple windows and I'm
> sure Alejandro will have more insight on where we are with it. Beyond that,
> I'm at least personally waiting for T4.1.4 release that has a fice niceties
> added, and I'd gladly include it into Trails 1.2. The
> session-per-conversation is out for 1.2 and there's been a lot of
> discussiong around making Trails 2.0 an integration with T5 and Seam. Is
> there anything specific you are looking for in the new release? It's always
> possible to consider cutting a point release with some specific fixes in it.
>
> Kalle
>

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

    http://xircles.codehaus.org/manage_email

[Alejandro Scandroli]

Yes this issue is already fixed in 1.2-SNAPSHOT

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

On Jan 18, 2008 4:57 PM, Kalle Korhonen <kalle.o.korhonen@...> wrote:

> What Alejandro was saying is that you need to have a a Spring bean with an
> operation marked @Transactional
> (org.springframework.transaction.annotation.Transactional) for your loading
> logic and call that operation from your page. It doesn't matter which bean
> it is, so you can either extend HibernatePersistenceService (already a
> Spring bean) or create a different service class that typically uses
> HibernatePersistenceService via composition; the latter option is often
> better from a design perspective. For example, I have multiple different
> persistence service for different entity types, e.g UserPersistenceService
> that has convenience and transactional operations for that element type.
>
> Kalle
>
>
>
>
> On 1/18/08, Tobias Marx < superoverdrive@...> wrote:
> > Sorry, for digging out old problems ;-)
> >
> > I circumvented the problem for the time being by eager fetches...now it'
> > s time to finally get rid of them and replace them by lazy fetches.
> >
> > I did not quite get the last answer to this.
> >
> > If I extend HibernatePersistenceService, what would I need to do exactly
> and where? And what does the spring configuration look like to make it work?
> >
> > Or is it already fixed in the latest version?
> >
> > Thanks in advance!
> >
> > Tobias
> >
> > >Hi Tobias
> > >
> > >This is bug in Trails 1.1.1 (http://jira.codehaus.org/browse/TRAILS-116 )
> > >To workaround it you need to create your own transactional method and
> > >then implement your logic inside that method.
> > >You can extend from HibernatePersistenceService, or you can create
> > >your own service class. As long as you mark your service method as
> > >@Transactional and inject your service class into the page via Spring
> > >you shouldn't have any problems making it work.
> > >
> > >--
> > >Alejandro Scandroli
> > >Amneris: We build process-driven web applications.
> > >http://www.amneris.es
> >
> > ---------------------------------------------------------------------
> > 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

[Kalle Korhonen-2]

On 1/18/08, Alejandro Scandroli <alejandroscandroli@...> wrote:

Trails 1.2 will the the last major release in the Trails 1.x and
Tapestry 4 era. We are still trying to figure out how we are going to
continue beyond 1.2. I personally want to continue working with Kalle
in some Tapestry5 related project, but It looks like all our ideas are
already being implemented. :(

Same here, but I'm still rather optimistic about T5/Seam as Trails future actually. Igor's Seam integration doesn't do anything for the workflow and session-per-conversation AFAIK, which for me is one of the most important things. And at any rate, Trails has traditionally offered an integrated full-stack web application framework rather than just a component/module to be integrated into a custom web app.

Kalle

[Toby78]

Is it ?

I have just upgraded my project and replaced EAGER fetches by LAZY fetches - and I still get those LazyInitializationExceptions...

-------- Original-Nachricht --------
> Datum: Fri, 18 Jan 2008 17:53:53 +0100
> Von: "Alejandro Scandroli" <alejandroscandroli@...>
> An: users@...
> Betreff: Re: [trails-users] Re: Lazy Initialization Exception adn reattach ?

> Yes this issue is already fixed in 1.2-SNAPSHOT
>
> --
> Alejandro Scandroli  - http://weblog.amneris.es/
> Amneris: We build process-driven web applications.
> http://www.amneris.es
>
> On Jan 18, 2008 4:57 PM, Kalle Korhonen <kalle.o.korhonen@...>
> wrote:
> > What Alejandro was saying is that you need to have a a Spring bean with
> an
> > operation marked @Transactional
> > (org.springframework.transaction.annotation.Transactional) for your
> loading
> > logic and call that operation from your page. It doesn't matter which
> bean
> > it is, so you can either extend HibernatePersistenceService (already a
> > Spring bean) or create a different service class that typically uses
> > HibernatePersistenceService via composition; the latter option is often
> > better from a design perspective. For example, I have multiple different
> > persistence service for different entity types, e.g
> UserPersistenceService
> > that has convenience and transactional operations for that element type.
> >
> > Kalle
> >
> >
> >
> >
> > On 1/18/08, Tobias Marx < superoverdrive@...> wrote:
> > > Sorry, for digging out old problems ;-)
> > >
> > > I circumvented the problem for the time being by eager fetches...now
> it'
> > > s time to finally get rid of them and replace them by lazy fetches.
> > >
> > > I did not quite get the last answer to this.
> > >
> > > If I extend HibernatePersistenceService, what would I need to do
> exactly
> > and where? And what does the spring configuration look like to make it
> work?
> > >
> > > Or is it already fixed in the latest version?
> > >
> > > Thanks in advance!
> > >
> > > Tobias
> > >
> > > >Hi Tobias
> > > >
> > > >This is bug in Trails 1.1.1
> (http://jira.codehaus.org/browse/TRAILS-116 )
> > > >To workaround it you need to create your own transactional method and
> > > >then implement your logic inside that method.
> > > >You can extend from HibernatePersistenceService, or you can create
> > > >your own service class. As long as you mark your service method as
> > > >@Transactional and inject your service class into the page via Spring
> > > >you shouldn't have any problems making it work.
> > > >
> > > >--
> > > >Alejandro Scandroli
> > > >Amneris: We build process-driven web applications.
> > > >http://www.amneris.es
> > >
> > > ---------------------------------------------------------------------
> > > 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

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

    http://xircles.codehaus.org/manage_email

[Toby78]

Ok - the reason why I still get the Lazy exception is probably because it was still using the old depenencies. When I clean the project and try to use 1.2-SNAPSHOT instead of 1.1, it is not built anymore due to TrailsTableColumn:

internal error; cannot instantiate org.trails.compon
ent.TrailsTableColumn.<init> at org.trails.component.TrailsTableColumn to ()

What where the changes there and how do you "upgrade" to 1.2 ?

Thanks!

Tobias


-------- Original-Nachricht --------
> Datum: Fri, 18 Jan 2008 17:53:53 +0100
> Von: "Alejandro Scandroli" <alejandroscandroli@...>
> An: users@...
> Betreff: Re: [trails-users] Re: Lazy Initialization Exception adn reattach ?

> Yes this issue is already fixed in 1.2-SNAPSHOT
>
> --
> Alejandro Scandroli  - http://weblog.amneris.es/
> Amneris: We build process-driven web applications.
> http://www.amneris.es
>
> On Jan 18, 2008 4:57 PM, Kalle Korhonen <kalle.o.korhonen@...>
> wrote:
> > What Alejandro was saying is that you need to have a a Spring bean with
> an
> > operation marked @Transactional
> > (org.springframework.transaction.annotation.Transactional) for your
> loading
> > logic and call that operation from your page. It doesn't matter which
> bean
> > it is, so you can either extend HibernatePersistenceService (already a
> > Spring bean) or create a different service class that typically uses
> > HibernatePersistenceService via composition; the latter option is often
> > better from a design perspective. For example, I have multiple different
> > persistence service for different entity types, e.g
> UserPersistenceService
> > that has convenience and transactional operations for that element type.
> >
> > Kalle
> >
> >
> >
> >
> > On 1/18/08, Tobias Marx < superoverdrive@...> wrote:
> > > Sorry, for digging out old problems ;-)
> > >
> > > I circumvented the problem for the time being by eager fetches...now
> it'
> > > s time to finally get rid of them and replace them by lazy fetches.
> > >
> > > I did not quite get the last answer to this.
> > >
> > > If I extend HibernatePersistenceService, what would I need to do
> exactly
> > and where? And what does the spring configuration look like to make it
> work?
> > >
> > > Or is it already fixed in the latest version?
> > >
> > > Thanks in advance!
> > >
> > > Tobias
> > >
> > > >Hi Tobias
> > > >
> > > >This is bug in Trails 1.1.1
> (http://jira.codehaus.org/browse/TRAILS-116 )
> > > >To workaround it you need to create your own transactional method and
> > > >then implement your logic inside that method.
> > > >You can extend from HibernatePersistenceService, or you can create
> > > >your own service class. As long as you mark your service method as
> > > >@Transactional and inject your service class into the page via Spring
> > > >you shouldn't have any problems making it work.
> > > >
> > > >--
> > > >Alejandro Scandroli
> > > >Amneris: We build process-driven web applications.
> > > >http://www.amneris.es
> > >
> > > ---------------------------------------------------------------------
> > > 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

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

    http://xircles.codehaus.org/manage_email

[Alejandro Scandroli]

Hi Tobias

Check this previous email:
http://www.nabble.com/new-%281.2%29-snapshots-of-Trails-artifacts-deployed-to14201532.html
Let me know how it goes.

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


On Jan 21, 2008 3:26 PM,  <superoverdrive@...> wrote:

> Ok - the reason why I still get the Lazy exception is probably because it was still using the old depenencies. When I clean the project and try to use 1.2-SNAPSHOT instead of 1.1, it is not built anymore due to TrailsTableColumn:
>
> internal error; cannot instantiate org.trails.compon
> ent.TrailsTableColumn.<init> at org.trails.component.TrailsTableColumn to ()
>
> What where the changes there and how do you "upgrade" to 1.2 ?
>
> Thanks!
>
> Tobias
>
>
> -------- Original-Nachricht --------
> > Datum: Fri, 18 Jan 2008 17:53:53 +0100
> > Von: "Alejandro Scandroli" <alejandroscandroli@...>
> > An: users@...
> > Betreff: Re: [trails-users] Re: Lazy Initialization Exception adn reattach ?
>
>
> > Yes this issue is already fixed in 1.2-SNAPSHOT
> >
> > --
> > Alejandro Scandroli  - http://weblog.amneris.es/
> > Amneris: We build process-driven web applications.
> > http://www.amneris.es
> >
> > On Jan 18, 2008 4:57 PM, Kalle Korhonen <kalle.o.korhonen@...>
> > wrote:
> > > What Alejandro was saying is that you need to have a a Spring bean with
> > an
> > > operation marked @Transactional
> > > (org.springframework.transaction.annotation.Transactional) for your
> > loading
> > > logic and call that operation from your page. It doesn't matter which
> > bean
> > > it is, so you can either extend HibernatePersistenceService (already a
> > > Spring bean) or create a different service class that typically uses
> > > HibernatePersistenceService via composition; the latter option is often
> > > better from a design perspective. For example, I have multiple different
> > > persistence service for different entity types, e.g
> > UserPersistenceService
> > > that has convenience and transactional operations for that element type.
> > >
> > > Kalle
> > >
> > >
> > >
> > >
> > > On 1/18/08, Tobias Marx < superoverdrive@...> wrote:
> > > > Sorry, for digging out old problems ;-)
> > > >
> > > > I circumvented the problem for the time being by eager fetches...now
> > it'
> > > > s time to finally get rid of them and replace them by lazy fetches.
> > > >
> > > > I did not quite get the last answer to this.
> > > >
> > > > If I extend HibernatePersistenceService, what would I need to do
> > exactly
> > > and where? And what does the spring configuration look like to make it
> > work?
> > > >
> > > > Or is it already fixed in the latest version?
> > > >
> > > > Thanks in advance!
> > > >
> > > > Tobias
> > > >
> > > > >Hi Tobias
> > > > >
> > > > >This is bug in Trails 1.1.1
> > (http://jira.codehaus.org/browse/TRAILS-116 )
> > > > >To workaround it you need to create your own transactional method and
> > > > >then implement your logic inside that method.
> > > > >You can extend from HibernatePersistenceService, or you can create
> > > > >your own service class. As long as you mark your service method as
> > > > >@Transactional and inject your service class into the page via Spring
> > > > >you shouldn't have any problems making it work.
> > > > >
> > > > >--
> > > > >Alejandro Scandroli
> > > > >Amneris: We build process-driven web applications.
> > > > >http://www.amneris.es
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
>
> ---------------------------------------------------------------------
> 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