Sure, I will !
2014-09-18 14:21 GMT+02:00 Thiago H de Paula Figueiredo
:
> On Wed, 17 Sep 2014 20:40:28 -0300, Charlouze wrote:
>
> Hey again !
>>
>
> Hi!
>
> Sorry for bothering everyone but I just wanted to say that I think I
>> found my perfect solution. I was looking at
>> the EntityAppli
On Wed, 17 Sep 2014 20:40:28 -0300, Charlouze wrote:
Hey again !
Hi!
Sorry for bothering everyone but I just wanted to say that I think I
found my perfect solution. I was looking at
the EntityApplicationStatePersistenceStrategy class and it just gave me
my answer...
Maybe my new soluti
Hey again !
Sorry for bothering everyone but I just wanted to say that I think I found
my perfect solution. I was looking at
the EntityApplicationStatePersistenceStrategy class and it just gave me my
answer...
Maybe my new solution should replace the clumsy
EntityPersistentFieldStrategy of tapest
Hello everybody,
I'm really not sure about what I did and I really appreciate a feedback
from people who knows how persistent fields works.
If i'm not clear enough or anything about my issue, just let me know.
Cheers,
Charles.
2014-09-16 17:13 GMT+02:00 Charlouze :
> As for now, I solved my pr
As for now, I solved my problem using a new PersistentFieldStrategy and I
want your opinion about it:
public class MultiplePersistentFieldStrategy implements
PersistentFieldStrategy {
private final Logger logger;
private final List delegates;
public MultiplePersistentFieldStrategy(f
Hello Tapestry users & devs,
I have a component which does lots of ajax requests. Parameters setted at
the first render are not available upon ajax requests so I decided to
persist them in specific properties.
One of those parameter is a database entity (I use tapestry-jpa) so I
decided to use the
