Hi

1.2.6 has issues w/ facelets. 1.2.7 has fixed this and will be released next week

Sent from my iPod.

Am 08.03.2008 um 20:34 schrieb Stephen Friedrich <[EMAIL PROTECTED]>:

Thanks for the answer Andrew - it encouraged me to continue.
Finally I found the culprit - hooray and hallelujah:
I used the phase and action listener as described/linked in the Wiki at
  http://wiki.apache.org/myfaces/Trinidad_And_Seam
to support Seam conversations in conjunction with Trinidad dialogs.
Removing them makes the action trigger fine.

But, of course that was only one big obstacle on the way, the next one
followed immediately (and I am sure there are more on the way):
Now I have to figure out why my redirect after successful login (to the original page that the use invoked before being redirected to the login
page) is suddenly throwing an IllegalStateException.
Then of course I have to check if dialog and conversation now play together
nicely, or if I have to fix the old phase/action listeners.

Oh, and do you know if it is possible to run Trinidad 1.2 on Tomcat 5.5 (using facelets, of course)? Unfortunately I am stuck with Tomcat 5.5 for
at least another year.

Thanks again for your help!

Andrew Robinson wrote:
Could you provide somd of the view code?
Are there any FacesMessages added to the FacesContext?
You can also debug the decoding of the view (CommandLinkRenderer may
be the name -- but I am not at my home computer to know)
Are you sure the POST is being made and making it to the server?
On Fri, Mar 7, 2008 at 7:46 PM, Stephen Friedrich <[EMAIL PROTECTED] > wrote:
Hi, it's me again - the guy that always complains about incompatibilities and how he hates spending his nights on configuration and debugging ;-)

Well...

I just tried to upgrade from
  Trinidad 1.0.6, MyFaces Core, Seam 1.2.1
to
  Trinidad 1.2.6, JSF RI 1.2, Seam 2.0.1

After twiddling with xmls files and countless trial-and-errors I made some
progress but finally seem to have hit a dead end:

My login page displays fine, but the login button's action is never executed.
No log output, no validation failures.
Strange thing is that I can use an actionListener just fine.

Most of my app then works fine (very few actions, mostly REST- style navigation).

WT*?

I tried debugging, but I can't even find the place where the action is supposed
to be executed.

UIXCommand.broadcast() looks like it should do it, but no such code in sight?

Help, please!


Reply via email to