Since WSRP work is almost impossible due to this issue in trunk, I've recreated the
wsrp2-integration branch with the changes from revision 4242 reverted so that WSRP work
can still progress. Hopefully, this won't lead to too many headaches come merging
timeā¦ :(
On Oct 1, 2010, at 7:20 PM, Christophe Laprun wrote:
Folks,
I've spent the last couple of days trying to fix an issue with the WSRP admin UI
which is currently behaving very erratically. After lots of trials and errors I have
finally isolated the issue to commit 4242 in trunk:
http://fisheye.jboss.org/changelog/gatein/portal/trunk?cs=4242
I have no idea why it's causing so many issues but I assume that something in that
commit has broken the Portlet Bridge state management. Julien, Wesley: any ideas?
Moving forward, I will make sure that we have some Selenium tests that check the WSRP
admin and the gatein vs gatein WSRP consumption that are run in Hudson as we certainly
could have caught that issue sooner (and avoided losing 2-3 days tracking the issue).
Thanks.
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow GateIn:
http://blog.gatein.org /
http://twitter.com/gatein
Follow me:
http://metacosm.codepuccino.com /
http://twitter.com/metacosm
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow GateIn:
http://blog.gatein.org /
http://twitter.com/gatein
Follow me:
http://metacosm.codepuccino.com /
http://twitter.com/metacosm