Thanks for the detailed response.
How would the server generally tell which came from which window using
jsf_sequence?
Because each window would postback the id rendered in that page, telling
the server which ViewState to associate to process update/action logic.
Does the server actually
Oh, you can put one h:form around the entire page? What if on a page you had
a login form, a sign-up for mailing list form, and a couple more...if you
put one form around the whole thing, is it still possible then? (Would the
only downside be that you'd have a lot more request parameters -- many
On 12/21/06, lightbulb432 [EMAIL PROTECTED] wrote:
Thanks for the detailed response.
How would the server generally tell which came from which window using
jsf_sequence?
Because each window would postback the id rendered in that page, telling
the server which ViewState to associate to
[
http://issues.apache.org/jira/browse/MYFACES-1396?page=comments#action_12460203
]
Paul Pogonyshev commented on MYFACES-1396:
--
I don't actively see it anywhere. However, I did see it in
[
http://issues.apache.org/jira/browse/TOMAHAWK-829?page=comments#action_12460204
]
Gerald Müllan commented on TOMAHAWK-829:
The proper way of contributing some code is by providing a all-in-one patch.
Please submit such a file;
[
http://issues.apache.org/jira/browse/MYFACES-1396?page=comments#action_12460211
]
Paul Spencer commented on MYFACES-1396:
---
Paul,
The JSP, test.jsp, includes /base/taglibInclude.jsp, but that file is not
attached to this issue. Is it
[
http://issues.apache.org/jira/browse/MYFACES-1396?page=comments#action_12460212
]
Tomas Fischer commented on MYFACES-1396:
I didn't complain that the UTF-8 characters would be passed incorrectly, I did
complain that the
[
http://issues.apache.org/jira/browse/MYFACES-1396?page=comments#action_12460214
]
Paul Pogonyshev commented on MYFACES-1396:
--
Paul: sorry, no, it is not needed. Just accidentally left from a real page.
Tomas: yes, I started a
[
http://issues.apache.org/jira/browse/MYFACES-1396?page=comments#action_12460231
]
Paul Spencer commented on MYFACES-1396:
---
When I add the following to the outputText test case:
h:outputText id=escape escape=true value=10 gt; 5 /
Hi there,
As you may know there has been some work towards the complete implementation
of JSF 1.2. For this new version of MyFaces, all the components from the
basic renderkit are autogenerated using Trinidad's maven-faces-plugin, which
has been adapted to generate components fully complicant
[
http://issues.apache.org/jira/browse/MYFACES-1396?page=comments#action_12460244
]
Tomas Fischer commented on MYFACES-1396:
The main problem (for our project) ist that the escaping occurs at all. We need
exactly the described
JSF was designed to accomodate this behavior-- having multiple buttons,
complex interactions, etc-- just wrap everything in one form.
lightbulb432 wrote:
Oh, you can put one h:form around the entire page? What if on a page you had
a login form, a sign-up for mailing list form, and a couple
[
http://issues.apache.org/jira/browse/MYFACES-1396?page=comments#action_12460259
]
Paul Spencer commented on MYFACES-1396:
---
Thomas,
I am not sure what the JSR says about escaping international characters. Martin
Marinschek may be able
[ http://issues.apache.org/jira/browse/TOMAHAWK-829?page=all ]
Ji Kim updated TOMAHAWK-829:
Status: Patch Available (was: Open)
Batch of Java codes and JavaScript files for creating Dynamic Tables [such as
changing between different List, and etceteras]
Hi *,
during performance profiling run we found that the iterator
_FacetsAndChildrenIterator is
created quite often (more than 5 times than any other non JDK object).
Also we noticed that there
is a search algorithm that looks like a tree scan where all children are
scanned linearly.
Due to the
Aneesha Govil wrote:
I would second that. There is no way to apply bug-fix patches without
upgrading to a newer, not-stable-yet snapshot nightly build.
Well yes, unless you are comfortable applying the patches yourself and
maintaining/building the source locally. While this will always be
Hi Volker:
Is this fix for the selectable tree issue? I download the
Tobago 1.0.9 snapshot and tried, It was not able to notify any
de-selcted checkbox in the tree leafs. I have three leafs display with
checkbox.
First:
_selectedCategories = new TreeState();
Lightbulb,
Take a look at the context-param:
context-param
description
Only applicable if state saving method is server (= default).
Defines the amount (default = 20) of the latest views are
stored in session.
/description
[ http://issues.apache.org/jira/browse/TOBAGO-107?page=all ]
Udo Schnurpfeil resolved TOBAGO-107.
Fix Version/s: 1.0.10
Resolution: Fixed
tc:page should use a reasonable default width+height and state
[
http://issues.apache.org/jira/browse/TOMAHAWK-826?page=comments#action_12460284
]
Jeff Bischoff commented on TOMAHAWK-826:
Alex,
I can't speak to the specifics of using this particular component. However,
normally you don't need to
Hi,
no, this fix was a problem with validation.
There is no issue with treeSelection, at least no known issue.
I currendly working on a app which uses this and there is no problem.
There is no direct way to get the nodes wich was deselected, you can
just get the currently selected ones, to
Ok, I'll look at the source and see what I come up with. Could somebody
please provide guidance as to how to get started (as I've never seriously
looked at code for a real program and knew what I was doing...)
I saw the wiki page that somebody posted earlier on the different classes
and methods
I, personally, find reading the specifications to be the easiest route-- check
out JSR 252 at the JCP.org site and download the specification PDFs to give you
an introductory view into the lifecycle of JSF, then provide the gritty details
of how JSF works.
http://jcp.org/en/jsr/detail?id=252
Should I be reading version 1.2 or version 1.2 (Revision A)?
I figure that there are implementations of 1.2 but not 1.2A so if I read the
latter there may be things that haven't been implemented yet in the version
of JSF I'm playing with, leading to confusion? Is this correct reasoning, or
is
For the level of information you need, you could read any of them, or even find
the JSF 1.1 JSR at JCP.org and read that.
Should I be reading version 1.2 or version 1.2 (Revision A)?
I figure that there are implementations of 1.2 but not 1.2A so if I read the
latter there may be things that
[
http://issues.apache.org/jira/browse/TOMAHAWK-826?page=comments#action_12460297
]
Alex Savitsky commented on TOMAHAWK-826:
Ah, I see now. I thought this ifMessage component to be more like the c:if -
should've looked at the source
[
http://issues.apache.org/jira/browse/TOMAHAWK-826?page=comments#action_12460300
]
Jeff Bischoff commented on TOMAHAWK-826:
Yes it would require an extra outputLabel for each one, which is why I do think
that your suggestion would be
[ http://issues.apache.org/jira/browse/TOBAGO-223?page=all ]
Bernd Bohmann resolved TOBAGO-223.
--
Resolution: Fixed
Process Validate, Update and Decode for UIPopup only if popup is submitted
not activated
I was reading the 1.2 spec and saw the following line:
The separation between tree structure and component state is now a
recommended implementation detail.
Is it that line which explains the removal of two different structures - the
tree structure and component state (e.g. jsf_view_64 and
It works not, I could able to capture it. Thanks.
-Original Message-
From: Volker Weber [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 21, 2006 9:57 AM
To: MyFaces Development
Subject: Re: [jira] Created: (TOBAGO-224) validation of tree works
incorrect
Hi,
no, this fix was a
Regarding the back button problem, I have a question:
So the issue is that you have an original page with a form on it
(page1.html) that was obtained through a GET; the browser bar shows
page1.html. You POST that form to a destination of page2.html (as defined in
form) and a response is
Actually, the one downside of a single form is that it doesn't
accomodate independent validation sets.A validation error on your
mailing list form could very well break your login form.
The immediate flag can handle trivial cases, but not complex ones.
The ADFaces, Trinidad, and MyFaces
[
http://issues.apache.org/jira/browse/MYFACES-434?page=comments#action_12460376
]
Shinsuke SUGAYA commented on MYFACES-434:
-
Tomahawk Bridge 0.9 is available. myfaces-bridge 0.8 was replaced with it.
33 matches
Mail list logo
