two days ago i started using tomahawk ExtensionsFilter components im my jsf application. i noticed that all javascript alerts were not displaying special characters (ç, ã, ó ô), it displays things like #231 instead. When i remove ExtensionsFilter from my web.xml file, javascript displays allright. Anybody had this issue before? thanks ins advance -- View this message in context: http://old.nabble.com/Does-myfaces-ExtensionsFilter-change-page-encoding--tp26635896p26635896.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Hello community, Tobago and Orchestra is pretty cool. But i think the TobagoMultipartFormdataFilter cuts the Orchestra conversation context parameter "?conversationContext=n" . Is there something wrong with the MultipartFormdataFilter or its a general problem to parse parameters in multipart form data requests? To adjust the behavior use Tobago with Spring and Orchestra and submit a form with one <tc:file value="..."/> input field. Without <tc:file value="..."/> everything works fine. The conversation is gone and the backend creates new controller instances. Thanks, kai.
add attribute
immediate="true"
Dave, by the way - do you know what is google? search?
2009/12/3 laredotornado <laredotornado@gmail.com>
>
> Hi,
>
> I'm using MyFaces 1.1.6. I have this commandButton on my page, within a
> form
>
> <h:commandButton id="cancelButton" value="Cancel"
> action="#{myController.cancelTourRequests}" />
>
> I would like that if a user clicks this button, they are automatically
> redirected to another page. Despite the fact I have set up the
> navigation-rule in faces-config.xml, when I click the button, JSF attempts
> to validate the form (which makes sense) and I'll get form validation
> errors
> instead of redirecting. How would I create this button such that the user
> is automatically redirected to another page without any type of form
> validation?
>
> Thanks, - Dave
> --
> View this message in context:
> http://old.nabble.com/Trouble-creating-a-Cancel-button-tp26633404p26633404.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
Hi,
I'm using MyFaces 1.1.6. I have this commandButton on my page, within a
form
<h:commandButton id="cancelButton" value="Cancel"
action="#{myController.cancelTourRequests}" />
I would like that if a user clicks this button, they are automatically
redirected to another page. Despite the fact I have set up the
navigation-rule in faces-config.xml, when I click the button, JSF attempts
to validate the form (which makes sense) and I'll get form validation errors
instead of redirecting. How would I create this button such that the user
is automatically redirected to another page without any type of form
validation?
Thanks, - Dave
--
View this message in context: http://old.nabble.com/Trouble-creating-a-Cancel-button-tp26633404p26633404.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
All - Please let me know if this issue is caused because of any misconfiguration..
--- On Tue, 1/12/09, Shasi Mitra Yarram <shasimitra@yahoo.com> wrote:
From: Shasi Mitra Yarram <shasimitra@yahoo.com>
Subject: Problem with number of views in session
To: "MyFaces Discussion" <users@myfaces.apache.org>
Date: Tuesday, 1 December, 2009, 5:01 PM
Hi all,I had gone thru <http://wiki.apache.org/myfaces/Performance> and updatedorg.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION
to "4" to have less session usage. Now the problem is I have a link on a page, on click of
which a new window opens. After going through more than 4 screens in the child window, none
of the links in the parent window work. The page simply refreshes. Can anyone suggest solution
for this? It works if I put more number of views in session. But I wanna know if there is
any other alternative..
Thanks,Shasi
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/
I once ran into such a problem (although with JasperReports), so it is possible! 2009/12/3 Anton Gavazuk <antongavazuk@gmail.com> > I suspect lack of internet connection shouldnt be a problem for DTD... > > 2009/12/3 Jakob Korherr <jakob.korherr@gmail.com> > > > Hi, > > > > Also: Does your AS have internet access? I think it might be a problem, > > because it can not obtain the schema information (or DTDs) for web.xml, > for > > example http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd. > > > > Regards > > > > Jakob Korherr > > > > 2009/12/3 Jakob Korherr <jakob.korherr@gmail.com> > > > > > Hi, > > > > > > did you try it on an other machine (e.g. JBoss) also and did you get > the > > > same error? > > > > > > Regards, > > > > > > Jakob Korherr > > > > > > 2009/12/3 viswam k <viswamy2k@gmail.com> > > > > > > Hi, > > >> this im getting when i deploy my webapplication on AIX,WAS7 box > > >> > > >> > > >> org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser parse Unable > > to > > >> parse web.xml > > >> java.net.ConnectException: A remote host did not respond within the > > >> timeout > > >> period. > > >> > > >> thanks > > >> -viswam > > >> > > > > > > > > >
I'm using the basic javascript... 2009/11/30 <pbreen@johnson.ca> > I am using the Tomahawk set of tags for this project. I need a pop to > confirm the deletion of a record. There doesn't seem to be any concept of > a popup in JSF or Tomahawk. I can use a basic javascript cofirm popup and > functionaly it works perfect but the color scheme doesn't match my > application and it doesn't look good. Just wondering what everyone else > does to confirm a delete? > > Pat
I suspect lack of internet connection shouldnt be a problem for DTD... 2009/12/3 Jakob Korherr <jakob.korherr@gmail.com> > Hi, > > Also: Does your AS have internet access? I think it might be a problem, > because it can not obtain the schema information (or DTDs) for web.xml, for > example http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd. > > Regards > > Jakob Korherr > > 2009/12/3 Jakob Korherr <jakob.korherr@gmail.com> > > > Hi, > > > > did you try it on an other machine (e.g. JBoss) also and did you get the > > same error? > > > > Regards, > > > > Jakob Korherr > > > > 2009/12/3 viswam k <viswamy2k@gmail.com> > > > > Hi, > >> this im getting when i deploy my webapplication on AIX,WAS7 box > >> > >> > >> org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser parse Unable > to > >> parse web.xml > >> java.net.ConnectException: A remote host did not respond within the > >> timeout > >> period. > >> > >> thanks > >> -viswam > >> > > > > >
Andrew Robinson-5 wrote: > > tr:selectOneRadio and optionally put it in a popup? > Well, that would offer a similar functionality but wouldn't look as much like a combobox as our guidelines require... Anyhow, as I mentioned IE6' z-index bug, I found out that a neat little jQuery plugin called bgiframe can be used to easily work around that bug (and as we're already making use of jQuery, that eases our pain a lot...). If anyone's interested: http://plugins.jquery.com/project/bgiframe http://plugins.jquery.com/project/bgiframe Thanks, Carsten -- View this message in context: http://old.nabble.com/-TRINIDAD--Alternative-for-tr%3AselectOneChoice-tp26525141p26624170.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Hi, Also: Does your AS have internet access? I think it might be a problem, because it can not obtain the schema information (or DTDs) for web.xml, for example http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd. Regards Jakob Korherr 2009/12/3 Jakob Korherr <jakob.korherr@gmail.com> > Hi, > > did you try it on an other machine (e.g. JBoss) also and did you get the > same error? > > Regards, > > Jakob Korherr > > 2009/12/3 viswam k <viswamy2k@gmail.com> > > Hi, >> this im getting when i deploy my webapplication on AIX,WAS7 box >> >> >> org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser parse Unable to >> parse web.xml >> java.net.ConnectException: A remote host did not respond within the >> timeout >> period. >> >> thanks >> -viswam >> > >
Hi, did you try it on an other machine (e.g. JBoss) also and did you get the same error? Regards, Jakob Korherr 2009/12/3 viswam k <viswamy2k@gmail.com> > Hi, > this im getting when i deploy my webapplication on AIX,WAS7 box > > > org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser parse Unable to > parse web.xml > java.net.ConnectException: A remote host did not respond within the timeout > period. > > thanks > -viswam >
Hi, this im getting when i deploy my webapplication on AIX,WAS7 box org.apache.myfaces.shared_impl.webapp.webxml.WebXmlParser parse Unable to parse web.xml java.net.ConnectException: A remote host did not respond within the timeout period. thanks -viswam
Hi,
You can obtain the label from a managed bean (e.g. #{bean.label}) and check
FacesContext.getCurrentInstance().getRenderResponse().
If true, it is the value for the label.
If false, it is the value for the FacesMessage.
I hope this works in your version. I only did a short (and a bit different)
test in myfaces 1.2, but that worked well.
Regards
Jakob Korherr
2009/12/2 laredotornado <laredotornado@gmail.com>
>
> Ah, I see. In that case I have one last question. I want the validation
> error message to contain a slightly different value than what the label
> contains in its "value" field. As such, is a custom phase listener my only
> option?
>
> Thanks, -
>
>
>
> Rene Guenther wrote:
> >
> > Hi Dave,
> >
> > I just looked it up, it is
> > <h:outputLabel ...>
> >
> > Eg.:
> >
> > <h:outputLabel for="status" value="#{text['entity.gos.status']}"/>
> > <t:inputText forceId="true" value="#{documentData.documentStatus}"
> > id="status"
> > required="true"/>
> >
> >
> > That way the ... is required message included the value of the label for
> > us.
> >
> > Cheers
> > Rene
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: laredotornado [mailto:laredotornado@gmail.com]
> > Gesendet: Mittwoch, 2. Dezember 2009 19:10
> > An: users@myfaces.apache.org
> > Betreff: Re: AW: Any way to customize this validate number message?
> >
> >
> > Hi Rene,
> >
> > I changed the input ... is this what you meant because I still get the
> > same
> > error ...
> >
> > <label id="Dome Tour, Number of Adults"
> > for="domeTourNumber_of_Adults">
> > *
> > <strong>Number of Adults:</strong>
> > </label>
> > <t:inputText forceId="true" id="domeTourNumber_of_Adults"
> > value="#{domeTour.numAdults}"
> > required="false"
> > size="60"
> > maxlength="60"
> > styleClass="textFields
> > numAdultsField">
> > <f:validator validatorId="TourRequiredIfCheckedValidator"
> > />
> > <f:validator validatorId="TourTotalPeopleValidator"
> />
> > <f:validator
> validatorId="TourAdultChildRatioValidator" />
> > </t:inputText>
> >
> > The error that appears is
> >
> > domeTourNumber_of_Adults: 'bbb' must be a number between -2147483648 and
> > 2147483647 Example: 9346
> >
> > Any ideas what I might be doing wrong? Thanks, - Dave
> >
> >
> >
> > Rene Guenther wrote:
> >>
> >> Hi Dave,
> >>
> >> If I remember correctly, if you use a label and use t:inputText instead
> >> of
> >> h:inputText together with forceId="true" in the message
> >> tourType:domeTourNumber_of_Adults: will be replaced with the name of the
> >> label.
> >>
> >> There is also a key relating to MyFaces applicationResources.properties
> >> file
> >> which contains the message. If you find the key you could use that key
> >> along
> >> with your customized message into your applicationResources file which
> >> takes
> >> precedence over MyFaces one. You might find the message key eg. by
> >> looking
> >> up the file in the MyFaces sources.
> >>
> >> If you need different parameters than the default one you'd probably
> have
> >> to
> >> write your own validator.
> >>
> >> Cheers
> >> Rene
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: laredotornado [mailto:laredotornado@gmail.com]
> >> Gesendet: Mittwoch, 2. Dezember 2009 18:10
> >> An: users@myfaces.apache.org
> >> Betreff: Any way to customize this validate number message?
> >>
> >>
> >> Hi,
> >>
> >> I'm using MyFaces 1.1.6. I have this ...
> >>
> >> <h:inputText id="domeTourNumber_of_Adults"
> >> value="#{domeTour.numAdults}"
> >> required="false"
> >> size="60"
> >> maxlength="60"
> >> styleClass="textFields
> >> numAdultsField">
> >> <f:validator
> validatorId="TourRequiredIfCheckedValidator"
> >> />
> >>
> >> <f:validator validatorId="TourTotalPeopleValidator"
> />
> >> <f:validator
> validatorId="TourAdultChildRatioValidator"
> >> />
> >> </h:inputText>
> >>
> >> in which the bean's set and get type is an int. So if I enter a value
> >> like
> >> "aaa" into the field, I get a message like
> >>
> >> tourType:domeTourNumber_of_Adults: 'aaa' must be a number between
> >> -2147483648 and 2147483647 Example: 9346
> >>
> >> I would like to customize this message. Anyone know how I can do that?
> >> Thanks, - Dave
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp2
> >> 6612567p26612567.html
> >> Sent from the MyFaces - Users mailing list archive at Nabble.com.
> >>
> >>
> >>
> >
> > --
> > View this message in context:
> >
> http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp26612567p26613605.html
> > Sent from the MyFaces - Users mailing list archive at Nabble.com.
> >
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp26612567p26614138.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
Ah, I see. In that case I have one last question. I want the validation
error message to contain a slightly different value than what the label
contains in its "value" field. As such, is a custom phase listener my only
option?
Thanks, -
Rene Guenther wrote:
>
> Hi Dave,
>
> I just looked it up, it is
> <h:outputLabel ...>
>
> Eg.:
>
> <h:outputLabel for="status" value="#{text['entity.gos.status']}"/>
> <t:inputText forceId="true" value="#{documentData.documentStatus}"
> id="status"
> required="true"/>
>
>
> That way the ... is required message included the value of the label for
> us.
>
> Cheers
> Rene
>
>
> -----Ursprüngliche Nachricht-----
> Von: laredotornado [mailto:laredotornado@gmail.com]
> Gesendet: Mittwoch, 2. Dezember 2009 19:10
> An: users@myfaces.apache.org
> Betreff: Re: AW: Any way to customize this validate number message?
>
>
> Hi Rene,
>
> I changed the input ... is this what you meant because I still get the
> same
> error ...
>
> <label id="Dome Tour, Number of Adults"
> for="domeTourNumber_of_Adults">
> *
> <strong>Number of Adults:</strong>
> </label>
> <t:inputText forceId="true" id="domeTourNumber_of_Adults"
> value="#{domeTour.numAdults}"
> required="false"
> size="60"
> maxlength="60"
> styleClass="textFields
> numAdultsField">
> <f:validator validatorId="TourRequiredIfCheckedValidator"
> />
> <f:validator validatorId="TourTotalPeopleValidator" />
> <f:validator validatorId="TourAdultChildRatioValidator" />
> </t:inputText>
>
> The error that appears is
>
> domeTourNumber_of_Adults: 'bbb' must be a number between -2147483648 and
> 2147483647 Example: 9346
>
> Any ideas what I might be doing wrong? Thanks, - Dave
>
>
>
> Rene Guenther wrote:
>>
>> Hi Dave,
>>
>> If I remember correctly, if you use a label and use t:inputText instead
>> of
>> h:inputText together with forceId="true" in the message
>> tourType:domeTourNumber_of_Adults: will be replaced with the name of the
>> label.
>>
>> There is also a key relating to MyFaces applicationResources.properties
>> file
>> which contains the message. If you find the key you could use that key
>> along
>> with your customized message into your applicationResources file which
>> takes
>> precedence over MyFaces one. You might find the message key eg. by
>> looking
>> up the file in the MyFaces sources.
>>
>> If you need different parameters than the default one you'd probably have
>> to
>> write your own validator.
>>
>> Cheers
>> Rene
>>
>> -----Ursprüngliche Nachricht-----
>> Von: laredotornado [mailto:laredotornado@gmail.com]
>> Gesendet: Mittwoch, 2. Dezember 2009 18:10
>> An: users@myfaces.apache.org
>> Betreff: Any way to customize this validate number message?
>>
>>
>> Hi,
>>
>> I'm using MyFaces 1.1.6. I have this ...
>>
>> <h:inputText id="domeTourNumber_of_Adults"
>> value="#{domeTour.numAdults}"
>> required="false"
>> size="60"
>> maxlength="60"
>> styleClass="textFields
>> numAdultsField">
>> <f:validator validatorId="TourRequiredIfCheckedValidator"
>> />
>>
>> <f:validator validatorId="TourTotalPeopleValidator" />
>> <f:validator validatorId="TourAdultChildRatioValidator"
>> />
>> </h:inputText>
>>
>> in which the bean's set and get type is an int. So if I enter a value
>> like
>> "aaa" into the field, I get a message like
>>
>> tourType:domeTourNumber_of_Adults: 'aaa' must be a number between
>> -2147483648 and 2147483647 Example: 9346
>>
>> I would like to customize this message. Anyone know how I can do that?
>> Thanks, - Dave
>> --
>> View this message in context:
>> http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp2
>> 6612567p26612567.html
>> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>>
>>
>>
>
> --
> View this message in context:
> http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp26612567p26613605.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp26612567p26614138.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Btw. the file where are the messages are located is
myfaces-impl-x.x.x.jar!/javax.faces/MessagesXXX.properties
-----Ursprüngliche Nachricht-----
Von: laredotornado [mailto:laredotornado@gmail.com]
Gesendet: Mittwoch, 2. Dezember 2009 19:10
An: users@myfaces.apache.org
Betreff: Re: AW: Any way to customize this validate number message?
Hi Rene,
I changed the input ... is this what you meant because I still get the same
error ...
<label id="Dome Tour, Number of Adults"
for="domeTourNumber_of_Adults">
*
<strong>Number of Adults:</strong>
</label>
<t:inputText forceId="true" id="domeTourNumber_of_Adults"
value="#{domeTour.numAdults}"
required="false"
size="60"
maxlength="60"
styleClass="textFields
numAdultsField">
<f:validator validatorId="TourRequiredIfCheckedValidator" />
<f:validator validatorId="TourTotalPeopleValidator" />
<f:validator validatorId="TourAdultChildRatioValidator" />
</t:inputText>
The error that appears is
domeTourNumber_of_Adults: 'bbb' must be a number between -2147483648 and
2147483647 Example: 9346
Any ideas what I might be doing wrong? Thanks, - Dave
Rene Guenther wrote:
>
> Hi Dave,
>
> If I remember correctly, if you use a label and use t:inputText instead of
> h:inputText together with forceId="true" in the message
> tourType:domeTourNumber_of_Adults: will be replaced with the name of the
> label.
>
> There is also a key relating to MyFaces applicationResources.properties
> file
> which contains the message. If you find the key you could use that key
> along
> with your customized message into your applicationResources file which
> takes
> precedence over MyFaces one. You might find the message key eg. by looking
> up the file in the MyFaces sources.
>
> If you need different parameters than the default one you'd probably have
> to
> write your own validator.
>
> Cheers
> Rene
>
> -----Ursprüngliche Nachricht-----
> Von: laredotornado [mailto:laredotornado@gmail.com]
> Gesendet: Mittwoch, 2. Dezember 2009 18:10
> An: users@myfaces.apache.org
> Betreff: Any way to customize this validate number message?
>
>
> Hi,
>
> I'm using MyFaces 1.1.6. I have this ...
>
> <h:inputText id="domeTourNumber_of_Adults"
> value="#{domeTour.numAdults}"
> required="false"
> size="60"
> maxlength="60"
> styleClass="textFields
> numAdultsField">
> <f:validator validatorId="TourRequiredIfCheckedValidator"
> />
>
> <f:validator validatorId="TourTotalPeopleValidator" />
> <f:validator validatorId="TourAdultChildRatioValidator" />
> </h:inputText>
>
> in which the bean's set and get type is an int. So if I enter a value
> like
> "aaa" into the field, I get a message like
>
> tourType:domeTourNumber_of_Adults: 'aaa' must be a number between
> -2147483648 and 2147483647 Example: 9346
>
> I would like to customize this message. Anyone know how I can do that?
> Thanks, - Dave
> --
> View this message in context:
> http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp2
> 6612567p26612567.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp26612567p26613605.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Hi Dave,
I just looked it up, it is
<h:outputLabel ...>
Eg.:
<h:outputLabel for="status" value="#{text['entity.gos.status']}"/>
<t:inputText forceId="true" value="#{documentData.documentStatus}" id="status"
required="true"/>
That way the ... is required message included the value of the label for us.
Cheers
Rene
-----Ursprüngliche Nachricht-----
Von: laredotornado [mailto:laredotornado@gmail.com]
Gesendet: Mittwoch, 2. Dezember 2009 19:10
An: users@myfaces.apache.org
Betreff: Re: AW: Any way to customize this validate number message?
Hi Rene,
I changed the input ... is this what you meant because I still get the same
error ...
<label id="Dome Tour, Number of Adults"
for="domeTourNumber_of_Adults">
*
<strong>Number of Adults:</strong>
</label>
<t:inputText forceId="true" id="domeTourNumber_of_Adults"
value="#{domeTour.numAdults}"
required="false"
size="60"
maxlength="60"
styleClass="textFields
numAdultsField">
<f:validator validatorId="TourRequiredIfCheckedValidator" />
<f:validator validatorId="TourTotalPeopleValidator" />
<f:validator validatorId="TourAdultChildRatioValidator" />
</t:inputText>
The error that appears is
domeTourNumber_of_Adults: 'bbb' must be a number between -2147483648 and
2147483647 Example: 9346
Any ideas what I might be doing wrong? Thanks, - Dave
Rene Guenther wrote:
>
> Hi Dave,
>
> If I remember correctly, if you use a label and use t:inputText instead of
> h:inputText together with forceId="true" in the message
> tourType:domeTourNumber_of_Adults: will be replaced with the name of the
> label.
>
> There is also a key relating to MyFaces applicationResources.properties
> file
> which contains the message. If you find the key you could use that key
> along
> with your customized message into your applicationResources file which
> takes
> precedence over MyFaces one. You might find the message key eg. by looking
> up the file in the MyFaces sources.
>
> If you need different parameters than the default one you'd probably have
> to
> write your own validator.
>
> Cheers
> Rene
>
> -----Ursprüngliche Nachricht-----
> Von: laredotornado [mailto:laredotornado@gmail.com]
> Gesendet: Mittwoch, 2. Dezember 2009 18:10
> An: users@myfaces.apache.org
> Betreff: Any way to customize this validate number message?
>
>
> Hi,
>
> I'm using MyFaces 1.1.6. I have this ...
>
> <h:inputText id="domeTourNumber_of_Adults"
> value="#{domeTour.numAdults}"
> required="false"
> size="60"
> maxlength="60"
> styleClass="textFields
> numAdultsField">
> <f:validator validatorId="TourRequiredIfCheckedValidator"
> />
>
> <f:validator validatorId="TourTotalPeopleValidator" />
> <f:validator validatorId="TourAdultChildRatioValidator" />
> </h:inputText>
>
> in which the bean's set and get type is an int. So if I enter a value
> like
> "aaa" into the field, I get a message like
>
> tourType:domeTourNumber_of_Adults: 'aaa' must be a number between
> -2147483648 and 2147483647 Example: 9346
>
> I would like to customize this message. Anyone know how I can do that?
> Thanks, - Dave
> --
> View this message in context:
> http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp2
> 6612567p26612567.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp26612567p26613605.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Hi Rene,
I changed the input ... is this what you meant because I still get the same
error ...
<label id="Dome Tour, Number of Adults"
for="domeTourNumber_of_Adults">
*
<strong>Number of Adults:</strong>
</label>
<t:inputText forceId="true" id="domeTourNumber_of_Adults"
value="#{domeTour.numAdults}"
required="false"
size="60"
maxlength="60"
styleClass="textFields
numAdultsField">
<f:validator validatorId="TourRequiredIfCheckedValidator" />
<f:validator validatorId="TourTotalPeopleValidator" />
<f:validator validatorId="TourAdultChildRatioValidator" />
</t:inputText>
The error that appears is
domeTourNumber_of_Adults: 'bbb' must be a number between -2147483648 and
2147483647 Example: 9346
Any ideas what I might be doing wrong? Thanks, - Dave
Rene Guenther wrote:
>
> Hi Dave,
>
> If I remember correctly, if you use a label and use t:inputText instead of
> h:inputText together with forceId="true" in the message
> tourType:domeTourNumber_of_Adults: will be replaced with the name of the
> label.
>
> There is also a key relating to MyFaces applicationResources.properties
> file
> which contains the message. If you find the key you could use that key
> along
> with your customized message into your applicationResources file which
> takes
> precedence over MyFaces one. You might find the message key eg. by looking
> up the file in the MyFaces sources.
>
> If you need different parameters than the default one you'd probably have
> to
> write your own validator.
>
> Cheers
> Rene
>
> -----Ursprüngliche Nachricht-----
> Von: laredotornado [mailto:laredotornado@gmail.com]
> Gesendet: Mittwoch, 2. Dezember 2009 18:10
> An: users@myfaces.apache.org
> Betreff: Any way to customize this validate number message?
>
>
> Hi,
>
> I'm using MyFaces 1.1.6. I have this ...
>
> <h:inputText id="domeTourNumber_of_Adults"
> value="#{domeTour.numAdults}"
> required="false"
> size="60"
> maxlength="60"
> styleClass="textFields
> numAdultsField">
> <f:validator validatorId="TourRequiredIfCheckedValidator"
> />
>
> <f:validator validatorId="TourTotalPeopleValidator" />
> <f:validator validatorId="TourAdultChildRatioValidator" />
> </h:inputText>
>
> in which the bean's set and get type is an int. So if I enter a value
> like
> "aaa" into the field, I get a message like
>
> tourType:domeTourNumber_of_Adults: 'aaa' must be a number between
> -2147483648 and 2147483647 Example: 9346
>
> I would like to customize this message. Anyone know how I can do that?
> Thanks, - Dave
> --
> View this message in context:
> http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp2
> 6612567p26612567.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp26612567p26613605.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Hi Dave,
If I remember correctly, if you use a label and use t:inputText instead of
h:inputText together with forceId="true" in the message
tourType:domeTourNumber_of_Adults: will be replaced with the name of the
label.
There is also a key relating to MyFaces applicationResources.properties file
which contains the message. If you find the key you could use that key along
with your customized message into your applicationResources file which takes
precedence over MyFaces one. You might find the message key eg. by looking
up the file in the MyFaces sources.
If you need different parameters than the default one you'd probably have to
write your own validator.
Cheers
Rene
-----Ursprngliche Nachricht-----
Von: laredotornado [mailto:laredotornado@gmail.com]
Gesendet: Mittwoch, 2. Dezember 2009 18:10
An: users@myfaces.apache.org
Betreff: Any way to customize this validate number message?
Hi,
I'm using MyFaces 1.1.6. I have this ...
<h:inputText id="domeTourNumber_of_Adults"
value="#{domeTour.numAdults}"
required="false"
size="60"
maxlength="60"
styleClass="textFields
numAdultsField">
<f:validator validatorId="TourRequiredIfCheckedValidator" />
<f:validator validatorId="TourTotalPeopleValidator" />
<f:validator validatorId="TourAdultChildRatioValidator" />
</h:inputText>
in which the bean's set and get type is an int. So if I enter a value like
"aaa" into the field, I get a message like
tourType:domeTourNumber_of_Adults: 'aaa' must be a number between
-2147483648 and 2147483647 Example: 9346
I would like to customize this message. Anyone know how I can do that?
Thanks, - Dave
--
View this message in context:
http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp2
6612567p26612567.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Greetings!!!
You can use javascript to validate this field or you can build your own
validator
On Wed, Dec 2, 2009 at 12:10 PM, laredotornado <laredotornado@gmail.com>wrote:
>
> Hi,
>
> I'm using MyFaces 1.1.6. I have this ...
>
> <h:inputText id="domeTourNumber_of_Adults"
> value="#{domeTour.numAdults}"
> required="false"
> size="60"
> maxlength="60"
> styleClass="textFields
> numAdultsField">
> <f:validator validatorId="TourRequiredIfCheckedValidator" />
> <f:validator validatorId="TourTotalPeopleValidator" />
> <f:validator validatorId="TourAdultChildRatioValidator" />
> </h:inputText>
>
> in which the bean's set and get type is an int. So if I enter a value like
> "aaa" into the field, I get a message like
>
> tourType:domeTourNumber_of_Adults: 'aaa' must be a number between
> -2147483648 and 2147483647 Example: 9346
>
> I would like to customize this message. Anyone know how I can do that?
> Thanks, - Dave
> --
> View this message in context:
> http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp26612567p26612567.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
>
--
Julin Osorio Amaya.
Hi,
I'm using MyFaces 1.1.6. I have this ...
<h:inputText id="domeTourNumber_of_Adults"
value="#{domeTour.numAdults}"
required="false"
size="60"
maxlength="60"
styleClass="textFields
numAdultsField">
<f:validator validatorId="TourRequiredIfCheckedValidator" />
<f:validator validatorId="TourTotalPeopleValidator" />
<f:validator validatorId="TourAdultChildRatioValidator" />
</h:inputText>
in which the bean's set and get type is an int. So if I enter a value like
"aaa" into the field, I get a message like
tourType:domeTourNumber_of_Adults: 'aaa' must be a number between
-2147483648 and 2147483647 Example: 9346
I would like to customize this message. Anyone know how I can do that?
Thanks, - Dave
--
View this message in context: http://old.nabble.com/Any-way-to-customize-this-validate-number-message--tp26612567p26612567.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Hi Gerhard, thanks for your answers. I checked out the trunk and it's working as i expect it. I forgot to mention that i'm using facelets and trinidad, but the component support handles this great. Regards, Markus -----Ursprngliche Nachricht----- Von: Gerhard Petracek [mailto:gerhard.petracek@gmail.com] Gesendet: Dienstag, 1. Dezember 2009 21:45 An: MyFaces Discussion Betreff: Re: [EXTVal] Validators wihtout implicit required validations hi markus, i introduced marker annotations [1] so that you can easily mark validation strategies which are aware of empty- and null-values. i committed the changes as well as test-cases. there will be a new (milestone) version quite soon. regards, gerhard [1] http://issues.apache.org/jira/browse/EXTVAL-74 http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2009/11/30 Gerhard Petracek <gerhard.petracek@gmail.com> > short addition: > > i see your point and i'll change that. > for now: my previous post contains a list of simple solutions you can use. > > regards, > gerhard > > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > > > 2009/11/30 Gerhard Petracek <gerhard.petracek@gmail.com> > > hi, >> >> it's a bit different. >> the parameter mentioned by jakob is a jsf 2.0 parameter especially for the >> jsr 303 integration. >> if you set it to true, the not-null constraint will be interpreted like >> required (= true). >> extval uses it in an abstract class in a similar way. that means: you just >> have to use it to explicitly deactivate the behavior described above. >> it's automatically available for custom validation interceptors. an >> internal example is the validation interceptor of the bean-validation module >> (which allows to use jsr 303 with all jsf versions). >> >> the property validation module of the next release (as well as the >> available milestone) overrides this new default behavior so that an empty >> field doesn't lead to a null value for validation (due to backward >> compatibility reasons). however, you can easily customize this behavior. >> >> back to the original question: >> >> extval just delegates to the (configured) jsf length validator. so >> basically the behavior depends on the implementation you are using in your >> application. >> >> in this case the default implementation throws an exception because it >> isn't aware of empty values. to change this behavior you can: >> - register your custom jsf-length-validator implementation (see: >> javax.faces.Length) which handles it as you expect it (that's plain jsf) >> or >> - replace the default extval validation strategy for @Length to ignore >> empty values >> or >> - implement your custom extval annotation >> >> all 3 possibilities are quite easy. >> >> regards, >> gerhard >> >> http://www.irian.at >> >> Your JSF powerhouse - >> JSF Consulting, Development and >> Courses in English and German >> >> Professional Support for Apache MyFaces >> >> >> 2009/11/30 Jakob Korherr <jakob.korherr@gmail.com> >> >> Hi Markus, >>> >>> Take a look at the >>> javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL >>> config parameter in web.xml. >>> >>> Setting this to true will cause that your property "input" will be null, >>> if >>> the user submits an empty field and thus @Length will not be processed. >>> >>> Also take a look at http://jsfatwork.irian.at/semistatic/jsf.html, >>> chapter >>> 2.12 Validierung fur further information. It's written in german, but I >>> assume you're from Germany... >>> >>> Regards >>> >>> Jakob Korherr >>> >>> >>> 2009/11/30 Dreher, Markus <M.Dreher@dzbw.de> >>> >>> > Hi all, >>> > >>> > i want to validate a field only when the user filled it out. >>> > >>> > It's not a reuqired field, but when it is filled out, the input should >>> > be at least for example 3 digits. >>> > >>> > @Length(minimum=3, maximum = 60) >>> > private String input; >>> > >>> > With @Length this leads to a required field. >>> > >>> > Do i miss something? >>> > >>> > Regards, >>> > >>> > Markus >>> > >>> > >>> > >>> >> >> >
Greetings!!! Leonardo, you're right. I've used the same libraries (tomahawk 1.1.9 and tomahawk-sandbox-1.1.9) in Netbeans 6.7.1 and the web app runs. Maybe there's a bug in this JDeveloper version. Thanks. Leonardo Uribe escribi: > Hi > > This could be related to your IDE. Try run your app using other IDE to check > if there is a problem there. > > regards, > > Leonardo Uribe > > 2009/11/30 Julin Osorio Amaya EuphoriaIT <josorio@euphoriait.com> > > >> Greetings!!! >> >> I'm working on a JSF web app using tomahawk 1.1.9 but now I want to >> implement Sandbox to use the inputSuggestAjax tag. >> Actually I'm using JDeveloper 10.3.3.1 but after adding the >> tomahawk-sandbox-1.1.9-SNAPSHOT.jar to the project's library >> the app doesn't run. >> >> How can I solve this issue? >> >> Thanks for your help. >> >> > > > > __________ Informacin de NOD32, revisin 2277 (20070518) __________ > > Este mensaje ha sido analizado con NOD32 antivirus system > http://www.nod32.com > >
Hi This could be related to your IDE. Try run your app using other IDE to check if there is a problem there. regards, Leonardo Uribe 2009/11/30 Julin Osorio Amaya EuphoriaIT <josorio@euphoriait.com> > Greetings!!! > > I'm working on a JSF web app using tomahawk 1.1.9 but now I want to > implement Sandbox to use the inputSuggestAjax tag. > Actually I'm using JDeveloper 10.3.3.1 but after adding the > tomahawk-sandbox-1.1.9-SNAPSHOT.jar to the project's library > the app doesn't run. > > How can I solve this issue? > > Thanks for your help. >
tr:selectOneRadio and optionally put it in a popup? -Andrew On Thu, Nov 26, 2009 at 12:09 AM, Carsten Pieper <carsten.pieper@continentale.de> wrote: > > Hi there, > > as our applications still have to be compatible to IE6 we're quite unhappy > with > the tr:selectOneChoice as is makes use of the HTML select component which > is a pain in IE6 (IE6 being the culprit, not the select, of course; e.g. the > good > old z-index bug...). > > So, here's my question: Does anyone know of an alternative to the > tr:selectOneChoice > that doesn't make use of the HTML select and that can easily be plugged into > an > existing Trinidad based application? > > Thanks, Carsten > -- > View this message in context: http://old.nabble.com/-TRINIDAD--Alternative-for-tr%3AselectOneChoice-tp26525141p26525141.html > Sent from the MyFaces - Users mailing list archive at Nabble.com. > >
hi markus, i introduced marker annotations [1] so that you can easily mark validation strategies which are aware of empty- and null-values. i committed the changes as well as test-cases. there will be a new (milestone) version quite soon. regards, gerhard [1] http://issues.apache.org/jira/browse/EXTVAL-74 http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2009/11/30 Gerhard Petracek <gerhard.petracek@gmail.com> > short addition: > > i see your point and ill change that. > for now: my previous post contains a list of simple solutions you can use. > > regards, > gerhard > > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > > > 2009/11/30 Gerhard Petracek <gerhard.petracek@gmail.com> > > hi, >> >> it's a bit different. >> the parameter mentioned by jakob is a jsf 2.0 parameter especially for the >> jsr 303 integration. >> if you set it to true, the not-null constraint will be interpreted like >> required (= true). >> extval uses it in an abstract class in a similar way. that means: you just >> have to use it to explicitly deactivate the behavior described above. >> it's automatically available for custom validation interceptors. an >> internal example is the validation interceptor of the bean-validation module >> (which allows to use jsr 303 with all jsf versions). >> >> the property validation module of the next release (as well as the >> available milestone) overrides this new default behavior so that an empty >> field doesn't lead to a null value for validation (due to backward >> compatibility reasons). however, you can easily customize this behavior. >> >> back to the original question: >> >> extval just delegates to the (configured) jsf length validator. so >> basically the behavior depends on the implementation you are using in your >> application. >> >> in this case the default implementation throws an exception because it >> isn't aware of empty values. to change this behavior you can: >> - register your custom jsf-length-validator implementation (see: >> javax.faces.Length) which handles it as you expect it (that's plain jsf) >> or >> - replace the default extval validation strategy for @Length to ignore >> empty values >> or >> - implement your custom extval annotation >> >> all 3 possibilities are quite easy. >> >> regards, >> gerhard >> >> http://www.irian.at >> >> Your JSF powerhouse - >> JSF Consulting, Development and >> Courses in English and German >> >> Professional Support for Apache MyFaces >> >> >> 2009/11/30 Jakob Korherr <jakob.korherr@gmail.com> >> >> Hi Markus, >>> >>> Take a look at the >>> javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL >>> config parameter in web.xml. >>> >>> Setting this to true will cause that your property "input" will be null, >>> if >>> the user submits an empty field and thus @Length will not be processed. >>> >>> Also take a look at http://jsfatwork.irian.at/semistatic/jsf.html, >>> chapter >>> 2.12 Validierung fur further information. It's written in german, but I >>> assume you're from Germany... >>> >>> Regards >>> >>> Jakob Korherr >>> >>> >>> 2009/11/30 Dreher, Markus <M.Dreher@dzbw.de> >>> >>> > Hi all, >>> > >>> > i want to validate a field only when the user filled it out. >>> > >>> > It's not a reuqired field, but when it is filled out, the input should >>> > be at least for example 3 digits. >>> > >>> > @Length(minimum=3, maximum = 60) >>> > private String input; >>> > >>> > With @Length this leads to a required field. >>> > >>> > Do i miss something? >>> > >>> > Regards, >>> > >>> > Markus >>> > >>> > >>> > >>> >> >> >
Hi all,I had gone thru <http://wiki.apache.org/myfaces/Performance> and updatedorg.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION
to "4" to have less session usage. Now the problem is I have a link on a page, on click of
which a new window opens. After going through more than 4 screens in the child window, none
of the links in the parent window work. The page simply refreshes. Can anyone suggest solution
for this? It works if I put more number of views in session. But I wanna know if there is
any other alternative..
Thanks,Shasi
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/
Hi Myfaces Core 2.0.0-alpha still not pass all TCK tests, but working hard to get things done. The idea of doing an alpha release is give the people interested the oportunity to try it and report any bugs that could appear. Note this jsf version has a lot of changes and feedback is most welcome. regards, Leonardo Uribe 2009/11/30 Delos <daition@gmail.com> > Hi, > > Just want to know if MyFaces Core 2.0.0 has passed the TCK? If not , is > there any plan for it? > > Thanks! > > 2009/12/1 Leonardo Uribe <lu4242@apache.org> > > > The Apache MyFaces team is pleased to announce the release of MyFaces > Core > > 2.0.0-alpha. > > > > MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified by > > JSR-314. > > > > MyFaces Core 2.0.0-alpha is available in both binary and source > > distributions. > > > > * http://myfaces.apache.org/download.html > > > > MyFaces Core is also available in the central Maven repository under > Group > > ID "org.apache.myfaces.core". > > > > Release Notes - MyFaces Core - Version 2.0.0-alpha > > > > Sub-task > > > > * [MYFACES-2174] - MyFaces 2.0 AJAX API extension proposal > > * [MYFACES-2191] - Move the myfaces params into the context > > * [MYFACES-2195] - rename xhrcore_xxx to xhrcore._xxx > > * [MYFACES-2200] - Send events and errors at the various xhr stages > > * [MYFACES-2223] - switch viewstate replacement from id to name > > * [MYFACES-2238] - offer extension point for AJAX Javascript > > * [MYFACES-2240] - typo in javascript build script and target folder > > doesn't fit the spec > > * [MYFACES-2257] - trigger external scripts after AJAX reload > > * [MYFACES-2311] - Implement <composite:actionSource> tag handler > > * [MYFACES-2312] - Implement <composite:attribute> tag handler > > * [MYFACES-2313] - Implement <composite:editableValueHolder> tag > handler > > * [MYFACES-2314] - Implement <composite:extension> tag handler > > * [MYFACES-2315] - Implement <composite:facet> tag handler > > * [MYFACES-2316] - Implement <composite:implementation> tag handler > > * [MYFACES-2317] - Implement <composite:insertChildren> tag handler > > * [MYFACES-2318] - Implement <composite:insertFacet> tag handler > > * [MYFACES-2319] - Implement <composite:interface> tag handler > > * [MYFACES-2320] - Implement <composite:renderFacet> tag handler > > * [MYFACES-2324] - Add ViewDeclarationLanguage.retargetAttachedObjects > > and ViewDeclarationLanguage.retargetMethodExpressions > > * [MYFACES-2325] - Add Composite Renderer class > > * [MYFACES-2331] - Implement Composite Component Attributes ELResolver > > (jsf 2.0 spec section 5.6.2.2) and add implicit object "cc" and > "component" > > * [MYFACES-2362] - Move default validator registration from > > UIInput.validateValue to ComponentTagHandlerDelegate > > > > Bug > > > > * [MYFACES-2083] - FacesContext contains several unnecessary methods > > * [MYFACES-2131] - Import to internal Sun class > > * [MYFACES-2146] - Bug in UIViewRoot causes Exception in > > popComponentFromEL() > > * [MYFACES-2147] - NoSuchMethodException when instantiating SystemEvent > > objects > > * [MYFACES-2287] - getting the myfaces 1.2 simple example app running > on > > 2.0 impl > > * [MYFACES-2296] - Annotation scanning bugs > > * [MYFACES-2357] - currency validation does not fall through to the > > default JVM local when a default locale is not specified in faces-config > > * [MYFACES-2358] - System event system not working > > * [MYFACES-2359] - ComponentSystemEvents are not globally dispatched > > * [MYFACES-2360] - Facelets JSTL escapeXML function not escaping '>' > > * [MYFACES-2381] - Broken link: "Core JSF-2.0" > > * [MYFACES-2384] - @FacesBehavior not handled correctly > > * [MYFACES-2386] - Refactor Bean Validation "constants" to > > package-private class > > * [MYFACES-2387] - component state not being restored when > > ValueChangeListener is attached > > * [MYFACES-2390] - h:graphic image doesn't handle library attribue > > * [MYFACES-2391] - classpath resources not checking for valid version > > pattern > > * [MYFACES-2393] - graphicImage tag does not handle resource EL > > expressions properly > > * [MYFACES-2394] - ResourceDependency annotations not being handled > > properly if target attribute is set > > * [MYFACES-2397] - f:ajax attributes execute and render should take > space > > delimited clientIds > > * [MYFACES-2398] - no spaces in html-output of f:ajax with render and > > execute attributes with more than one target > > * [MYFACES-2402] - Fix conditional navigation > > * [MYFACES-2404] - JspViewDeclarationLanguageStrategy is always the > > default strategy, so it should always return true on handles() method > > * [MYFACES-2405] - f:ajax renderer not handling multiple IDs properly > > * [MYFACES-2406] - Create a view with viewId is null should be possible > > * [MYFACES-2408] - UIComponent.subscribeToEvent and unsubscribeToEvent > > should throw NullPointerException when eventClass or componentListener is > > null > > * [MYFACES-2415] - EnumConverter should only conver to String valid > enum > > values > > * [MYFACES-2416] - h:outputLabel does not handle escape property > > > > Improvement > > > > * [MYFACES-1910] - Add resetValue() to EditableValueHolder interface > > (this is a JSF 2.0 related issue) > > * [MYFACES-2010] - Implement JSF 2.0 - Comment in the class > > * [MYFACES-2036] - Comment on javax.faces.application.FacesMessage > Class > > * [MYFACES-2235] - ProjectStage extension > > * [MYFACES-2354] - update javax.faces.component classes which utilize > the > > context classloader to handle java2 security > > * [MYFACES-2389] - clean up the UIComponentBase.setParent() > > > > New Feature > > > > * [MYFACES-2133] - The implementation of ResourceHandler must be > > thread-safe > > * [MYFACES-2140] - Add annotation processing logic > > * [MYFACES-2162] - Default RenderKitId should be HTML_BASIC when using > > annotations > > * [MYFACES-2173] - JSF 2.0 AJAX library > > * [MYFACES-2372] - h:commandButton should render UIParameter children > > > > Task > > > > * [MYFACES-1911] - Implement JSF 2.0 logic at TODO #1 > > * [MYFACES-1912] - Implement JSF 2.0 logic at TODO #2 > > * [MYFACES-1913] - Implement JSF 2.0 logic at TODO #3 > > * [MYFACES-1914] - Implement JSF 2.0 logic at TODO #4 > > * [MYFACES-1915] - Implement JSF 2.0 logic at TODO #5 > > * [MYFACES-1916] - Implement JSF 2.0 logic at TODO #6 > > * [MYFACES-1917] - Implement JSF 2.0 logic at TODO #7 > > * [MYFACES-1918] - Implement JSF 2.0 logic at TODO #8 > > * [MYFACES-1919] - Implement JSF 2.0 logic at TODO #9 > > * [MYFACES-1920] - Implement JSF 2.0 logic at TODO #10 > > * [MYFACES-1921] - Implement JSF 2.0 logic at TODO #16 > > * [MYFACES-1922] - Implement JSF 2.0 logic at TODO #17 > > * [MYFACES-1923] - Implement JSF 2.0 logic at TODO #11 > > * [MYFACES-1924] - Implement JSF 2.0 logic at TODO #18 > > * [MYFACES-1925] - Implement JSF 2.0 logic at TODO #19 > > * [MYFACES-1926] - Implement JSF 2.0 logic at TODO #20 > > * [MYFACES-1927] - Implement JSF 2.0 logic at TODO #21 > > * [MYFACES-1928] - Implement JSF 2.0 logic at TODO #22 > > * [MYFACES-1929] - Implement JSF 2.0 logic at TODO #23 > > * [MYFACES-1930] - Implement JSF 2.0 logic at TODO #22 > > * [MYFACES-1931] - Implement JSF 2.0 logic at TODO #35 > > * [MYFACES-1932] - Implement JSF 2.0 logic at TODO #24 > > * [MYFACES-1933] - Implement JSF 2.0 logic at TODO #24 > > * [MYFACES-1934] - Implement JSF 2.0 logic at TODO #25 > > * [MYFACES-1935] - Implement JSF 2.0 logic at TODO #34 > > * [MYFACES-1936] - Implement JSF 2.0 logic at TODO #26 > > * [MYFACES-1938] - Implement JSF 2.0 logic at TODO #28 > > * [MYFACES-1939] - Implement JSF 2.0 logic at TODO #33 > > * [MYFACES-1940] - Implement JSF 2.0 logic at TODO #29 > > * [MYFACES-1941] - Implement JSF 2.0 logic at TODO #30 > > * [MYFACES-1942] - Implement JSF 2.0 logic at TODO #32 > > * [MYFACES-1943] - Implement JSF 2.0 logic at TODO #12 > > * [MYFACES-1944] - Implement JSF 2.0 logic at TODO #13 > > * [MYFACES-1945] - Implement JSF 2.0 logic at TODO #14 > > * [MYFACES-1946] - Implement JSF 2.0 logic at TODO #31 > > * [MYFACES-1947] - Implement JSF 2.0 logic at TODO #15 > > * [MYFACES-1948] - Implement JSF 2.0 logic at TODO #27 > > * [MYFACES-1950] - Implement JSF 2.0 - ExternalContext is missing some > > methods > > * [MYFACES-1951] - Update UIInput.validate() > > * [MYFACES-1958] - Implement AfterAddToParentEvent > > * [MYFACES-1959] - Add missing javax.faces.event Classes & Interfaces > > * [MYFACES-1968] - Implement JSF 2.0 logic at TODO #35 > > * [MYFACES-1969] - Implement JSF 2.0 logic at TODO #36 > > * [MYFACES-1970] - Implement JSF 2.0 logic at TODO #37 > > * [MYFACES-1971] - Implement JSF 2.0 logic at TODO #38 > > * [MYFACES-1972] - Implement JSF 2.0 logic at TODO #39 > > * [MYFACES-1973] - Implement JSF 2.0 logic at TODO #40 > > * [MYFACES-1974] - Apply Java 5 specific features to the code, mainly > > generics and enhanced for > > * [MYFACES-1977] - add to FacesServlet.service call to ResourceHandler > > and update digester code > > * [MYFACES-1978] - Remove org.apache.myfaces.portlet from JSF 2.0 > branch, > > because it has no use anymore > > * [MYFACES-1980] - Implement JSF 2.0 logic at TODO #41 > > * [MYFACES-1983] - Implement JSF 2.0 logic at TODO #42 > > * [MYFACES-1984] - Implement JSF 2.0 logic at TODO #43 > > * [MYFACES-1985] - Implement JSF 2.0 logic at TODO #44 > > * [MYFACES-1986] - Implement JSF 2.0 logic at TODO #45 > > * [MYFACES-1987] - Implement JSF 2.0 logic at TODO #46 > > * [MYFACES-1998] - Implement JSF 2.0 logic at TODO #57 > > * [MYFACES-2003] - Implement JSF 2.0 logic at TODO #58 > > * [MYFACES-2014] - Implement > > ResponseStateManager.getViewState(FacesContext, Object) and update state > > saving field on client when ajax response is processed > > * [MYFACES-2015] - Implements AJAX lifecycle on UIViewRoot > > * [MYFACES-2018] - Implement @ResourceDependency support for > setConverter > > and addValidator > > * [MYFACES-2019] - Implement iterator() on DataModel > > * [MYFACES-2020] - Implement changes to RenderKit > > * [MYFACES-2021] - Add EDR2 part of error handling to FacesServlet > > * [MYFACES-2022] - Add setSubmitted(false) in UIForm.saveState > > * [MYFACES-2032] - Implement > > javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE config > > param > > * [MYFACES-2040] - Implement tag c:catch > > * [MYFACES-2041] - Implement tag c:choose > > * [MYFACES-2042] - Implement tag c:forEach > > * [MYFACES-2043] - Implement tag c:if > > * [MYFACES-2044] - Implement tag c:otherwise > > * [MYFACES-2045] - Implement tag c:set > > * [MYFACES-2046] - Implement tag c:when > > * [MYFACES-2047] - Implement tag composite:actionSource > > * [MYFACES-2048] - Implement tag composite:attribute > > * [MYFACES-2049] - Implement tag composite:editableValueHolder > > * [MYFACES-2050] - Implement tag composite:facet > > * [MYFACES-2051] - Implement tag composite:implementation > > * [MYFACES-2052] - Implement tag composite:insertChildren > > * [MYFACES-2053] - Implement tag composite:insertFacet > > * [MYFACES-2054] - Implement tag composite:interface > > * [MYFACES-2055] - Implement tag composite:valueHolder > > * [MYFACES-2056] - Implement tag fn:contains() > > * [MYFACES-2057] - Implement tag fn:containsIgnoreCase() > > * [MYFACES-2058] - Implement tag fn:endsWith() > > * [MYFACES-2059] - Implement tag fn:escapeXml() > > * [MYFACES-2060] - Implement tag fn:indexOf() > > * [MYFACES-2061] - Implement tag fn:join() > > * [MYFACES-2062] - Implement tag fn:length() > > * [MYFACES-2063] - Implement tag fn:replace() > > * [MYFACES-2064] - Implement tag fn:split() > > * [MYFACES-2065] - Implement tag fn:startsWith() > > * [MYFACES-2066] - Implement tag fn:substring() > > * [MYFACES-2067] - Implement tag fn:substringAfter() > > * [MYFACES-2068] - Implement tag fn:substringBefore() > > * [MYFACES-2069] - Implement tag fn:toLowerCase() > > * [MYFACES-2070] - Implement tag fn:toUpperCase() > > * [MYFACES-2071] - Implement tag fn:trim() > > * [MYFACES-2072] - Implement tag ui:component > > * [MYFACES-2073] - Implement tag ui:composition > > * [MYFACES-2074] - Implement tag ui:debug > > * [MYFACES-2075] - Implement tag ui:decorate > > * [MYFACES-2076] - Implement tag ui:define > > * [MYFACES-2077] - Implement tag ui:fragment > > * [MYFACES-2078] - Implement tag ui:include > > * [MYFACES-2079] - Implement tag ui:insert > > * [MYFACES-2080] - Implement tag ui:param > > * [MYFACES-2081] - Implement tag ui:repeat > > * [MYFACES-2085] - Add ApplicationWrapper class > > * [MYFACES-2086] - Add DiscoveryHandler class > > * [MYFACES-2088] - Add ExceptionHandler class > > * [MYFACES-2093] - Add ExceptionEvent class > > * [MYFACES-2096] - Make DataModel types generic > > * [MYFACES-2098] - Add RegexValidator class > > * [MYFACES-2101] - Javadoc update for method Object getFactory(String > > factoryName) of FactoryFinder class > > * [MYFACES-2102] - Implement JSF 2.0 logic for UIComponent > > createComponent(FacesContext context,Resource componentResource) TODO #60 > > * [MYFACES-2105] - Implement JSF 2.0 logic for UIComponent > > createComponent(final String componentType) > > * [MYFACES-2106] - add Exception handler factory to FactoryFinder and > > update getFactory method > > * [MYFACES-2108] - implement ExceptionHandler contract on myfaces-impl > > * [MYFACES-2123] - Add javax.faces.webapp.pdl.facelets.* API classes > > * [MYFACES-2125] - Add UIComponent.doTreeTraversal method > > * [MYFACES-2136] - UISelectMany > > * [MYFACES-2151] - Make test work using shale test (changes in jsf 2.0 > > make it fail) > > * [MYFACES-2163] - Add RequiredValidator > > * [MYFACES-2166] - Some Resources contains ValueExpressions that must > be > > evaluated > > * [MYFACES-2171] - Add Config Ordering feature > > * [MYFACES-2178] - Implement IMPL - method addResponseHeader of > > ExternalContext > > * [MYFACES-2179] - Implement IMPL - method getRequestContentLength of > > ExternalContext > > * [MYFACES-2180] - Implement IMPL - method getResponseBufferSize of > > ExternalContext > > * [MYFACES-2181] - Implement IMPL - method getResponseOutputWriter of > > ExternalContext > > * [MYFACES-2182] - Implement IMPL - method isResponseCommitted of > > ExternalContext > > * [MYFACES-2184] - Implement IMPL - all TODO methods of ExternalContext > > * [MYFACES-2187] - Implement encodeBookmarkableURL and > encodeRedirectURL > > in ExternalContext > > * [MYFACES-2189] - Implement ApplicationImpl TODO's for Behavior > > * [MYFACES-2197] - ExceptionQueuedEventContext todos > > * [MYFACES-2198] - remaining FacesContext/FacesContextImpl TODOs. > > * [MYFACES-2205] - Update UIViewRoot to latest spec draft > > * [MYFACES-2215] - Handle RenderKit TODOs for JSF 2.0 > > * [MYFACES-2219] - ViewHandler TODOs for JSF 2.0 > > * [MYFACES-2220] - FacesConfigurator should scan application config > > resources(files on META-INF/) ending with .faces-config.xml > > * [MYFACES-2222] - ViewHandler.DEFAULT_SUFFIX could contain several > > suffixes > > * [MYFACES-2225] - Implement PostAddToViewEvent and > > PreRemoveFromViewEvent thrown conditions > > * [MYFACES-2226] - Add support for remaining 2.0 faces-config.xml > > elements > > * [MYFACES-2227] - Update ResponseWriter/ResponseWriterWrapper to > latest > > spec > > * [MYFACES-2228] - Add h:head, h:body, h:outputScript and > > h:outputStylesheet renderers > > * [MYFACES-2229] - update viewid calculation to new algorithm > > * [MYFACES-2230] - FaceletViewDeclarationLanguage TODOs > > * [MYFACES-2231] - Handle the TODOs for JSPViewDeclarationLanguage > > * [MYFACES-2254] - Finish ExceptionHandler support > > * [MYFACES-2255] - Create UIOutcomeTarget API class > > * [MYFACES-2258] - Add support for <if> navigation > > * [MYFACES-2259] - Implement Partial State Saving feature > > * [MYFACES-2262] - implement outcomtarget renderers > > * [MYFACES-2263] - Create Composite component EL resolver > > * [MYFACES-2264] - Behavior registration > > * [MYFACES-2266] - Implement Flash object and EL resolver > > * [MYFACES-2267] - handle TODOs for UIComponentBase > > * [MYFACES-2268] - Add support for registering client behavior > renderers > > * [MYFACES-2270] - Add FacesContext param to Application.publishEvent > > * [MYFACES-2271] - Call FacesMessage.rendered on message renderers > > * [MYFACES-2272] - Apply changes related to UIInput.validateValue and > > UIInput.VALIDATE_EMPTY_FIELDS_PARAM_NAME > > * [MYFACES-2273] - ClientBehaviorRenderer/ClientbehaviorBase TODOs > > * [MYFACES-2274] - Implement UIMessage.isRedisplay and > > UIMessages.isRedisplay > > * [MYFACES-2275] - UIMessages.getFor (Filter messages of a selected > > component) > > * [MYFACES-2276] - Update renderers that receive UIParameter to deal > with > > "disable" param. > > * [MYFACES-2277] - UISelectItem.isNoSelectionOption (deal with it on > > UISelectOne.validateValue and UISelectMany.validateValue) > > * [MYFACES-2278] - Render columns with th instead td, according to > > HtmlColumn.isRowHeader > > * [MYFACES-2279] - TODOs for javax.faces.application.NavigationCase > > * [MYFACES-2280] - ValidatorException should support collections of > > messages. > > * [MYFACES-2281] - Implement ViewListeners-Events api on UIViewRoot > > * [MYFACES-2282] - h:dataTable and h:panelGrid should implement > bodyrows > > behavior (tbody encapsulation) > > * [MYFACES-2283] - Apply selected/unselected css class to > > h:selectManyCheckbox > > * [MYFACES-2284] - Allow h:outputLink "fragment" property to append > text > > to url after '#' > > * [MYFACES-2285] - Add ExternalContextFactory Implementation > > * [MYFACES-2286] - javax.faces.view.facelets TODOs > > * [MYFACES-2291] - Components implementing ClientBehaviorHolder should > > override getEventNames() and getDefaultEventName() > > * [MYFACES-2292] - update NavigationHandlerImpl to extend > > ConfigurableNavigationHandler > > * [MYFACES-2293] - ui:composition, ui:define and ui:insert component > tag > > handlers does not work as expected > > * [MYFACES-2294] - Sync API with final 2.0 spec > > * [MYFACES-2297] - Add TagHandlerDelegateFactory implementation > > * [MYFACES-2298] - Apply algorithm described on > > javax.faces.view.facelets.ComponentHandler in implementation > > * [MYFACES-2299] - Add AttachedObjectHandler implementation when it is > > necessary > > * [MYFACES-2300] - binding property on facelets tag handlers should be > > retrieved from javax.faces.view.facelets.DelegatingMetaTagHandler > > * [MYFACES-2302] - Get simple 2.0 app working > > * [MYFACES-2304] - Annotate facelets stuff adding @JSFFaceletTag and > > @JSFFaceletAttribute to myfaces-builder-plugin > > * [MYFACES-2307] - Generate HtmlHead and HtmlBody > > * [MYFACES-2309] - Add new attributes to f:selectItems > > * [MYFACES-2310] - Implement Composite Component feature > > * [MYFACES-2322] - Implement <f:metadata> tag handler > > * [MYFACES-2327] - Move facelets test code to myfaces > > * [MYFACES-2330] - Get "basic-ajax" 2.0 sample app working > > * [MYFACES-2337] - Implement UniqueIdVendor.createUniqueId method and > > review all related code to UniqueIdVendor > > * [MYFACES-2340] - Get "basic-ezcomp" 2.0 sample working > > * [MYFACES-2341] - facelet tag lib parser includes <behavior> section > > * [MYFACES-2345] - Add View Parameters feature > > * [MYFACES-2349] - h:commandButton allows type="button" on jsf 2.0 > > * [MYFACES-2364] - PostRestoreStateEvent should be called from > > DefaultRestoreViewSupport.processComponentBinding > > * [MYFACES-2365] - DefaultRestoreViewSupport.calculateViewId should not > > call ViewHandler.deriveViewId, it should be called later from > > ViewHandler.createView and ViewHandler.restoreView > > * [MYFACES-2366] - RestoreViewExecutor should check also if the server > is > > showing an error page when check for postback > > * [MYFACES-2367] - FacesContext.isProcessingEvents should be called > from > > Application.publishEvent > > * [MYFACES-2375] - <managed-bean-scope> could also be an EL expression, > > to allow easy implementation of new scopes > > * [MYFACES-2376] - h:outputScript should force type="text/javascript" > > * [MYFACES-2378] - Use java util logging on 2.0.x branch > > * [MYFACES-2379] - Create site for core 2.0.x > > * [MYFACES-2399] - ManagedBeanResolver does not handle view scope > > * [MYFACES-2403] - Myfaces core 2.0 uses jdk 6, but it should be jdk 5 > > * [MYFACES-2407] - _ComponentChildrenList does not implement all List > > methods > > * [MYFACES-2411] - Update api to match latest signature > > * [MYFACES-2413] - @ResourceDependency annotations should be scanned > when > > Application.createConverter(String) and > Application.createValidator(String) > > is called > > * [MYFACES-2414] - ResourceHandlerImpl should scan first with locale > > prefix and then without it > > * [MYFACES-2419] - NavigationHandler does not deal with no outcome & no > > action & no if case > > * [MYFACES-2422] - Change package name to org.apache.myfaces.test in > > myfaces-test project > > * [MYFACES-2424] - c namespace changed to > > http://java.sun.com/jsp/jstl/core > > > > regards > > > > Leonardo Uribe > > > > > > -- > Best Regards, > > Delos >
Hi, Just want to know if MyFaces Core 2.0.0 has passed the TCK? If not , is there any plan for it? Thanks! 2009/12/1 Leonardo Uribe <lu4242@apache.org> > The Apache MyFaces team is pleased to announce the release of MyFaces Core > 2.0.0-alpha. > > MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified by > JSR-314. > > MyFaces Core 2.0.0-alpha is available in both binary and source > distributions. > > * http://myfaces.apache.org/download.html > > MyFaces Core is also available in the central Maven repository under Group > ID "org.apache.myfaces.core". > > Release Notes - MyFaces Core - Version 2.0.0-alpha > > Sub-task > > * [MYFACES-2174] - MyFaces 2.0 AJAX API extension proposal > * [MYFACES-2191] - Move the myfaces params into the context > * [MYFACES-2195] - rename xhrcore_xxx to xhrcore._xxx > * [MYFACES-2200] - Send events and errors at the various xhr stages > * [MYFACES-2223] - switch viewstate replacement from id to name > * [MYFACES-2238] - offer extension point for AJAX Javascript > * [MYFACES-2240] - typo in javascript build script and target folder > doesn't fit the spec > * [MYFACES-2257] - trigger external scripts after AJAX reload > * [MYFACES-2311] - Implement <composite:actionSource> tag handler > * [MYFACES-2312] - Implement <composite:attribute> tag handler > * [MYFACES-2313] - Implement <composite:editableValueHolder> tag handler > * [MYFACES-2314] - Implement <composite:extension> tag handler > * [MYFACES-2315] - Implement <composite:facet> tag handler > * [MYFACES-2316] - Implement <composite:implementation> tag handler > * [MYFACES-2317] - Implement <composite:insertChildren> tag handler > * [MYFACES-2318] - Implement <composite:insertFacet> tag handler > * [MYFACES-2319] - Implement <composite:interface> tag handler > * [MYFACES-2320] - Implement <composite:renderFacet> tag handler > * [MYFACES-2324] - Add ViewDeclarationLanguage.retargetAttachedObjects > and ViewDeclarationLanguage.retargetMethodExpressions > * [MYFACES-2325] - Add Composite Renderer class > * [MYFACES-2331] - Implement Composite Component Attributes ELResolver > (jsf 2.0 spec section 5.6.2.2) and add implicit object "cc" and "component" > * [MYFACES-2362] - Move default validator registration from > UIInput.validateValue to ComponentTagHandlerDelegate > > Bug > > * [MYFACES-2083] - FacesContext contains several unnecessary methods > * [MYFACES-2131] - Import to internal Sun class > * [MYFACES-2146] - Bug in UIViewRoot causes Exception in > popComponentFromEL() > * [MYFACES-2147] - NoSuchMethodException when instantiating SystemEvent > objects > * [MYFACES-2287] - getting the myfaces 1.2 simple example app running on > 2.0 impl > * [MYFACES-2296] - Annotation scanning bugs > * [MYFACES-2357] - currency validation does not fall through to the > default JVM local when a default locale is not specified in faces-config > * [MYFACES-2358] - System event system not working > * [MYFACES-2359] - ComponentSystemEvents are not globally dispatched > * [MYFACES-2360] - Facelets JSTL escapeXML function not escaping '>' > * [MYFACES-2381] - Broken link: "Core JSF-2.0" > * [MYFACES-2384] - @FacesBehavior not handled correctly > * [MYFACES-2386] - Refactor Bean Validation "constants" to > package-private class > * [MYFACES-2387] - component state not being restored when > ValueChangeListener is attached > * [MYFACES-2390] - h:graphic image doesn't handle library attribue > * [MYFACES-2391] - classpath resources not checking for valid version > pattern > * [MYFACES-2393] - graphicImage tag does not handle resource EL > expressions properly > * [MYFACES-2394] - ResourceDependency annotations not being handled > properly if target attribute is set > * [MYFACES-2397] - f:ajax attributes execute and render should take space > delimited clientIds > * [MYFACES-2398] - no spaces in html-output of f:ajax with render and > execute attributes with more than one target > * [MYFACES-2402] - Fix conditional navigation > * [MYFACES-2404] - JspViewDeclarationLanguageStrategy is always the > default strategy, so it should always return true on handles() method > * [MYFACES-2405] - f:ajax renderer not handling multiple IDs properly > * [MYFACES-2406] - Create a view with viewId is null should be possible > * [MYFACES-2408] - UIComponent.subscribeToEvent and unsubscribeToEvent > should throw NullPointerException when eventClass or componentListener is > null > * [MYFACES-2415] - EnumConverter should only conver to String valid enum > values > * [MYFACES-2416] - h:outputLabel does not handle escape property > > Improvement > > * [MYFACES-1910] - Add resetValue() to EditableValueHolder interface > (this is a JSF 2.0 related issue) > * [MYFACES-2010] - Implement JSF 2.0 - Comment in the class > * [MYFACES-2036] - Comment on javax.faces.application.FacesMessage Class > * [MYFACES-2235] - ProjectStage extension > * [MYFACES-2354] - update javax.faces.component classes which utilize the > context classloader to handle java2 security > * [MYFACES-2389] - clean up the UIComponentBase.setParent() > > New Feature > > * [MYFACES-2133] - The implementation of ResourceHandler must be > thread-safe > * [MYFACES-2140] - Add annotation processing logic > * [MYFACES-2162] - Default RenderKitId should be HTML_BASIC when using > annotations > * [MYFACES-2173] - JSF 2.0 AJAX library > * [MYFACES-2372] - h:commandButton should render UIParameter children > > Task > > * [MYFACES-1911] - Implement JSF 2.0 logic at TODO #1 > * [MYFACES-1912] - Implement JSF 2.0 logic at TODO #2 > * [MYFACES-1913] - Implement JSF 2.0 logic at TODO #3 > * [MYFACES-1914] - Implement JSF 2.0 logic at TODO #4 > * [MYFACES-1915] - Implement JSF 2.0 logic at TODO #5 > * [MYFACES-1916] - Implement JSF 2.0 logic at TODO #6 > * [MYFACES-1917] - Implement JSF 2.0 logic at TODO #7 > * [MYFACES-1918] - Implement JSF 2.0 logic at TODO #8 > * [MYFACES-1919] - Implement JSF 2.0 logic at TODO #9 > * [MYFACES-1920] - Implement JSF 2.0 logic at TODO #10 > * [MYFACES-1921] - Implement JSF 2.0 logic at TODO #16 > * [MYFACES-1922] - Implement JSF 2.0 logic at TODO #17 > * [MYFACES-1923] - Implement JSF 2.0 logic at TODO #11 > * [MYFACES-1924] - Implement JSF 2.0 logic at TODO #18 > * [MYFACES-1925] - Implement JSF 2.0 logic at TODO #19 > * [MYFACES-1926] - Implement JSF 2.0 logic at TODO #20 > * [MYFACES-1927] - Implement JSF 2.0 logic at TODO #21 > * [MYFACES-1928] - Implement JSF 2.0 logic at TODO #22 > * [MYFACES-1929] - Implement JSF 2.0 logic at TODO #23 > * [MYFACES-1930] - Implement JSF 2.0 logic at TODO #22 > * [MYFACES-1931] - Implement JSF 2.0 logic at TODO #35 > * [MYFACES-1932] - Implement JSF 2.0 logic at TODO #24 > * [MYFACES-1933] - Implement JSF 2.0 logic at TODO #24 > * [MYFACES-1934] - Implement JSF 2.0 logic at TODO #25 > * [MYFACES-1935] - Implement JSF 2.0 logic at TODO #34 > * [MYFACES-1936] - Implement JSF 2.0 logic at TODO #26 > * [MYFACES-1938] - Implement JSF 2.0 logic at TODO #28 > * [MYFACES-1939] - Implement JSF 2.0 logic at TODO #33 > * [MYFACES-1940] - Implement JSF 2.0 logic at TODO #29 > * [MYFACES-1941] - Implement JSF 2.0 logic at TODO #30 > * [MYFACES-1942] - Implement JSF 2.0 logic at TODO #32 > * [MYFACES-1943] - Implement JSF 2.0 logic at TODO #12 > * [MYFACES-1944] - Implement JSF 2.0 logic at TODO #13 > * [MYFACES-1945] - Implement JSF 2.0 logic at TODO #14 > * [MYFACES-1946] - Implement JSF 2.0 logic at TODO #31 > * [MYFACES-1947] - Implement JSF 2.0 logic at TODO #15 > * [MYFACES-1948] - Implement JSF 2.0 logic at TODO #27 > * [MYFACES-1950] - Implement JSF 2.0 - ExternalContext is missing some > methods > * [MYFACES-1951] - Update UIInput.validate() > * [MYFACES-1958] - Implement AfterAddToParentEvent > * [MYFACES-1959] - Add missing javax.faces.event Classes & Interfaces > * [MYFACES-1968] - Implement JSF 2.0 logic at TODO #35 > * [MYFACES-1969] - Implement JSF 2.0 logic at TODO #36 > * [MYFACES-1970] - Implement JSF 2.0 logic at TODO #37 > * [MYFACES-1971] - Implement JSF 2.0 logic at TODO #38 > * [MYFACES-1972] - Implement JSF 2.0 logic at TODO #39 > * [MYFACES-1973] - Implement JSF 2.0 logic at TODO #40 > * [MYFACES-1974] - Apply Java 5 specific features to the code, mainly > generics and enhanced for > * [MYFACES-1977] - add to FacesServlet.service call to ResourceHandler > and update digester code > * [MYFACES-1978] - Remove org.apache.myfaces.portlet from JSF 2.0 branch, > because it has no use anymore > * [MYFACES-1980] - Implement JSF 2.0 logic at TODO #41 > * [MYFACES-1983] - Implement JSF 2.0 logic at TODO #42 > * [MYFACES-1984] - Implement JSF 2.0 logic at TODO #43 > * [MYFACES-1985] - Implement JSF 2.0 logic at TODO #44 > * [MYFACES-1986] - Implement JSF 2.0 logic at TODO #45 > * [MYFACES-1987] - Implement JSF 2.0 logic at TODO #46 > * [MYFACES-1998] - Implement JSF 2.0 logic at TODO #57 > * [MYFACES-2003] - Implement JSF 2.0 logic at TODO #58 > * [MYFACES-2014] - Implement > ResponseStateManager.getViewState(FacesContext, Object) and update state > saving field on client when ajax response is processed > * [MYFACES-2015] - Implements AJAX lifecycle on UIViewRoot > * [MYFACES-2018] - Implement @ResourceDependency support for setConverter > and addValidator > * [MYFACES-2019] - Implement iterator() on DataModel > * [MYFACES-2020] - Implement changes to RenderKit > * [MYFACES-2021] - Add EDR2 part of error handling to FacesServlet > * [MYFACES-2022] - Add setSubmitted(false) in UIForm.saveState > * [MYFACES-2032] - Implement > javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE config > param > * [MYFACES-2040] - Implement tag c:catch > * [MYFACES-2041] - Implement tag c:choose > * [MYFACES-2042] - Implement tag c:forEach > * [MYFACES-2043] - Implement tag c:if > * [MYFACES-2044] - Implement tag c:otherwise > * [MYFACES-2045] - Implement tag c:set > * [MYFACES-2046] - Implement tag c:when > * [MYFACES-2047] - Implement tag composite:actionSource > * [MYFACES-2048] - Implement tag composite:attribute > * [MYFACES-2049] - Implement tag composite:editableValueHolder > * [MYFACES-2050] - Implement tag composite:facet > * [MYFACES-2051] - Implement tag composite:implementation > * [MYFACES-2052] - Implement tag composite:insertChildren > * [MYFACES-2053] - Implement tag composite:insertFacet > * [MYFACES-2054] - Implement tag composite:interface > * [MYFACES-2055] - Implement tag composite:valueHolder > * [MYFACES-2056] - Implement tag fn:contains() > * [MYFACES-2057] - Implement tag fn:containsIgnoreCase() > * [MYFACES-2058] - Implement tag fn:endsWith() > * [MYFACES-2059] - Implement tag fn:escapeXml() > * [MYFACES-2060] - Implement tag fn:indexOf() > * [MYFACES-2061] - Implement tag fn:join() > * [MYFACES-2062] - Implement tag fn:length() > * [MYFACES-2063] - Implement tag fn:replace() > * [MYFACES-2064] - Implement tag fn:split() > * [MYFACES-2065] - Implement tag fn:startsWith() > * [MYFACES-2066] - Implement tag fn:substring() > * [MYFACES-2067] - Implement tag fn:substringAfter() > * [MYFACES-2068] - Implement tag fn:substringBefore() > * [MYFACES-2069] - Implement tag fn:toLowerCase() > * [MYFACES-2070] - Implement tag fn:toUpperCase() > * [MYFACES-2071] - Implement tag fn:trim() > * [MYFACES-2072] - Implement tag ui:component > * [MYFACES-2073] - Implement tag ui:composition > * [MYFACES-2074] - Implement tag ui:debug > * [MYFACES-2075] - Implement tag ui:decorate > * [MYFACES-2076] - Implement tag ui:define > * [MYFACES-2077] - Implement tag ui:fragment > * [MYFACES-2078] - Implement tag ui:include > * [MYFACES-2079] - Implement tag ui:insert > * [MYFACES-2080] - Implement tag ui:param > * [MYFACES-2081] - Implement tag ui:repeat > * [MYFACES-2085] - Add ApplicationWrapper class > * [MYFACES-2086] - Add DiscoveryHandler class > * [MYFACES-2088] - Add ExceptionHandler class > * [MYFACES-2093] - Add ExceptionEvent class > * [MYFACES-2096] - Make DataModel types generic > * [MYFACES-2098] - Add RegexValidator class > * [MYFACES-2101] - Javadoc update for method Object getFactory(String > factoryName) of FactoryFinder class > * [MYFACES-2102] - Implement JSF 2.0 logic for UIComponent > createComponent(FacesContext context,Resource componentResource) TODO #60 > * [MYFACES-2105] - Implement JSF 2.0 logic for UIComponent > createComponent(final String componentType) > * [MYFACES-2106] - add Exception handler factory to FactoryFinder and > update getFactory method > * [MYFACES-2108] - implement ExceptionHandler contract on myfaces-impl > * [MYFACES-2123] - Add javax.faces.webapp.pdl.facelets.* API classes > * [MYFACES-2125] - Add UIComponent.doTreeTraversal method > * [MYFACES-2136] - UISelectMany > * [MYFACES-2151] - Make test work using shale test (changes in jsf 2.0 > make it fail) > * [MYFACES-2163] - Add RequiredValidator > * [MYFACES-2166] - Some Resources contains ValueExpressions that must be > evaluated > * [MYFACES-2171] - Add Config Ordering feature > * [MYFACES-2178] - Implement IMPL - method addResponseHeader of > ExternalContext > * [MYFACES-2179] - Implement IMPL - method getRequestContentLength of > ExternalContext > * [MYFACES-2180] - Implement IMPL - method getResponseBufferSize of > ExternalContext > * [MYFACES-2181] - Implement IMPL - method getResponseOutputWriter of > ExternalContext > * [MYFACES-2182] - Implement IMPL - method isResponseCommitted of > ExternalContext > * [MYFACES-2184] - Implement IMPL - all TODO methods of ExternalContext > * [MYFACES-2187] - Implement encodeBookmarkableURL and encodeRedirectURL > in ExternalContext > * [MYFACES-2189] - Implement ApplicationImpl TODO's for Behavior > * [MYFACES-2197] - ExceptionQueuedEventContext todos > * [MYFACES-2198] - remaining FacesContext/FacesContextImpl TODOs. > * [MYFACES-2205] - Update UIViewRoot to latest spec draft > * [MYFACES-2215] - Handle RenderKit TODOs for JSF 2.0 > * [MYFACES-2219] - ViewHandler TODOs for JSF 2.0 > * [MYFACES-2220] - FacesConfigurator should scan application config > resources(files on META-INF/) ending with .faces-config.xml > * [MYFACES-2222] - ViewHandler.DEFAULT_SUFFIX could contain several > suffixes > * [MYFACES-2225] - Implement PostAddToViewEvent and > PreRemoveFromViewEvent thrown conditions > * [MYFACES-2226] - Add support for remaining 2.0 faces-config.xml > elements > * [MYFACES-2227] - Update ResponseWriter/ResponseWriterWrapper to latest > spec > * [MYFACES-2228] - Add h:head, h:body, h:outputScript and > h:outputStylesheet renderers > * [MYFACES-2229] - update viewid calculation to new algorithm > * [MYFACES-2230] - FaceletViewDeclarationLanguage TODOs > * [MYFACES-2231] - Handle the TODOs for JSPViewDeclarationLanguage > * [MYFACES-2254] - Finish ExceptionHandler support > * [MYFACES-2255] - Create UIOutcomeTarget API class > * [MYFACES-2258] - Add support for <if> navigation > * [MYFACES-2259] - Implement Partial State Saving feature > * [MYFACES-2262] - implement outcomtarget renderers > * [MYFACES-2263] - Create Composite component EL resolver > * [MYFACES-2264] - Behavior registration > * [MYFACES-2266] - Implement Flash object and EL resolver > * [MYFACES-2267] - handle TODOs for UIComponentBase > * [MYFACES-2268] - Add support for registering client behavior renderers > * [MYFACES-2270] - Add FacesContext param to Application.publishEvent > * [MYFACES-2271] - Call FacesMessage.rendered on message renderers > * [MYFACES-2272] - Apply changes related to UIInput.validateValue and > UIInput.VALIDATE_EMPTY_FIELDS_PARAM_NAME > * [MYFACES-2273] - ClientBehaviorRenderer/ClientbehaviorBase TODOs > * [MYFACES-2274] - Implement UIMessage.isRedisplay and > UIMessages.isRedisplay > * [MYFACES-2275] - UIMessages.getFor (Filter messages of a selected > component) > * [MYFACES-2276] - Update renderers that receive UIParameter to deal with > "disable" param. > * [MYFACES-2277] - UISelectItem.isNoSelectionOption (deal with it on > UISelectOne.validateValue and UISelectMany.validateValue) > * [MYFACES-2278] - Render columns with th instead td, according to > HtmlColumn.isRowHeader > * [MYFACES-2279] - TODOs for javax.faces.application.NavigationCase > * [MYFACES-2280] - ValidatorException should support collections of > messages. > * [MYFACES-2281] - Implement ViewListeners-Events api on UIViewRoot > * [MYFACES-2282] - h:dataTable and h:panelGrid should implement bodyrows > behavior (tbody encapsulation) > * [MYFACES-2283] - Apply selected/unselected css class to > h:selectManyCheckbox > * [MYFACES-2284] - Allow h:outputLink "fragment" property to append text > to url after '#' > * [MYFACES-2285] - Add ExternalContextFactory Implementation > * [MYFACES-2286] - javax.faces.view.facelets TODOs > * [MYFACES-2291] - Components implementing ClientBehaviorHolder should > override getEventNames() and getDefaultEventName() > * [MYFACES-2292] - update NavigationHandlerImpl to extend > ConfigurableNavigationHandler > * [MYFACES-2293] - ui:composition, ui:define and ui:insert component tag > handlers does not work as expected > * [MYFACES-2294] - Sync API with final 2.0 spec > * [MYFACES-2297] - Add TagHandlerDelegateFactory implementation > * [MYFACES-2298] - Apply algorithm described on > javax.faces.view.facelets.ComponentHandler in implementation > * [MYFACES-2299] - Add AttachedObjectHandler implementation when it is > necessary > * [MYFACES-2300] - binding property on facelets tag handlers should be > retrieved from javax.faces.view.facelets.DelegatingMetaTagHandler > * [MYFACES-2302] - Get simple 2.0 app working > * [MYFACES-2304] - Annotate facelets stuff adding @JSFFaceletTag and > @JSFFaceletAttribute to myfaces-builder-plugin > * [MYFACES-2307] - Generate HtmlHead and HtmlBody > * [MYFACES-2309] - Add new attributes to f:selectItems > * [MYFACES-2310] - Implement Composite Component feature > * [MYFACES-2322] - Implement <f:metadata> tag handler > * [MYFACES-2327] - Move facelets test code to myfaces > * [MYFACES-2330] - Get "basic-ajax" 2.0 sample app working > * [MYFACES-2337] - Implement UniqueIdVendor.createUniqueId method and > review all related code to UniqueIdVendor > * [MYFACES-2340] - Get "basic-ezcomp" 2.0 sample working > * [MYFACES-2341] - facelet tag lib parser includes <behavior> section > * [MYFACES-2345] - Add View Parameters feature > * [MYFACES-2349] - h:commandButton allows type="button" on jsf 2.0 > * [MYFACES-2364] - PostRestoreStateEvent should be called from > DefaultRestoreViewSupport.processComponentBinding > * [MYFACES-2365] - DefaultRestoreViewSupport.calculateViewId should not > call ViewHandler.deriveViewId, it should be called later from > ViewHandler.createView and ViewHandler.restoreView > * [MYFACES-2366] - RestoreViewExecutor should check also if the server is > showing an error page when check for postback > * [MYFACES-2367] - FacesContext.isProcessingEvents should be called from > Application.publishEvent > * [MYFACES-2375] - <managed-bean-scope> could also be an EL expression, > to allow easy implementation of new scopes > * [MYFACES-2376] - h:outputScript should force type="text/javascript" > * [MYFACES-2378] - Use java util logging on 2.0.x branch > * [MYFACES-2379] - Create site for core 2.0.x > * [MYFACES-2399] - ManagedBeanResolver does not handle view scope > * [MYFACES-2403] - Myfaces core 2.0 uses jdk 6, but it should be jdk 5 > * [MYFACES-2407] - _ComponentChildrenList does not implement all List > methods > * [MYFACES-2411] - Update api to match latest signature > * [MYFACES-2413] - @ResourceDependency annotations should be scanned when > Application.createConverter(String) and Application.createValidator(String) > is called > * [MYFACES-2414] - ResourceHandlerImpl should scan first with locale > prefix and then without it > * [MYFACES-2419] - NavigationHandler does not deal with no outcome & no > action & no if case > * [MYFACES-2422] - Change package name to org.apache.myfaces.test in > myfaces-test project > * [MYFACES-2424] - c namespace changed to > http://java.sun.com/jsp/jstl/core > > regards > > Leonardo Uribe > -- Best Regards, Delos
short addition: i see your point and ill change that. for now: my previous post contains a list of simple solutions you can use. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2009/11/30 Gerhard Petracek <gerhard.petracek@gmail.com> > hi, > > it's a bit different. > the parameter mentioned by jakob is a jsf 2.0 parameter especially for the > jsr 303 integration. > if you set it to true, the not-null constraint will be interpreted like > required (= true). > extval uses it in an abstract class in a similar way. that means: you just > have to use it to explicitly deactivate the behavior described above. > it's automatically available for custom validation interceptors. an > internal example is the validation interceptor of the bean-validation module > (which allows to use jsr 303 with all jsf versions). > > the property validation module of the next release (as well as the > available milestone) overrides this new default behavior so that an empty > field doesn't lead to a null value for validation (due to backward > compatibility reasons). however, you can easily customize this behavior. > > back to the original question: > > extval just delegates to the (configured) jsf length validator. so > basically the behavior depends on the implementation you are using in your > application. > > in this case the default implementation throws an exception because it > isn't aware of empty values. to change this behavior you can: > - register your custom jsf-length-validator implementation (see: > javax.faces.Length) which handles it as you expect it (that's plain jsf) > or > - replace the default extval validation strategy for @Length to ignore > empty values > or > - implement your custom extval annotation > > all 3 possibilities are quite easy. > > regards, > gerhard > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > > > 2009/11/30 Jakob Korherr <jakob.korherr@gmail.com> > > Hi Markus, >> >> Take a look at the >> javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL >> config parameter in web.xml. >> >> Setting this to true will cause that your property "input" will be null, >> if >> the user submits an empty field and thus @Length will not be processed. >> >> Also take a look at http://jsfatwork.irian.at/semistatic/jsf.html, >> chapter >> 2.12 Validierung fur further information. It's written in german, but I >> assume you're from Germany... >> >> Regards >> >> Jakob Korherr >> >> >> 2009/11/30 Dreher, Markus <M.Dreher@dzbw.de> >> >> > Hi all, >> > >> > i want to validate a field only when the user filled it out. >> > >> > It's not a reuqired field, but when it is filled out, the input should >> > be at least for example 3 digits. >> > >> > @Length(minimum=3, maximum = 60) >> > private String input; >> > >> > With @Length this leads to a required field. >> > >> > Do i miss something? >> > >> > Regards, >> > >> > Markus >> > >> > >> > >> > >
Greetings!!! I'm working on a JSF web app using tomahawk 1.1.9 but now I want to implement Sandbox to use the inputSuggestAjax tag. Actually I'm using JDeveloper 10.3.3.1 but after adding the tomahawk-sandbox-1.1.9-SNAPSHOT.jar to the project's library the app doesn't run. How can I solve this issue? Thanks for your help.
The Apache MyFaces team is pleased to announce the release of MyFaces
Core 2.0.0-alpha.
MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified
by JSR-314.
MyFaces Core 2.0.0-alpha is available in both binary and source
distributions.
* http://myfaces.apache.org/download.html
MyFaces Core is also available in the central Maven repository under
Group ID "org.apache.myfaces.core".
Release Notes - MyFaces Core - Version 2.0.0-alpha
Sub-task
* [MYFACES-2174] - MyFaces 2.0 AJAX API extension proposal
* [MYFACES-2191] - Move the myfaces params into the context
* [MYFACES-2195] - rename xhrcore_xxx to xhrcore._xxx
* [MYFACES-2200] - Send events and errors at the various xhr stages
* [MYFACES-2223] - switch viewstate replacement from id to name
* [MYFACES-2238] - offer extension point for AJAX Javascript
* [MYFACES-2240] - typo in javascript build script and target folder
doesn't fit the spec
* [MYFACES-2257] - trigger external scripts after AJAX reload
* [MYFACES-2311] - Implement <composite:actionSource> tag handler
* [MYFACES-2312] - Implement <composite:attribute> tag handler
* [MYFACES-2313] - Implement <composite:editableValueHolder> tag handler
* [MYFACES-2314] - Implement <composite:extension> tag handler
* [MYFACES-2315] - Implement <composite:facet> tag handler
* [MYFACES-2316] - Implement <composite:implementation> tag handler
* [MYFACES-2317] - Implement <composite:insertChildren> tag handler
* [MYFACES-2318] - Implement <composite:insertFacet> tag handler
* [MYFACES-2319] - Implement <composite:interface> tag handler
* [MYFACES-2320] - Implement <composite:renderFacet> tag handler
* [MYFACES-2324] - Add
ViewDeclarationLanguage.retargetAttachedObjects and
ViewDeclarationLanguage.retargetMethodExpressions
* [MYFACES-2325] - Add Composite Renderer class
* [MYFACES-2331] - Implement Composite Component Attributes
ELResolver (jsf 2.0 spec section 5.6.2.2) and add implicit object "cc"
and "component"
* [MYFACES-2362] - Move default validator registration from
UIInput.validateValue to ComponentTagHandlerDelegate
Bug
* [MYFACES-2083] - FacesContext contains several unnecessary methods
* [MYFACES-2131] - Import to internal Sun class
* [MYFACES-2146] - Bug in UIViewRoot causes Exception in
popComponentFromEL()
* [MYFACES-2147] - NoSuchMethodException when instantiating
SystemEvent objects
* [MYFACES-2287] - getting the myfaces 1.2 simple example app
running on 2.0 impl
* [MYFACES-2296] - Annotation scanning bugs
* [MYFACES-2357] - currency validation does not fall through to the
default JVM local when a default locale is not specified in faces-config
* [MYFACES-2358] - System event system not working
* [MYFACES-2359] - ComponentSystemEvents are not globally dispatched
* [MYFACES-2360] - Facelets JSTL escapeXML function not escaping '>'
* [MYFACES-2381] - Broken link: "Core JSF-2.0"
* [MYFACES-2384] - @FacesBehavior not handled correctly
* [MYFACES-2386] - Refactor Bean Validation "constants" to
package-private class
* [MYFACES-2387] - component state not being restored when
ValueChangeListener is attached
* [MYFACES-2390] - h:graphic image doesn't handle library attribue
* [MYFACES-2391] - classpath resources not checking for valid
version pattern
* [MYFACES-2393] - graphicImage tag does not handle resource EL
expressions properly
* [MYFACES-2394] - ResourceDependency annotations not being handled
properly if target attribute is set
* [MYFACES-2397] - f:ajax attributes execute and render should take
space delimited clientIds
* [MYFACES-2398] - no spaces in html-output of f:ajax with render
and execute attributes with more than one target
* [MYFACES-2402] - Fix conditional navigation
* [MYFACES-2404] - JspViewDeclarationLanguageStrategy is always the
default strategy, so it should always return true on handles() method
* [MYFACES-2405] - f:ajax renderer not handling multiple IDs properly
* [MYFACES-2406] - Create a view with viewId is null should be possible
* [MYFACES-2408] - UIComponent.subscribeToEvent and
unsubscribeToEvent should throw NullPointerException when eventClass or
componentListener is null
* [MYFACES-2415] - EnumConverter should only conver to String valid
enum values
* [MYFACES-2416] - h:outputLabel does not handle escape property
Improvement
* [MYFACES-1910] - Add resetValue() to EditableValueHolder interface
(this is a JSF 2.0 related issue)
* [MYFACES-2010] - Implement JSF 2.0 - Comment in the class
* [MYFACES-2036] - Comment on javax.faces.application.FacesMessage Class
* [MYFACES-2235] - ProjectStage extension
* [MYFACES-2354] - update javax.faces.component classes which
utilize the context classloader to handle java2 security
* [MYFACES-2389] - clean up the UIComponentBase.setParent()
New Feature
* [MYFACES-2133] - The implementation of ResourceHandler must be
thread-safe
* [MYFACES-2140] - Add annotation processing logic
* [MYFACES-2162] - Default RenderKitId should be HTML_BASIC when
using annotations
* [MYFACES-2173] - JSF 2.0 AJAX library
* [MYFACES-2372] - h:commandButton should render UIParameter children
Task
* [MYFACES-1911] - Implement JSF 2.0 logic at TODO #1
* [MYFACES-1912] - Implement JSF 2.0 logic at TODO #2
* [MYFACES-1913] - Implement JSF 2.0 logic at TODO #3
* [MYFACES-1914] - Implement JSF 2.0 logic at TODO #4
* [MYFACES-1915] - Implement JSF 2.0 logic at TODO #5
* [MYFACES-1916] - Implement JSF 2.0 logic at TODO #6
* [MYFACES-1917] - Implement JSF 2.0 logic at TODO #7
* [MYFACES-1918] - Implement JSF 2.0 logic at TODO #8
* [MYFACES-1919] - Implement JSF 2.0 logic at TODO #9
* [MYFACES-1920] - Implement JSF 2.0 logic at TODO #10
* [MYFACES-1921] - Implement JSF 2.0 logic at TODO #16
* [MYFACES-1922] - Implement JSF 2.0 logic at TODO #17
* [MYFACES-1923] - Implement JSF 2.0 logic at TODO #11
* [MYFACES-1924] - Implement JSF 2.0 logic at TODO #18
* [MYFACES-1925] - Implement JSF 2.0 logic at TODO #19
* [MYFACES-1926] - Implement JSF 2.0 logic at TODO #20
* [MYFACES-1927] - Implement JSF 2.0 logic at TODO #21
* [MYFACES-1928] - Implement JSF 2.0 logic at TODO #22
* [MYFACES-1929] - Implement JSF 2.0 logic at TODO #23
* [MYFACES-1930] - Implement JSF 2.0 logic at TODO #22
* [MYFACES-1931] - Implement JSF 2.0 logic at TODO #35
* [MYFACES-1932] - Implement JSF 2.0 logic at TODO #24
* [MYFACES-1933] - Implement JSF 2.0 logic at TODO #24
* [MYFACES-1934] - Implement JSF 2.0 logic at TODO #25
* [MYFACES-1935] - Implement JSF 2.0 logic at TODO #34
* [MYFACES-1936] - Implement JSF 2.0 logic at TODO #26
* [MYFACES-1938] - Implement JSF 2.0 logic at TODO #28
* [MYFACES-1939] - Implement JSF 2.0 logic at TODO #33
* [MYFACES-1940] - Implement JSF 2.0 logic at TODO #29
* [MYFACES-1941] - Implement JSF 2.0 logic at TODO #30
* [MYFACES-1942] - Implement JSF 2.0 logic at TODO #32
* [MYFACES-1943] - Implement JSF 2.0 logic at TODO #12
* [MYFACES-1944] - Implement JSF 2.0 logic at TODO #13
* [MYFACES-1945] - Implement JSF 2.0 logic at TODO #14
* [MYFACES-1946] - Implement JSF 2.0 logic at TODO #31
* [MYFACES-1947] - Implement JSF 2.0 logic at TODO #15
* [MYFACES-1948] - Implement JSF 2.0 logic at TODO #27
* [MYFACES-1950] - Implement JSF 2.0 - ExternalContext is missing
some methods
* [MYFACES-1951] - Update UIInput.validate()
* [MYFACES-1958] - Implement AfterAddToParentEvent
* [MYFACES-1959] - Add missing javax.faces.event Classes & Interfaces
* [MYFACES-1968] - Implement JSF 2.0 logic at TODO #35
* [MYFACES-1969] - Implement JSF 2.0 logic at TODO #36
* [MYFACES-1970] - Implement JSF 2.0 logic at TODO #37
* [MYFACES-1971] - Implement JSF 2.0 logic at TODO #38
* [MYFACES-1972] - Implement JSF 2.0 logic at TODO #39
* [MYFACES-1973] - Implement JSF 2.0 logic at TODO #40
* [MYFACES-1974] - Apply Java 5 specific features to the code,
mainly generics and enhanced for
* [MYFACES-1977] - add to FacesServlet.service call to
ResourceHandler and update digester code
* [MYFACES-1978] - Remove org.apache.myfaces.portlet from JSF 2.0
branch, because it has no use anymore
* [MYFACES-1980] - Implement JSF 2.0 logic at TODO #41
* [MYFACES-1983] - Implement JSF 2.0 logic at TODO #42
* [MYFACES-1984] - Implement JSF 2.0 logic at TODO #43
* [MYFACES-1985] - Implement JSF 2.0 logic at TODO #44
* [MYFACES-1986] - Implement JSF 2.0 logic at TODO #45
* [MYFACES-1987] - Implement JSF 2.0 logic at TODO #46
* [MYFACES-1998] - Implement JSF 2.0 logic at TODO #57
* [MYFACES-2003] - Implement JSF 2.0 logic at TODO #58
* [MYFACES-2014] - Implement
ResponseStateManager.getViewState(FacesContext, Object) and update state
saving field on client when ajax response is processed
* [MYFACES-2015] - Implements AJAX lifecycle on UIViewRoot
* [MYFACES-2018] - Implement @ResourceDependency support for
setConverter and addValidator
* [MYFACES-2019] - Implement iterator() on DataModel
* [MYFACES-2020] - Implement changes to RenderKit
* [MYFACES-2021] - Add EDR2 part of error handling to FacesServlet
* [MYFACES-2022] - Add setSubmitted(false) in UIForm.saveState
* [MYFACES-2032] - Implement
javax.faces.DATETIMECONVERTER_DEFAULT_TIMEZONE_IS_SYSTEM_TIMEZONE config
param
* [MYFACES-2040] - Implement tag c:catch
* [MYFACES-2041] - Implement tag c:choose
* [MYFACES-2042] - Implement tag c:forEach
* [MYFACES-2043] - Implement tag c:if
* [MYFACES-2044] - Implement tag c:otherwise
* [MYFACES-2045] - Implement tag c:set
* [MYFACES-2046] - Implement tag c:when
* [MYFACES-2047] - Implement tag composite:actionSource
* [MYFACES-2048] - Implement tag composite:attribute
* [MYFACES-2049] - Implement tag composite:editableValueHolder
* [MYFACES-2050] - Implement tag composite:facet
* [MYFACES-2051] - Implement tag composite:implementation
* [MYFACES-2052] - Implement tag composite:insertChildren
* [MYFACES-2053] - Implement tag composite:insertFacet
* [MYFACES-2054] - Implement tag composite:interface
* [MYFACES-2055] - Implement tag composite:valueHolder
* [MYFACES-2056] - Implement tag fn:contains()
* [MYFACES-2057] - Implement tag fn:containsIgnoreCase()
* [MYFACES-2058] - Implement tag fn:endsWith()
* [MYFACES-2059] - Implement tag fn:escapeXml()
* [MYFACES-2060] - Implement tag fn:indexOf()
* [MYFACES-2061] - Implement tag fn:join()
* [MYFACES-2062] - Implement tag fn:length()
* [MYFACES-2063] - Implement tag fn:replace()
* [MYFACES-2064] - Implement tag fn:split()
* [MYFACES-2065] - Implement tag fn:startsWith()
* [MYFACES-2066] - Implement tag fn:substring()
* [MYFACES-2067] - Implement tag fn:substringAfter()
* [MYFACES-2068] - Implement tag fn:substringBefore()
* [MYFACES-2069] - Implement tag fn:toLowerCase()
* [MYFACES-2070] - Implement tag fn:toUpperCase()
* [MYFACES-2071] - Implement tag fn:trim()
* [MYFACES-2072] - Implement tag ui:component
* [MYFACES-2073] - Implement tag ui:composition
* [MYFACES-2074] - Implement tag ui:debug
* [MYFACES-2075] - Implement tag ui:decorate
* [MYFACES-2076] - Implement tag ui:define
* [MYFACES-2077] - Implement tag ui:fragment
* [MYFACES-2078] - Implement tag ui:include
* [MYFACES-2079] - Implement tag ui:insert
* [MYFACES-2080] - Implement tag ui:param
* [MYFACES-2081] - Implement tag ui:repeat
* [MYFACES-2085] - Add ApplicationWrapper class
* [MYFACES-2086] - Add DiscoveryHandler class
* [MYFACES-2088] - Add ExceptionHandler class
* [MYFACES-2093] - Add ExceptionEvent class
* [MYFACES-2096] - Make DataModel types generic
* [MYFACES-2098] - Add RegexValidator class
* [MYFACES-2101] - Javadoc update for method Object
getFactory(String factoryName) of FactoryFinder class
* [MYFACES-2102] - Implement JSF 2.0 logic for UIComponent
createComponent(FacesContext context,Resource componentResource) TODO #60
* [MYFACES-2105] - Implement JSF 2.0 logic for UIComponent
createComponent(final String componentType)
* [MYFACES-2106] - add Exception handler factory to FactoryFinder
and update getFactory method
* [MYFACES-2108] - implement ExceptionHandler contract on myfaces-impl
* [MYFACES-2123] - Add javax.faces.webapp.pdl.facelets.* API classes
* [MYFACES-2125] - Add UIComponent.doTreeTraversal method
* [MYFACES-2136] - UISelectMany
* [MYFACES-2151] - Make test work using shale test (changes in jsf
2.0 make it fail)
* [MYFACES-2163] - Add RequiredValidator
* [MYFACES-2166] - Some Resources contains ValueExpressions that
must be evaluated
* [MYFACES-2171] - Add Config Ordering feature
* [MYFACES-2178] - Implement IMPL - method addResponseHeader of
ExternalContext
* [MYFACES-2179] - Implement IMPL - method getRequestContentLength
of ExternalContext
* [MYFACES-2180] - Implement IMPL - method getResponseBufferSize of
ExternalContext
* [MYFACES-2181] - Implement IMPL - method getResponseOutputWriter
of ExternalContext
* [MYFACES-2182] - Implement IMPL - method isResponseCommitted of
ExternalContext
* [MYFACES-2184] - Implement IMPL - all TODO methods of ExternalContext
* [MYFACES-2187] - Implement encodeBookmarkableURL and
encodeRedirectURL in ExternalContext
* [MYFACES-2189] - Implement ApplicationImpl TODO's for Behavior
* [MYFACES-2197] - ExceptionQueuedEventContext todos
* [MYFACES-2198] - remaining FacesContext/FacesContextImpl TODOs.
* [MYFACES-2205] - Update UIViewRoot to latest spec draft
* [MYFACES-2215] - Handle RenderKit TODOs for JSF 2.0
* [MYFACES-2219] - ViewHandler TODOs for JSF 2.0
* [MYFACES-2220] - FacesConfigurator should scan application config
resources(files on META-INF/) ending with .faces-config.xml
* [MYFACES-2222] - ViewHandler.DEFAULT_SUFFIX could contain several
suffixes
* [MYFACES-2225] - Implement PostAddToViewEvent and
PreRemoveFromViewEvent thrown conditions
* [MYFACES-2226] - Add support for remaining 2.0 faces-config.xml
elements
* [MYFACES-2227] - Update ResponseWriter/ResponseWriterWrapper to
latest spec
* [MYFACES-2228] - Add h:head, h:body, h:outputScript and
h:outputStylesheet renderers
* [MYFACES-2229] - update viewid calculation to new algorithm
* [MYFACES-2230] - FaceletViewDeclarationLanguage TODOs
* [MYFACES-2231] - Handle the TODOs for JSPViewDeclarationLanguage
* [MYFACES-2254] - Finish ExceptionHandler support
* [MYFACES-2255] - Create UIOutcomeTarget API class
* [MYFACES-2258] - Add support for <if> navigation
* [MYFACES-2259] - Implement Partial State Saving feature
* [MYFACES-2262] - implement outcomtarget renderers
* [MYFACES-2263] - Create Composite component EL resolver
* [MYFACES-2264] - Behavior registration
* [MYFACES-2266] - Implement Flash object and EL resolver
* [MYFACES-2267] - handle TODOs for UIComponentBase
* [MYFACES-2268] - Add support for registering client behavior renderers
* [MYFACES-2270] - Add FacesContext param to Application.publishEvent
* [MYFACES-2271] - Call FacesMessage.rendered on message renderers
* [MYFACES-2272] - Apply changes related to UIInput.validateValue
and UIInput.VALIDATE_EMPTY_FIELDS_PARAM_NAME
* [MYFACES-2273] - ClientBehaviorRenderer/ClientbehaviorBase TODOs
* [MYFACES-2274] - Implement UIMessage.isRedisplay and
UIMessages.isRedisplay
* [MYFACES-2275] - UIMessages.getFor (Filter messages of a selected
component)
* [MYFACES-2276] - Update renderers that receive UIParameter to deal
with "disable" param.
* [MYFACES-2277] - UISelectItem.isNoSelectionOption (deal with it on
UISelectOne.validateValue and UISelectMany.validateValue)
* [MYFACES-2278] - Render columns with th instead td, according to
HtmlColumn.isRowHeader
* [MYFACES-2279] - TODOs for javax.faces.application.NavigationCase
* [MYFACES-2280] - ValidatorException should support collections of
messages.
* [MYFACES-2281] - Implement ViewListeners-Events api on UIViewRoot
* [MYFACES-2282] - h:dataTable and h:panelGrid should implement
bodyrows behavior (tbody encapsulation)
* [MYFACES-2283] - Apply selected/unselected css class to
h:selectManyCheckbox
* [MYFACES-2284] - Allow h:outputLink "fragment" property to append
text to url after '#'
* [MYFACES-2285] - Add ExternalContextFactory Implementation
* [MYFACES-2286] - javax.faces.view.facelets TODOs
* [MYFACES-2291] - Components implementing ClientBehaviorHolder
should override getEventNames() and getDefaultEventName()
* [MYFACES-2292] - update NavigationHandlerImpl to extend
ConfigurableNavigationHandler
* [MYFACES-2293] - ui:composition, ui:define and ui:insert component
tag handlers does not work as expected
* [MYFACES-2294] - Sync API with final 2.0 spec
* [MYFACES-2297] - Add TagHandlerDelegateFactory implementation
* [MYFACES-2298] - Apply algorithm described on
javax.faces.view.facelets.ComponentHandler in implementation
* [MYFACES-2299] - Add AttachedObjectHandler implementation when it
is necessary
* [MYFACES-2300] - binding property on facelets tag handlers should
be retrieved from javax.faces.view.facelets.DelegatingMetaTagHandler
* [MYFACES-2302] - Get simple 2.0 app working
* [MYFACES-2304] - Annotate facelets stuff adding @JSFFaceletTag and
@JSFFaceletAttribute to myfaces-builder-plugin
* [MYFACES-2307] - Generate HtmlHead and HtmlBody
* [MYFACES-2309] - Add new attributes to f:selectItems
* [MYFACES-2310] - Implement Composite Component feature
* [MYFACES-2322] - Implement <f:metadata> tag handler
* [MYFACES-2327] - Move facelets test code to myfaces
* [MYFACES-2330] - Get "basic-ajax" 2.0 sample app working
* [MYFACES-2337] - Implement UniqueIdVendor.createUniqueId method
and review all related code to UniqueIdVendor
* [MYFACES-2340] - Get "basic-ezcomp" 2.0 sample working
* [MYFACES-2341] - facelet tag lib parser includes <behavior> section
* [MYFACES-2345] - Add View Parameters feature
* [MYFACES-2349] - h:commandButton allows type="button" on jsf 2.0
* [MYFACES-2364] - PostRestoreStateEvent should be called from
DefaultRestoreViewSupport.processComponentBinding
* [MYFACES-2365] - DefaultRestoreViewSupport.calculateViewId should
not call ViewHandler.deriveViewId, it should be called later from
ViewHandler.createView and ViewHandler.restoreView
* [MYFACES-2366] - RestoreViewExecutor should check also if the
server is showing an error page when check for postback
* [MYFACES-2367] - FacesContext.isProcessingEvents should be called
from Application.publishEvent
* [MYFACES-2375] - <managed-bean-scope> could also be an EL
expression, to allow easy implementation of new scopes
* [MYFACES-2376] - h:outputScript should force type="text/javascript"
* [MYFACES-2378] - Use java util logging on 2.0.x branch
* [MYFACES-2379] - Create site for core 2.0.x
* [MYFACES-2399] - ManagedBeanResolver does not handle view scope
* [MYFACES-2403] - Myfaces core 2.0 uses jdk 6, but it should be jdk 5
* [MYFACES-2407] - _ComponentChildrenList does not implement all
List methods
* [MYFACES-2411] - Update api to match latest signature
* [MYFACES-2413] - @ResourceDependency annotations should be scanned
when Application.createConverter(String) and
Application.createValidator(String) is called
* [MYFACES-2414] - ResourceHandlerImpl should scan first with locale
prefix and then without it
* [MYFACES-2419] - NavigationHandler does not deal with no outcome &
no action & no if case
* [MYFACES-2422] - Change package name to org.apache.myfaces.test in
myfaces-test project
* [MYFACES-2424] - c namespace changed to
http://java.sun.com/jsp/jstl/core
regards
Leonardo Uribe
hi, it's a bit different. the parameter mentioned by jakob is a jsf 2.0 parameter especially for the jsr 303 integration. if you set it to true, the not-null constraint will be interpreted like required (= true). extval uses it in an abstract class in a similar way. that means: you just have to use it to explicitly deactivate the behavior described above. it's automatically available for custom validation interceptors. an internal example is the validation interceptor of the bean-validation module (which allows to use jsr 303 with all jsf versions). the property validation module of the next release (as well as the available milestone) overrides this new default behavior so that an empty field doesn't lead to a null value for validation (due to backward compatibility reasons). however, you can easily customize this behavior. back to the original question: extval just delegates to the (configured) jsf length validator. so basically the behavior depends on the implementation you are using in your application. in this case the default implementation throws an exception because it isn't aware of empty values. to change this behavior you can: - register your custom jsf-length-validator implementation (see: javax.faces.Length) which handles it as you expect it (that's plain jsf) or - replace the default extval validation strategy for @Length to ignore empty values or - implement your custom extval annotation all 3 possibilities are quite easy. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2009/11/30 Jakob Korherr <jakob.korherr@gmail.com> > Hi Markus, > > Take a look at the > javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL > config parameter in web.xml. > > Setting this to true will cause that your property "input" will be null, if > the user submits an empty field and thus @Length will not be processed. > > Also take a look at http://jsfatwork.irian.at/semistatic/jsf.html, chapter > 2.12 Validierung fur further information. It's written in german, but I > assume you're from Germany... > > Regards > > Jakob Korherr > > > 2009/11/30 Dreher, Markus <M.Dreher@dzbw.de> > > > Hi all, > > > > i want to validate a field only when the user filled it out. > > > > It's not a reuqired field, but when it is filled out, the input should > > be at least for example 3 digits. > > > > @Length(minimum=3, maximum = 60) > > private String input; > > > > With @Length this leads to a required field. > > > > Do i miss something? > > > > Regards, > > > > Markus > > > > > > >
In the trinidad-demo, check out the suede.css file. It renders the train
nicely.
I copied this from the file:
/*train */
af|train::stop:selected-icon {
content:url('/skins/suede/images/trVisStop.png');
}
af|train::join:unvisited,
af|train::join:disabled,
af|train::join-overflow {
background-image:url('/skins/suede/images/ctruj.gif');
}
af|train::stop:unvisited-icon {
content:url('/skins/suede/images/trUnVisStop.png');
}
af|train::link {
-tr-rule-ref:selector(".AFDefaultFont:alias");
padding:0px 4px;
}
af|train::stop-content:selected a,
af|train::stop-content:read-only a,
af|train::overflow-end a {
-tr-rule-ref:selector(".TextForegroundDarkBackground:alias");
}
af|train::overflow-end:unvisited-icon {
content:url('/skins/suede/images/ctrumore.gif');
}
af|train {
-tr-render-parent-train:true
}
af|train::join:Visited,
af|train::join-overflow:Visited {
background-image:url('/skins/suede/images/trvj.gif');
}
af|train::stop:visited-icon {
content:url('/skins/suede/images/trVisStopA.png');
}
af|train::overflow-end:visited-icon {
content:url('/skins/suede/images/trvmore.gif');
}
af|train::overflow-start:visited-icon {
content:url('/skins/suede/images/trprev.gif');
}
af|train::parent-start-icon {
content:url('/skins/suede/images/trsubl.gif');
}
af|train::parent-end-icon {
content:url('/skins/suede/images/trsubr.gif');
}
/*train */
Paul Spencer wrote, On 11/19/2009 8:25 AM PT:
> I am using <tr:train> in Trinidad v1.2.12. Per the documentation [1],
> the selector af|train::join defines the style between stop icons.
> Using the selector below, the appearance is different on Safari vs
> other browser, although none of the browsers display the expected
> result. The differences are either the join image is NOT displayed,
> or it is displayed to many times.
>
> Safari 4.0.4 - Displays the image 4 time between stations, with the
> middle two are stacked so the four dashes look like "-=-".
>
> IE7, IE6, Firefox 3.5.5(Mac), Firefox 3.0.7 (Windows), Nokia E61i
> browser - The join image is not displayed.
>
> I expected to see the following for a train with three stations.
>
> -selected----unvisited----unvisited-
>
> ***
> * From the Style Sheet
> ***
> af|train::stop {
> text-align: center;
> }
>
> af|train::join {
> content: url("/adf/images/tree-line-middle.gif");
> }
> af|train::stop-icon-cell {
> background-color: blue;
> }
>
> af|train::stop:selected-icon {
> content:"selected";
> }
>
> af|train::stop:unvisited-icon {
> content: "unvisited" ;
> }
>
> af|train::stop:visited-icon {
> content: "visted");
> }
>
> af|train::stop:read-only-icon {
> content: "read-only");
> }
>
>
> Paul Spencer
>
> [1] http://myfaces.apache.org/trinidad/skin-selectors.html
>
I am using the Tomahawk set of tags for this project. I need a pop to confirm the deletion of a record. There doesn't seem to be any concept of a popup in JSF or Tomahawk. I can use a basic javascript cofirm popup and functionaly it works perfect but the color scheme doesn't match my application and it doesn't look good. Just wondering what everyone else does to confirm a delete? Pat
Hi Markus, Take a look at the javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL config parameter in web.xml. Setting this to true will cause that your property "input" will be null, if the user submits an empty field and thus @Length will not be processed. Also take a look at http://jsfatwork.irian.at/semistatic/jsf.html, chapter 2.12 Validierung fur further information. It's written in german, but I assume you're from Germany... Regards Jakob Korherr 2009/11/30 Dreher, Markus <M.Dreher@dzbw.de> > Hi all, > > i want to validate a field only when the user filled it out. > > It's not a reuqired field, but when it is filled out, the input should > be at least for example 3 digits. > > @Length(minimum=3, maximum = 60) > private String input; > > With @Length this leads to a required field. > > Do i miss something? > > Regards, > > Markus > > >
Hi all,
i want to validate a field only when the user filled it out.
It's not a reuqired field, but when it is filled out, the input should
be at least for example 3 digits.
@Length(minimum=3, maximum = 60)
private String input;
With @Length this leads to a required field.
Do i miss something?
Regards,
Markus
Hi Markus, I wrote a small HTML file to test if the javascript events are triggered correctly in the mentioned browsers, and they are. So it is not a javascript event problem, but a trinidad (javascript) problem. Unfortunately I am not that familiar with trinidad to determine why this does not function properly, but I hope there is someone at the list, who can help you. Regards Jakob Korherr 2009/11/26 Döring Markus <Markus.Doering@tcc-products.de> > Hi, > > have done some more test's: > > FireFox 3.5.5: as described below > Internet Explorer 7: same as FireFox > Opera 9.51: works correctly with both ValueChangeEvents in one Request, but > don't fires a ValueChangeEvent at all if only the InputText changes > Opera 10.10: same as 9.51 > Google Chrome 3.0.195.33: same as FireFox and IE7 > Apple Safari 3.1.1: same as Firefox, IE7 and Chrome > > Regards > Markus > > -----Ursprüngliche Nachricht----- > Von: sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] Im > Auftrag von Jakob Korherr > Gesendet: Donnerstag, 26. November 2009 10:46 > An: MyFaces Discussion > Betreff: Re: [Trinidad] ValueChangeListener issues > > Hi Markus, > > It would be great to know in which browsers you tested this, because it > looks like a javascript error to me. > > Regards > > Jakob Korherr > > 2009/11/26 Döring Markus <Markus.Doering@tcc-products.de> > > > Hi list, > > > > > > > > I have found an issue with “multiple” value change events in one request. > > > > I have a simple test setup: > > > > One page with just a form, an InputText and an SelectBooleanCheckbox (see > > file attached). > > > > Both inputs save their value in a HashMap in session (could also be a > > managed bean but so less test code is needed). > > > > Both inputs have a ValueChangeListener and autoSubmit on true. > > > > > > > > The InputText auto submits when it loose focus. > > > > The SelectBooleanCheckbox auto submits when it’s get clicked. > > > > But if I enter the page, enter some text and immediate click on the > > checkbox without leaving the InputText before clicking only the text in > the > > InputText is submitted and only the InputText ValueChangeListener is > called. > > > > The SelectBooleanCheckbox “looks” like checked, but if I reload the page > > (without fire event, clicking button, ect.) the SelectBooleanCheckbox > get’s > > deselected automatically because the value in the session never changed. > > > > > > > > Any idea how to get around this? > > > > Should I fill a Jira? > > > > > > > > Tested with > > > > jsf-facelets 1.1.13 > > > > myfaces 1.1.5 > > > > trinidad 1.0.11 > > > > > > > > (Sorry have not test setup for JSF 1.2 so can’t test with Trinidad 1.2, > but > > the test setup is straight forward) > > > > > > > > Regards > > > > Markus > > > > > > >
Hi, have done some more test's: FireFox 3.5.5: as described below Internet Explorer 7: same as FireFox Opera 9.51: works correctly with both ValueChangeEvents in one Request, but don't fires a ValueChangeEvent at all if only the InputText changes Opera 10.10: same as 9.51 Google Chrome 3.0.195.33: same as FireFox and IE7 Apple Safari 3.1.1: same as Firefox, IE7 and Chrome Regards Markus -----Ursprüngliche Nachricht----- Von: sethfromaustria@gmail.com [mailto:sethfromaustria@gmail.com] Im Auftrag von Jakob Korherr Gesendet: Donnerstag, 26. November 2009 10:46 An: MyFaces Discussion Betreff: Re: [Trinidad] ValueChangeListener issues Hi Markus, It would be great to know in which browsers you tested this, because it looks like a javascript error to me. Regards Jakob Korherr 2009/11/26 Döring Markus <Markus.Doering@tcc-products.de> > Hi list, > > > > I have found an issue with “multiple” value change events in one request. > > I have a simple test setup: > > One page with just a form, an InputText and an SelectBooleanCheckbox (see > file attached). > > Both inputs save their value in a HashMap in session (could also be a > managed bean but so less test code is needed). > > Both inputs have a ValueChangeListener and autoSubmit on true. > > > > The InputText auto submits when it loose focus. > > The SelectBooleanCheckbox auto submits when it’s get clicked. > > But if I enter the page, enter some text and immediate click on the > checkbox without leaving the InputText before clicking only the text in the > InputText is submitted and only the InputText ValueChangeListener is called. > > The SelectBooleanCheckbox “looks” like checked, but if I reload the page > (without fire event, clicking button, ect.) the SelectBooleanCheckbox get’s > deselected automatically because the value in the session never changed. > > > > Any idea how to get around this? > > Should I fill a Jira? > > > > Tested with > > jsf-facelets 1.1.13 > > myfaces 1.1.5 > > trinidad 1.0.11 > > > > (Sorry have not test setup for JSF 1.2 so can’t test with Trinidad 1.2, but > the test setup is straight forward) > > > > Regards > > Markus > > >
Hi Markus, It would be great to know in which browsers you tested this, because it looks like a javascript error to me. Regards Jakob Korherr 2009/11/26 Döring Markus <Markus.Doering@tcc-products.de> > Hi list, > > > > I have found an issue with “multiple” value change events in one request. > > I have a simple test setup: > > One page with just a form, an InputText and an SelectBooleanCheckbox (see > file attached). > > Both inputs save their value in a HashMap in session (could also be a > managed bean but so less test code is needed). > > Both inputs have a ValueChangeListener and autoSubmit on true. > > > > The InputText auto submits when it loose focus. > > The SelectBooleanCheckbox auto submits when it’s get clicked. > > But if I enter the page, enter some text and immediate click on the > checkbox without leaving the InputText before clicking only the text in the > InputText is submitted and only the InputText ValueChangeListener is called. > > The SelectBooleanCheckbox “looks” like checked, but if I reload the page > (without fire event, clicking button, ect.) the SelectBooleanCheckbox get’s > deselected automatically because the value in the session never changed. > > > > Any idea how to get around this? > > Should I fill a Jira? > > > > Tested with > > jsf-facelets 1.1.13 > > myfaces 1.1.5 > > trinidad 1.0.11 > > > > (Sorry have not test setup for JSF 1.2 so can’t test with Trinidad 1.2, but > the test setup is straight forward) > > > > Regards > > Markus > > >
Hi list, I have found an issue with "multiple" value change events in one request. I have a simple test setup: One page with just a form, an InputText and an SelectBooleanCheckbox (see file attached). Both inputs save their value in a HashMap in session (could also be a managed bean but so less test code is needed). Both inputs have a ValueChangeListener and autoSubmit on true. The InputText auto submits when it loose focus. The SelectBooleanCheckbox auto submits when it's get clicked. But if I enter the page, enter some text and immediate click on the checkbox without leaving the InputText before clicking only the text in the InputText is submitted and only the InputText ValueChangeListener is called. The SelectBooleanCheckbox "looks" like checked, but if I reload the page (without fire event, clicking button, ect.) the SelectBooleanCheckbox get's deselected automatically because the value in the session never changed. Any idea how to get around this? Should I fill a Jira? Tested with jsf-facelets 1.1.13 myfaces 1.1.5 trinidad 1.0.11 (Sorry have not test setup for JSF 1.2 so can't test with Trinidad 1.2, but the test setup is straight forward) Regards Markus