A lot of this was all spurred on by changes in *both* code bases around
state management and identities. The recent releases (1.0.4) should be
working fine (again).
There were some questions around letting UIComponents (UICommands
specifically) generate their own identities, but then people were
emailing the Facelets list saying that they were now getting warnings
from MyFaces that the user should specify ids (which shouldn't be
necessary or an issue).
-- Jacob
Martin Marinschek wrote:
Jacob,
as we are in the discussion right now, Thomas Spiegl recently tried to
use Facelets and gave up on a whole bunch of duplicate-id exceptions.
He didn't try long though, so this doesn't have to say much ;).
Is this something that might in any way be related to any of the open
jira-issues on MyFaces and Facelets not working correctly together?
regards,
Martin
On 12/15/05, Martin Marinschek <[EMAIL PROTECTED]> wrote:
Sorry for the late answer,
I do think that most of what you are talking about has been in MyFaces
right from the beginning, so I think the situation is at least not
deteriorating, as your post suggests ;)
We haven't started implementing JSF1.2 so far (and the 1.2 spec didn't
even exist in early stages when the code you refer to (at least in the
ViewTag) was implemented), so I suppose it wasn't programmed
especially with this spec in mind.
Maybe you could help us out with a patch here which cleans this whole
thing up a little in a JSF1.2 compliant way? Would be great!
And - for clarification, are you just talking about the view-tag, or
also about other tags as well? I didn't quite get this from your post,
you talk about the view-tag first, and then it rather sounds general?
regards,
Martin
On 11/27/05, Jacob Hookom <[EMAIL PROTECTED]> wrote:
I've noticed in your recent releases that you've included a lot of
write-behind code within the JSP View Tag. What was the reason for
spreading the logic around between the individual component renderers,
JSP tags, and the JspViewHandler implementation? The state write-behind
could have just been contained within the JspViewHandler.
Also state-saving server w/ commandlinks doesn't work without using a
View Tag, because of the specialized URL write behinds. I don't
experience the commandLink issue with state-saving client.
*grump* JSF was designed to delegate controller concerns as
interchangeable blocks, and the implementation now seems to be
missmashed between specialized Application delegates. This will cause
issues when you start implementing JSF 1.2 as things like View and
SubView concepts are falling by the wayside as unecessary, also there
are quite a few other projects popping up that are exploring things like
AJAX such that the inter-dependencies between tags and components as a
processed whole, will basically not function with the MyFaces
implementation.
I don't want to sound like I'm in a poor mood, I just hope some of this
can be simplified and consolidated within the myfaces code base.
-- Jacob
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
--
Jacob Hookom - Minneapolis
--------------------------
http://hookom.blogspot.com
