From jira-events at lists.jboss.org  Fri Nov  1 00:14:01 2013
From: jira-events at lists.jboss.org (alexey plotnikov (JIRA))
Date: Fri, 1 Nov 2013 00:14:01 -0400 (EDT)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: ignored
 API call .setValue('')
In-Reply-To: <JIRA.12509251.1383279199103@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509251.1383279199103@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509251.1383279199103.27631.1383279241979@jira02.app.mwc.hst.phx2.redhat.com>

alexey plotnikov created RF-13306:
-------------------------------------

             Summary: Autocomplete: ignored API call .setValue('')
                 Key: RF-13306
                 URL: https://issues.jboss.org/browse/RF-13306
             Project: RichFaces
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.3.4
            Reporter: alexey plotnikov


All described here https://community.jboss.org/thread/233973
I have this autocomplete component:
{code}
<table>   
   <tr>   
      <td>   
         <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"   
                            minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"   
                            autofill="false"   
                            onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"   
                            layout="table" value="#{autocomplete.providerName}" >   
            <a4j:queue requestDelay="500" ignoreDupResponses="true" />   
            <h:column>   
               <h:outputText style="display:none;" value="#{s.id}"/>   
               <h:outputText style="display:none;" value="#{s.realName}"/>   
            </h:column>   
            <h:column>   
               <h:outputText value="#{s.name}" escape="false"/>   
            </h:column>   
         </rich:autocomplete>   
      </td>   
      <td>   
         <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"   
                         alt=""/>   
         <h:graphicImage value="/img/cancel.png"   
                         onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"   
                         alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>   
         <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>   
      </td>   
   </tr>   
</table>
{code}
as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
I use JavaScript function "autocompleteChangeProvider" for extract selected id.
I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
 
And a problem:
if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
 
I think i found a solution
AutocompleteBase.js has this code:
{code}
rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
        // call constructor of parent class  
        $super.constructor.call(this, componentId);  
        this.selectId = selectId;  
        this.fieldId = fieldId;  
        this.options = $.extend({}, defaultOptions, options);  
        this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
        this.currentValue = "";  
        this.tempValue = this.getValue();  
        this.isChanged = this.tempValue.length != 0;  
        bindEventHandlers.call(this);  
    };
{code}

as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
i replace this code by this:

{code}
rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
        // call constructor of parent class  
        $super.constructor.call(this, componentId);  
        this.selectId = selectId;  
        this.fieldId = fieldId;  
        this.options = $.extend({}, defaultOptions, options);  
        this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
        this.currentValue = $(rf.getDomElement(fieldId)).val();  
        this.tempValue = this.getValue();  
        this.isChanged = this.tempValue.length != 0;  
        bindEventHandlers.call(this);  
    };
{code}

and it works!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  1 06:29:01 2013
From: jira-events at lists.jboss.org (Matti Bickel (JIRA))
Date: Fri, 1 Nov 2013 06:29:01 -0400 (EDT)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13307) Support java.util.Set in
 iteration components
In-Reply-To: <JIRA.12509268.1383301701348@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509268.1383301701348@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509268.1383301701348.28061.1383301741955@jira02.app.mwc.hst.phx2.redhat.com>

Matti Bickel created RF-13307:
---------------------------------

             Summary: Support java.util.Set in iteration components
                 Key: RF-13307
                 URL: https://issues.jboss.org/browse/RF-13307
             Project: RichFaces
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
          Components: component-tables
    Affects Versions: 4.5-Tracking, 5.0.0.Alpha3
         Environment: Wildfly-8.0.0.Beta1
            Reporter: Matti Bickel


JSF-2.2 now supports iteration over sets as in

<h:dataTable value="#{myBean.mySet}" var="elem">
  <h:column>#{elem.name}"</h:column>
</h:dataTable>

Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
Would be nice if RF catches up with JSF here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  1 06:31:03 2013
From: jira-events at lists.jboss.org (Matti Bickel (JIRA))
Date: Fri, 1 Nov 2013 06:31:03 -0400 (EDT)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13307) Support java.util.Set in
 iteration components
In-Reply-To: <JIRA.12509268.1383301701000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509268.1383301701000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509268.1383301701000.28064.1383301863575@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matti Bickel updated RF-13307:
------------------------------

    Description: 
JSF-2.2 now supports iteration over sets as in

{code:xml}
<h:dataTable value="#{myBean.mySet}" var="elem">
  <h:column>#{elem.name}</h:column>
</h:dataTable>
{code}

Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
Would be nice if RF catches up with JSF here.

  was:
JSF-2.2 now supports iteration over sets as in

<h:dataTable value="#{myBean.mySet}" var="elem">
  <h:column>#{elem.name}"</h:column>
</h:dataTable>

Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
Would be nice if RF catches up with JSF here.


    
> Support java.util.Set in iteration components
> ---------------------------------------------
>
>                 Key: RF-13307
>                 URL: https://issues.jboss.org/browse/RF-13307
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.5-Tracking, 5.0.0.Alpha3
>         Environment: Wildfly-8.0.0.Beta1
>            Reporter: Matti Bickel
>
> JSF-2.2 now supports iteration over sets as in
> {code:xml}
> <h:dataTable value="#{myBean.mySet}" var="elem">
>   <h:column>#{elem.name}</h:column>
> </h:dataTable>
> {code}
> Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
> Would be nice if RF catches up with JSF here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  1 07:28:01 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 1 Nov 2013 07:28:01 -0400 (EDT)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13308) Autocomplete:
 clientFilterFunction doesn't work in Firefox
In-Reply-To: <JIRA.12509275.1383305248578@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509275.1383305248578@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509275.1383305248578.28169.1383305281942@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13308:
----------------------------------

             Summary: Autocomplete: clientFilterFunction doesn't work in Firefox
                 Key: RF-13308
                 URL: https://issues.jboss.org/browse/RF-13308
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-input, regression
    Affects Versions: 5.0.0.Alpha2
         Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
Mojarra 2.1.19
EAP 6.1.1
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Firefox 24 @ Linux x86_64
            Reporter: Pavol Pitonak
            Priority: Critical


# deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/filtering.xhtml
# set attribute mode to "client"
# set attribute clientFilterFunction to "customClientFilterFunction"
# type "no" to the autocomplete
# select "Raleigh of North Carolina"
# click outside of autocomplete in order to send selected value to the server
# check that output contains "North Carolina"

result:
* works fine in Chrome 30
* in Firefox 24, after you type "no", popup with suggestions is not displayed
* works fine in RichFaces 4.3.4.Final

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  1 10:26:02 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 1 Nov 2013 10:26:02 -0400 (EDT)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13309) Autocomplete doesn't
 work correctly when r:ajax bound to selectitem event
In-Reply-To: <JIRA.12509603.1383315889508@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509603.1383315889508@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509603.1383315889508.28430.1383315962023@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13309:
----------------------------------

             Summary: Autocomplete doesn't work correctly when r:ajax bound to selectitem event
                 Key: RF-13309
                 URL: https://issues.jboss.org/browse/RF-13309
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-input, regression
    Affects Versions: 5.0.0.Alpha2
         Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
Mojarra 2.1.19
EAP 6.1.1
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 30.0.1599.114 @ Linux x86_64
            Reporter: Pavol Pitonak
            Priority: Critical


# deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/ajaxOnSelectitem.xhtml
# type "a" into autocomplete
# select "Alabama"
# check output below the autocomplete
# check output of value change listener in page's header

result:
* there is "Your selection: alabama" below the autocomplete instead of "Your selection: Alabama" with upper case A
* value change listener's output contains "alabama" instead of "Alabama": * 1 value changed: null -> alabama
* it works fine on page http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml which is exactly the same but uses event=change in r:ajax
* works fine in RichFaces 4.3.4, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  1 16:47:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 1 Nov 2013 16:47:01 -0400 (EDT)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13310) Upgrade Graphene and
	Warp in 4.3.5 branch
In-Reply-To: <JIRA.12510980.1383338818781@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12510980.1383338818781@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12510980.1383338818781.29050.1383338821903@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13310:
-------------------------------

             Summary: Upgrade Graphene and Warp in 4.3.5 branch
                 Key: RF-13310
                 URL: https://issues.jboss.org/browse/RF-13310
             Project: RichFaces
          Issue Type: Component  Upgrade
      Security Level: Public (Everyone can see)
          Components: tests - functional 
    Affects Versions: 4.3.5
            Reporter: Luk?? Fry?


The state of 4.3 branch framework tests is not as stable as 5.0, thus I track this as a separate issue.

Why we want to upgrade:

* Graphene = Final version API changes changes
* Warp = ease of debugging

I don't think this is absolutely necessary, I doesn;'t work with 4.3.x tests regularly and QE doesn't run them afaik.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  1 16:49:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 1 Nov 2013 16:49:01 -0400 (EDT)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13310) Upgrade Graphene and
	Warp in 4.3 branch
In-Reply-To: <JIRA.12510980.1383338818000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12510980.1383338818000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12510980.1383338818000.29053.1383338941903@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13310:
----------------------------

    Summary: Upgrade Graphene and Warp in 4.3 branch  (was: Upgrade Graphene and Warp in 4.3.5 branch)

    
> Upgrade Graphene and Warp in 4.3 branch
> ---------------------------------------
>
>                 Key: RF-13310
>                 URL: https://issues.jboss.org/browse/RF-13310
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>    Affects Versions: 4.3.5
>            Reporter: Luk?? Fry?
>
> The state of 4.3 branch framework tests is not as stable as 5.0, thus I track this as a separate issue.
> Why we want to upgrade:
> * Graphene = Final version API changes changes
> * Warp = ease of debugging
> I don't think this is absolutely necessary, I doesn;'t work with 4.3.x tests regularly and QE doesn't run them afaik.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov  4 04:43:02 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Mon, 4 Nov 2013 04:43:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13311) Make Push independent of
	BaseComponent
In-Reply-To: <JIRA.12511012.1383558111870@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511012.1383558111870@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511012.1383558111870.29713.1383558182190@jira02.app.mwc.hst.phx2.redhat.com>

Michal Petrov created RF-13311:
----------------------------------

             Summary: Make Push independent of BaseComponent
                 Key: RF-13311
                 URL: https://issues.jboss.org/browse/RF-13311
             Project: RichFaces
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: 5-Tracking
            Reporter: Michal Petrov


Currently Push extends BaseComponent but since BaseComponent is not a part of core the extending fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 05:09:02 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Mon, 4 Nov 2013 05:09:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638602@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638602@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638602.29780.1383559742864@jira02.app.mwc.hst.phx2.redhat.com>

Michal Petrov created RF-13312:
----------------------------------

             Summary: rich:editor doesn't work in RF 4.5
                 Key: RF-13312
                 URL: https://issues.jboss.org/browse/RF-13312
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-input
    Affects Versions: 4.5-Tracking
            Reporter: Michal Petrov


The editor's UI doesn't get rendered. The rendering fails with:
{panel}
10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
{panel}

It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 05:09:02 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Mon, 4 Nov 2013 05:09:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638000.29782.1383559742995@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov updated RF-13312:
-------------------------------

    Fix Version/s: 4.5.0.Alpha1

    
> rich:editor doesn't work in RF 4.5
> ----------------------------------
>
>                 Key: RF-13312
>                 URL: https://issues.jboss.org/browse/RF-13312
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> The editor's UI doesn't get rendered. The rendering fails with:
> {panel}
> 10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> {panel}
> It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 05:11:02 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Mon, 4 Nov 2013 05:11:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638000.29796.1383559862975@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829710#comment-12829710 ] 

Michal Petrov commented on RF-13312:
------------------------------------

I'm guessing we can just check if the path contains the {{"db="}} substring and if not just return the path.
                
> rich:editor doesn't work in RF 4.5
> ----------------------------------
>
>                 Key: RF-13312
>                 URL: https://issues.jboss.org/browse/RF-13312
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> The editor's UI doesn't get rendered. The rendering fails with:
> {panel}
> 10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> {panel}
> It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 05:23:01 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Mon, 4 Nov 2013 05:23:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload
 fileuploadprogress unavailable in RF 4.5
In-Reply-To: <JIRA.12511966.1383560542249@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542249@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542249.29850.1383560581914@jira02.app.mwc.hst.phx2.redhat.com>

Michal Petrov created RF-13313:
----------------------------------

             Summary: rich:fileupload fileuploadprogress unavailable in RF 4.5
                 Key: RF-13313
                 URL: https://issues.jboss.org/browse/RF-13313
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.5-Tracking
            Reporter: Michal Petrov


After uploading an image error appears in console:

{panel}
GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
{panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 08:08:01 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Mon, 4 Nov 2013 08:08:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13314) Deprecate reslib
	resource files
In-Reply-To: <JIRA.12514982.1383570367035@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12514982.1383570367035@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12514982.1383570367035.30389.1383570481983@jira02.app.mwc.hst.phx2.redhat.com>

Michal Petrov created RF-13314:
----------------------------------

             Summary: Deprecate reslib resource files
                 Key: RF-13314
                 URL: https://issues.jboss.org/browse/RF-13314
             Project: RichFaces
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
          Components: component
    Affects Versions: 5-Tracking
            Reporter: Michal Petrov




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 08:08:02 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Mon, 4 Nov 2013 08:08:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13314) Deprecate reslib
	resource files
In-Reply-To: <JIRA.12514982.1383570367000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12514982.1383570367000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12514982.1383570367000.30390.1383570482036@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840892#comment-12840892 ] 

Michal Petrov commented on RF-13314:
------------------------------------

I've copied the ajax and base-component reslibs to RF 4.5, there should be no issue in removing them from RF 5.
                
> Deprecate reslib resource files
> -------------------------------
>
>                 Key: RF-13314
>                 URL: https://issues.jboss.org/browse/RF-13314
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5-Tracking
>            Reporter: Michal Petrov
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:04:02 2013
From: jira-events at lists.jboss.org (Andreas Zschorn (JIRA))
Date: Mon, 4 Nov 2013 12:04:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12987) NPE in
 UIComponent$ComponentSystemEventListenerAdapter.processEvent when placing
 UITree in UIAccordionItem programmatically.
In-Reply-To: <JIRA.12491835.1368621907000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12491835.1368621907000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12491835.1368621907000.31577.1383584642352@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850590#comment-12850590 ] 

Andreas Zschorn commented on RF-12987:
--------------------------------------

Reason is to 90% that  during restore, the component is not pushed to the el context
At line 2527: ComponentSystemEventListenerAdapter.

 UIComponent .getCurrentComponent(context)  returns null.
---------------------------------------------------------------------------------------------------------------
            wrapped = (ComponentSystemEventListener) ((listener == null)
                                                      ? UIComponent .getCurrentComponent(context)
                                                      : ((StateHolderSaver) listener).restore(context));
                
> NPE in UIComponent$ComponentSystemEventListenerAdapter.processEvent when placing UITree in UIAccordionItem programmatically.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-12987
>                 URL: https://issues.jboss.org/browse/RF-12987
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tree
>    Affects Versions: 4.3.1
>         Environment: JBoss 7.1.1.Final
> Mojarra 2.1.21
>            Reporter: Yuriy Granovskiy
>             Fix For: 5-Tracking
>
>         Attachments: trepanelnbar.zip
>
>
> NPE appears when we place UITree into UIAccordionItem programmatically.
> After postback we get:
> {panel:title NPE stacktrace}
> java.lang.NullPointerException
> 	javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2486)
> 	javax.faces.event.SystemEvent.processListener(SystemEvent.java:106)
> 	com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2168)
> 	com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2116)
> 	com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:288)
> 	com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:246)
> 	javax.faces.component.UIComponentBase.publishAfterViewEvents(UIComponentBase.java:2201)
> 	javax.faces.component.UIComponentBase.doPostAddProcessing(UIComponentBase.java:1883)
> 	javax.faces.component.UIComponentBase.setParent(UIComponentBase.java:400)
> 	javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2635)
> 	javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2607)
> 	com.sun.faces.application.view.StateManagementStrategyImpl.restoreDynamicAdd(StateManagementStrategyImpl.java:393)
> 	com.sun.faces.application.view.StateManagementStrategyImpl.restoreDynamicActions(StateManagementStrategyImpl.java:314)
> 	com.sun.faces.application.view.StateManagementStrategyImpl.restoreView(StateManagementStrategyImpl.java:281)
> 	com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:188)
> 	com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:453)
> 	com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:142)
> 	javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:303)
> 	com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:192)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116)
> 	com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
> {panel}
> Works fine if we store some another components(such as command button) in the accordion item. But UITree causes the problem.
> Here is a component class:
> {code:java|title TreePanelBar.java}
> @FacesComponent( value = "extended.TreePanelBar" )
> @ResourceDependencies( { @ResourceDependency( library = "org.richfaces", name = "ajax.reslib" ),
>         @ResourceDependency( library = "org.richfaces", name = "base-component.reslib" ),
>         @ResourceDependency( library = "org.richfaces", name = "togglePanel.js" ),
>         @ResourceDependency( library = "org.richfaces", name = "accordion.js" ),
>         @ResourceDependency( library = "org.richfaces", name = "AccordionItem.js" ),
>         @ResourceDependency( library = "org.richfaces", name = "tree.js", target = "" ),
>         @ResourceDependency( library = "", name = "richfaces-event.js", target = "" ),
>         @ResourceDependency( library = "org.richfaces", name = "icons.ecss" ),
>         @ResourceDependency( library = "org.richfaces", name = "accordion.ecss" ),
>         @ResourceDependency( library = "org.richfaces", name = "tree.ecss", target = "" ) } )
> public class TreePanelBar extends UIAccordion implements SystemEventListener, Serializable {
>     private static final long serialVersionUID = -7698934343515911542L;
>     protected enum Properties {
>         node
>     }
>     public TreePanelBar() {
>         UIViewRoot root = getFacesContext().getViewRoot();
>         root.subscribeToViewEvent( PreRenderViewEvent.class, this );
>     }
>     /** {@inheritDoc} */
>     @Override
>     public void processEvent( final SystemEvent event ) throws AbortProcessingException {
>         if ( getChildCount() == 0 ) {
>             Iterator<Object> iterator = getNode().getChildrenKeysIterator();
>             while ( iterator.hasNext() ) {
>                 Object childKey = iterator.next();
>                 DataHolderTreeNodeImpl entry = (DataHolderTreeNodeImpl) getNode().getChild( childKey );
>                 UIAccordionItem item = (UIAccordionItem) getFacesContext().getApplication().createComponent( getFacesContext(),
>                         UIAccordionItem.COMPONENT_TYPE, "org.richfaces.AccordionItemRenderer" );
>                 item.setId( FacesContext.getCurrentInstance().getViewRoot().createUniqueId() );
>                 item.setHeader( ( entry.getData() ).getLabel() );
>                 getChildren().add( item );
>                 // Adding a button programmatically. Works fine without tree.
>                 UICommand button = (UICommand) getFacesContext().getApplication().createComponent(
>                 UICommand.COMPONENT_TYPE );
>                 button.setId(item.getId() + "_button");
>                 button.setValue( "Button " + item.getHeader() );
>                 item.getChildren().add( button );
>                 //Adding a tree programmatically. NPE in javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent after postback.
>                 UITree tree = createTree( childKey, entry );
>                 tree.setId( item.getId() + "_tree");
>                 item.getChildren().add( tree );                
>             }
>         }
>     }
>     /**
>      * @param childKey
>      * @param entry
>      * @return
>      */
>     private UITree createTree( final Object childKey, final DataHolderTreeNodeImpl entry ) {
>         UITree tree = (UITree) getFacesContext().getApplication().createComponent( UITree.COMPONENT_TYPE );
>         tree.setValue( entry );
>         UITreeNode uiNode = (UITreeNode) getFacesContext().getApplication().createComponent( UITreeNode.COMPONENT_TYPE );
>         uiNode.setTitle( (String) entry.getKey() );
>         uiNode.setIconCollapsed( entry.getData().getIcon() );
>         uiNode.setIconExpanded( entry.getData().getIcon() );
>         uiNode.setId( getFacesContext().getViewRoot().createUniqueId() );
>         tree.getChildren().add( uiNode );
>         return tree;
>     }
>     /**
>      * @return
>      */
>     public TreeNode getNode() {
>         return (TreeNode) getStateHelper().eval( Properties.node );
>     }
>     public void setNode( final TreeNode node ) {
>         getStateHelper().put( Properties.node, node );
>     }
>     /** {@inheritDoc} */
>     @Override
>     public boolean isListenerForSource( final Object source ) {
>         return true;
>     }
> }
> {code}
> The exception is very similar to [RF-11423|https://issues.jboss.org/browse/RF-11423]
> The listener that is trying to get processed is for PostRenderEvent which is not mensioned in the component code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:14:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:14:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13314) Deprecate reslib
	resource files
In-Reply-To: <JIRA.12514982.1383570367000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12514982.1383570367000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12514982.1383570367000.31652.1383585242514@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850595#comment-12850595 ] 

Brian Leathem commented on RF-13314:
------------------------------------

Many RF 5 components still use these reslibs.  We cannot remove the reslibs from RF 5 until those components have been migrated.
                
> Deprecate reslib resource files
> -------------------------------
>
>                 Key: RF-13314
>                 URL: https://issues.jboss.org/browse/RF-13314
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5-Tracking
>            Reporter: Michal Petrov
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:14:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:14:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13314) Deprecate reslib
	resource files
In-Reply-To: <JIRA.12514982.1383570367000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12514982.1383570367000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12514982.1383570367000.31654.1383585242591@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13314:
-------------------------------

    Fix Version/s: 5-Tracking

    
> Deprecate reslib resource files
> -------------------------------
>
>                 Key: RF-13314
>                 URL: https://issues.jboss.org/browse/RF-13314
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5-Tracking
>            Reporter: Michal Petrov
>             Fix For: 5-Tracking
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:16:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:16:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload
 fileuploadprogress unavailable in RF 4.5
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.31661.1383585362874@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13313:
-------------------------------

    Fix Version/s: 4.5.0.Alpha1

    
> rich:fileupload fileuploadprogress unavailable in RF 4.5
> --------------------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:16:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:16:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload
 fileuploadprogress unavailable in RF 4.5
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.31663.1383585362949@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13313:
-------------------------------

    Component/s: component-input

    
> rich:fileupload fileuploadprogress unavailable in RF 4.5
> --------------------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:20:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:20:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638000.31678.1383585602183@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850598#comment-12850598 ] 

Brian Leathem commented on RF-13312:
------------------------------------

+1.  [~lfryc] any idea why this would have started failing in RF 4.5?
                
> rich:editor doesn't work in RF 4.5
> ----------------------------------
>
>                 Key: RF-13312
>                 URL: https://issues.jboss.org/browse/RF-13312
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> The editor's UI doesn't get rendered. The rendering fails with:
> {panel}
> 10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> {panel}
> It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:20:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:20:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13311) Make Push independent of
	BaseComponent
In-Reply-To: <JIRA.12511012.1383558111000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511012.1383558111000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511012.1383558111000.31682.1383585602460@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13311:
----------------------------------

    Assignee: Luk?? Fry?

    
> Make Push independent of BaseComponent
> --------------------------------------
>
>                 Key: RF-13311
>                 URL: https://issues.jboss.org/browse/RF-13311
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> Currently Push extends BaseComponent but since BaseComponent is not a part of core the extending fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov  4 12:22:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:22:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13310) Upgrade Graphene and
	Warp in 4.3 branch
In-Reply-To: <JIRA.12510980.1383338818000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12510980.1383338818000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12510980.1383338818000.31699.1383585722391@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13310:
-------------------------------

    Fix Version/s: 4.3.5

    
> Upgrade Graphene and Warp in 4.3 branch
> ---------------------------------------
>
>                 Key: RF-13310
>                 URL: https://issues.jboss.org/browse/RF-13310
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>    Affects Versions: 4.3.5
>            Reporter: Luk?? Fry?
>             Fix For: 4.3.5
>
>
> The state of 4.3 branch framework tests is not as stable as 5.0, thus I track this as a separate issue.
> Why we want to upgrade:
> * Graphene = Final version API changes changes
> * Warp = ease of debugging
> I don't think this is absolutely necessary, I doesn;'t work with 4.3.x tests regularly and QE doesn't run them afaik.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov  4 12:22:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:22:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13310) Upgrade Graphene and
	Warp in 4.3 branch
In-Reply-To: <JIRA.12510980.1383338818000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12510980.1383338818000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12510980.1383338818000.31704.1383585722586@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850601#comment-12850601 ] 

Brian Leathem commented on RF-13310:
------------------------------------

Better to keep things current and consistent IMO,  We will be supporting RF 4.3 for a while yet.
                
> Upgrade Graphene and Warp in 4.3 branch
> ---------------------------------------
>
>                 Key: RF-13310
>                 URL: https://issues.jboss.org/browse/RF-13310
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>    Affects Versions: 4.3.5
>            Reporter: Luk?? Fry?
>             Fix For: 4.3.5
>
>
> The state of 4.3 branch framework tests is not as stable as 5.0, thus I track this as a separate issue.
> Why we want to upgrade:
> * Graphene = Final version API changes changes
> * Warp = ease of debugging
> I don't think this is absolutely necessary, I doesn;'t work with 4.3.x tests regularly and QE doesn't run them afaik.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov  4 12:22:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:22:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13309) Autocomplete doesn't
 work correctly when r:ajax bound to selectitem event
In-Reply-To: <JIRA.12509603.1383315889000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509603.1383315889000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509603.1383315889000.31710.1383585722974@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13309:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Autocomplete doesn't work correctly when r:ajax bound to selectitem event
> -------------------------------------------------------------------------
>
>                 Key: RF-13309
>                 URL: https://issues.jboss.org/browse/RF-13309
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 30.0.1599.114 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/ajaxOnSelectitem.xhtml
> # type "a" into autocomplete
> # select "Alabama"
> # check output below the autocomplete
> # check output of value change listener in page's header
> result:
> * there is "Your selection: alabama" below the autocomplete instead of "Your selection: Alabama" with upper case A
> * value change listener's output contains "alabama" instead of "Alabama": * 1 value changed: null -> alabama
> * it works fine on page http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml which is exactly the same but uses event=change in r:ajax
> * works fine in RichFaces 4.3.4, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:24:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:24:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13308) Autocomplete:
 clientFilterFunction doesn't work in Firefox
In-Reply-To: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509275.1383305248000.31715.1383585842096@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13308:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Autocomplete: clientFilterFunction doesn't work in Firefox
> ----------------------------------------------------------
>
>                 Key: RF-13308
>                 URL: https://issues.jboss.org/browse/RF-13308
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/filtering.xhtml
> # set attribute mode to "client"
> # set attribute clientFilterFunction to "customClientFilterFunction"
> # type "no" to the autocomplete
> # select "Raleigh of North Carolina"
> # click outside of autocomplete in order to send selected value to the server
> # check that output contains "North Carolina"
> result:
> * works fine in Chrome 30
> * in Firefox 24, after you type "no", popup with suggestions is not displayed
> * works fine in RichFaces 4.3.4.Final

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:24:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:24:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13307) Support java.util.Set in
 iteration components
In-Reply-To: <JIRA.12509268.1383301701000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509268.1383301701000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509268.1383301701000.31726.1383585842604@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13307:
-------------------------------

    Fix Version/s: 5.0.0.Alpha3

    
> Support java.util.Set in iteration components
> ---------------------------------------------
>
>                 Key: RF-13307
>                 URL: https://issues.jboss.org/browse/RF-13307
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.5-Tracking, 5.0.0.Alpha3
>         Environment: Wildfly-8.0.0.Beta1
>            Reporter: Matti Bickel
>              Labels: jsf22
>             Fix For: 5.0.0.Alpha3
>
>
> JSF-2.2 now supports iteration over sets as in
> {code:xml}
> <h:dataTable value="#{myBean.mySet}" var="elem">
>   <h:column>#{elem.name}</h:column>
> </h:dataTable>
> {code}
> Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
> Would be nice if RF catches up with JSF here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:24:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:24:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13307) Support java.util.Set in
 iteration components
In-Reply-To: <JIRA.12509268.1383301701000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509268.1383301701000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509268.1383301701000.31724.1383585842503@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13307:
-------------------------------

    Labels: jsf22  (was: )

    
> Support java.util.Set in iteration components
> ---------------------------------------------
>
>                 Key: RF-13307
>                 URL: https://issues.jboss.org/browse/RF-13307
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.5-Tracking, 5.0.0.Alpha3
>         Environment: Wildfly-8.0.0.Beta1
>            Reporter: Matti Bickel
>              Labels: jsf22
>
> JSF-2.2 now supports iteration over sets as in
> {code:xml}
> <h:dataTable value="#{myBean.mySet}" var="elem">
>   <h:column>#{elem.name}</h:column>
> </h:dataTable>
> {code}
> Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
> Would be nice if RF catches up with JSF here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:24:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:24:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13307) Support java.util.Set in
 iteration components
In-Reply-To: <JIRA.12509268.1383301701000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509268.1383301701000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509268.1383301701000.31730.1383585842774@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13307:
-------------------------------

    Affects Version/s: 5.0.0.Alpha1
                       4.3.4
                           (was: 5.0.0.Alpha3)
                           (was: 4.5-Tracking)

    
> Support java.util.Set in iteration components
> ---------------------------------------------
>
>                 Key: RF-13307
>                 URL: https://issues.jboss.org/browse/RF-13307
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>         Environment: Wildfly-8.0.0.Beta1
>            Reporter: Matti Bickel
>              Labels: jsf22
>             Fix For: 5.0.0.Alpha3
>
>
> JSF-2.2 now supports iteration over sets as in
> {code:xml}
> <h:dataTable value="#{myBean.mySet}" var="elem">
>   <h:column>#{elem.name}</h:column>
> </h:dataTable>
> {code}
> Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
> Would be nice if RF catches up with JSF here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov  4 12:26:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:26:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: ignored
 API call .setValue('')
In-Reply-To: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509251.1383279199000.31738.1383585962056@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13306:
----------------------------------

    Assignee: Luk?? Fry?


[~lfryc] please assess the proposed fix and schedule accordingly.
                
> Autocomplete: ignored API call .setValue('')
> --------------------------------------------
>
>                 Key: RF-13306
>                 URL: https://issues.jboss.org/browse/RF-13306
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Luk?? Fry?
>
> All described here https://community.jboss.org/thread/233973
> I have this autocomplete component:
> {code}
> <table>   
>    <tr>   
>       <td>   
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"   
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"   
>                             autofill="false"   
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"   
>                             layout="table" value="#{autocomplete.providerName}" >   
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />   
>             <h:column>   
>                <h:outputText style="display:none;" value="#{s.id}"/>   
>                <h:outputText style="display:none;" value="#{s.realName}"/>   
>             </h:column>   
>             <h:column>   
>                <h:outputText value="#{s.name}" escape="false"/>   
>             </h:column>   
>          </rich:autocomplete>   
>       </td>   
>       <td>   
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"   
>                          alt=""/>   
>          <h:graphicImage value="/img/cancel.png"   
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"   
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>   
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>   
>       </td>   
>    </tr>   
> </table>
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And a problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
>  
> I think i found a solution
> AutocompleteBase.js has this code:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = "";  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
> i replace this code by this:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = $(rf.getDomElement(fieldId)).val();  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> and it works!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov  4 12:28:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:28:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13305) Autocomplete: i must
 press button twice for popup window
In-Reply-To: <JIRA.12509249.1383274376000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509249.1383274376000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509249.1383274376000.31746.1383586082020@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13305:
----------------------------------

    Assignee: Luk?? Fry?


[~lfryc] please assess the proposed fix and schedule accordingly.
                
> Autocomplete: i must press button twice for popup window
> --------------------------------------------------------
>
>                 Key: RF-13305
>                 URL: https://issues.jboss.org/browse/RF-13305
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Luk?? Fry?
>
> All described here https://community.jboss.org/thread/233971
> I try repeat:
> I have this autocomplete component:
> {code}
> <table>  
>    <tr>  
>       <td>  
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"  
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"  
>                             autofill="false"  
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"  
>                             layout="table" value="#{autocomplete.providerName}" >  
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
>             <h:column>  
>                <h:outputText style="display:none;" value="#{s.id}"/>  
>                <h:outputText style="display:none;" value="#{s.realName}"/>  
>             </h:column>  
>             <h:column>  
>                <h:outputText value="#{s.name}" escape="false"/>  
>             </h:column>  
>          </rich:autocomplete>  
>       </td>  
>       <td>  
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"  
>                          alt=""/>  
>          <h:graphicImage value="/img/cancel.png"  
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"  
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>  
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>  
>       </td>  
>    </tr>  
> </table>  
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on cancel button(img/cancel.png), then after that, if user clicks on show button(/img/arrow.png) popup not showing, user must clicks twice on this button.
> *This problem shows if i use showButton from rich:autocomplete instead my show button.*
> I think i found a solution of this problem:
> Autocomplete.js has this code:
> {code}
> var onChangeValue = function (event, value, callback) {  
>         selectItem.call(this, event);  
>   
>         // value is undefined if called from AutocompleteBase onChange  
>         var subValue = (typeof value == "undefined") ? this.__getSubValue() : value;  
>         var oldValue = this.value;  
>         this.value = subValue;  
>   
>         if ((this.options.isCachedAjax || !this.options.ajaxMode) &&  
>             this.cache && this.cache.isCached(subValue)) {  
>             ...  
>         } else {  
>             if (event.keyCode == rf.KEYS.RETURN || event.type == "click") {  
>                 this.__setInputValue(subValue);  
>             }  
>             if (subValue.length >= this.options.minChars) {  
>                 if ((this.options.ajaxMode || this.options.lazyClientMode) && oldValue != subValue) {  
>                     callAjax.call(this, event, callback);  
>                 }  
>             } else {  
>                 if (this.options.ajaxMode) {  
>                     clearItems.call(this);  
>                     this.__hide(event);  
>                 }  
>             }  
>         }  
>      }; 
> {code}
> for show popup this must be true: 
> {code}
> oldValue != subValue
> {code}
> but in this part of code 
> oldValue is ''(empty string) and subValue is ''(empty string),
> so this condition 
> {code}
> oldValue != subValue
> {code}
> return false!
>  
> i replace this code by this:
> {code}
> var onChangeValue = function (event, value, callback) {  
>         selectItem.call(this, event);  
>   
>         // value is undefined if called from AutocompleteBase onChange  
>         var subValue = (typeof value == "undefined") ? this.__getSubValue() : value;  
>         var oldValue = this.value;  
>         this.value = subValue;  
>   
>         if ((this.options.isCachedAjax || !this.options.ajaxMode) &&  
>             this.cache && this.cache.isCached(subValue)) {  
>             ...  
>         } else {  
>             if (event.keyCode == rf.KEYS.RETURN || event.type == "click") {  
>                 this.__setInputValue(subValue);  
>             }  
>             if (subValue.length >= this.options.minChars) {  
>                 if ((this.options.ajaxMode || this.options.lazyClientMode) && (oldValue != subValue || (oldValue === '' && subValue === ''))) {  
>                     callAjax.call(this, event, callback);  
>                 }  
>             } else {  
>                 if (this.options.ajaxMode) {  
>                     clearItems.call(this);  
>                     this.__hide(event);  
>                 }  
>             }  
>         }  
>   
>     };  
> {code}
> so, than oldValue='' and subValue=='' callAjax.call will be called and popup will be showing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov  4 12:44:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 4 Nov 2013 12:44:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638000.31823.1383587042211@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850622#comment-12850622 ] 

Luk?? Fry? commented on RF-13312:
---------------------------------

This can be caused by re-mapping of org.richfaces.* library to resource servlet: RF-13078
                
> rich:editor doesn't work in RF 4.5
> ----------------------------------
>
>                 Key: RF-13312
>                 URL: https://issues.jboss.org/browse/RF-13312
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> The editor's UI doesn't get rendered. The rendering fails with:
> {panel}
> 10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> {panel}
> It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov  4 12:44:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 4 Nov 2013 12:44:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638000.31828.1383587042532@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850622#comment-12850622 ] 

Luk?? Fry? edited comment on RF-13312 at 11/4/13 12:43 PM:
-----------------------------------------------------------

This can be caused by re-mapping of org.richfaces.* library to resource servlet: RF-13078

Not sure how it's related yet though.
                
      was (Author: lfryc):
    This can be caused by re-mapping of org.richfaces.* library to resource servlet: RF-13078
                  
> rich:editor doesn't work in RF 4.5
> ----------------------------------
>
>                 Key: RF-13312
>                 URL: https://issues.jboss.org/browse/RF-13312
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> The editor's UI doesn't get rendered. The rendering fails with:
> {panel}
> 10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> {panel}
> It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov  4 12:48:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 4 Nov 2013 12:48:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638000.31854.1383587282037@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13312:
----------------------------------

    Assignee: Luk?? Fry?

    
> rich:editor doesn't work in RF 4.5
> ----------------------------------
>
>                 Key: RF-13312
>                 URL: https://issues.jboss.org/browse/RF-13312
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> The editor's UI doesn't get rendered. The rendering fails with:
> {panel}
> 10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> {panel}
> It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 02:54:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 02:54:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13288) EDT: sortOrder gets
 re-set when resizing a column
In-Reply-To: <JIRA.12508688.1382618301000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508688.1382618301000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508688.1382618301000.32445.1383638041975@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13288.
-----------------------------

    Fix Version/s: 4.3.4
       Resolution: Out of Date


[~jtrantin] confirmed offline that the issue is fixed in 4.3.4.
                
> EDT: sortOrder gets re-set when resizing a column
> -------------------------------------------------
>
>                 Key: RF-13288
>                 URL: https://issues.jboss.org/browse/RF-13288
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.2
>            Reporter: Jon?? Trantina
>            Assignee: Luk?? Fry?
>              Labels: waiting_on_user
>             Fix For: 4.3.4
>
>         Attachments: reproducer.tar.gz
>
>
> I have the following extendedDataTable:
> {noformat}
>  <rich:extendedDataTable value="#{sandboxHandler.workItems}"
>                                     keepSaved="true" var="workitem" id="table">
>                 <rich:column sortBy="#{workitem}"
>                              sortOrder="#{sandboxHandler.sortingBean.sortsOrders['entryPD']}">
>                     <f:facet name="header">
>                         <h:outputText value="bla" />
>                         <uwl:simpleSortIcons sortingBean="#{sandboxHandler.sortingBean}"
>                                              sortBy="entryPD" render="table" />
>                     </f:facet>
>                     <h:outputFormat value="{0, date, dd.MM.yyyy - HH:mm}">
>                         <f:param value="#{workitem}" />
>                     </h:outputFormat>
>                 </rich:column>
>             </rich:extendedDataTable>
> {noformat}
> The issue is the sorting stops working after resizing a column. It gets stuck at ASC or DESC. This is caused by ELResolver, that is setting sandboxHandler.sortingBean.sortsOrders['entryPD'] back to the old value right after the SortingBean has done its job and set the right sort order.
> Note that before resizing the column everything works fine and nobody (except SortingBean) touches the sortOrders map.
> Please see the attached reproducer app, that is debug-friendly and shows the behaviour.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 02:54:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 02:54:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13288) EDT: sortOrder gets
 re-set when resizing a column
In-Reply-To: <JIRA.12508688.1382618301000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508688.1382618301000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508688.1382618301000.32448.1383638042124@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13288:
----------------------------

    Fix Version/s:     (was: 4.3.4)

    
> EDT: sortOrder gets re-set when resizing a column
> -------------------------------------------------
>
>                 Key: RF-13288
>                 URL: https://issues.jboss.org/browse/RF-13288
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.2
>            Reporter: Jon?? Trantina
>            Assignee: Luk?? Fry?
>              Labels: waiting_on_user
>         Attachments: reproducer.tar.gz
>
>
> I have the following extendedDataTable:
> {noformat}
>  <rich:extendedDataTable value="#{sandboxHandler.workItems}"
>                                     keepSaved="true" var="workitem" id="table">
>                 <rich:column sortBy="#{workitem}"
>                              sortOrder="#{sandboxHandler.sortingBean.sortsOrders['entryPD']}">
>                     <f:facet name="header">
>                         <h:outputText value="bla" />
>                         <uwl:simpleSortIcons sortingBean="#{sandboxHandler.sortingBean}"
>                                              sortBy="entryPD" render="table" />
>                     </f:facet>
>                     <h:outputFormat value="{0, date, dd.MM.yyyy - HH:mm}">
>                         <f:param value="#{workitem}" />
>                     </h:outputFormat>
>                 </rich:column>
>             </rich:extendedDataTable>
> {noformat}
> The issue is the sorting stops working after resizing a column. It gets stuck at ASC or DESC. This is caused by ELResolver, that is setting sandboxHandler.sortingBean.sortsOrders['entryPD'] back to the old value right after the SortingBean has done its job and set the right sort order.
> Note that before resizing the column everything works fine and nobody (except SortingBean) touches the sortOrders map.
> Please see the attached reproducer app, that is debug-friendly and shows the behaviour.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 04:57:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 04:57:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13315) bridgeBase: bears
 orderingList specific event namespacing and has wrong name of destroy
 method
In-Reply-To: <JIRA.12518001.1383645379710@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518001.1383645379710@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518001.1383645379710.32638.1383645421980@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13315:
-------------------------------

             Summary: bridgeBase: bears orderingList specific event namespacing and has wrong name of destroy method
                 Key: RF-13315
                 URL: https://issues.jboss.org/browse/RF-13315
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?


{code}
$('body').on("cleanDom.orderingList.bootstrap.RICH", function(event, ui) {
{code}

{code}
destroy : function() {
{code}

should be {{_destroy}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 05:28:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Jon=C3=A1=C5=A1_Trantina_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 05:28:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269982@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269982@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269982.32752.1383647282007@jira02.app.mwc.hst.phx2.redhat.com>

Jon?? Trantina created RF-13316:
-----------------------------------

             Summary: PDF is rendered on top of components
                 Key: RF-13316
                 URL: https://issues.jboss.org/browse/RF-13316
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.3.4, 4.3.2
         Environment: Internet Explorer with Adobe Reader plugin
            Reporter: Jon?? Trantina


If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
Take a look at images attached to this case, also there is a reproducer app attached.

This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 05:30:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Jon=C3=A1=C5=A1_Trantina_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 05:30:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269000.32755.1383647402100@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon?? Trantina updated RF-13316:
--------------------------------

    Attachment: reproducer.zip


Reproducer application.
                
> PDF is rendered on top of components
> ------------------------------------
>
>                 Key: RF-13316
>                 URL: https://issues.jboss.org/browse/RF-13316
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.2, 4.3.4
>         Environment: Internet Explorer with Adobe Reader plugin
>            Reporter: Jon?? Trantina
>         Attachments: correct.jpg, incorrect.jpg, reproducer.zip
>
>
> If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
> Take a look at images attached to this case, also there is a reproducer app attached.
> This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
> Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 05:30:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Jon=C3=A1=C5=A1_Trantina_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 05:30:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269000.32762.1383647402372@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon?? Trantina updated RF-13316:
--------------------------------

    Attachment: incorrect.jpg

    
> PDF is rendered on top of components
> ------------------------------------
>
>                 Key: RF-13316
>                 URL: https://issues.jboss.org/browse/RF-13316
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.2, 4.3.4
>         Environment: Internet Explorer with Adobe Reader plugin
>            Reporter: Jon?? Trantina
>         Attachments: correct.jpg, incorrect.jpg, reproducer.zip
>
>
> If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
> Take a look at images attached to this case, also there is a reproducer app attached.
> This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
> Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 05:30:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Jon=C3=A1=C5=A1_Trantina_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 05:30:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269000.32759.1383647402240@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon?? Trantina updated RF-13316:
--------------------------------

    Attachment: correct.jpg

    
> PDF is rendered on top of components
> ------------------------------------
>
>                 Key: RF-13316
>                 URL: https://issues.jboss.org/browse/RF-13316
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.2, 4.3.4
>         Environment: Internet Explorer with Adobe Reader plugin
>            Reporter: Jon?? Trantina
>         Attachments: correct.jpg, incorrect.jpg, reproducer.zip
>
>
> If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
> Take a look at images attached to this case, also there is a reproducer app attached.
> This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
> Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 05:36:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Jon=C3=A1=C5=A1_Trantina_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 05:36:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269000.32781.1383647762085@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon?? Trantina updated RF-13316:
--------------------------------

    Attachment:     (was: pdf_popup_fehler.zip)

    
> PDF is rendered on top of components
> ------------------------------------
>
>                 Key: RF-13316
>                 URL: https://issues.jboss.org/browse/RF-13316
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.2, 4.3.4
>         Environment: Internet Explorer with Adobe Reader plugin
>            Reporter: Jon?? Trantina
>         Attachments: correct.jpg, incorrect.jpg, reproducer.zip
>
>
> If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
> Take a look at images attached to this case, also there is a reproducer app attached.
> This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
> Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 05:36:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Jon=C3=A1=C5=A1_Trantina_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 05:36:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269000.32783.1383647762197@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon?? Trantina updated RF-13316:
--------------------------------

    Comment: was deleted

(was: A comment with security level 'Red Hat' was removed.)

    
> PDF is rendered on top of components
> ------------------------------------
>
>                 Key: RF-13316
>                 URL: https://issues.jboss.org/browse/RF-13316
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.2, 4.3.4
>         Environment: Internet Explorer with Adobe Reader plugin
>            Reporter: Jon?? Trantina
>         Attachments: correct.jpg, incorrect.jpg, reproducer.zip
>
>
> If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
> Take a look at images attached to this case, also there is a reproducer app attached.
> This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
> Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 05:58:01 2013
From: jira-events at lists.jboss.org (Matti Bickel (JIRA))
Date: Tue, 5 Nov 2013 05:58:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13317)
 ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState
 id in startUpdate()
In-Reply-To: <JIRA.12518007.1383648996868@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518007.1383648996868@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518007.1383648996868.32843.1383649081912@jira02.app.mwc.hst.phx2.redhat.com>

Matti Bickel created RF-13317:
---------------------------------

             Summary: ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()
                 Key: RF-13317
                 URL: https://issues.jboss.org/browse/RF-13317
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.3.4
         Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1
            Reporter: Matti Bickel


I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests:

When the response comes back, the data is fine but I get a JSF error saying
bq. During update: javax.faces.ViewState not found

Following that, no componentData is available to the Autocomplete component and no suggestions get displayed.

For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says:
{quote}
Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view.
{quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov  5 06:37:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 06:37:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13317)
 ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState
 id in startUpdate()
In-Reply-To: <JIRA.12518007.1383648996000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518007.1383648996000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518007.1383648996000.32918.1383651422036@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850807#comment-12850807 ] 

Luk?? Fry? commented on RF-13317:
---------------------------------

VIEW_STATE_MARKER is inserted [1] but it is not prefixed with clientId as specified above.

[1] https://github.com/richfaces4/core/blob/master/impl/src/main/java/org/richfaces/context/ExtendedPartialViewContextImpl.java#L415
                
> ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13317
>                 URL: https://issues.jboss.org/browse/RF-13317
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>         Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1
>            Reporter: Matti Bickel
>              Labels: jsf22
>
> I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests:
> When the response comes back, the data is fine but I get a JSF error saying
> bq. During update: javax.faces.ViewState not found
> Following that, no componentData is available to the Autocomplete component and no suggestions get displayed.
> For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says:
> {quote}
> Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 06:37:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 06:37:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13317)
 ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState
 id in startUpdate()
In-Reply-To: <JIRA.12518007.1383648996000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518007.1383648996000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518007.1383648996000.32924.1383651422378@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13317:
----------------------------

    Fix Version/s: 4.3.5

    
> ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13317
>                 URL: https://issues.jboss.org/browse/RF-13317
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>         Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1
>            Reporter: Matti Bickel
>              Labels: jsf22
>             Fix For: 4.3.5
>
>
> I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests:
> When the response comes back, the data is fine but I get a JSF error saying
> bq. During update: javax.faces.ViewState not found
> Following that, no componentData is available to the Autocomplete component and no suggestions get displayed.
> For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says:
> {quote}
> Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 06:37:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 06:37:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13317)
 ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState
 id in startUpdate()
In-Reply-To: <JIRA.12518007.1383648996000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518007.1383648996000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518007.1383648996000.32926.1383651422472@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13317:
----------------------------

    Priority: Critical  (was: Major)

    
> ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13317
>                 URL: https://issues.jboss.org/browse/RF-13317
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>         Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1
>            Reporter: Matti Bickel
>            Priority: Critical
>              Labels: jsf22
>             Fix For: 4.3.5
>
>
> I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests:
> When the response comes back, the data is fine but I get a JSF error saying
> bq. During update: javax.faces.ViewState not found
> Following that, no componentData is available to the Autocomplete component and no suggestions get displayed.
> For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says:
> {quote}
> Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 06:43:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 06:43:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269000.32935.1383651782084@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850808#comment-12850808 ] 

Luk?? Fry? commented on RF-13316:
---------------------------------

Hey Jonas, does this answer your concerns?

http://stackoverflow.com/questions/12974115/to-open-pdf-file-in-iframe


----

Please, avoid posting general questions that are not related to how RichFaces works.

Valid report would be "feature request" for

* New component for displaying PDF in a page

That component we could make to work in interoperable fashion with other RF components.

Otherwise please look for other ways how to consult general questions such as Stackoverflow or RichFaces forums.
                
> PDF is rendered on top of components
> ------------------------------------
>
>                 Key: RF-13316
>                 URL: https://issues.jboss.org/browse/RF-13316
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.2, 4.3.4
>         Environment: Internet Explorer with Adobe Reader plugin
>            Reporter: Jon?? Trantina
>         Attachments: correct.jpg, incorrect.jpg, reproducer.zip
>
>
> If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
> Take a look at images attached to this case, also there is a reproducer app attached.
> This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
> Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 06:43:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 06:43:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269000.32938.1383651782244@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13316.
-----------------------------

      Assignee: Luk?? Fry?
    Resolution: Rejected


Rejecting as this is not a RichFaces bug.
                
> PDF is rendered on top of components
> ------------------------------------
>
>                 Key: RF-13316
>                 URL: https://issues.jboss.org/browse/RF-13316
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.2, 4.3.4
>         Environment: Internet Explorer with Adobe Reader plugin
>            Reporter: Jon?? Trantina
>            Assignee: Luk?? Fry?
>         Attachments: correct.jpg, incorrect.jpg, reproducer.zip
>
>
> If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
> Take a look at images attached to this case, also there is a reproducer app attached.
> This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
> Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 07:34:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Jon=C3=A1=C5=A1_Trantina_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 07:34:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269000.33054.1383654842003@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850832#comment-12850832 ] 

Jon?? Trantina commented on RF-13316:
-------------------------------------

I don't think you understand the issue. The issue is not displaying the PDF itself, it is that some component are not rendered correctly when the PDF is displayed. E.g. You have a page with rich:popupPanel as seen in the correct.jpg. But when you add the PDF, the popupPanel is no longer rendered correctly, even with the overlapEmbedObjects enabled (which I believe is just the usercase for this feature), as seen in the incorrect.jpg. Do you suggest RichFaces components are not supported in this usecase?
                
> PDF is rendered on top of components
> ------------------------------------
>
>                 Key: RF-13316
>                 URL: https://issues.jboss.org/browse/RF-13316
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.2, 4.3.4
>         Environment: Internet Explorer with Adobe Reader plugin
>            Reporter: Jon?? Trantina
>            Assignee: Luk?? Fry?
>         Attachments: correct.jpg, incorrect.jpg, reproducer.zip
>
>
> If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
> Take a look at images attached to this case, also there is a reproducer app attached.
> This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
> Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 10:05:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 10:05:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269000.34004.1383663901993@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850966#comment-12850966 ] 

Luk?? Fry? commented on RF-13316:
---------------------------------

Jonas, in my opinion, this is still issue that comes from browser-specific rendering engine and is not really an issue of RichFaces implementation. I guess other implementations of modal panels will behave same.

It is possible that there is some workaround. Could you please investigate general solutions and see if some could be applied to RichFaces?

If yes, feel free to reopen this issue.
                
> PDF is rendered on top of components
> ------------------------------------
>
>                 Key: RF-13316
>                 URL: https://issues.jboss.org/browse/RF-13316
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.2, 4.3.4
>         Environment: Internet Explorer with Adobe Reader plugin
>            Reporter: Jon?? Trantina
>            Assignee: Luk?? Fry?
>         Attachments: correct.jpg, incorrect.jpg, reproducer.zip
>
>
> If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
> Take a look at images attached to this case, also there is a reproducer app attached.
> This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
> Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 10:07:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 10:07:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13316) PDF is rendered on top
	of components
In-Reply-To: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518002.1383647269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518002.1383647269000.34007.1383664021971@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850966#comment-12850966 ] 

Luk?? Fry? edited comment on RF-13316 at 11/5/13 10:05 AM:
-----------------------------------------------------------

Jonas, in my opinion, this is still issue that comes from browser-specific rendering engine and is not really an issue of RichFaces implementation. I guess other implementations of modal panels will behave same.

It is possible that there is some workaround.

Could you please investigate general solutions and see if some could be applied to RichFaces?

If yes, feel free to reopen this issue.
                
      was (Author: lfryc):
    Jonas, in my opinion, this is still issue that comes from browser-specific rendering engine and is not really an issue of RichFaces implementation. I guess other implementations of modal panels will behave same.

It is possible that there is some workaround. Could you please investigate general solutions and see if some could be applied to RichFaces?

If yes, feel free to reopen this issue.
                  
> PDF is rendered on top of components
> ------------------------------------
>
>                 Key: RF-13316
>                 URL: https://issues.jboss.org/browse/RF-13316
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.2, 4.3.4
>         Environment: Internet Explorer with Adobe Reader plugin
>            Reporter: Jon?? Trantina
>            Assignee: Luk?? Fry?
>         Attachments: correct.jpg, incorrect.jpg, reproducer.zip
>
>
> If I try to display RichFaces components over a PDF object (either PDF in iframe, or object or embed tag) in Internet Explorer with Adobe Reader plugin, the PDF is either always on top of everything or some components are over the PDF and some are under (e.g. when using overlapEmbedObjects attribute).
> Take a look at images attached to this case, also there is a reproducer app attached.
> This seems as a  issue with Adobe Reader and IE, as in Linux environment in Chrome there is no problem with that setup, components are rendered on top, even without the overlapEmbedObjects option.
> Let me know if you need anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 12:42:04 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 12:42:04 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13318) Update Autocomplete with
 refactored Autocomplete widget
In-Reply-To: <JIRA.12518058.1383673289545@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518058.1383673289545@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518058.1383673289545.34579.1383673324344@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13318:
-------------------------------

             Summary: Update Autocomplete with refactored Autocomplete widget
                 Key: RF-13318
                 URL: https://issues.jboss.org/browse/RF-13318
             Project: RichFaces
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
            Assignee: Luk?? Fry?
             Fix For: 5.0.0.Alpha2




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 12:42:04 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 12:42:04 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13318) Update Autocomplete with
 refactored Autocomplete widget
In-Reply-To: <JIRA.12518058.1383673289000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518058.1383673289000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518058.1383673289000.34583.1383673324490@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13318:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 4

    
> Update Autocomplete with refactored Autocomplete widget
> -------------------------------------------------------
>
>                 Key: RF-13318
>                 URL: https://issues.jboss.org/browse/RF-13318
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 12:44:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 12:44:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13311) Make Push independent of
	BaseComponent
In-Reply-To: <JIRA.12511012.1383558111000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511012.1383558111000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511012.1383558111000.34590.1383673442110@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13311.
-----------------------------

    Resolution: Done

    
> Make Push independent of BaseComponent
> --------------------------------------
>
>                 Key: RF-13311
>                 URL: https://issues.jboss.org/browse/RF-13311
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> Currently Push extends BaseComponent but since BaseComponent is not a part of core the extending fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 12:46:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 12:46:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13280) RF 5 packed resources
 cause conflict in RF 4.5
In-Reply-To: <JIRA.12508458.1382446287000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508458.1382446287000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508458.1382446287000.34594.1383673562804@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13280.
-----------------------------

    Resolution: Done

    
> RF 5 packed resources cause conflict in RF 4.5
> ----------------------------------------------
>
>                 Key: RF-13280
>                 URL: https://issues.jboss.org/browse/RF-13280
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Michal Petrov
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> Showcase uses resource from RF 5 core instead of using the proper ones from RF 4.5 components. (e.g. packed.js)
> The solution is to split core and ui resources in RF 5. RF 4.5 will only generate ui resources and use core resources from RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 12:46:03 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 12:46:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13280) RF 5 packed resources
 cause conflict in RF 4.5
In-Reply-To: <JIRA.12508458.1382446287000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508458.1382446287000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508458.1382446287000.34601.1383673563377@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reopened RF-13280:
-----------------------------

      Assignee: Luk?? Fry?  (was: Michal Petrov)

    
> RF 5 packed resources cause conflict in RF 4.5
> ----------------------------------------------
>
>                 Key: RF-13280
>                 URL: https://issues.jboss.org/browse/RF-13280
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> Showcase uses resource from RF 5 core instead of using the proper ones from RF 4.5 components. (e.g. packed.js)
> The solution is to split core and ui resources in RF 5. RF 4.5 will only generate ui resources and use core resources from RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 12:46:03 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 12:46:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13280) RF 5 packed resources
 cause conflict in RF 4.5
In-Reply-To: <JIRA.12508458.1382446287000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508458.1382446287000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508458.1382446287000.34606.1383673563720@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13280:
----------------------------

    Assignee: Michal Petrov  (was: Luk?? Fry?)

    
> RF 5 packed resources cause conflict in RF 4.5
> ----------------------------------------------
>
>                 Key: RF-13280
>                 URL: https://issues.jboss.org/browse/RF-13280
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Michal Petrov
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> Showcase uses resource from RF 5 core instead of using the proper ones from RF 4.5 components. (e.g. packed.js)
> The solution is to split core and ui resources in RF 5. RF 4.5 will only generate ui resources and use core resources from RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov  5 13:58:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 5 Nov 2013 13:58:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13318) Update Autocomplete with
 refactored Autocomplete widget
In-Reply-To: <JIRA.12518058.1383673289000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518058.1383673289000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518058.1383673289000.34749.1383677881943@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13318.
-----------------------------

    Resolution: Done

    
> Update Autocomplete with refactored Autocomplete widget
> -------------------------------------------------------
>
>                 Key: RF-13318
>                 URL: https://issues.jboss.org/browse/RF-13318
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 01:55:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ronny_Sch=C3=B6ne_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 01:55:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13319) Strange scroll behavier
 of rich:autocomplete field in IE9/10
In-Reply-To: <JIRA.12518095.1383720821030@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518095.1383720821030@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518095.1383720821030.35512.1383720902981@jira02.app.mwc.hst.phx2.redhat.com>

Ronny Sch?ne created RF-13319:
---------------------------------

             Summary: Strange scroll behavier of rich:autocomplete field in IE9/10
                 Key: RF-13319
                 URL: https://issues.jboss.org/browse/RF-13319
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Ronny Sch?ne


Hi

i have a strange scroll behavier in a rich:autocomplete list.

The list has a lot of elements so the list has a scrollbar.

If i open the list and scroll a little bit with the scrollbar and move the mouse to the elemets, an other element which is not within the viewport of the list is shown in the textfield.

Here is the sorce code, there is nothing special:

    <rich:autocomplete  
        id="inField"  
        requiredMessage="Add value."  
        style="vertical-align: middle"  
        mode="client" selectFirst="false"  
        showButton="true" minChars="1"  
        value="${bean.input}"  
        autocompleteList="${bean.definedInputList}"  
        onblur="#{rich:component('inField')}.hidePopup();" />  

Link to a example video: https://vimeo.com/78525787


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 07:27:02 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Wed, 6 Nov 2013 07:27:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13280) RF 5 packed resources
 cause conflict in RF 4.5
In-Reply-To: <JIRA.12508458.1382446287000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508458.1382446287000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508458.1382446287000.36298.1383740822377@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov resolved RF-13280.
--------------------------------

    Resolution: Done

    
> RF 5 packed resources cause conflict in RF 4.5
> ----------------------------------------------
>
>                 Key: RF-13280
>                 URL: https://issues.jboss.org/browse/RF-13280
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Michal Petrov
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> Showcase uses resource from RF 5 core instead of using the proper ones from RF 4.5 components. (e.g. packed.js)
> The solution is to split core and ui resources in RF 5. RF 4.5 will only generate ui resources and use core resources from RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov  6 07:57:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 07:57:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12913) Run framework QUnit
 tests using Arquillian extension
In-Reply-To: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12489457.1366021799000.36359.1383742621978@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851353#comment-12851353 ] 

Luk?? Fry? commented on RF-12913:
---------------------------------

[~bleathem] I would consider using our `src/main/js` Grunt-based infrastructure for testing framework resources such as {{richfaces.js}}.
                
> Run framework QUnit tests using Arquillian extension
> ----------------------------------------------------
>
>                 Key: RF-12913
>                 URL: https://issues.jboss.org/browse/RF-12913
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: qe, tests - functional 
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> There is Arquillian QUnit extension [1] for running QUnit tests.
> Use this extension to replace currenct HtmlUnit based runner.
> Communicate with the author to make it work and report any requests for enhancements.
> [1] https://github.com/qa/arquillian-qunit/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 07:59:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 07:59:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13304) Autocomplete: value
 change listener doesn't work
In-Reply-To: <JIRA.12509202.1383227643000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509202.1383227643000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509202.1383227643000.36364.1383742742107@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13304:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 4

    
> Autocomplete: value change listener doesn't work
> ------------------------------------------------
>
>                 Key: RF-13304
>                 URL: https://issues.jboss.org/browse/RF-13304
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19-jbossorg-1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml in Firefox 24
> # type 'h' into autocomplete
> # select 'Hawaii'
> # click outside the autocomplete so that the value is sent to the server
> # check phases panel in header
> result:
> * you can see "* 1 value changed: null -> Hawaii" and "* 2 value changed" for a short while
> * after ca. 1s yet another ajax request is done and only "* 2 value changed" is visible
> * in Chrome 30, the second ajax request is not fired
> * in Chrome 30, when you select some nonexisting value in autocomplete, e.g. "xxx", it behaves the same as Firefox 24
> * in RichFaces 4.3.4.Final, output of both listeners is visible, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 07:59:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 07:59:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13308) Autocomplete:
 clientFilterFunction doesn't work in Firefox
In-Reply-To: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509275.1383305248000.36367.1383742742271@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13308:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 4

    
> Autocomplete: clientFilterFunction doesn't work in Firefox
> ----------------------------------------------------------
>
>                 Key: RF-13308
>                 URL: https://issues.jboss.org/browse/RF-13308
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/filtering.xhtml
> # set attribute mode to "client"
> # set attribute clientFilterFunction to "customClientFilterFunction"
> # type "no" to the autocomplete
> # select "Raleigh of North Carolina"
> # click outside of autocomplete in order to send selected value to the server
> # check that output contains "North Carolina"
> result:
> * works fine in Chrome 30
> * in Firefox 24, after you type "no", popup with suggestions is not displayed
> * works fine in RichFaces 4.3.4.Final

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 07:59:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 07:59:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13309) Autocomplete doesn't
 work correctly when r:ajax bound to selectitem event
In-Reply-To: <JIRA.12509603.1383315889000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509603.1383315889000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509603.1383315889000.36371.1383742742436@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13309:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 4

    
> Autocomplete doesn't work correctly when r:ajax bound to selectitem event
> -------------------------------------------------------------------------
>
>                 Key: RF-13309
>                 URL: https://issues.jboss.org/browse/RF-13309
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 30.0.1599.114 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/ajaxOnSelectitem.xhtml
> # type "a" into autocomplete
> # select "Alabama"
> # check output below the autocomplete
> # check output of value change listener in page's header
> result:
> * there is "Your selection: alabama" below the autocomplete instead of "Your selection: Alabama" with upper case A
> * value change listener's output contains "alabama" instead of "Alabama": * 1 value changed: null -> alabama
> * it works fine on page http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml which is exactly the same but uses event=change in r:ajax
> * works fine in RichFaces 4.3.4, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 07:59:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 07:59:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13304) Autocomplete: value
 change listener doesn't work
In-Reply-To: <JIRA.12509202.1383227643000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509202.1383227643000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509202.1383227643000.36374.1383742742589@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13304:
-------------------------------

    Assignee: Luk?? Fry?

    
> Autocomplete: value change listener doesn't work
> ------------------------------------------------
>
>                 Key: RF-13304
>                 URL: https://issues.jboss.org/browse/RF-13304
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19-jbossorg-1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml in Firefox 24
> # type 'h' into autocomplete
> # select 'Hawaii'
> # click outside the autocomplete so that the value is sent to the server
> # check phases panel in header
> result:
> * you can see "* 1 value changed: null -> Hawaii" and "* 2 value changed" for a short while
> * after ca. 1s yet another ajax request is done and only "* 2 value changed" is visible
> * in Chrome 30, the second ajax request is not fired
> * in Chrome 30, when you select some nonexisting value in autocomplete, e.g. "xxx", it behaves the same as Firefox 24
> * in RichFaces 4.3.4.Final, output of both listeners is visible, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 07:59:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 07:59:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13308) Autocomplete:
 clientFilterFunction doesn't work in Firefox
In-Reply-To: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509275.1383305248000.36377.1383742742698@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13308:
-------------------------------

    Assignee: Luk?? Fry?

    
> Autocomplete: clientFilterFunction doesn't work in Firefox
> ----------------------------------------------------------
>
>                 Key: RF-13308
>                 URL: https://issues.jboss.org/browse/RF-13308
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/filtering.xhtml
> # set attribute mode to "client"
> # set attribute clientFilterFunction to "customClientFilterFunction"
> # type "no" to the autocomplete
> # select "Raleigh of North Carolina"
> # click outside of autocomplete in order to send selected value to the server
> # check that output contains "North Carolina"
> result:
> * works fine in Chrome 30
> * in Firefox 24, after you type "no", popup with suggestions is not displayed
> * works fine in RichFaces 4.3.4.Final

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 07:59:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 07:59:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13309) Autocomplete doesn't
 work correctly when r:ajax bound to selectitem event
In-Reply-To: <JIRA.12509603.1383315889000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509603.1383315889000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509603.1383315889000.36380.1383742742797@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13309:
-------------------------------

    Assignee: Luk?? Fry?

    
> Autocomplete doesn't work correctly when r:ajax bound to selectitem event
> -------------------------------------------------------------------------
>
>                 Key: RF-13309
>                 URL: https://issues.jboss.org/browse/RF-13309
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 30.0.1599.114 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/ajaxOnSelectitem.xhtml
> # type "a" into autocomplete
> # select "Alabama"
> # check output below the autocomplete
> # check output of value change listener in page's header
> result:
> * there is "Your selection: alabama" below the autocomplete instead of "Your selection: Alabama" with upper case A
> * value change listener's output contains "alabama" instead of "Alabama": * 1 value changed: null -> alabama
> * it works fine on page http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml which is exactly the same but uses event=change in r:ajax
> * works fine in RichFaces 4.3.4, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 09:03:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 09:03:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13320) Update
 OrderingList/PickList with refactored Widgets
In-Reply-To: <JIRA.12518147.1383746573531@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518147.1383746573531@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518147.1383746573531.36589.1383746582648@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13320:
-------------------------------

             Summary: Update OrderingList/PickList with refactored Widgets
                 Key: RF-13320
                 URL: https://issues.jboss.org/browse/RF-13320
             Project: RichFaces
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
            Assignee: Luk?? Fry?
             Fix For: 5.0.0.Alpha2




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 09:05:04 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 09:05:04 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13320) Update
 OrderingList/PickList with refactored Widgets
In-Reply-To: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518147.1383746573000.36591.1383746704093@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13320:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 4

    
> Update OrderingList/PickList with refactored Widgets
> ----------------------------------------------------
>
>                 Key: RF-13320
>                 URL: https://issues.jboss.org/browse/RF-13320
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 09:09:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 09:09:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13321) Rename
 orderingList/pickList bridge and templates file names to use dashes instead
 of camelCase
In-Reply-To: <JIRA.12518149.1383746834717@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518149.1383746834717@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518149.1383746834717.36600.1383746942661@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13321:
-------------------------------

             Summary: Rename orderingList/pickList bridge and templates file names to use dashes instead of camelCase
                 Key: RF-13321
                 URL: https://issues.jboss.org/browse/RF-13321
             Project: RichFaces
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: component
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?


We have renamed orderingList/pickList to ordering-list/pick-list in RW.

I think we should update naming in RF.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 09:18:03 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Wed, 6 Nov 2013 09:18:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload
 fileuploadprogress unavailable in RF 4.5
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.36641.1383747483786@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851380#comment-12851380 ] 

Michal Petrov commented on RF-13313:
------------------------------------

The resource is being incorrectly handled

The request path looks like this:
{{/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.4089094325900078}}
but it should be this:
{{/showcase/rfRes/fileUploadProgress.jsf?ln=org.richfaces&rf_fu_uid_alt=0.4089094325900078}}
                
> rich:fileupload fileuploadprogress unavailable in RF 4.5
> --------------------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov  6 09:18:03 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Wed, 6 Nov 2013 09:18:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload
 fileuploadprogress unavailable in RF 4.5
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.36642.1383747483835@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov reassigned RF-13313:
----------------------------------

    Assignee: Michal Petrov

    
> rich:fileupload fileuploadprogress unavailable in RF 4.5
> --------------------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov  6 11:18:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 6 Nov 2013 11:18:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13321) Rename
 orderingList/pickList bridge and templates file names to use dashes instead
 of camelCase
In-Reply-To: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518149.1383746834000.37189.1383754682335@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13321:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Rename orderingList/pickList bridge and templates file names to use dashes instead of camelCase
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13321
>                 URL: https://issues.jboss.org/browse/RF-13321
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> We have renamed orderingList/pickList to ordering-list/pick-list in RW.
> I think we should update naming in RF.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 11:20:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 6 Nov 2013 11:20:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13319) Strange scroll behavier
 of rich:autocomplete field in IE9/10
In-Reply-To: <JIRA.12518095.1383720821000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518095.1383720821000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518095.1383720821000.37197.1383754802458@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13319:
-------------------------------

    Description: 
Hi

i have a strange scroll behaviour in a rich:autocomplete list.

The list has a lot of elements so the list has a scrollbar.

If i open the list and scroll a little bit with the scrollbar and move the mouse to the elements, an other element which is not within the viewport of the list is shown in the textfield.

Here is the source code, there is nothing special:

{code}
    <rich:autocomplete  
        id="inField"  
        requiredMessage="Add value."  
        style="vertical-align: middle"  
        mode="client" selectFirst="false"  
        showButton="true" minChars="1"  
        value="${bean.input}"  
        autocompleteList="${bean.definedInputList}"  
        onblur="#{rich:component('inField')}.hidePopup();" />  
{code}

Link to a example video: https://vimeo.com/78525787


  was:
Hi

i have a strange scroll behavier in a rich:autocomplete list.

The list has a lot of elements so the list has a scrollbar.

If i open the list and scroll a little bit with the scrollbar and move the mouse to the elemets, an other element which is not within the viewport of the list is shown in the textfield.

Here is the sorce code, there is nothing special:

    <rich:autocomplete  
        id="inField"  
        requiredMessage="Add value."  
        style="vertical-align: middle"  
        mode="client" selectFirst="false"  
        showButton="true" minChars="1"  
        value="${bean.input}"  
        autocompleteList="${bean.definedInputList}"  
        onblur="#{rich:component('inField')}.hidePopup();" />  

Link to a example video: https://vimeo.com/78525787



    
> Strange scroll behavier of rich:autocomplete field in IE9/10
> ------------------------------------------------------------
>
>                 Key: RF-13319
>                 URL: https://issues.jboss.org/browse/RF-13319
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Ronny Sch?ne
>
> Hi
> i have a strange scroll behaviour in a rich:autocomplete list.
> The list has a lot of elements so the list has a scrollbar.
> If i open the list and scroll a little bit with the scrollbar and move the mouse to the elements, an other element which is not within the viewport of the list is shown in the textfield.
> Here is the source code, there is nothing special:
> {code}
>     <rich:autocomplete  
>         id="inField"  
>         requiredMessage="Add value."  
>         style="vertical-align: middle"  
>         mode="client" selectFirst="false"  
>         showButton="true" minChars="1"  
>         value="${bean.input}"  
>         autocompleteList="${bean.definedInputList}"  
>         onblur="#{rich:component('inField')}.hidePopup();" />  
> {code}
> Link to a example video: https://vimeo.com/78525787

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 11:22:01 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 6 Nov 2013 11:22:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13319) Strange scroll behavier
 of rich:autocomplete field in IE9/10
In-Reply-To: <JIRA.12518095.1383720821000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518095.1383720821000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518095.1383720821000.37201.1383754921959@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13319:
-------------------------------

    Forum Reference: https://community.jboss.org/thread/234145

    
> Strange scroll behavier of rich:autocomplete field in IE9/10
> ------------------------------------------------------------
>
>                 Key: RF-13319
>                 URL: https://issues.jboss.org/browse/RF-13319
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Ronny Sch?ne
>
> Hi
> i have a strange scroll behaviour in a rich:autocomplete list.
> The list has a lot of elements so the list has a scrollbar.
> If i open the list and scroll a little bit with the scrollbar and move the mouse to the elements, an other element which is not within the viewport of the list is shown in the textfield.
> Here is the source code, there is nothing special:
> {code}
>     <rich:autocomplete  
>         id="inField"  
>         requiredMessage="Add value."  
>         style="vertical-align: middle"  
>         mode="client" selectFirst="false"  
>         showButton="true" minChars="1"  
>         value="${bean.input}"  
>         autocompleteList="${bean.definedInputList}"  
>         onblur="#{rich:component('inField')}.hidePopup();" />  
> {code}
> Link to a example video: https://vimeo.com/78525787

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 11:22:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 6 Nov 2013 11:22:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13319) Strange scroll behavier
 of rich:autocomplete field in IE9/10
In-Reply-To: <JIRA.12518095.1383720821000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518095.1383720821000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518095.1383720821000.37205.1383754922153@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13319:
-------------------------------

    Fix Version/s: 4.5-Tracking

    
> Strange scroll behavier of rich:autocomplete field in IE9/10
> ------------------------------------------------------------
>
>                 Key: RF-13319
>                 URL: https://issues.jboss.org/browse/RF-13319
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>            Reporter: Ronny Sch?ne
>             Fix For: 4.5-Tracking
>
>
> Hi
> i have a strange scroll behaviour in a rich:autocomplete list.
> The list has a lot of elements so the list has a scrollbar.
> If i open the list and scroll a little bit with the scrollbar and move the mouse to the elements, an other element which is not within the viewport of the list is shown in the textfield.
> Here is the source code, there is nothing special:
> {code}
>     <rich:autocomplete  
>         id="inField"  
>         requiredMessage="Add value."  
>         style="vertical-align: middle"  
>         mode="client" selectFirst="false"  
>         showButton="true" minChars="1"  
>         value="${bean.input}"  
>         autocompleteList="${bean.definedInputList}"  
>         onblur="#{rich:component('inField')}.hidePopup();" />  
> {code}
> Link to a example video: https://vimeo.com/78525787

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 11:22:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 6 Nov 2013 11:22:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13319) Strange scroll behavier
 of rich:autocomplete field in IE9/10
In-Reply-To: <JIRA.12518095.1383720821000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518095.1383720821000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518095.1383720821000.37203.1383754922055@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13319:
-------------------------------

    Component/s: component-input

    
> Strange scroll behavier of rich:autocomplete field in IE9/10
> ------------------------------------------------------------
>
>                 Key: RF-13319
>                 URL: https://issues.jboss.org/browse/RF-13319
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>            Reporter: Ronny Sch?ne
>
> Hi
> i have a strange scroll behaviour in a rich:autocomplete list.
> The list has a lot of elements so the list has a scrollbar.
> If i open the list and scroll a little bit with the scrollbar and move the mouse to the elements, an other element which is not within the viewport of the list is shown in the textfield.
> Here is the source code, there is nothing special:
> {code}
>     <rich:autocomplete  
>         id="inField"  
>         requiredMessage="Add value."  
>         style="vertical-align: middle"  
>         mode="client" selectFirst="false"  
>         showButton="true" minChars="1"  
>         value="${bean.input}"  
>         autocompleteList="${bean.definedInputList}"  
>         onblur="#{rich:component('inField')}.hidePopup();" />  
> {code}
> Link to a example video: https://vimeo.com/78525787

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 11:24:01 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 6 Nov 2013 11:24:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13315) bridgeBase: bears
 orderingList specific event namespacing and has wrong name of destroy
 method
In-Reply-To: <JIRA.12518001.1383645379000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518001.1383645379000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518001.1383645379000.37209.1383755041947@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13315:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> bridgeBase: bears orderingList specific event namespacing and has wrong name of destroy method
> ----------------------------------------------------------------------------------------------
>
>                 Key: RF-13315
>                 URL: https://issues.jboss.org/browse/RF-13315
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> {code}
> $('body').on("cleanDom.orderingList.bootstrap.RICH", function(event, ui) {
> {code}
> {code}
> destroy : function() {
> {code}
> should be {{_destroy}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 11:28:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 6 Nov 2013 11:28:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload
 fileuploadprogress unavailable in RF 4.5
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.37233.1383755282525@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851454#comment-12851454 ] 

Brian Leathem commented on RF-13313:
------------------------------------

Thanks for digging in Michal, do you have any idea of how to resolve this?
                
> rich:fileupload fileuploadprogress unavailable in RF 4.5
> --------------------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov  6 11:32:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 6 Nov 2013 11:32:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12913) Run framework QUnit
 tests using Arquillian extension
In-Reply-To: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12489457.1366021799000.37240.1383755522060@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851455#comment-12851455 ] 

Brian Leathem commented on RF-12913:
------------------------------------

+1 - can you change the summary and description accordingly?
                
> Run framework QUnit tests using Arquillian extension
> ----------------------------------------------------
>
>                 Key: RF-12913
>                 URL: https://issues.jboss.org/browse/RF-12913
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: qe, tests - functional 
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> There is Arquillian QUnit extension [1] for running QUnit tests.
> Use this extension to replace currenct HtmlUnit based runner.
> Communicate with the author to make it work and report any requests for enhancements.
> [1] https://github.com/qa/arquillian-qunit/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 13:19:03 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 13:19:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12913) Use Grunt/Karma to run
 tests for RichFaces bridge and core JavaScripts
In-Reply-To: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12489457.1366021799000.37590.1383761943896@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-12913:
----------------------------

    Summary: Use Grunt/Karma to run tests for RichFaces bridge and core JavaScripts  (was: Run framework QUnit tests using Arquillian extension)

    
> Use Grunt/Karma to run tests for RichFaces bridge and core JavaScripts
> ----------------------------------------------------------------------
>
>                 Key: RF-12913
>                 URL: https://issues.jboss.org/browse/RF-12913
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: qe, tests - functional 
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> There is Arquillian QUnit extension [1] for running QUnit tests.
> Use this extension to replace currenct HtmlUnit based runner.
> Communicate with the author to make it work and report any requests for enhancements.
> [1] https://github.com/qa/arquillian-qunit/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 13:21:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 13:21:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12913) Use Grunt/Karma to run
 tests for RichFaces bridge and core JavaScripts
In-Reply-To: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12489457.1366021799000.37593.1383762062016@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851497#comment-12851497 ] 

Luk?? Fry? commented on RF-12913:
---------------------------------

Automation of such a solution assumes we will integrate Grunt into our build.

We can make it part of release process so far.
                
> Use Grunt/Karma to run tests for RichFaces bridge and core JavaScripts
> ----------------------------------------------------------------------
>
>                 Key: RF-12913
>                 URL: https://issues.jboss.org/browse/RF-12913
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: qe, tests - functional 
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> There is Arquillian QUnit extension [1] for running QUnit tests.
> Use this extension to replace currenct HtmlUnit based runner.
> Communicate with the author to make it work and report any requests for enhancements.
> [1] https://github.com/qa/arquillian-qunit/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov  6 13:21:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 6 Nov 2013 13:21:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12913) Use Grunt/Karma to run
 tests for RichFaces bridge and core JavaScripts
In-Reply-To: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12489457.1366021799000.37597.1383762062147@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851497#comment-12851497 ] 

Luk?? Fry? edited comment on RF-12913 at 11/6/13 1:20 PM:
----------------------------------------------------------

Automation of such a solution assumes we will integrate Grunt build into Maven build.

We can make running of those tests part of release process so far.
                
      was (Author: lfryc):
    Automation of such a solution assumes we will integrate Grunt into our build.

We can make it part of release process so far.
                  
> Use Grunt/Karma to run tests for RichFaces bridge and core JavaScripts
> ----------------------------------------------------------------------
>
>                 Key: RF-12913
>                 URL: https://issues.jboss.org/browse/RF-12913
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: qe, tests - functional 
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> There is Arquillian QUnit extension [1] for running QUnit tests.
> Use this extension to replace currenct HtmlUnit based runner.
> Communicate with the author to make it work and report any requests for enhancements.
> [1] https://github.com/qa/arquillian-qunit/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 02:36:03 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 02:36:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638000.38336.1383809763207@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13312:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 4

    
> rich:editor doesn't work in RF 4.5
> ----------------------------------
>
>                 Key: RF-13312
>                 URL: https://issues.jboss.org/browse/RF-13312
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> The editor's UI doesn't get rendered. The rendering fails with:
> {panel}
> 10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> {panel}
> It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 02:36:03 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 02:36:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload
 fileuploadprogress unavailable in RF 4.5
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.38339.1383809763401@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13313:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 4

    
> rich:fileupload fileuploadprogress unavailable in RF 4.5
> --------------------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 03:31:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ronny_Sch=C3=B6ne_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 03:31:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13319) Strange scroll behavier
 of rich:autocomplete field in IE9/10
In-Reply-To: <JIRA.12518095.1383720821000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518095.1383720821000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518095.1383720821000.38402.1383813062025@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ronny Sch?ne updated RF-13319:
------------------------------

    Description: 
Hi

i have a strange scroll behaviour in a rich:autocomplete list.

The list has a lot of elements so the list has a scrollbar.

If i open the list and scroll a little bit with the scrollbar and move the mouse to the elements, an other element which is not within the viewport of the list is shown in the textfield and the list scrolls automatically.

Here is the source code, there is nothing special:

{code}
    <rich:autocomplete  
        id="inField"  
        requiredMessage="Add value."  
        style="vertical-align: middle"  
        mode="client" selectFirst="false"  
        showButton="true" minChars="1"  
        value="${bean.input}"  
        autocompleteList="${bean.definedInputList}"  
        onblur="#{rich:component('inField')}.hidePopup();" />  
{code}

Link to a example video: https://vimeo.com/78525787


  was:
Hi

i have a strange scroll behaviour in a rich:autocomplete list.

The list has a lot of elements so the list has a scrollbar.

If i open the list and scroll a little bit with the scrollbar and move the mouse to the elements, an other element which is not within the viewport of the list is shown in the textfield.

Here is the source code, there is nothing special:

{code}
    <rich:autocomplete  
        id="inField"  
        requiredMessage="Add value."  
        style="vertical-align: middle"  
        mode="client" selectFirst="false"  
        showButton="true" minChars="1"  
        value="${bean.input}"  
        autocompleteList="${bean.definedInputList}"  
        onblur="#{rich:component('inField')}.hidePopup();" />  
{code}

Link to a example video: https://vimeo.com/78525787



    
> Strange scroll behavier of rich:autocomplete field in IE9/10
> ------------------------------------------------------------
>
>                 Key: RF-13319
>                 URL: https://issues.jboss.org/browse/RF-13319
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>            Reporter: Ronny Sch?ne
>             Fix For: 4.5-Tracking
>
>
> Hi
> i have a strange scroll behaviour in a rich:autocomplete list.
> The list has a lot of elements so the list has a scrollbar.
> If i open the list and scroll a little bit with the scrollbar and move the mouse to the elements, an other element which is not within the viewport of the list is shown in the textfield and the list scrolls automatically.
> Here is the source code, there is nothing special:
> {code}
>     <rich:autocomplete  
>         id="inField"  
>         requiredMessage="Add value."  
>         style="vertical-align: middle"  
>         mode="client" selectFirst="false"  
>         showButton="true" minChars="1"  
>         value="${bean.input}"  
>         autocompleteList="${bean.definedInputList}"  
>         onblur="#{rich:component('inField')}.hidePopup();" />  
> {code}
> Link to a example video: https://vimeo.com/78525787

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 03:42:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 03:42:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13304) Autocomplete: value
 change listener doesn't work
In-Reply-To: <JIRA.12509202.1383227643000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509202.1383227643000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509202.1383227643000.38421.1383813722052@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13304.
-----------------------------

    Resolution: Done

    
> Autocomplete: value change listener doesn't work
> ------------------------------------------------
>
>                 Key: RF-13304
>                 URL: https://issues.jboss.org/browse/RF-13304
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19-jbossorg-1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml in Firefox 24
> # type 'h' into autocomplete
> # select 'Hawaii'
> # click outside the autocomplete so that the value is sent to the server
> # check phases panel in header
> result:
> * you can see "* 1 value changed: null -> Hawaii" and "* 2 value changed" for a short while
> * after ca. 1s yet another ajax request is done and only "* 2 value changed" is visible
> * in Chrome 30, the second ajax request is not fired
> * in Chrome 30, when you select some nonexisting value in autocomplete, e.g. "xxx", it behaves the same as Firefox 24
> * in RichFaces 4.3.4.Final, output of both listeners is visible, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 03:47:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 03:47:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13308) Autocomplete:
 clientFilterFunction doesn't work in Firefox
In-Reply-To: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509275.1383305248000.38439.1383814022683@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13308.
-----------------------------

    Resolution: Cannot Reproduce Bug


[~ppitonak], I have  checked with Firefox 24 and 25 and everything works fine.

Could you please verify?
                
> Autocomplete: clientFilterFunction doesn't work in Firefox
> ----------------------------------------------------------
>
>                 Key: RF-13308
>                 URL: https://issues.jboss.org/browse/RF-13308
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/filtering.xhtml
> # set attribute mode to "client"
> # set attribute clientFilterFunction to "customClientFilterFunction"
> # type "no" to the autocomplete
> # select "Raleigh of North Carolina"
> # click outside of autocomplete in order to send selected value to the server
> # check that output contains "North Carolina"
> result:
> * works fine in Chrome 30
> * in Firefox 24, after you type "no", popup with suggestions is not displayed
> * works fine in RichFaces 4.3.4.Final

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 03:47:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 03:47:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13308) Autocomplete:
 clientFilterFunction doesn't work in Firefox
In-Reply-To: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509275.1383305248000.38443.1383814022947@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851622#comment-12851622 ] 

Luk?? Fry? edited comment on RF-13308 at 11/7/13 3:46 AM:
----------------------------------------------------------

[~ppitonak], I have  checked with Firefox 24 and 25, following exactly the instructions you have given, and everything works fine.

Could you please verify?
                
      was (Author: lfryc):
    [~ppitonak], I have  checked with Firefox 24 and 25 and everything works fine.

Could you please verify?
                  
> Autocomplete: clientFilterFunction doesn't work in Firefox
> ----------------------------------------------------------
>
>                 Key: RF-13308
>                 URL: https://issues.jboss.org/browse/RF-13308
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/filtering.xhtml
> # set attribute mode to "client"
> # set attribute clientFilterFunction to "customClientFilterFunction"
> # type "no" to the autocomplete
> # select "Raleigh of North Carolina"
> # click outside of autocomplete in order to send selected value to the server
> # check that output contains "North Carolina"
> result:
> * works fine in Chrome 30
> * in Firefox 24, after you type "no", popup with suggestions is not displayed
> * works fine in RichFaces 4.3.4.Final

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 03:54:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 03:54:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13309) Autocomplete doesn't
 work correctly when r:ajax bound to selectitem event
In-Reply-To: <JIRA.12509603.1383315889000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509603.1383315889000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509603.1383315889000.38450.1383814442108@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13309.
-----------------------------

    Resolution: Cannot Reproduce Bug


Hey [~ppitonak], I can't reproduce this issue with Chrome 30.

Is it possible that it is already fixed?
                
> Autocomplete doesn't work correctly when r:ajax bound to selectitem event
> -------------------------------------------------------------------------
>
>                 Key: RF-13309
>                 URL: https://issues.jboss.org/browse/RF-13309
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 30.0.1599.114 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/ajaxOnSelectitem.xhtml
> # type "a" into autocomplete
> # select "Alabama"
> # check output below the autocomplete
> # check output of value change listener in page's header
> result:
> * there is "Your selection: alabama" below the autocomplete instead of "Your selection: Alabama" with upper case A
> * value change listener's output contains "alabama" instead of "Alabama": * 1 value changed: null -> alabama
> * it works fine on page http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml which is exactly the same but uses event=change in r:ajax
> * works fine in RichFaces 4.3.4, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 07:20:02 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Thu, 7 Nov 2013 07:20:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13322) Tree: selectionchange
 event fired twice inside r:region
In-Reply-To: <JIRA.12524458.1383826726260@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524458.1383826726260@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524458.1383826726260.39000.1383826802051@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13322:
----------------------------------

             Summary: Tree: selectionchange event fired twice inside r:region
                 Key: RF-13322
                 URL: https://issues.jboss.org/browse/RF-13322
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-tree
    Affects Versions: 5.0.0.Alpha1, 4.3.4
         Environment: RichFaces 4.3.4.Final-redhat-1
Metamer 4.3.5-SNAPSHOT
JBoss Application Server: Weld Integration 7.2.1.Final-redhat-10
JBoss AS 7.2.1.Final-redhat-10
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 30.0.1599.114 @ Linux x86_64
            Reporter: Pavol Pitonak


# deploy Metamer and open http://localhost:8080/metamer/faces/components/richTree/simpleSwingTreeNode.xhtml?templates=a4jRegion
# set attribute onselectionchange=alert('changed')
# select first node in tree ("Europe")

result:
* alert is displayed twice
* you can also run Metamer tests 
{code}
mvn clean verify -P jbossas-managed-7-1 -Dtest=TestTreeAttributes#testOnselectionchange -Dtemplates=a4jRegion
{code}
* all other templates work fine

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov  7 07:50:02 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Thu, 7 Nov 2013 07:50:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13289) inputspinner : setting
 the value to empty/null
In-Reply-To: <JIRA.12508761.1382687176000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508761.1382687176000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508761.1382687176000.39133.1383828602429@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak reassigned RF-13289:
----------------------------------

    Assignee: Juraj H?ska  (was: Pavol Pitonak)

    
>  inputspinner : setting the value to empty/null
> -----------------------------------------------
>
>                 Key: RF-13289
>                 URL: https://issues.jboss.org/browse/RF-13289
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.3
>            Reporter: liumin hu
>            Assignee: Juraj H?ska
>
>  can put empty/null value in a spinner, everytime the spinner changes empty to 0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 08:08:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 08:08:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13320) Update
 OrderingList/PickList with refactored Widgets
In-Reply-To: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518147.1383746573000.39157.1383829681931@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek reopened RF-13320:
------------------------------



[~lfryc] could also apply the renaming introduced with https://github.com/richwidgets/richwidgets/commit/cd7f1ac77f5298aa033d1ed182da6f694ae6b533
`_dumpState()` >>> `uiHash()` to `orderingListBridge.js`?
                
> Update OrderingList/PickList with refactored Widgets
> ----------------------------------------------------
>
>                 Key: RF-13320
>                 URL: https://issues.jboss.org/browse/RF-13320
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 08:14:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 08:14:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13320) Update
 OrderingList/PickList with refactored Widgets
In-Reply-To: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518147.1383746573000.39199.1383830042021@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921256#comment-12921256 ] 

Ji?? ?tefek edited comment on RF-13320 at 11/7/13 8:13 AM:
-----------------------------------------------------------

[~lfryc] could also apply the renaming introduced with this [commint|https://github.com/richwidgets/richwidgets/commit/cd7f1ac77f5298aa033d1ed182da6f694ae6b533] to _orderingListBridge.js_?

( renaming of _dumpState()_ to _uiHash()_ )
                
      was (Author: jstefek):
    [~lfryc] could also apply the renaming introduced with https://github.com/richwidgets/richwidgets/commit/cd7f1ac77f5298aa033d1ed182da6f694ae6b533
`_dumpState()` >>> `uiHash()` to `orderingListBridge.js`?
                  
> Update OrderingList/PickList with refactored Widgets
> ----------------------------------------------------
>
>                 Key: RF-13320
>                 URL: https://issues.jboss.org/browse/RF-13320
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 08:26:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 08:26:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13320) Update
 OrderingList/PickList with refactored Widgets
In-Reply-To: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518147.1383746573000.39291.1383830762928@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921270#comment-12921270 ] 

Luk?? Fry? commented on RF-13320:
---------------------------------

[~jstefek] could you please modify the OrderingList framework tests so that fail due to such problem?

In my opinion, there should really be a test that fails when OrderingList fails to update server-side model.
                
> Update OrderingList/PickList with refactored Widgets
> ----------------------------------------------------
>
>                 Key: RF-13320
>                 URL: https://issues.jboss.org/browse/RF-13320
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 08:42:17 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 08:42:17 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13320) Update
 OrderingList/PickList with refactored Widgets
In-Reply-To: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518147.1383746573000.39459.1383831737667@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921287#comment-12921287 ] 

Ji?? ?tefek commented on RF-13320:
----------------------------------

OK, I'll do that as a part of [RFPL-3053|https://issues.jboss.org/browse/RFPL-3053].
                
> Update OrderingList/PickList with refactored Widgets
> ----------------------------------------------------
>
>                 Key: RF-13320
>                 URL: https://issues.jboss.org/browse/RF-13320
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 09:47:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 09:47:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload -
 progress bar doesn't show up
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.39885.1383835622144@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13313:
----------------------------

    Summary: rich:fileupload - progress bar doesn't show up  (was: rich:fileupload fileuploadprogress unavailable in RF 4.5)

    
> rich:fileupload - progress bar doesn't show up
> ----------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 09:47:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 09:47:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload -
 progress bar doesn't show up
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.39888.1383835622318@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13313:
-------------------------------

    Assignee: Luk?? Fry?  (was: Michal Petrov)

    
> rich:fileupload - progress bar doesn't show up
> ----------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 09:47:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 09:47:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload -
 progress bar doesn't show up
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.39893.1383835622581@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13313:
----------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> rich:fileupload - progress bar doesn't show up
> ----------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 10:07:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 10:07:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638000.39982.1383836822115@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13312.
-----------------------------

    Resolution: Done

    
> rich:editor doesn't work in RF 4.5
> ----------------------------------
>
>                 Key: RF-13312
>                 URL: https://issues.jboss.org/browse/RF-13312
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> The editor's UI doesn't get rendered. The rendering fails with:
> {panel}
> 10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> {panel}
> It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 10:07:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 10:07:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload -
 progress bar doesn't show up
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.39985.1383836822608@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13313.
-----------------------------

    Resolution: Done

    
> rich:fileupload - progress bar doesn't show up
> ----------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 10:17:02 2013
From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 7 Nov 2013 10:17:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13154) Upgrade Atmosphere to
 1.0.17 (a4j:push fails with CNFE for
 org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6)
In-Reply-To: <JIRA.12499404.1377547327000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12499404.1377547327000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12499404.1377547327000.40054.1383837422911@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921395#comment-12921395 ] 

RH Bugzilla Integration commented on RF-13154:
----------------------------------------------

Ken Finnigan <kfinniga at redhat.com> changed the Status of [bug 1002971|https://bugzilla.redhat.com/show_bug.cgi?id=1002971] from ASSIGNED to MODIFIED
                
> Upgrade Atmosphere to 1.0.17 (a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6)
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13154
>                 URL: https://issues.jboss.org/browse/RF-13154
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.3
>         Environment: EAP 6.1.1.ER7
>            Reporter: Ken Finnigan
>            Assignee: Brian Leathem
>             Fix For: 4.3.4
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> When accessing a4j:push example in showcase on EAP 6.1.1.ER7 the network tab of the developer console in Chrome shows failed network attempts for richfaces push and the following exception in the server logs:
> {code}
> 15:21:29,295 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[AutoRegisteredPushServlet]] (http-/127.0.0.1:8080-2) JBWEB000236: Servlet.service() for servlet AutoRegisteredPushServlet threw exception: java.lang.ClassNotFoundException: org.apache.coyote.http11.upgrade.UpgradeInbound from [Module "deployment.richfaces-showcase-4.3.3.Final-jbas71.war:main" from Service Module Loader]
> 	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {code}
> Running the exact same showcase example war on EAP 6.1.0.GA works fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov  7 10:17:03 2013
From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA))
Date: Thu, 7 Nov 2013 10:17:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13154) Upgrade Atmosphere to
 1.0.17 (a4j:push fails with CNFE for
 org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6)
In-Reply-To: <JIRA.12499404.1377547327000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12499404.1377547327000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12499404.1377547327000.40059.1383837423353@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921396#comment-12921396 ] 

RH Bugzilla Integration commented on RF-13154:
----------------------------------------------

Ken Finnigan <kfinniga at redhat.com> made a comment on [bug 1002971|https://bugzilla.redhat.com/show_bug.cgi?id=1002971]

Resolved with upgrade to RichFaces 4.3.4.Final
                
> Upgrade Atmosphere to 1.0.17 (a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6)
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13154
>                 URL: https://issues.jboss.org/browse/RF-13154
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.3
>         Environment: EAP 6.1.1.ER7
>            Reporter: Ken Finnigan
>            Assignee: Brian Leathem
>             Fix For: 4.3.4
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> When accessing a4j:push example in showcase on EAP 6.1.1.ER7 the network tab of the developer console in Chrome shows failed network attempts for richfaces push and the following exception in the server logs:
> {code}
> 15:21:29,295 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[AutoRegisteredPushServlet]] (http-/127.0.0.1:8080-2) JBWEB000236: Servlet.service() for servlet AutoRegisteredPushServlet threw exception: java.lang.ClassNotFoundException: org.apache.coyote.http11.upgrade.UpgradeInbound from [Module "deployment.richfaces-showcase-4.3.3.Final-jbas71.war:main" from Service Module Loader]
> 	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {code}
> Running the exact same showcase example war on EAP 6.1.0.GA works fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov  7 10:21:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 7 Nov 2013 10:21:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13315) bridgeBase: bears
 orderingList specific event namespacing and has wrong name of destroy
 method
In-Reply-To: <JIRA.12518001.1383645379000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518001.1383645379000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518001.1383645379000.40095.1383837663362@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13315:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> bridgeBase: bears orderingList specific event namespacing and has wrong name of destroy method
> ----------------------------------------------------------------------------------------------
>
>                 Key: RF-13315
>                 URL: https://issues.jboss.org/browse/RF-13315
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> {code}
> $('body').on("cleanDom.orderingList.bootstrap.RICH", function(event, ui) {
> {code}
> {code}
> destroy : function() {
> {code}
> should be {{_destroy}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 10:21:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 7 Nov 2013 10:21:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13299) Page Fragments: added
 license headers to all sources
In-Reply-To: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509045.1383079873000.40098.1383837663533@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13299:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> Page Fragments: added license headers to all sources
> ----------------------------------------------------
>
>                 Key: RF-13299
>                 URL: https://issues.jboss.org/browse/RF-13299
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> Issue mentioned during impl review:
> https://github.com/richfaces/richfaces/pull/55

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 10:21:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 7 Nov 2013 10:21:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13300) Page Fragments: refine
	module dependencies
In-Reply-To: <JIRA.12509046.1383080055000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509046.1383080055000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509046.1383080055000.40105.1383837663893@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13300:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> Page Fragments: refine module dependencies
> ------------------------------------------
>
>                 Key: RF-13300
>                 URL: https://issues.jboss.org/browse/RF-13300
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> During the review, I have found out we may need to fine module dependencies:
> https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441
> ----
> {code}
> joda-time:2.3
> - DateTime
> commons-lang:2.6
> - Validate.isTrue
> - StringEscapeUtils.unescapeJava
> json-simple:1.1.1
> - JSONParser
> org.jodah:typetools:0.3.0
> - TypeResolver.resolveRawArguments
> {code}
> I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}.
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few suggestions for dependency free Java-unescaping.
> {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of JSR-353.
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider shading it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 10:21:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 7 Nov 2013 10:21:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13301) Favor use of Page
 Fragments in Framework Tests
In-Reply-To: <JIRA.12509047.1383080150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509047.1383080150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509047.1383080150000.40102.1383837663770@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13301:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> Favor use of Page Fragments in Framework Tests
> ----------------------------------------------
>
>                 Key: RF-13301
>                 URL: https://issues.jboss.org/browse/RF-13301
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Pavol Pitonak
>             Fix For: 5.0.0.Alpha2
>
>
> Since we have introduced Page Fragments in Alpha2, we could favor their usage in fragment tests.
> We could start to refactor tests for  components rewritten in Alpha2 and continue as we rewrite other components.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 10:21:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 7 Nov 2013 10:21:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13321) Rename
 orderingList/pickList bridge and templates file names to use dashes instead
 of camelCase
In-Reply-To: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518149.1383746834000.40107.1383837663993@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13321:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> Rename orderingList/pickList bridge and templates file names to use dashes instead of camelCase
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13321
>                 URL: https://issues.jboss.org/browse/RF-13321
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> We have renamed orderingList/pickList to ordering-list/pick-list in RW.
> I think we should update naming in RF.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 10:34:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 10:34:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13320) Update
 OrderingList/PickList with refactored Widgets
In-Reply-To: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518147.1383746573000.40161.1383838442882@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921413#comment-12921413 ] 

Luk?? Fry? commented on RF-13320:
---------------------------------

Thanks [~jstefek], nice catch btw. :-)

And don't hesitate to send a PR for such a trivial fixes!
                
> Update OrderingList/PickList with refactored Widgets
> ----------------------------------------------------
>
>                 Key: RF-13320
>                 URL: https://issues.jboss.org/browse/RF-13320
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 12:07:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 7 Nov 2013 12:07:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13320) Update
 OrderingList/PickList with refactored Widgets
In-Reply-To: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518147.1383746573000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518147.1383746573000.40462.1383844022343@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13320.
-----------------------------

    Resolution: Done

    
> Update OrderingList/PickList with refactored Widgets
> ----------------------------------------------------
>
>                 Key: RF-13320
>                 URL: https://issues.jboss.org/browse/RF-13320
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov  7 18:03:01 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 7 Nov 2013 18:03:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13322) Tree: selectionchange
 event fired twice inside r:region
In-Reply-To: <JIRA.12524458.1383826726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524458.1383826726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524458.1383826726000.41180.1383865381890@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921588#comment-12921588 ] 

Brian Leathem commented on RF-13322:
------------------------------------

[~ppitonak] is this a regression or the result of a new test?
                
> Tree: selectionchange event fired twice inside r:region
> -------------------------------------------------------
>
>                 Key: RF-13322
>                 URL: https://issues.jboss.org/browse/RF-13322
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tree
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>         Environment: RichFaces 4.3.4.Final-redhat-1
> Metamer 4.3.5-SNAPSHOT
> JBoss Application Server: Weld Integration 7.2.1.Final-redhat-10
> JBoss AS 7.2.1.Final-redhat-10
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 30.0.1599.114 @ Linux x86_64
>            Reporter: Pavol Pitonak
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTree/simpleSwingTreeNode.xhtml?templates=a4jRegion
> # set attribute onselectionchange=alert('changed')
> # select first node in tree ("Europe")
> result:
> * alert is displayed twice
> * you can also run Metamer tests 
> {code}
> mvn clean verify -P jbossas-managed-7-1 -Dtest=TestTreeAttributes#testOnselectionchange -Dtemplates=a4jRegion
> {code}
> * all other templates work fine

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 02:40:01 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 8 Nov 2013 02:40:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13322) Tree: selectionchange
 event fired twice inside r:region
In-Reply-To: <JIRA.12524458.1383826726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524458.1383826726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524458.1383826726000.41420.1383896401987@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921638#comment-12921638 ] 

Pavol Pitonak commented on RF-13322:
------------------------------------

I was able to reproduce in 4.3.4.Final so it looks like a result of a new test.
                
> Tree: selectionchange event fired twice inside r:region
> -------------------------------------------------------
>
>                 Key: RF-13322
>                 URL: https://issues.jboss.org/browse/RF-13322
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tree
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>         Environment: RichFaces 4.3.4.Final-redhat-1
> Metamer 4.3.5-SNAPSHOT
> JBoss Application Server: Weld Integration 7.2.1.Final-redhat-10
> JBoss AS 7.2.1.Final-redhat-10
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 30.0.1599.114 @ Linux x86_64
>            Reporter: Pavol Pitonak
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTree/simpleSwingTreeNode.xhtml?templates=a4jRegion
> # set attribute onselectionchange=alert('changed')
> # select first node in tree ("Europe")
> result:
> * alert is displayed twice
> * you can also run Metamer tests 
> {code}
> mvn clean verify -P jbossas-managed-7-1 -Dtest=TestTreeAttributes#testOnselectionchange -Dtemplates=a4jRegion
> {code}
> * all other templates work fine

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 03:42:02 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Fri, 8 Nov 2013 03:42:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080840@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080840@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080840.41558.1383900122407@jira02.app.mwc.hst.phx2.redhat.com>

Mohammad Weshah created RF-13323:
------------------------------------

             Summary: FileUploadEvent listener reset the list value with Viewscope
                 Key: RF-13323
                 URL: https://issues.jboss.org/browse/RF-13323
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-input
    Affects Versions: 4.3.4
         Environment: Jboss 7.1
Richfaces 4.3.4
JSF 2.1.9
 
            Reporter: Mohammad Weshah


Hello All,
i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
 
protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
  
public void FileUploadlistener(FileUploadEvent event) throws Exception {  
        UploadedFile item = event.getUploadedFile();  
        UploadedImage file = new UploadedImage();  
        file.setLength(item.getData().length);  
        file.setName(item.getName());  
        file.setData(item.getData());  
         
        files.add(file);  
      }  
 
but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
 
Regards
Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 03:55:02 2013
From: jira-events at lists.jboss.org (Balaji S (JIRA))
Date: Fri, 8 Nov 2013 03:55:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13324) Dispaly year's and
	month's as Dropdown
In-Reply-To: <JIRA.12524558.1383900897871@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524558.1383900897871@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524558.1383900897871.41575.1383900902059@jira02.app.mwc.hst.phx2.redhat.com>

Balaji S created RF-13324:
-----------------------------

             Summary: Dispaly year's and month's as Dropdown 
                 Key: RF-13324
                 URL: https://issues.jboss.org/browse/RF-13324
             Project: RichFaces
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: component
    Affects Versions: 4.3.0.Final
            Reporter: Balaji S
             Fix For: 4.3.0.Final


 
It would be better to display year's and month's as List in Rich calender like below 

 




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 03:59:01 2013
From: jira-events at lists.jboss.org (Balaji S (JIRA))
Date: Fri, 8 Nov 2013 03:59:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13324) Dispaly year's and
	month's as Dropdown
In-Reply-To: <JIRA.12524558.1383900897000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524558.1383900897000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524558.1383900897000.41593.1383901141986@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Balaji S updated RF-13324:
--------------------------

    Description: 
 
It would be better to display year's and month's as List in Rich calender like bel

 



  was:
 
It would be better to display year's and month's as List in Rich calender like below 

 





    
> Dispaly year's and month's as Dropdown 
> ---------------------------------------
>
>                 Key: RF-13324
>                 URL: https://issues.jboss.org/browse/RF-13324
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.0.Final
>            Reporter: Balaji S
>             Fix For: 4.3.0.Final
>
>
>  
> It would be better to display year's and month's as List in Rich calender like bel
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 04:01:05 2013
From: jira-events at lists.jboss.org (Balaji S (JIRA))
Date: Fri, 8 Nov 2013 04:01:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13324) Dispaly year's and
	month's as Dropdown
In-Reply-To: <JIRA.12524558.1383900897000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524558.1383900897000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524558.1383900897000.41607.1383901265334@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Balaji S updated RF-13324:
--------------------------

    Description: 
 
It would be better to display year's and month's as List in Rich calender

 



  was:
 
It would be better to display year's and month's as List in Rich calender like bel

 




    
> Dispaly year's and month's as Dropdown 
> ---------------------------------------
>
>                 Key: RF-13324
>                 URL: https://issues.jboss.org/browse/RF-13324
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.0.Final
>            Reporter: Balaji S
>             Fix For: 4.3.0.Final
>
>
>  
> It would be better to display year's and month's as List in Rich calender
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 04:49:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 8 Nov 2013 04:49:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList: onmouseout is
 triggered even when pointer button is not moved out from element
In-Reply-To: <JIRA.12524571.1383904100788@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100788@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100788.41771.1383904142075@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13325:
--------------------------------

             Summary: pickList: onmouseout is triggered even when pointer button is not moved out from element
                 Key: RF-13325
                 URL: https://issues.jboss.org/browse/RF-13325
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska


{{r:pickList}} event callback for *onmouseout* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 04:53:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 8 Nov 2013 04:53:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.41774.1383904381936@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13325:
-----------------------------

    Summary: pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element  (was: pickList: onmouseout is triggered even when pointer button is not moved out from element)

    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> {{r:pickList}} event callback for *onmouseout* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 04:53:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 8 Nov 2013 04:53:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.41776.1383904382020@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13325:
-----------------------------

    Description: {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.  (was: {{r:pickList}} event callback for *onmouseout* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.)

    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 04:53:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 8 Nov 2013 04:53:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.41777.1383904382061@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13325:
-----------------------------

    Description: 
{{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.

I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

  was:{{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.


    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 04:55:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 8 Nov 2013 04:55:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.41781.1383904501990@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921688#comment-12921688 ] 

Juraj H?ska commented on RF-13325:
----------------------------------

Just tell me if you feel like there should be two issues for these two events. IMHO it is the same issue, with the same root cause.
                
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 04:55:01 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 8 Nov 2013 04:55:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.41780.1383904501943@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13325:
-----------------------------

    Steps to Reproduce: 
# deploy metamer and load: http://localhost:8080/metamer/faces/components/richPickList/simple.xhtml
# register callback to _onmouseout_ event handler
# focus the pickList, e.g. point the mouse to source list
# move the mouse inside the source list
# see that the *onmouseout* call back is called even when the source list is not leaved

The similar apply for *onmouseover*.

  was:
# deploy metamer and load: http://localhost:8080/metamer/faces/components/richPickList/simple.xhtml
# register callback to _onmouseout_ event handler
# focus the pickList, e.g. point the mouse to source list
# move the mouse inside the source list
# see that the *onmouseout* call back is called even when the source list is not leaved


    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 07:38:02 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 8 Nov 2013 07:38:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13304) Autocomplete: value
 change listener doesn't work
In-Reply-To: <JIRA.12509202.1383227643000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509202.1383227643000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509202.1383227643000.42182.1383914282348@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13304.
------------------------------


    
> Autocomplete: value change listener doesn't work
> ------------------------------------------------
>
>                 Key: RF-13304
>                 URL: https://issues.jboss.org/browse/RF-13304
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19-jbossorg-1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml in Firefox 24
> # type 'h' into autocomplete
> # select 'Hawaii'
> # click outside the autocomplete so that the value is sent to the server
> # check phases panel in header
> result:
> * you can see "* 1 value changed: null -> Hawaii" and "* 2 value changed" for a short while
> * after ca. 1s yet another ajax request is done and only "* 2 value changed" is visible
> * in Chrome 30, the second ajax request is not fired
> * in Chrome 30, when you select some nonexisting value in autocomplete, e.g. "xxx", it behaves the same as Firefox 24
> * in RichFaces 4.3.4.Final, output of both listeners is visible, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 07:38:02 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 8 Nov 2013 07:38:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13304) Autocomplete: value
 change listener doesn't work
In-Reply-To: <JIRA.12509202.1383227643000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509202.1383227643000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509202.1383227643000.42183.1383914282402@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921753#comment-12921753 ] 

Pavol Pitonak commented on RF-13304:
------------------------------------

Verified
                
> Autocomplete: value change listener doesn't work
> ------------------------------------------------
>
>                 Key: RF-13304
>                 URL: https://issues.jboss.org/browse/RF-13304
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19-jbossorg-1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml in Firefox 24
> # type 'h' into autocomplete
> # select 'Hawaii'
> # click outside the autocomplete so that the value is sent to the server
> # check phases panel in header
> result:
> * you can see "* 1 value changed: null -> Hawaii" and "* 2 value changed" for a short while
> * after ca. 1s yet another ajax request is done and only "* 2 value changed" is visible
> * in Chrome 30, the second ajax request is not fired
> * in Chrome 30, when you select some nonexisting value in autocomplete, e.g. "xxx", it behaves the same as Firefox 24
> * in RichFaces 4.3.4.Final, output of both listeners is visible, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 07:42:02 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 8 Nov 2013 07:42:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13308) Autocomplete:
 clientFilterFunction doesn't work in Firefox
In-Reply-To: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509275.1383305248000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509275.1383305248000.42199.1383914522341@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13308.
------------------------------



I cannot reproduce anymore.
                
> Autocomplete: clientFilterFunction doesn't work in Firefox
> ----------------------------------------------------------
>
>                 Key: RF-13308
>                 URL: https://issues.jboss.org/browse/RF-13308
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/filtering.xhtml
> # set attribute mode to "client"
> # set attribute clientFilterFunction to "customClientFilterFunction"
> # type "no" to the autocomplete
> # select "Raleigh of North Carolina"
> # click outside of autocomplete in order to send selected value to the server
> # check that output contains "North Carolina"
> result:
> * works fine in Chrome 30
> * in Firefox 24, after you type "no", popup with suggestions is not displayed
> * works fine in RichFaces 4.3.4.Final

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 07:44:02 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 8 Nov 2013 07:44:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13309) Autocomplete doesn't
 work correctly when r:ajax bound to selectitem event
In-Reply-To: <JIRA.12509603.1383315889000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509603.1383315889000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509603.1383315889000.42215.1383914642119@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13309.
------------------------------



I cannot reproduce anymore.
                
> Autocomplete doesn't work correctly when r:ajax bound to selectitem event
> -------------------------------------------------------------------------
>
>                 Key: RF-13309
>                 URL: https://issues.jboss.org/browse/RF-13309
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 30.0.1599.114 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/ajaxOnSelectitem.xhtml
> # type "a" into autocomplete
> # select "Alabama"
> # check output below the autocomplete
> # check output of value change listener in page's header
> result:
> * there is "Your selection: alabama" below the autocomplete instead of "Your selection: Alabama" with upper case A
> * value change listener's output contains "alabama" instead of "Alabama": * 1 value changed: null -> alabama
> * it works fine on page http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml which is exactly the same but uses event=change in r:ajax
> * works fine in RichFaces 4.3.4, it is a regression

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 08:12:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 8 Nov 2013 08:12:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13326) pickList - caption
 attribute is not rendered in to its faces-config
In-Reply-To: <JIRA.12524612.1383916208217@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524612.1383916208217@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524612.1383916208217.42277.1383916322252@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13326:
--------------------------------

             Summary: pickList - caption attribute is not rendered in to its faces-config
                 Key: RF-13326
                 URL: https://issues.jboss.org/browse/RF-13326
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska


There should be attribute {{caption}} in the {{pickList}} faces-config. It is not.

The attribute is defined in [AbstractOrderingList|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/orderingList/AbstractOrderingList.java], which is the ancestor of {{AbstractPickList}}.

Is it caused because {{orderingList}} has also that attribute and it is somehow overriden as {{pickList}} consists from {{orderingLists}} ? - bit weird

Note that {{orderingList}} has generated {{caption}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 08:18:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 8 Nov 2013 08:18:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680834@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680834@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680834.42314.1383916682843@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13327:
--------------------------------

             Summary: pickList - setting of multiple attributes does not have any effect on the component
                 Key: RF-13327
                 URL: https://issues.jboss.org/browse/RF-13327
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska


Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).

*Buttons text*
* addAllText
* addText
* removeAllText
* removeText
* downBottomText
* downText
* upText
* upTopText

*List style*
* maxListHeight
* minListHeight
* style
* columnClasses

*Other RW options*
* switchByClick
* switchByDblClick

*Callbacks*
* onremoveitems
* value
* valueChangeListener

I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 08:44:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 08:44:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.42387.1383918242087@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13327:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 08:46:01 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 08:46:01 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13326) pickList - caption
 attribute is not rendered in to its faces-config
In-Reply-To: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524612.1383916208000.42389.1383918361936@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13326:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> pickList - caption attribute is not rendered in to its faces-config
> -------------------------------------------------------------------
>
>                 Key: RF-13326
>                 URL: https://issues.jboss.org/browse/RF-13326
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> There should be attribute {{caption}} in the {{pickList}} faces-config. It is not.
> The attribute is defined in [AbstractOrderingList|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/orderingList/AbstractOrderingList.java], which is the ancestor of {{AbstractPickList}}.
> Is it caused because {{orderingList}} has also that attribute and it is somehow overriden as {{pickList}} consists from {{orderingLists}} ? - bit weird
> Note that {{orderingList}} has generated {{caption}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 08:46:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 08:46:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.42391.1383918362068@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13325:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 08:46:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 08:46:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13324) Dispaly year's and
	month's as Dropdown
In-Reply-To: <JIRA.12524558.1383900897000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524558.1383900897000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524558.1383900897000.42393.1383918362155@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13324:
-------------------------------

    Fix Version/s: 5-Tracking
                       (was: 4.3.0.Final)

    
> Dispaly year's and month's as Dropdown 
> ---------------------------------------
>
>                 Key: RF-13324
>                 URL: https://issues.jboss.org/browse/RF-13324
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.0.Final
>            Reporter: Balaji S
>             Fix For: 5-Tracking
>
>
>  
> It would be better to display year's and month's as List in Rich calender
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 09:00:04 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:00:04 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.42420.1383919204381@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13323:
-------------------------------

    Description: 
Hello All,
i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
 
{code}
protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
  
public void FileUploadlistener(FileUploadEvent event) throws Exception {  
        UploadedFile item = event.getUploadedFile();  
        UploadedImage file = new UploadedImage();  
        file.setLength(item.getData().length);  
        file.setName(item.getName());  
        file.setData(item.getData());  
         
        files.add(file);  
      }  
{code}
 
but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
 
Regards
Wish79

  was:
Hello All,
i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
 
protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
  
public void FileUploadlistener(FileUploadEvent event) throws Exception {  
        UploadedFile item = event.getUploadedFile();  
        UploadedImage file = new UploadedImage();  
        file.setLength(item.getData().length);  
        file.setName(item.getName());  
        file.setData(item.getData());  
         
        files.add(file);  
      }  
 
but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
 
Regards
Wish79


    
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>              Labels: rich:fileUpload
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 09:00:04 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:00:04 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.42423.1383919204578@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13323:
----------------------------------

    Assignee: Pavol Pitonak


QA would you please verify whether the fileupload component works with a ViewScoped backing bean?
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Pavol Pitonak
>              Labels: rich:fileUpload
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 09:04:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:04:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13322) Tree: selectionchange
 event fired twice inside r:region
In-Reply-To: <JIRA.12524458.1383826726000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524458.1383826726000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524458.1383826726000.42446.1383919442026@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13322:
-------------------------------

    Fix Version/s: 5-Tracking

    
> Tree: selectionchange event fired twice inside r:region
> -------------------------------------------------------
>
>                 Key: RF-13322
>                 URL: https://issues.jboss.org/browse/RF-13322
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tree
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>         Environment: RichFaces 4.3.4.Final-redhat-1
> Metamer 4.3.5-SNAPSHOT
> JBoss Application Server: Weld Integration 7.2.1.Final-redhat-10
> JBoss AS 7.2.1.Final-redhat-10
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 30.0.1599.114 @ Linux x86_64
>            Reporter: Pavol Pitonak
>             Fix For: 5-Tracking
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTree/simpleSwingTreeNode.xhtml?templates=a4jRegion
> # set attribute onselectionchange=alert('changed')
> # select first node in tree ("Europe")
> result:
> * alert is displayed twice
> * you can also run Metamer tests 
> {code}
> mvn clean verify -P jbossas-managed-7-1 -Dtest=TestTreeAttributes#testOnselectionchange -Dtemplates=a4jRegion
> {code}
> * all other templates work fine

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 09:06:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:06:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13283) Move the chart
 components from the sandbox into the framework
In-Reply-To: <JIRA.12508521.1382475986000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508521.1382475986000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508521.1382475986000.42458.1383919563780@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13283:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 4, 5.0.0.Alpha2 - Sprint 5  (was: 5.0.0.Alpha2 - Sprint 4)

    
> Move the chart components from the sandbox into the framework
> -------------------------------------------------------------
>
>                 Key: RF-13283
>                 URL: https://issues.jboss.org/browse/RF-13283
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Brian Leathem
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:06:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:06:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13284) Create showcase samples
 for the chart components
In-Reply-To: <JIRA.12508522.1382476109000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508522.1382476109000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508522.1382476109000.42460.1383919563937@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13284:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 4, 5.0.0.Alpha2 - Sprint 5  (was: 5.0.0.Alpha2 - Sprint 4)

    
> Create showcase samples for the chart components
> ------------------------------------------------
>
>                 Key: RF-13284
>                 URL: https://issues.jboss.org/browse/RF-13284
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Brian Leathem
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:06:04 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:06:04 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13281) orderingList: ordering
 button's text overflows the button on Firefox
In-Reply-To: <JIRA.12508466.1382449117000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508466.1382449117000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508466.1382449117000.42462.1383919564042@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13281:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 4, 5.0.0.Alpha2 - Sprint 5  (was: 5.0.0.Alpha2 - Sprint 4)

    
> orderingList: ordering button's text overflows the button on Firefox
> --------------------------------------------------------------------
>
>                 Key: RF-13281
>                 URL: https://issues.jboss.org/browse/RF-13281
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Firefox 24
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: OL.png
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> The ordering button's text overflows the button.
> Works in Chrome.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:08:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:08:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.42472.1383919682545@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13325:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:08:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:08:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.42474.1383919682694@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13327:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:08:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:08:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13326) pickList - caption
 attribute is not rendered in to its faces-config
In-Reply-To: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524612.1383916208000.42476.1383919682855@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13326:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> pickList - caption attribute is not rendered in to its faces-config
> -------------------------------------------------------------------
>
>                 Key: RF-13326
>                 URL: https://issues.jboss.org/browse/RF-13326
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> There should be attribute {{caption}} in the {{pickList}} faces-config. It is not.
> The attribute is defined in [AbstractOrderingList|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/orderingList/AbstractOrderingList.java], which is the ancestor of {{AbstractPickList}}.
> Is it caused because {{orderingList}} has also that attribute and it is somehow overriden as {{pickList}} consists from {{orderingLists}} ? - bit weird
> Note that {{orderingList}} has generated {{caption}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:08:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:08:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13299) Page Fragments: added
 license headers to all sources
In-Reply-To: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509045.1383079873000.42479.1383919683065@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13299:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> Page Fragments: added license headers to all sources
> ----------------------------------------------------
>
>                 Key: RF-13299
>                 URL: https://issues.jboss.org/browse/RF-13299
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Issue mentioned during impl review:
> https://github.com/richfaces/richfaces/pull/55

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:08:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:08:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13300) Page Fragments: refine
	module dependencies
In-Reply-To: <JIRA.12509046.1383080055000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509046.1383080055000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509046.1383080055000.42482.1383919683179@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13300:
-------------------------------

     Original Estimate: 30 minutes
    Remaining Estimate: 30 minutes

    
> Page Fragments: refine module dependencies
> ------------------------------------------
>
>                 Key: RF-13300
>                 URL: https://issues.jboss.org/browse/RF-13300
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> During the review, I have found out we may need to fine module dependencies:
> https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441
> ----
> {code}
> joda-time:2.3
> - DateTime
> commons-lang:2.6
> - Validate.isTrue
> - StringEscapeUtils.unescapeJava
> json-simple:1.1.1
> - JSONParser
> org.jodah:typetools:0.3.0
> - TypeResolver.resolveRawArguments
> {code}
> I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}.
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few suggestions for dependency free Java-unescaping.
> {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of JSR-353.
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider shading it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:10:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:10:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13301) Favor use of Page
 Fragments in Framework Tests
In-Reply-To: <JIRA.12509047.1383080150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509047.1383080150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509047.1383080150000.42486.1383919802298@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13301:
-------------------------------

    Sprint:   (was: 5.0.0.Alpha2 - Sprint 5)

    
> Favor use of Page Fragments in Framework Tests
> ----------------------------------------------
>
>                 Key: RF-13301
>                 URL: https://issues.jboss.org/browse/RF-13301
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Pavol Pitonak
>             Fix For: 5.0.0.Alpha2
>
>
> Since we have introduced Page Fragments in Alpha2, we could favor their usage in fragment tests.
> We could start to refactor tests for  components rewritten in Alpha2 and continue as we rewrite other components.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:10:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:10:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13315) bridgeBase: bears
 orderingList specific event namespacing and has wrong name of destroy
 method
In-Reply-To: <JIRA.12518001.1383645379000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518001.1383645379000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518001.1383645379000.42488.1383919802410@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13315:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> bridgeBase: bears orderingList specific event namespacing and has wrong name of destroy method
> ----------------------------------------------------------------------------------------------
>
>                 Key: RF-13315
>                 URL: https://issues.jboss.org/browse/RF-13315
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {code}
> $('body').on("cleanDom.orderingList.bootstrap.RICH", function(event, ui) {
> {code}
> {code}
> destroy : function() {
> {code}
> should be {{_destroy}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:10:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:10:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13326) pickList - caption
 attribute is not rendered in to its faces-config
In-Reply-To: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524612.1383916208000.42494.1383919802736@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13326:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> pickList - caption attribute is not rendered in to its faces-config
> -------------------------------------------------------------------
>
>                 Key: RF-13326
>                 URL: https://issues.jboss.org/browse/RF-13326
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> There should be attribute {{caption}} in the {{pickList}} faces-config. It is not.
> The attribute is defined in [AbstractOrderingList|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/orderingList/AbstractOrderingList.java], which is the ancestor of {{AbstractPickList}}.
> Is it caused because {{orderingList}} has also that attribute and it is somehow overriden as {{pickList}} consists from {{orderingLists}} ? - bit weird
> Note that {{orderingList}} has generated {{caption}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:10:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:10:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.42492.1383919802623@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13325:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:10:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:10:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13321) Rename
 orderingList/pickList bridge and templates file names to use dashes instead
 of camelCase
In-Reply-To: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518149.1383746834000.42490.1383919802518@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13321:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> Rename orderingList/pickList bridge and templates file names to use dashes instead of camelCase
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13321
>                 URL: https://issues.jboss.org/browse/RF-13321
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> We have renamed orderingList/pickList to ordering-list/pick-list in RW.
> I think we should update naming in RF.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:10:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:10:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.42498.1383919803090@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13325:
----------------------------------

    Assignee: Brian Leathem

    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:10:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:10:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.42496.1383919802891@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13327:
-------------------------------

     Original Estimate: 1 hour
    Remaining Estimate: 1 hour

    
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:10:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:10:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.42500.1383919803263@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13327:
----------------------------------

    Assignee: Brian Leathem

    
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:10:03 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:10:03 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13326) pickList - caption
 attribute is not rendered in to its faces-config
In-Reply-To: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524612.1383916208000.42502.1383919803402@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13326:
----------------------------------

    Assignee: Brian Leathem

    
> pickList - caption attribute is not rendered in to its faces-config
> -------------------------------------------------------------------
>
>                 Key: RF-13326
>                 URL: https://issues.jboss.org/browse/RF-13326
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> There should be attribute {{caption}} in the {{pickList}} faces-config. It is not.
> The attribute is defined in [AbstractOrderingList|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/orderingList/AbstractOrderingList.java], which is the ancestor of {{AbstractPickList}}.
> Is it caused because {{orderingList}} has also that attribute and it is somehow overriden as {{pickList}} consists from {{orderingLists}} ? - bit weird
> Note that {{orderingList}} has generated {{caption}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 09:18:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 09:18:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13328) Investigate and impose
 consistent change event behaviour for all components
In-Reply-To: <JIRA.12524624.1383920246816@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524624.1383920246816@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524624.1383920246816.42545.1383920282448@jira02.app.mwc.hst.phx2.redhat.com>

Brian Leathem created RF-13328:
----------------------------------

             Summary: Investigate and impose consistent change event behaviour for all components
                 Key: RF-13328
                 URL: https://issues.jboss.org/browse/RF-13328
             Project: RichFaces
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: component
            Reporter: Brian Leathem
             Fix For: 5.0.0.Alpha3




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov  8 10:42:02 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 8 Nov 2013 10:42:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13329) Delete old 4.x and below
 pickList and orderingList resources from RF5
In-Reply-To: <JIRA.12524633.1383925284927@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524633.1383925284927@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524633.1383925284927.42778.1383925322641@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13329:
--------------------------------

             Summary: Delete old 4.x and below pickList and orderingList resources from RF5
                 Key: RF-13329
                 URL: https://issues.jboss.org/browse/RF-13329
             Project: RichFaces
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska


Now it should be safe to delete the old resources for {{pickList}} and {{orderingList}}.

I mean {{.js}} and {{.ecss}} files from this folder:
https://github.com/richfaces/richfaces/tree/master/framework/src/main/resources/META-INF/resources/org.richfaces/select

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov  8 10:58:02 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 8 Nov 2013 10:58:02 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13329) Delete old 4.x and below
 pickList and orderingList resources from RF5
In-Reply-To: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524633.1383925284000.42853.1383926282116@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13329:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Delete old 4.x and below pickList and orderingList resources from RF5
> ---------------------------------------------------------------------
>
>                 Key: RF-13329
>                 URL: https://issues.jboss.org/browse/RF-13329
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> Now it should be safe to delete the old resources for {{pickList}} and {{orderingList}}.
> I mean {{.js}} and {{.ecss}} files from this folder:
> https://github.com/richfaces/richfaces/tree/master/framework/src/main/resources/META-INF/resources/org.richfaces/select

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sat Nov  9 11:30:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sat, 9 Nov 2013 11:30:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13315) bridgeBase: bears
 orderingList specific event namespacing and has wrong name of destroy
 method
In-Reply-To: <JIRA.12518001.1383645379000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518001.1383645379000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518001.1383645379000.28.1384014606463@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13315:
-------------------------------

    Assignee: Luk?? Fry?

    
> bridgeBase: bears orderingList specific event namespacing and has wrong name of destroy method
> ----------------------------------------------------------------------------------------------
>
>                 Key: RF-13315
>                 URL: https://issues.jboss.org/browse/RF-13315
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {code}
> $('body').on("cleanDom.orderingList.bootstrap.RICH", function(event, ui) {
> {code}
> {code}
> destroy : function() {
> {code}
> should be {{_destroy}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sat Nov  9 11:32:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sat, 9 Nov 2013 11:32:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13321) Rename
 orderingList/pickList bridge and templates file names to use dashes instead
 of camelCase
In-Reply-To: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518149.1383746834000.30.1384014725861@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13321:
-------------------------------

    Assignee: Luk?? Fry?

    
> Rename orderingList/pickList bridge and templates file names to use dashes instead of camelCase
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13321
>                 URL: https://issues.jboss.org/browse/RF-13321
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> We have renamed orderingList/pickList to ordering-list/pick-list in RW.
> I think we should update naming in RF.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sat Nov  9 11:32:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sat, 9 Nov 2013 11:32:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13300) Page Fragments: refine
	module dependencies
In-Reply-To: <JIRA.12509046.1383080055000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509046.1383080055000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509046.1383080055000.33.1384014726038@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13300:
-------------------------------

    Assignee: Luk?? Fry?

    
> Page Fragments: refine module dependencies
> ------------------------------------------
>
>                 Key: RF-13300
>                 URL: https://issues.jboss.org/browse/RF-13300
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> During the review, I have found out we may need to fine module dependencies:
> https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441
> ----
> {code}
> joda-time:2.3
> - DateTime
> commons-lang:2.6
> - Validate.isTrue
> - StringEscapeUtils.unescapeJava
> json-simple:1.1.1
> - JSONParser
> org.jodah:typetools:0.3.0
> - TypeResolver.resolveRawArguments
> {code}
> I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}.
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few suggestions for dependency free Java-unescaping.
> {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of JSR-353.
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider shading it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sat Nov  9 11:40:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sat, 9 Nov 2013 11:40:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13299) Page Fragments: added
 license headers to all sources
In-Reply-To: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509045.1383079873000.41.1384015206013@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13299:
-------------------------------

    Assignee: Luk?? Fry?  (was: Brian Leathem)

    
> Page Fragments: added license headers to all sources
> ----------------------------------------------------
>
>                 Key: RF-13299
>                 URL: https://issues.jboss.org/browse/RF-13299
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Issue mentioned during impl review:
> https://github.com/richfaces/richfaces/pull/55

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sat Nov  9 11:40:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sat, 9 Nov 2013 11:40:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13283) Move the chart
 components from the sandbox into the framework
In-Reply-To: <JIRA.12508521.1382475986000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508521.1382475986000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508521.1382475986000.44.1384015206177@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13283:
-------------------------------

    Assignee: Luk?? Fry?  (was: Luk?? Macko)

    
> Move the chart components from the sandbox into the framework
> -------------------------------------------------------------
>
>                 Key: RF-13283
>                 URL: https://issues.jboss.org/browse/RF-13283
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Brian Leathem
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sat Nov  9 11:40:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sat, 9 Nov 2013 11:40:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13284) Create showcase samples
 for the chart components
In-Reply-To: <JIRA.12508522.1382476109000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508522.1382476109000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508522.1382476109000.47.1384015206388@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13284:
-------------------------------

    Assignee: Luk?? Fry?  (was: Luk?? Macko)

    
> Create showcase samples for the chart components
> ------------------------------------------------
>
>                 Key: RF-13284
>                 URL: https://issues.jboss.org/browse/RF-13284
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Brian Leathem
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sat Nov  9 11:50:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sat, 9 Nov 2013 11:50:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13321) Rename bridges,
 bridge-base and templates file names to use dashes instead of
 camelCase
In-Reply-To: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518149.1383746834000.49.1384015805851@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13321:
----------------------------

    Summary: Rename bridges, bridge-base and templates file names to use dashes instead of camelCase  (was: Rename orderingList/pickList bridge and templates file names to use dashes instead of camelCase)

    
> Rename bridges, bridge-base and templates file names to use dashes instead of camelCase
> ---------------------------------------------------------------------------------------
>
>                 Key: RF-13321
>                 URL: https://issues.jboss.org/browse/RF-13321
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> We have renamed orderingList/pickList to ordering-list/pick-list in RW.
> I think we should update naming in RF.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sat Nov  9 12:42:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Sat, 9 Nov 2013 12:42:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13299) Page Fragments: added
 license headers to all sources
In-Reply-To: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509045.1383079873000.52.1384018926401@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13299:
----------------------------------

    Assignee: Brian Leathem  (was: Luk?? Fry?)

    
> Page Fragments: added license headers to all sources
> ----------------------------------------------------
>
>                 Key: RF-13299
>                 URL: https://issues.jboss.org/browse/RF-13299
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Issue mentioned during impl review:
> https://github.com/richfaces/richfaces/pull/55

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 10 09:50:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 10 Nov 2013 09:50:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13321) Rename bridges,
 bridge-base and templates file names to use dashes instead of
 camelCase
In-Reply-To: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518149.1383746834000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518149.1383746834000.180.1384095006182@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13321.
-----------------------------

    Resolution: Done

    
> Rename bridges, bridge-base and templates file names to use dashes instead of camelCase
> ---------------------------------------------------------------------------------------
>
>                 Key: RF-13321
>                 URL: https://issues.jboss.org/browse/RF-13321
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> We have renamed orderingList/pickList to ordering-list/pick-list in RW.
> I think we should update naming in RF.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 10 09:54:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 10 Nov 2013 09:54:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223318@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223318@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223318.183.1384095246262@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13330:
-------------------------------

             Summary: RichFaces.jQuery should be used in CDK templates instead of $
                 Key: RF-13330
                 URL: https://issues.jboss.org/browse/RF-13330
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?


https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44

https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 10 09:56:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 10 Nov 2013 09:56:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.185.1384095365813@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922125#comment-12922125 ] 

Luk?? Fry? commented on RF-13330:
---------------------------------

RichFaces.jQuery is too long expression considering it needs to be transfered with each request.
                
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 10 09:56:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 10 Nov 2013 09:56:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.186.1384095365872@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13330:
----------------------------

    Description: 
RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.

https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44

https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

  was:
https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44

https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92


    
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 10 10:02:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 10 Nov 2013 10:02:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13315) bridgeBase: bears
 orderingList specific event namespacing and has wrong name of destroy
 method
In-Reply-To: <JIRA.12518001.1383645379000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518001.1383645379000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518001.1383645379000.189.1384095725817@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13315.
-----------------------------

    Resolution: Done

    
> bridgeBase: bears orderingList specific event namespacing and has wrong name of destroy method
> ----------------------------------------------------------------------------------------------
>
>                 Key: RF-13315
>                 URL: https://issues.jboss.org/browse/RF-13315
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {code}
> $('body').on("cleanDom.orderingList.bootstrap.RICH", function(event, ui) {
> {code}
> {code}
> destroy : function() {
> {code}
> should be {{_destroy}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 03:11:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 11 Nov 2013 03:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.521.1384157466179@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak reassigned RF-13323:
----------------------------------

    Assignee: Ji?? ?tefek  (was: Pavol Pitonak)

    
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 06:26:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 06:26:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13299) Page Fragments: added
 license headers to all sources
In-Reply-To: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509045.1383079873000.989.1384169166313@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13299:
-------------------------------

    Assignee: Luk?? Fry?  (was: Brian Leathem)

    
> Page Fragments: added license headers to all sources
> ----------------------------------------------------
>
>                 Key: RF-13299
>                 URL: https://issues.jboss.org/browse/RF-13299
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Issue mentioned during impl review:
> https://github.com/richfaces/richfaces/pull/55

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 07:10:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 07:10:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743220@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743220@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743220.1190.1384171805941@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13331:
-------------------------------

             Summary: Move tests for Chart component from Sandbox to Framework Tests
                 Key: RF-13331
                 URL: https://issues.jboss.org/browse/RF-13331
             Project: RichFaces
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: component-output
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
            Assignee: Luk?? Macko
             Fix For: 5.0.0.Alpha2




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 07:10:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 07:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.1193.1384171806284@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13331:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 07:40:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 07:40:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13333) Charts: click server
 handlers throws exception
In-Reply-To: <JIRA.12524764.1384173557811@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524764.1384173557811@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524764.1384173557811.1288.1384173605894@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13333:
-------------------------------

             Summary: Charts: click server handlers throws exception
                 Key: RF-13333
                 URL: https://issues.jboss.org/browse/RF-13333
             Project: RichFaces
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Luk?? Fry?


Stack trace:

{code}
13:37:19,467 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-1) Error Rendering View[/richfaces/component-sample.xhtml]: javax.faces.FacesException: Error in conversion Java Object to JavaScript
	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:194) [:]
	at org.richfaces.javascript.ScriptUtils.toScript(ScriptUtils.java:241) [:]
	at org.richfaces.context.AjaxDataSerializerImpl.asString(AjaxDataSerializerImpl.java:32) [:]
	at org.richfaces.context.ExtendedPartialViewContextImpl.renderExtensions(ExtendedPartialViewContextImpl.java:531) [:]
	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:327) [:]
	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:222) [:]
	at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:391) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [:]
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardContextValve.__invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: java.lang.NoSuchMethodException: Read method for property 'JSONArray' not found
	at org.richfaces.javascript.PropertyUtils.readPropertyValue(PropertyUtils.java:74) [:]
	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:191) [:]
	... 37 more
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 07:40:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 07:40:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13332) Showcase: update what
 components are new in 5.0 Alpha2
In-Reply-To: <JIRA.12524763.1384173502298@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524763.1384173502298@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524763.1384173502298.1287.1384173605843@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13332:
-------------------------------

             Summary: Showcase: update what components are new in 5.0 Alpha2
                 Key: RF-13332
                 URL: https://issues.jboss.org/browse/RF-13332
             Project: RichFaces
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: showcase
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
            Assignee: Luk?? Fry?
             Fix For: 5.0.0.Alpha2




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 07:44:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 07:44:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13333) Charts: click server
 handlers throws exception
In-Reply-To: <JIRA.12524764.1384173557000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524764.1384173557000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524764.1384173557000.1299.1384173846051@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13333:
----------------------------

        Fix Version/s: 5.0.0.Alpha2
          Description: 
Steps to reproduce:

1. open r:chart -> Event handling demo
http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky
2. click on one of points on the chart
FAIL: there is an error in the server console

{{NoSuchMethodException: Read method for property 'JSONArray' not found}}

Stack trace:

{code}
13:37:19,467 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-1) Error Rendering View[/richfaces/component-sample.xhtml]: javax.faces.FacesException: Error in conversion Java Object to JavaScript
	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:194) [:]
	at org.richfaces.javascript.ScriptUtils.toScript(ScriptUtils.java:241) [:]
	at org.richfaces.context.AjaxDataSerializerImpl.asString(AjaxDataSerializerImpl.java:32) [:]
	at org.richfaces.context.ExtendedPartialViewContextImpl.renderExtensions(ExtendedPartialViewContextImpl.java:531) [:]
	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:327) [:]
	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:222) [:]
	at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:391) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [:]
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardContextValve.__invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: java.lang.NoSuchMethodException: Read method for property 'JSONArray' not found
	at org.richfaces.javascript.PropertyUtils.readPropertyValue(PropertyUtils.java:74) [:]
	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:191) [:]
	... 37 more
{code}

  was:
Stack trace:

{code}
13:37:19,467 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-1) Error Rendering View[/richfaces/component-sample.xhtml]: javax.faces.FacesException: Error in conversion Java Object to JavaScript
	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:194) [:]
	at org.richfaces.javascript.ScriptUtils.toScript(ScriptUtils.java:241) [:]
	at org.richfaces.context.AjaxDataSerializerImpl.asString(AjaxDataSerializerImpl.java:32) [:]
	at org.richfaces.context.ExtendedPartialViewContextImpl.renderExtensions(ExtendedPartialViewContextImpl.java:531) [:]
	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:327) [:]
	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:222) [:]
	at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:391) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [:]
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardContextValve.__invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: java.lang.NoSuchMethodException: Read method for property 'JSONArray' not found
	at org.richfaces.javascript.PropertyUtils.readPropertyValue(PropertyUtils.java:74) [:]
	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:191) [:]
	... 37 more
{code}

             Assignee: Luk?? Macko
    Affects Version/s: 5.0.0.Alpha2
          Component/s: component-output

    
> Charts: click server handlers throws exception
> ----------------------------------------------
>
>                 Key: RF-13333
>                 URL: https://issues.jboss.org/browse/RF-13333
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>
> Steps to reproduce:
> 1. open r:chart -> Event handling demo
> http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky
> 2. click on one of points on the chart
> FAIL: there is an error in the server console
> {{NoSuchMethodException: Read method for property 'JSONArray' not found}}
> Stack trace:
> {code}
> 13:37:19,467 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-1) Error Rendering View[/richfaces/component-sample.xhtml]: javax.faces.FacesException: Error in conversion Java Object to JavaScript
> 	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:194) [:]
> 	at org.richfaces.javascript.ScriptUtils.toScript(ScriptUtils.java:241) [:]
> 	at org.richfaces.context.AjaxDataSerializerImpl.asString(AjaxDataSerializerImpl.java:32) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.renderExtensions(ExtendedPartialViewContextImpl.java:531) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:327) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:222) [:]
> 	at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:391) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [:]
> 	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardContextValve.__invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java) [jbossweb-7.0.13.Final.jar:]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> 	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: java.lang.NoSuchMethodException: Read method for property 'JSONArray' not found
> 	at org.richfaces.javascript.PropertyUtils.readPropertyValue(PropertyUtils.java:74) [:]
> 	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:191) [:]
> 	... 37 more
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 07:46:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 07:46:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13332) Showcase: update what
 components are new in 5.0 Alpha2
In-Reply-To: <JIRA.12524763.1384173502000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524763.1384173502000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524763.1384173502000.1310.1384173965839@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13332:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> Showcase: update what components are new in 5.0 Alpha2
> ------------------------------------------------------
>
>                 Key: RF-13332
>                 URL: https://issues.jboss.org/browse/RF-13332
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 07:46:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 07:46:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13333) Charts: click server
 handlers throws exception
In-Reply-To: <JIRA.12524764.1384173557000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524764.1384173557000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524764.1384173557000.1313.1384173965962@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13333:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> Charts: click server handlers throws exception
> ----------------------------------------------
>
>                 Key: RF-13333
>                 URL: https://issues.jboss.org/browse/RF-13333
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>
> Steps to reproduce:
> 1. open r:chart -> Event handling demo
> http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky
> 2. click on one of points on the chart
> FAIL: there is an error in the server console
> {{NoSuchMethodException: Read method for property 'JSONArray' not found}}
> Stack trace:
> {code}
> 13:37:19,467 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-1) Error Rendering View[/richfaces/component-sample.xhtml]: javax.faces.FacesException: Error in conversion Java Object to JavaScript
> 	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:194) [:]
> 	at org.richfaces.javascript.ScriptUtils.toScript(ScriptUtils.java:241) [:]
> 	at org.richfaces.context.AjaxDataSerializerImpl.asString(AjaxDataSerializerImpl.java:32) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.renderExtensions(ExtendedPartialViewContextImpl.java:531) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:327) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:222) [:]
> 	at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:391) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [:]
> 	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardContextValve.__invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java) [jbossweb-7.0.13.Final.jar:]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> 	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: java.lang.NoSuchMethodException: Read method for property 'JSONArray' not found
> 	at org.richfaces.javascript.PropertyUtils.readPropertyValue(PropertyUtils.java:74) [:]
> 	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:191) [:]
> 	... 37 more
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 08:48:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 08:48:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to
	1.10.3
In-Reply-To: <JIRA.12524778.1384177649551@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524778.1384177649551@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524778.1384177649551.1454.1384177686298@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13334:
-------------------------------

             Summary: Upgrade jQuery UI to 1.10.3
                 Key: RF-13334
                 URL: https://issues.jboss.org/browse/RF-13334
             Project: RichFaces
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: third-party
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?


RichWidgets issue:


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 08:48:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 08:48:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to
	1.10.3
In-Reply-To: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524778.1384177649000.1457.1384177686393@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13334:
----------------------------

    Description: 
RichWidgets issue:
https://github.com/richwidgets/richwidgets/issues/99


  was:
RichWidgets issue:



    
> Upgrade jQuery UI to 1.10.3
> ---------------------------
>
>                 Key: RF-13334
>                 URL: https://issues.jboss.org/browse/RF-13334
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> RichWidgets issue:
> https://github.com/richwidgets/richwidgets/issues/99

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 09:11:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 09:11:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to
	1.10.3
In-Reply-To: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524778.1384177649000.1488.1384179065878@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922349#comment-12922349 ] 

Luk?? Fry? commented on RF-13334:
---------------------------------

Opened feature branch:
https://github.com/richfaces/richfaces/tree/RF-13334-upgrade-jquery-ui-1-10-3

DND test fails:
{code}
Tests in error: 
  test_dnd(org.richfaces.ui.drag.ITDnd): Request type 'XHR' was expected, but type 'NONE' was done instead

Tests run: 38, Failures: 0, Errors: 1, Skipped: 4
{code}
                
> Upgrade jQuery UI to 1.10.3
> ---------------------------
>
>                 Key: RF-13334
>                 URL: https://issues.jboss.org/browse/RF-13334
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> RichWidgets issue:
> https://github.com/richwidgets/richwidgets/issues/99

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 09:17:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 09:17:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to
	1.10.3
In-Reply-To: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524778.1384177649000.1508.1384179425873@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922349#comment-12922349 ] 

Luk?? Fry? edited comment on RF-13334 at 11/11/13 9:15 AM:
-----------------------------------------------------------

Opened feature branch:
https://github.com/richfaces/richfaces/tree/RF-13334-upgrade-jquery-ui-1-10-3

DND test fails:
{code}
Tests in error: 
  test_dnd(org.richfaces.ui.drag.ITDnd): Request type 'XHR' was expected, but type 'NONE' was done instead

Tests run: 38, Failures: 0, Errors: 1, Skipped: 4
{code}

The DND demo in showcase works for first drag-drop action, but then it fails to start dragging.
                
      was (Author: lfryc):
    Opened feature branch:
https://github.com/richfaces/richfaces/tree/RF-13334-upgrade-jquery-ui-1-10-3

DND test fails:
{code}
Tests in error: 
  test_dnd(org.richfaces.ui.drag.ITDnd): Request type 'XHR' was expected, but type 'NONE' was done instead

Tests run: 38, Failures: 0, Errors: 1, Skipped: 4
{code}
                  
> Upgrade jQuery UI to 1.10.3
> ---------------------------
>
>                 Key: RF-13334
>                 URL: https://issues.jboss.org/browse/RF-13334
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> RichWidgets issue:
> https://github.com/richwidgets/richwidgets/issues/99

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 09:37:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 11 Nov 2013 09:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13332) Showcase: update what
 components are new in 5.0 Alpha2
In-Reply-To: <JIRA.12524763.1384173502000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524763.1384173502000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524763.1384173502000.1569.1384180626059@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13332.
-----------------------------

    Resolution: Done

    
> Showcase: update what components are new in 5.0 Alpha2
> ------------------------------------------------------
>
>                 Key: RF-13332
>                 URL: https://issues.jboss.org/browse/RF-13332
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 09:59:05 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Mon, 11 Nov 2013 09:59:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13292) Autocomplete: up and
 down arrow keys not working in Opera!
In-Reply-To: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508918.1383023336000.1630.1384181945887@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov reassigned RF-13292:
----------------------------------

    Assignee: Michal Petrov

    
> Autocomplete: up and down arrow keys not working in Opera!
> ----------------------------------------------------------
>
>                 Key: RF-13292
>                 URL: https://issues.jboss.org/browse/RF-13292
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Michal Petrov
>             Fix For: 4.5-Tracking
>
>
> Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 11 10:01:06 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Mon, 11 Nov 2013 10:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13292) Autocomplete: up and
 down arrow keys not working in Opera!
In-Reply-To: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508918.1383023336000.1636.1384182066143@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov updated RF-13292:
-------------------------------

    Component/s: component-input

    
> Autocomplete: up and down arrow keys not working in Opera!
> ----------------------------------------------------------
>
>                 Key: RF-13292
>                 URL: https://issues.jboss.org/browse/RF-13292
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Michal Petrov
>             Fix For: 4.5-Tracking
>
>
> Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 11 10:05:06 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Mon, 11 Nov 2013 10:05:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13292) Autocomplete: up and
 down arrow keys not working in Opera!
In-Reply-To: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508918.1383023336000.1645.1384182306507@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922374#comment-12922374 ] 

Michal Petrov commented on RF-13292:
------------------------------------

Looks like Opera 12.10 decided to fix its odd behaviour of keydown/keypressed. This also affects {{list}} and {{inputBase}}.
                
> Autocomplete: up and down arrow keys not working in Opera!
> ----------------------------------------------------------
>
>                 Key: RF-13292
>                 URL: https://issues.jboss.org/browse/RF-13292
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Michal Petrov
>             Fix For: 4.5-Tracking
>
>
> Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 11 10:13:06 2013
From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA))
Date: Mon, 11 Nov 2013 10:13:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13216) PoupPanel doesn't
 disappear when rendered="false" and rerender it.
In-Reply-To: <JIRA.12501363.1380018548000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501363.1380018548000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501363.1380018548000.1705.1384182786599@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922383#comment-12922383 ] 

RH Bugzilla Integration commented on RF-13216:
----------------------------------------------

Jiri Pallich <jpallich at redhat.com> changed the Status of [bug 1011466|https://bugzilla.redhat.com/show_bug.cgi?id=1011466] from NEW to ASSIGNED
                
> PoupPanel doesn't disappear when rendered="false" and rerender it.
> ------------------------------------------------------------------
>
>                 Key: RF-13216
>                 URL: https://issues.jboss.org/browse/RF-13216
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 4.3.3
>            Reporter: Takayuki Konishi
>              Labels: gss
>         Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip
>
>
> If you use the richfaces popupPanel in the default  domElementAttachment="body" mode it will not disappear under specific conditions.
> {code:xml} 
>     <h:body title="page 1">
>         <a4j:outputPanel id="myPanel">
>             <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}">
>                 <h:form>
>                     <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/>
>                 </h:form>
>             </rich:popupPanel>
>             <h:form>
>                 <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/>
>             </h:form>
>         </a4j:outputPanel>
>     </h:body>
> {code} 
> In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. 
> Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final.
> Note:
> In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 11 13:42:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 11 Nov 2013 13:42:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13333) Charts: click server
 handlers throws exception
In-Reply-To: <JIRA.12524764.1384173557000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524764.1384173557000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524764.1384173557000.2396.1384195326467@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13333:
-------------------------------

    Priority: Critical  (was: Major)

    
> Charts: click server handlers throws exception
> ----------------------------------------------
>
>                 Key: RF-13333
>                 URL: https://issues.jboss.org/browse/RF-13333
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> Steps to reproduce:
> 1. open r:chart -> Event handling demo
> http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky
> 2. click on one of points on the chart
> FAIL: there is an error in the server console
> {{NoSuchMethodException: Read method for property 'JSONArray' not found}}
> Stack trace:
> {code}
> 13:37:19,467 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-1) Error Rendering View[/richfaces/component-sample.xhtml]: javax.faces.FacesException: Error in conversion Java Object to JavaScript
> 	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:194) [:]
> 	at org.richfaces.javascript.ScriptUtils.toScript(ScriptUtils.java:241) [:]
> 	at org.richfaces.context.AjaxDataSerializerImpl.asString(AjaxDataSerializerImpl.java:32) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.renderExtensions(ExtendedPartialViewContextImpl.java:531) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:327) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:222) [:]
> 	at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:391) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [:]
> 	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardContextValve.__invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java) [jbossweb-7.0.13.Final.jar:]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> 	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: java.lang.NoSuchMethodException: Read method for property 'JSONArray' not found
> 	at org.richfaces.javascript.PropertyUtils.readPropertyValue(PropertyUtils.java:74) [:]
> 	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:191) [:]
> 	... 37 more
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 13:47:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 11 Nov 2013 13:47:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.2401.1384195626016@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922486#comment-12922486 ] 

Brian Leathem commented on RF-13330:
------------------------------------

Can you suggest an alternative?  IMO it's a small fraction of the payload, and shaving a few characters off isn't worth the cost of increased obscurity.
                
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 13:47:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 11 Nov 2013 13:47:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13299) Page Fragments: added
 license headers to all sources
In-Reply-To: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509045.1383079873000.2405.1384195626290@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13299:
----------------------------------

    Assignee: Brian Leathem  (was: Luk?? Fry?)

    
> Page Fragments: added license headers to all sources
> ----------------------------------------------------
>
>                 Key: RF-13299
>                 URL: https://issues.jboss.org/browse/RF-13299
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Issue mentioned during impl review:
> https://github.com/richfaces/richfaces/pull/55

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 13:49:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 11 Nov 2013 13:49:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13299) Page Fragments: added
 license headers to all sources
In-Reply-To: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509045.1383079873000.2408.1384195745878@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922487#comment-12922487 ] 

Brian Leathem commented on RF-13299:
------------------------------------

[~lfryc] Assigning to me.
                
> Page Fragments: added license headers to all sources
> ----------------------------------------------------
>
>                 Key: RF-13299
>                 URL: https://issues.jboss.org/browse/RF-13299
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Issue mentioned during impl review:
> https://github.com/richfaces/richfaces/pull/55

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 13:56:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 11 Nov 2013 13:56:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to
	1.10.3
In-Reply-To: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524778.1384177649000.2410.1384196165784@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13334:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Upgrade jQuery UI to 1.10.3
> ---------------------------
>
>                 Key: RF-13334
>                 URL: https://issues.jboss.org/browse/RF-13334
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> RichWidgets issue:
> https://github.com/richwidgets/richwidgets/issues/99

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 11 13:58:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 11 Nov 2013 13:58:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to
	1.10.3
In-Reply-To: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524778.1384177649000.2412.1384196285844@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922488#comment-12922488 ] 

Brian Leathem commented on RF-13334:
------------------------------------

Scheduling to 5.0.0.Alpha2 for further investigation.
                
> Upgrade jQuery UI to 1.10.3
> ---------------------------
>
>                 Key: RF-13334
>                 URL: https://issues.jboss.org/browse/RF-13334
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> RichWidgets issue:
> https://github.com/richwidgets/richwidgets/issues/99

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 02:35:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 02:35:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.2922.1384241705958@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922613#comment-12922613 ] 

Luk?? Fry? commented on RF-13330:
---------------------------------

We could hook into JSF DOM update process and replace $ reference in time of updating JSF component.
It would probably bring more issues than savings.
                
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:04:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:04:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13300) Page Fragments: refine
	module dependencies
In-Reply-To: <JIRA.12509046.1383080055000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509046.1383080055000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509046.1383080055000.2971.1384243446001@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13300:
----------------------------

    Description: 
During the review, I have found out we may need to fine module dependencies:

https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441

----

{code}
joda-time:2.3
- DateTime

commons-lang:2.6
- Validate.isTrue
- StringEscapeUtils.unescapeJava

json-simple:1.1.1
- JSONParser

org.jodah:typetools:0.3.0
- TypeResolver.resolveRawArguments
{code}

I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}.

I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.

I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].

{{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html].

I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/].

  was:
During the review, I have found out we may need to fine module dependencies:

https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441

----

{code}
joda-time:2.3
- DateTime

commons-lang:2.6
- Validate.isTrue
- StringEscapeUtils.unescapeJava

json-simple:1.1.1
- JSONParser

org.jodah:typetools:0.3.0
- TypeResolver.resolveRawArguments
{code}

I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}.

I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.

I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few suggestions for dependency free Java-unescaping.

{{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of JSR-353.

I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider shading it.


    
> Page Fragments: refine module dependencies
> ------------------------------------------
>
>                 Key: RF-13300
>                 URL: https://issues.jboss.org/browse/RF-13300
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> During the review, I have found out we may need to fine module dependencies:
> https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441
> ----
> {code}
> joda-time:2.3
> - DateTime
> commons-lang:2.6
> - Validate.isTrue
> - StringEscapeUtils.unescapeJava
> json-simple:1.1.1
> - JSONParser
> org.jodah:typetools:0.3.0
> - TypeResolver.resolveRawArguments
> {code}
> I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}.
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].
> {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html].
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:04:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:04:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid
 of commons-lang dependency
In-Reply-To: <JIRA.12524849.1384243427819@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524849.1384243427819@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524849.1384243427819.2979.1384243446579@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13335:
-------------------------------

             Summary: Page fragments: get rid of commons-lang dependency
                 Key: RF-13335
                 URL: https://issues.jboss.org/browse/RF-13335
             Project: RichFaces
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: page-fragments
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
            Assignee: Luk?? Fry?
             Fix For: 5.0.0.Alpha2




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:04:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:04:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid
 of commons-lang dependency
In-Reply-To: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524849.1384243427000.2981.1384243446694@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13335:
----------------------------

    Description: 
I didn't found reason to leave Validate.isTrue - this should be replaced by more verbose but dependency free code.
I did some googling for alternatives to StringEscapeUtils.unescapeJava and found out few suggestions for dependency free Java-unescaping.

    
> Page fragments: get rid of commons-lang dependency
> --------------------------------------------------
>
>                 Key: RF-13335
>                 URL: https://issues.jboss.org/browse/RF-13335
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I didn't found reason to leave Validate.isTrue - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to StringEscapeUtils.unescapeJava and found out few suggestions for dependency free Java-unescaping.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:06:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:06:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid
 of commons-lang dependency
In-Reply-To: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524849.1384243427000.2984.1384243566347@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13335:
----------------------------

    Description: 
I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.

I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].

  was:
I didn't found reason to leave Validate.isTrue - this should be replaced by more verbose but dependency free code.
I did some googling for alternatives to StringEscapeUtils.unescapeJava and found out few suggestions for dependency free Java-unescaping.


    
> Page fragments: get rid of commons-lang dependency
> --------------------------------------------------
>
>                 Key: RF-13335
>                 URL: https://issues.jboss.org/browse/RF-13335
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:06:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:06:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13336) Page fragments: get rid
 of json-simple dependency
In-Reply-To: <JIRA.12524850.1384243485696@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524850.1384243485696@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524850.1384243485696.2985.1384243566405@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13336:
-------------------------------

             Summary: Page fragments: get rid of json-simple dependency
                 Key: RF-13336
                 URL: https://issues.jboss.org/browse/RF-13336
             Project: RichFaces
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: page-fragments
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
            Assignee: Luk?? Fry?
             Fix For: 5.0.0.Alpha2




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:06:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:06:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13337) Page fragments: get rid
 of typetools dependency
In-Reply-To: <JIRA.12524851.1384243549274@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524851.1384243549274@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524851.1384243549274.2990.1384243566654@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13337:
-------------------------------

             Summary: Page fragments: get rid of typetools dependency
                 Key: RF-13337
                 URL: https://issues.jboss.org/browse/RF-13337
             Project: RichFaces
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: page-fragments
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
            Assignee: Luk?? Fry?
             Fix For: 5.0.0.Alpha2




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:06:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:06:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13337) Page fragments: get rid
 of typetools dependency
In-Reply-To: <JIRA.12524851.1384243549000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524851.1384243549000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524851.1384243549000.2993.1384243566829@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13337:
----------------------------

    Description: I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/].

    
> Page fragments: get rid of typetools dependency
> -----------------------------------------------
>
>                 Key: RF-13337
>                 URL: https://issues.jboss.org/browse/RF-13337
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:08:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:08:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13336) Page fragments: get rid
 of json-simple dependency
In-Reply-To: <JIRA.12524850.1384243485000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524850.1384243485000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524850.1384243485000.2995.1384243685873@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13336:
----------------------------

    Description: {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html].

    
> Page fragments: get rid of json-simple dependency
> -------------------------------------------------
>
>                 Key: RF-13336
>                 URL: https://issues.jboss.org/browse/RF-13336
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:12:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:12:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid
 of commons-lang dependency
In-Reply-To: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524849.1384243427000.3025.1384243927018@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922625#comment-12922625 ] 

Luk?? Fry? commented on RF-13335:
---------------------------------

I came to conclusion that we should not need JSON parsing at all - in RichFaces bridgeBase, we can retrieve options using following jQuery UI widget factory invocation:

{code}
$(element).pluginName("optionName");
{code}

Unfortunately, RichFaces 4 BaseComponent doesn't allow to retrieve options at runtime.

I suggest to introduce method {{getOptions}} to [{{BaseComponent}}|https://github.com/richfaces/richfaces/blob/0855b61d55533ad9c1b31555f222608911806cb0/framework/src/main/resources/META-INF/resources/org.richfaces/common/richfaces-base-component.js#L193]:

{code}
function getOptions() {
  return this.options;
}
{code}

This would need to be introduced in both, RF 4.3, RF 4.5 and RF 5.0.
                
> Page fragments: get rid of commons-lang dependency
> --------------------------------------------------
>
>                 Key: RF-13335
>                 URL: https://issues.jboss.org/browse/RF-13335
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:14:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:14:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid
 of commons-lang dependency
In-Reply-To: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524849.1384243427000.3028.1384244045951@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922625#comment-12922625 ] 

Luk?? Fry? edited comment on RF-13335 at 11/12/13 3:12 AM:
-----------------------------------------------------------

I came to conclusion that we should not need JSON parsing at all - leveraging RichFaces 5 {{bridgeBase}}, we can retrieve options using following jQuery UI widget factory invocation:

{code}
$(element).pluginName("optionName");
{code}

Unfortunately, RichFaces 4 BaseComponent doesn't allow to retrieve options at runtime.

I suggest to introduce method {{getOptions}} to [{{BaseComponent}}|https://github.com/richfaces/richfaces/blob/0855b61d55533ad9c1b31555f222608911806cb0/framework/src/main/resources/META-INF/resources/org.richfaces/common/richfaces-base-component.js#L193]:

{code}
function getOptions() {
  return this.options;
}
{code}

This would need to be introduced in both, RF 4.3, RF 4.5 and RF 5.0.
                
      was (Author: lfryc):
    I came to conclusion that we should not need JSON parsing at all - in RichFaces bridgeBase, we can retrieve options using following jQuery UI widget factory invocation:

{code}
$(element).pluginName("optionName");
{code}

Unfortunately, RichFaces 4 BaseComponent doesn't allow to retrieve options at runtime.

I suggest to introduce method {{getOptions}} to [{{BaseComponent}}|https://github.com/richfaces/richfaces/blob/0855b61d55533ad9c1b31555f222608911806cb0/framework/src/main/resources/META-INF/resources/org.richfaces/common/richfaces-base-component.js#L193]:

{code}
function getOptions() {
  return this.options;
}
{code}

This would need to be introduced in both, RF 4.3, RF 4.5 and RF 5.0.
                  
> Page fragments: get rid of commons-lang dependency
> --------------------------------------------------
>
>                 Key: RF-13335
>                 URL: https://issues.jboss.org/browse/RF-13335
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:14:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:14:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.3031.1384244046069@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13323:
-----------------------------

    Attachment: RF-13323-SessionScoped.png
                RF-13323-ViewScoped.png

    
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:18:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:18:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13338) Page Fragments: change
 package from .tests.page.fragments.impl to .fragments
In-Reply-To: <JIRA.12524852.1384244259425@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524852.1384244259425@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524852.1384244259425.3041.1384244286305@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13338:
-------------------------------

             Summary: Page Fragments: change package from .tests.page.fragments.impl to .fragments
                 Key: RF-13338
                 URL: https://issues.jboss.org/browse/RF-13338
             Project: RichFaces
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
          Components: page-fragments
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:54:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:54:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.3154.1384246446787@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922655#comment-12922655 ] 

Ji?? ?tefek commented on RF-13323:
----------------------------------

I tried this by changing the scope of the _FileUploadBean_ with the latest RF4 showcase on AS 7.1 and EAP 6.1 and uploading the same picture for multiple times. 
I have noticed, that when the scope was @ViewScoped:
* uploaded image preview didn't show,
* and encountered an error on the server side: 
{code}
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-23) Servlet.service() for servlet Faces Servlet threw exception: java.lang.NullPointerException
	at com.sun.faces.mgbean.BeanManager$ScopeManager$ViewScopeHandler.getFromScope(BeanManager.java:563) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.mgbean.BeanManager$ScopeManager.getFromScope(BeanManager.java:477) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.mgbean.BeanManager.getBeanFromScope(BeanManager.java:240) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.ManagedBeanELResolver.resolveBean(ManagedBeanELResolver.java:242) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.ManagedBeanELResolver.getValue(ManagedBeanELResolver.java:116) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:72) [jbossweb-7.0.13.Final.jar:]
	at org.apache.el.parser.AstValue.getTarget(AstValue.java:94) [jbossweb-7.0.13.Final.jar:]
	at org.apache.el.parser.AstValue.invoke(AstValue.java:244) [jbossweb-7.0.13.Final.jar:]
	at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at org.richfaces.resource.MediaOutputResource.encode(MediaOutputResource.java:62) [richfaces-components-ui-4.3.5-20131022.221155-19.jar:4.3.5-SNAPSHOT]
	at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.3.5-20131022.070629-12.jar:4.3.5-SNAPSHOT]
	at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) [richfaces-core-impl-4.3.5-20131022.070629-12.jar:4.3.5-SNAPSHOT]
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
{code}

But the list was updated as you can see on the images I've appended here. On the images you can also see that:
* 2 request were made (bottom left),
* scope of the bean (bottom right), 
* the updated list (top right) (with or without the image preview).

[~bleathem]: there is a problem, but it seems (from the stacktrace) that the bug is in MediaOutput(?) and is connected with Showcase sample not the FileUpload component itself. In this case I can not reproduce the bug.
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:56:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Fernando_Marin=C3=B2_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:56:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4491) pickList doesn't honor
 property 'disabled' of selectItems
In-Reply-To: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12367642.1221658985000.3160.1384246566287@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922656#comment-12922656 ] 

Fernando Marin? commented on RF-4491:
-------------------------------------

I'm agree with Kloot Perwee. This s not the same bug as RF-2357, and its still there in 4.3.4 final. Please fix it because is very annoying.
                
> pickList doesn't honor property 'disabled' of selectItems
> ---------------------------------------------------------
>
>                 Key: RF-4491
>                 URL: https://issues.jboss.org/browse/RF-4491
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.2
>            Reporter: Martin H?ller
>            Assignee: Nick Belaevski
>              Labels: disabled_selectItem, pickList
>
> selectItem components have a property 'disabled' to disable selection of items. The RichFaces component pickList ignores this property. Disabled items can be selected in the source list and added to the target list.
> For documentation of the disabed property see http://java.sun.com/javaee/javaserverfaces/1.1_01/docs/api/javax/faces/model/SelectItem.html#isDisabled()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:56:08 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:56:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.3191.1384246568096@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922655#comment-12922655 ] 

Ji?? ?tefek edited comment on RF-13323 at 11/12/13 3:55 AM:
------------------------------------------------------------

I tried this by changing the scope of the _FileUploadBean_ with the latest RF4 showcase on AS 7.1 and EAP 6.1 and uploading the same picture for multiple times. 
I have noticed, that when the scope was @ViewScoped:
* uploaded image preview didn't show,
* and encountered an error on the server side: 
{code}
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-23) Servlet.service() for servlet Faces Servlet threw exception: java.lang.NullPointerException
	at com.sun.faces.mgbean.BeanManager$ScopeManager$ViewScopeHandler.getFromScope(BeanManager.java:563) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.mgbean.BeanManager$ScopeManager.getFromScope(BeanManager.java:477) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.mgbean.BeanManager.getBeanFromScope(BeanManager.java:240) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.ManagedBeanELResolver.resolveBean(ManagedBeanELResolver.java:242) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.ManagedBeanELResolver.getValue(ManagedBeanELResolver.java:116) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:72) [jbossweb-7.0.13.Final.jar:]
	at org.apache.el.parser.AstValue.getTarget(AstValue.java:94) [jbossweb-7.0.13.Final.jar:]
	at org.apache.el.parser.AstValue.invoke(AstValue.java:244) [jbossweb-7.0.13.Final.jar:]
	at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at org.richfaces.resource.MediaOutputResource.encode(MediaOutputResource.java:62) [richfaces-components-ui-4.3.5-20131022.221155-19.jar:4.3.5-SNAPSHOT]
	at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.3.5-20131022.070629-12.jar:4.3.5-SNAPSHOT]
	at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) [richfaces-core-impl-4.3.5-20131022.070629-12.jar:4.3.5-SNAPSHOT]
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
{code}

But the list was updated as you can see on the images I've appended here. On the images you can also see that:
* 2 request were made (bottom left),
* scope of the bean (bottom right), 
* the updated list (top right) (with or without the image preview).

[~bleathem]: there is a problem, but it seems (from the stacktrace) that the bug is in MediaOutput(or not?) and is connected with Showcase sample not the FileUpload component itself. In this case I can not reproduce the bug.
                
      was (Author: jstefek):
    I tried this by changing the scope of the _FileUploadBean_ with the latest RF4 showcase on AS 7.1 and EAP 6.1 and uploading the same picture for multiple times. 
I have noticed, that when the scope was @ViewScoped:
* uploaded image preview didn't show,
* and encountered an error on the server side: 
{code}
ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[Faces Servlet]] (http--127.0.0.1-8080-23) Servlet.service() for servlet Faces Servlet threw exception: java.lang.NullPointerException
	at com.sun.faces.mgbean.BeanManager$ScopeManager$ViewScopeHandler.getFromScope(BeanManager.java:563) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.mgbean.BeanManager$ScopeManager.getFromScope(BeanManager.java:477) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.mgbean.BeanManager.getBeanFromScope(BeanManager.java:240) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.ManagedBeanELResolver.resolveBean(ManagedBeanELResolver.java:242) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.ManagedBeanELResolver.getValue(ManagedBeanELResolver.java:116) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:72) [jbossweb-7.0.13.Final.jar:]
	at org.apache.el.parser.AstValue.getTarget(AstValue.java:94) [jbossweb-7.0.13.Final.jar:]
	at org.apache.el.parser.AstValue.invoke(AstValue.java:244) [jbossweb-7.0.13.Final.jar:]
	at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:39) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at org.richfaces.resource.MediaOutputResource.encode(MediaOutputResource.java:62) [richfaces-components-ui-4.3.5-20131022.221155-19.jar:4.3.5-SNAPSHOT]
	at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:188) [richfaces-core-impl-4.3.5-20131022.070629-12.jar:4.3.5-SNAPSHOT]
	at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) [richfaces-core-impl-4.3.5-20131022.070629-12.jar:4.3.5-SNAPSHOT]
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
{code}

But the list was updated as you can see on the images I've appended here. On the images you can also see that:
* 2 request were made (bottom left),
* scope of the bean (bottom right), 
* the updated list (top right) (with or without the image preview).

[~bleathem]: there is a problem, but it seems (from the stacktrace) that the bug is in MediaOutput(?) and is connected with Showcase sample not the FileUpload component itself. In this case I can not reproduce the bug.
                  
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 03:58:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 03:58:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.3196.1384246685954@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek reassigned RF-13323:
--------------------------------

    Assignee: Brian Leathem  (was: Ji?? ?tefek)

    
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Brian Leathem
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:15:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:15:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to
	1.10.3
In-Reply-To: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524778.1384177649000.3232.1384247707035@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13334:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> Upgrade jQuery UI to 1.10.3
> ---------------------------
>
>                 Key: RF-13334
>                 URL: https://issues.jboss.org/browse/RF-13334
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> RichWidgets issue:
> https://github.com/richwidgets/richwidgets/issues/99

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:19:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to
	1.10.3
In-Reply-To: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524778.1384177649000.3242.1384247946032@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13334:
----------------------------

    Sprint:   (was: 5.0.0.Alpha2 - Sprint 5)

    
> Upgrade jQuery UI to 1.10.3
> ---------------------------
>
>                 Key: RF-13334
>                 URL: https://issues.jboss.org/browse/RF-13334
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> RichWidgets issue:
> https://github.com/richwidgets/richwidgets/issues/99

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:19:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13338) Page Fragments: change
 package from .tests.page.fragments.impl to .fragments
In-Reply-To: <JIRA.12524852.1384244259000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524852.1384244259000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524852.1384244259000.3244.1384247946156@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13338:
----------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Page Fragments: change package from .tests.page.fragments.impl to .fragments
> ----------------------------------------------------------------------------
>
>                 Key: RF-13338
>                 URL: https://issues.jboss.org/browse/RF-13338
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:21:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13336) Page fragments: get rid
 of json-simple dependency
In-Reply-To: <JIRA.12524850.1384243485000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524850.1384243485000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524850.1384243485000.3248.1384248065893@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13336.
-----------------------------

    Resolution: Done

    
> Page fragments: get rid of json-simple dependency
> -------------------------------------------------
>
>                 Key: RF-13336
>                 URL: https://issues.jboss.org/browse/RF-13336
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:21:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13337) Page fragments: get rid
 of typetools dependency
In-Reply-To: <JIRA.12524851.1384243549000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524851.1384243549000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524851.1384243549000.3249.1384248065942@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13337.
-----------------------------

    Resolution: Done

    
> Page fragments: get rid of typetools dependency
> -----------------------------------------------
>
>                 Key: RF-13337
>                 URL: https://issues.jboss.org/browse/RF-13337
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:39:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:39:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: ignored
 API call .setValue('')
In-Reply-To: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509251.1383279199000.3286.1384249145915@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922677#comment-12922677 ] 

Luk?? Fry? commented on RF-13306:
---------------------------------

The patch looks good, we may consider using one of Autocomplete methods to set the value, but generally initializing the field from the DOM is a right fix.
                
> Autocomplete: ignored API call .setValue('')
> --------------------------------------------
>
>                 Key: RF-13306
>                 URL: https://issues.jboss.org/browse/RF-13306
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Luk?? Fry?
>
> All described here https://community.jboss.org/thread/233973
> I have this autocomplete component:
> {code}
> <table>   
>    <tr>   
>       <td>   
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"   
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"   
>                             autofill="false"   
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"   
>                             layout="table" value="#{autocomplete.providerName}" >   
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />   
>             <h:column>   
>                <h:outputText style="display:none;" value="#{s.id}"/>   
>                <h:outputText style="display:none;" value="#{s.realName}"/>   
>             </h:column>   
>             <h:column>   
>                <h:outputText value="#{s.name}" escape="false"/>   
>             </h:column>   
>          </rich:autocomplete>   
>       </td>   
>       <td>   
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"   
>                          alt=""/>   
>          <h:graphicImage value="/img/cancel.png"   
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"   
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>   
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>   
>       </td>   
>    </tr>   
> </table>
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And a problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
>  
> I think i found a solution
> AutocompleteBase.js has this code:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = "";  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
> i replace this code by this:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = $(rf.getDomElement(fieldId)).val();  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> and it works!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:39:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: initialize
 value from DOM (was: ignored API call .setValue(''))
In-Reply-To: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509251.1383279199000.3292.1384249146221@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13306:
----------------------------

    Summary: Autocomplete: initialize value from DOM (was: ignored API call .setValue(''))  (was: Autocomplete: ignored API call .setValue(''))

    
> Autocomplete: initialize value from DOM (was: ignored API call .setValue(''))
> -----------------------------------------------------------------------------
>
>                 Key: RF-13306
>                 URL: https://issues.jboss.org/browse/RF-13306
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Luk?? Fry?
>
> All described here https://community.jboss.org/thread/233973
> I have this autocomplete component:
> {code}
> <table>   
>    <tr>   
>       <td>   
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"   
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"   
>                             autofill="false"   
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"   
>                             layout="table" value="#{autocomplete.providerName}" >   
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />   
>             <h:column>   
>                <h:outputText style="display:none;" value="#{s.id}"/>   
>                <h:outputText style="display:none;" value="#{s.realName}"/>   
>             </h:column>   
>             <h:column>   
>                <h:outputText value="#{s.name}" escape="false"/>   
>             </h:column>   
>          </rich:autocomplete>   
>       </td>   
>       <td>   
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"   
>                          alt=""/>   
>          <h:graphicImage value="/img/cancel.png"   
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"   
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>   
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>   
>       </td>   
>    </tr>   
> </table>
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And a problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
>  
> I think i found a solution
> AutocompleteBase.js has this code:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = "";  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
> i replace this code by this:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = $(rf.getDomElement(fieldId)).val();  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> and it works!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:41:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:41:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: initialize
 value from DOM (was: ignored API call .setValue(''))
In-Reply-To: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509251.1383279199000.3295.1384249265900@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922677#comment-12922677 ] 

Luk?? Fry? edited comment on RF-13306 at 11/12/13 4:39 AM:
-----------------------------------------------------------

The patch looks good, we may consider using one of Autocomplete methods to set the value, but generally initializing the field from the DOM is a right fix.

Btw the issue with {{setValue}} is here:
https://github.com/richfaces4/components/blob/master/input/ui/src/main/resources/META-INF/resources/org.richfaces/AutocompleteBase.js#L280
                
      was (Author: lfryc):
    The patch looks good, we may consider using one of Autocomplete methods to set the value, but generally initializing the field from the DOM is a right fix.
                  
> Autocomplete: initialize value from DOM (was: ignored API call .setValue(''))
> -----------------------------------------------------------------------------
>
>                 Key: RF-13306
>                 URL: https://issues.jboss.org/browse/RF-13306
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Luk?? Fry?
>
> All described here https://community.jboss.org/thread/233973
> I have this autocomplete component:
> {code}
> <table>   
>    <tr>   
>       <td>   
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"   
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"   
>                             autofill="false"   
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"   
>                             layout="table" value="#{autocomplete.providerName}" >   
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />   
>             <h:column>   
>                <h:outputText style="display:none;" value="#{s.id}"/>   
>                <h:outputText style="display:none;" value="#{s.realName}"/>   
>             </h:column>   
>             <h:column>   
>                <h:outputText value="#{s.name}" escape="false"/>   
>             </h:column>   
>          </rich:autocomplete>   
>       </td>   
>       <td>   
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"   
>                          alt=""/>   
>          <h:graphicImage value="/img/cancel.png"   
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"   
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>   
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>   
>       </td>   
>    </tr>   
> </table>
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And a problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
>  
> I think i found a solution
> AutocompleteBase.js has this code:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = "";  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
> i replace this code by this:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = $(rf.getDomElement(fieldId)).val();  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> and it works!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:41:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:41:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: initialize
 value from DOM (was: ignored API call .setValue(''))
In-Reply-To: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509251.1383279199000.3298.1384249266064@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922678#comment-12922678 ] 

Luk?? Fry? commented on RF-13306:
---------------------------------

Considering a small scope of a fix, I suggest to include it in 4.3.5.
                
> Autocomplete: initialize value from DOM (was: ignored API call .setValue(''))
> -----------------------------------------------------------------------------
>
>                 Key: RF-13306
>                 URL: https://issues.jboss.org/browse/RF-13306
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Luk?? Fry?
>
> All described here https://community.jboss.org/thread/233973
> I have this autocomplete component:
> {code}
> <table>   
>    <tr>   
>       <td>   
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"   
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"   
>                             autofill="false"   
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"   
>                             layout="table" value="#{autocomplete.providerName}" >   
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />   
>             <h:column>   
>                <h:outputText style="display:none;" value="#{s.id}"/>   
>                <h:outputText style="display:none;" value="#{s.realName}"/>   
>             </h:column>   
>             <h:column>   
>                <h:outputText value="#{s.name}" escape="false"/>   
>             </h:column>   
>          </rich:autocomplete>   
>       </td>   
>       <td>   
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"   
>                          alt=""/>   
>          <h:graphicImage value="/img/cancel.png"   
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"   
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>   
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>   
>       </td>   
>    </tr>   
> </table>
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And a problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
>  
> I think i found a solution
> AutocompleteBase.js has this code:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = "";  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
> i replace this code by this:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = $(rf.getDomElement(fieldId)).val();  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> and it works!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:41:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:41:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: initialize
 value from DOM (was: ignored API call .setValue(''))
In-Reply-To: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509251.1383279199000.3301.1384249266172@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13306:
----------------------------

    Fix Version/s: 4.3.5

    
> Autocomplete: initialize value from DOM (was: ignored API call .setValue(''))
> -----------------------------------------------------------------------------
>
>                 Key: RF-13306
>                 URL: https://issues.jboss.org/browse/RF-13306
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Luk?? Fry?
>             Fix For: 4.3.5
>
>
> All described here https://community.jboss.org/thread/233973
> I have this autocomplete component:
> {code}
> <table>   
>    <tr>   
>       <td>   
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"   
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"   
>                             autofill="false"   
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"   
>                             layout="table" value="#{autocomplete.providerName}" >   
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />   
>             <h:column>   
>                <h:outputText style="display:none;" value="#{s.id}"/>   
>                <h:outputText style="display:none;" value="#{s.realName}"/>   
>             </h:column>   
>             <h:column>   
>                <h:outputText value="#{s.name}" escape="false"/>   
>             </h:column>   
>          </rich:autocomplete>   
>       </td>   
>       <td>   
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"   
>                          alt=""/>   
>          <h:graphicImage value="/img/cancel.png"   
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"   
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>   
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>   
>       </td>   
>    </tr>   
> </table>
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And a problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
>  
> I think i found a solution
> AutocompleteBase.js has this code:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = "";  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
> i replace this code by this:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = $(rf.getDomElement(fieldId)).val();  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> and it works!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:41:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:41:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: initialize
 value from DOM (was: ignored API call .setValue(''))
In-Reply-To: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509251.1383279199000.3306.1384249266355@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13306:
-------------------------------

    Assignee:     (was: Luk?? Fry?)

    
> Autocomplete: initialize value from DOM (was: ignored API call .setValue(''))
> -----------------------------------------------------------------------------
>
>                 Key: RF-13306
>                 URL: https://issues.jboss.org/browse/RF-13306
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>             Fix For: 4.3.5
>
>
> All described here https://community.jboss.org/thread/233973
> I have this autocomplete component:
> {code}
> <table>   
>    <tr>   
>       <td>   
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"   
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"   
>                             autofill="false"   
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"   
>                             layout="table" value="#{autocomplete.providerName}" >   
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />   
>             <h:column>   
>                <h:outputText style="display:none;" value="#{s.id}"/>   
>                <h:outputText style="display:none;" value="#{s.realName}"/>   
>             </h:column>   
>             <h:column>   
>                <h:outputText value="#{s.name}" escape="false"/>   
>             </h:column>   
>          </rich:autocomplete>   
>       </td>   
>       <td>   
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"   
>                          alt=""/>   
>          <h:graphicImage value="/img/cancel.png"   
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"   
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>   
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>   
>       </td>   
>    </tr>   
> </table>
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And a problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
>  
> I think i found a solution
> AutocompleteBase.js has this code:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = "";  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
> i replace this code by this:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = $(rf.getDomElement(fieldId)).val();  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> and it works!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:49:06 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Tue, 12 Nov 2013 04:49:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13292) Autocomplete: up and
 down arrow keys not working in Opera!
In-Reply-To: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508918.1383023336000.3327.1384249746018@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov updated RF-13292:
-------------------------------

    Affects Version/s: 5.0.0.Alpha2

    
> Autocomplete: up and down arrow keys not working in Opera!
> ----------------------------------------------------------
>
>                 Key: RF-13292
>                 URL: https://issues.jboss.org/browse/RF-13292
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4, 5.0.0.Alpha2
>            Reporter: alexey plotnikov
>            Assignee: Michal Petrov
>             Fix For: 4.5-Tracking
>
>
> Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 04:51:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 04:51:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13338) Page Fragments: change
 package from .tests.page.fragments.impl to .fragments
In-Reply-To: <JIRA.12524852.1384244259000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524852.1384244259000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524852.1384244259000.3358.1384249866781@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13338:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> Page Fragments: change package from .tests.page.fragments.impl to .fragments
> ----------------------------------------------------------------------------
>
>                 Key: RF-13338
>                 URL: https://issues.jboss.org/browse/RF-13338
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 04:57:05 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Tue, 12 Nov 2013 04:57:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13292) Autocomplete: up and
 down arrow keys not working in Opera!
In-Reply-To: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508918.1383023336000.3379.1384250225926@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov closed RF-13292.
------------------------------

    Resolution: Done

    
> Autocomplete: up and down arrow keys not working in Opera!
> ----------------------------------------------------------
>
>                 Key: RF-13292
>                 URL: https://issues.jboss.org/browse/RF-13292
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4, 5.0.0.Alpha2
>            Reporter: alexey plotnikov
>            Assignee: Michal Petrov
>             Fix For: 4.5-Tracking
>
>
> Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 05:05:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 05:05:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13305) Autocomplete: i must
 press button twice for popup window
In-Reply-To: <JIRA.12509249.1383274376000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509249.1383274376000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509249.1383274376000.3407.1384250705925@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922688#comment-12922688 ] 

Luk?? Fry? commented on RF-13305:
---------------------------------

This fix generally allows to use AJAX call for populating list of suggestions ({{showPopup()}}) when the current value of an input is empty.

I'm fine with that solution.
                
> Autocomplete: i must press button twice for popup window
> --------------------------------------------------------
>
>                 Key: RF-13305
>                 URL: https://issues.jboss.org/browse/RF-13305
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Luk?? Fry?
>
> All described here https://community.jboss.org/thread/233971
> I try repeat:
> I have this autocomplete component:
> {code}
> <table>  
>    <tr>  
>       <td>  
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"  
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"  
>                             autofill="false"  
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"  
>                             layout="table" value="#{autocomplete.providerName}" >  
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
>             <h:column>  
>                <h:outputText style="display:none;" value="#{s.id}"/>  
>                <h:outputText style="display:none;" value="#{s.realName}"/>  
>             </h:column>  
>             <h:column>  
>                <h:outputText value="#{s.name}" escape="false"/>  
>             </h:column>  
>          </rich:autocomplete>  
>       </td>  
>       <td>  
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"  
>                          alt=""/>  
>          <h:graphicImage value="/img/cancel.png"  
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"  
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>  
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>  
>       </td>  
>    </tr>  
> </table>  
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on cancel button(img/cancel.png), then after that, if user clicks on show button(/img/arrow.png) popup not showing, user must clicks twice on this button.
> *This problem shows if i use showButton from rich:autocomplete instead my show button.*
> I think i found a solution of this problem:
> Autocomplete.js has this code:
> {code}
> var onChangeValue = function (event, value, callback) {  
>         selectItem.call(this, event);  
>   
>         // value is undefined if called from AutocompleteBase onChange  
>         var subValue = (typeof value == "undefined") ? this.__getSubValue() : value;  
>         var oldValue = this.value;  
>         this.value = subValue;  
>   
>         if ((this.options.isCachedAjax || !this.options.ajaxMode) &&  
>             this.cache && this.cache.isCached(subValue)) {  
>             ...  
>         } else {  
>             if (event.keyCode == rf.KEYS.RETURN || event.type == "click") {  
>                 this.__setInputValue(subValue);  
>             }  
>             if (subValue.length >= this.options.minChars) {  
>                 if ((this.options.ajaxMode || this.options.lazyClientMode) && oldValue != subValue) {  
>                     callAjax.call(this, event, callback);  
>                 }  
>             } else {  
>                 if (this.options.ajaxMode) {  
>                     clearItems.call(this);  
>                     this.__hide(event);  
>                 }  
>             }  
>         }  
>      }; 
> {code}
> for show popup this must be true: 
> {code}
> oldValue != subValue
> {code}
> but in this part of code 
> oldValue is ''(empty string) and subValue is ''(empty string),
> so this condition 
> {code}
> oldValue != subValue
> {code}
> return false!
>  
> i replace this code by this:
> {code}
> var onChangeValue = function (event, value, callback) {  
>         selectItem.call(this, event);  
>   
>         // value is undefined if called from AutocompleteBase onChange  
>         var subValue = (typeof value == "undefined") ? this.__getSubValue() : value;  
>         var oldValue = this.value;  
>         this.value = subValue;  
>   
>         if ((this.options.isCachedAjax || !this.options.ajaxMode) &&  
>             this.cache && this.cache.isCached(subValue)) {  
>             ...  
>         } else {  
>             if (event.keyCode == rf.KEYS.RETURN || event.type == "click") {  
>                 this.__setInputValue(subValue);  
>             }  
>             if (subValue.length >= this.options.minChars) {  
>                 if ((this.options.ajaxMode || this.options.lazyClientMode) && (oldValue != subValue || (oldValue === '' && subValue === ''))) {  
>                     callAjax.call(this, event, callback);  
>                 }  
>             } else {  
>                 if (this.options.ajaxMode) {  
>                     clearItems.call(this);  
>                     this.__hide(event);  
>                 }  
>             }  
>         }  
>   
>     };  
> {code}
> so, than oldValue='' and subValue=='' callAjax.call will be called and popup will be showing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 05:05:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 05:05:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13305) Autocomplete: i must
 press button twice for popup window
In-Reply-To: <JIRA.12509249.1383274376000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509249.1383274376000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509249.1383274376000.3410.1384250706066@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13305:
----------------------------

    Fix Version/s: 4.3.5

    
> Autocomplete: i must press button twice for popup window
> --------------------------------------------------------
>
>                 Key: RF-13305
>                 URL: https://issues.jboss.org/browse/RF-13305
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Luk?? Fry?
>             Fix For: 4.3.5
>
>
> All described here https://community.jboss.org/thread/233971
> I try repeat:
> I have this autocomplete component:
> {code}
> <table>  
>    <tr>  
>       <td>  
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"  
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"  
>                             autofill="false"  
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"  
>                             layout="table" value="#{autocomplete.providerName}" >  
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
>             <h:column>  
>                <h:outputText style="display:none;" value="#{s.id}"/>  
>                <h:outputText style="display:none;" value="#{s.realName}"/>  
>             </h:column>  
>             <h:column>  
>                <h:outputText value="#{s.name}" escape="false"/>  
>             </h:column>  
>          </rich:autocomplete>  
>       </td>  
>       <td>  
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"  
>                          alt=""/>  
>          <h:graphicImage value="/img/cancel.png"  
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"  
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>  
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>  
>       </td>  
>    </tr>  
> </table>  
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on cancel button(img/cancel.png), then after that, if user clicks on show button(/img/arrow.png) popup not showing, user must clicks twice on this button.
> *This problem shows if i use showButton from rich:autocomplete instead my show button.*
> I think i found a solution of this problem:
> Autocomplete.js has this code:
> {code}
> var onChangeValue = function (event, value, callback) {  
>         selectItem.call(this, event);  
>   
>         // value is undefined if called from AutocompleteBase onChange  
>         var subValue = (typeof value == "undefined") ? this.__getSubValue() : value;  
>         var oldValue = this.value;  
>         this.value = subValue;  
>   
>         if ((this.options.isCachedAjax || !this.options.ajaxMode) &&  
>             this.cache && this.cache.isCached(subValue)) {  
>             ...  
>         } else {  
>             if (event.keyCode == rf.KEYS.RETURN || event.type == "click") {  
>                 this.__setInputValue(subValue);  
>             }  
>             if (subValue.length >= this.options.minChars) {  
>                 if ((this.options.ajaxMode || this.options.lazyClientMode) && oldValue != subValue) {  
>                     callAjax.call(this, event, callback);  
>                 }  
>             } else {  
>                 if (this.options.ajaxMode) {  
>                     clearItems.call(this);  
>                     this.__hide(event);  
>                 }  
>             }  
>         }  
>      }; 
> {code}
> for show popup this must be true: 
> {code}
> oldValue != subValue
> {code}
> but in this part of code 
> oldValue is ''(empty string) and subValue is ''(empty string),
> so this condition 
> {code}
> oldValue != subValue
> {code}
> return false!
>  
> i replace this code by this:
> {code}
> var onChangeValue = function (event, value, callback) {  
>         selectItem.call(this, event);  
>   
>         // value is undefined if called from AutocompleteBase onChange  
>         var subValue = (typeof value == "undefined") ? this.__getSubValue() : value;  
>         var oldValue = this.value;  
>         this.value = subValue;  
>   
>         if ((this.options.isCachedAjax || !this.options.ajaxMode) &&  
>             this.cache && this.cache.isCached(subValue)) {  
>             ...  
>         } else {  
>             if (event.keyCode == rf.KEYS.RETURN || event.type == "click") {  
>                 this.__setInputValue(subValue);  
>             }  
>             if (subValue.length >= this.options.minChars) {  
>                 if ((this.options.ajaxMode || this.options.lazyClientMode) && (oldValue != subValue || (oldValue === '' && subValue === ''))) {  
>                     callAjax.call(this, event, callback);  
>                 }  
>             } else {  
>                 if (this.options.ajaxMode) {  
>                     clearItems.call(this);  
>                     this.__hide(event);  
>                 }  
>             }  
>         }  
>   
>     };  
> {code}
> so, than oldValue='' and subValue=='' callAjax.call will be called and popup will be showing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 06:19:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 06:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13339) orderingList: ordered
 values are reset after submit
In-Reply-To: <JIRA.12524863.1384255087687@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524863.1384255087687@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524863.1384255087687.3527.1384255145880@jira02.app.mwc.hst.phx2.redhat.com>

Ji?? ?tefek created RF-13339:
--------------------------------

             Summary: orderingList: ordered values are reset after submit
                 Key: RF-13339
                 URL: https://issues.jboss.org/browse/RF-13339
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Ji?? ?tefek
            Priority: Blocker




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 06:46:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 06:46:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13300) Page Fragments: refine
	module dependencies
In-Reply-To: <JIRA.12509046.1383080055000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509046.1383080055000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509046.1383080055000.3547.1384256766635@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13300.
-----------------------------

    Resolution: Done

    
> Page Fragments: refine module dependencies
> ------------------------------------------
>
>                 Key: RF-13300
>                 URL: https://issues.jboss.org/browse/RF-13300
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> During the review, I have found out we may need to fine module dependencies:
> https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441
> ----
> {code}
> joda-time:2.3
> - DateTime
> commons-lang:2.6
> - Validate.isTrue
> - StringEscapeUtils.unescapeJava
> json-simple:1.1.1
> - JSONParser
> org.jodah:typetools:0.3.0
> - TypeResolver.resolveRawArguments
> {code}
> I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}.
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].
> {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html].
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 06:46:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 06:46:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13338) Page Fragments: change
 package from .tests.page.fragments.impl to .fragments
In-Reply-To: <JIRA.12524852.1384244259000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524852.1384244259000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524852.1384244259000.3549.1384256766755@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13338:
-------------------------------

    Assignee: Luk?? Fry?

    
> Page Fragments: change package from .tests.page.fragments.impl to .fragments
> ----------------------------------------------------------------------------
>
>                 Key: RF-13338
>                 URL: https://issues.jboss.org/browse/RF-13338
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 06:52:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 06:52:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13338) Page Fragments: change
 package from .tests.page.fragments.impl to .fragments
In-Reply-To: <JIRA.12524852.1384244259000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524852.1384244259000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524852.1384244259000.3568.1384257125829@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13338.
-----------------------------

    Resolution: Done

    
> Page Fragments: change package from .tests.page.fragments.impl to .fragments
> ----------------------------------------------------------------------------
>
>                 Key: RF-13338
>                 URL: https://issues.jboss.org/browse/RF-13338
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 07:04:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 07:04:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806088@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806088@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806088.3606.1384257845846@jira02.app.mwc.hst.phx2.redhat.com>

Ji?? ?tefek created RF-13340:
--------------------------------

             Summary: orderingList - setting of multiple attributes does not have any effect on the component
                 Key: RF-13340
                 URL: https://issues.jboss.org/browse/RF-13340
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Ji?? ?tefek
            Assignee: Brian Leathem
             Fix For: 5.0.0.Alpha2


Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).

*Buttons text*
* addAllText
* addText
* removeAllText
* removeText
* downBottomText
* downText
* upText
* upTopText

*List style*
* maxListHeight
* minListHeight
* style
* columnClasses

*Other RW options*
* switchByClick
* switchByDblClick

*Callbacks*
* onremoveitems
* value
* valueChangeListener

I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 07:09:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 07:09:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.3608.1384258145833@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13340:
-----------------------------

    Description: 
Setting of these attributes on a {{orderingList}} has no effect on the rendered component
* style


  was:
Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).

*Buttons text*
* addAllText
* addText
* removeAllText
* removeText
* downBottomText
* downText
* upText
* upTopText

*List style*
* maxListHeight
* minListHeight
* style
* columnClasses

*Other RW options*
* switchByClick
* switchByDblClick

*Callbacks*
* onremoveitems
* value
* valueChangeListener

I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?


    
> orderingList - setting of multiple attributes does not have any effect on the component
> ---------------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 07:09:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 07:09:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of some attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.3610.1384258146007@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13340:
-----------------------------

    Summary: orderingList - setting of some attributes does not have any effect on the component  (was: orderingList - setting of multiple attributes does not have any effect on the component)

    
> orderingList - setting of some attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 07:11:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 07:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of some attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.3622.1384258266310@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13340:
-----------------------------

    Assignee:     (was: Brian Leathem)

    
> orderingList - setting of some attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 07:11:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 07:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of some attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.3623.1384258266334@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13340:
-----------------------------

     Original Estimate:     (was: 1 hour)
    Remaining Estimate:     (was: 1 hour)

    
> orderingList - setting of some attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 07:16:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 07:16:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of some attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.3626.1384258566556@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13340:
-----------------------------

    Description: 
Setting of these attributes on a {{orderingList}} has no effect on the rendered component
* style
* valueChangeListener


  was:
Setting of these attributes on a {{orderingList}} has no effect on the rendered component
* style



    
> orderingList - setting of some attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style
> * valueChangeListener

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 07:22:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 07:22:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13339) orderingList: ordered
 values are reset after submit
In-Reply-To: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524863.1384255087000.3632.1384258925812@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13339:
-----------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> orderingList: ordered values are reset after submit
> ---------------------------------------------------
>
>                 Key: RF-13339
>                 URL: https://issues.jboss.org/browse/RF-13339
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 10:11:05 2013
From: jira-events at lists.jboss.org (Robert Siebeck (JIRA))
Date: Tue, 12 Nov 2013 10:11:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11570) rich:extendedDataTable
 inside rich:collapsiblePanel and IE 8: disappearing header
In-Reply-To: <JIRA.12449798.1319031314000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12449798.1319031314000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12449798.1319031314000.4289.1384269065984@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-11570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922817#comment-12922817 ] 

Robert Siebeck commented on RF-11570:
-------------------------------------

I have the same problem with IE8 and IE9, both in standards and compatibility mode. Could someone please reopen this?
                
> rich:extendedDataTable inside rich:collapsiblePanel and IE 8: disappearing header
> ---------------------------------------------------------------------------------
>
>                 Key: RF-11570
>                 URL: https://issues.jboss.org/browse/RF-11570
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.1.0.Milestone3
>         Environment: IE 8 (strict mode)
>            Reporter: Jan Papousek
>         Attachments: buggy-richfaces-snapshot.zip, ie8_compatibilty-buggy.png, ie8_strict-buggy.png
>
>
> Using IE 8 in strict mode, the rich:extendedDataTable header disappears sometimes (see steps to reproduce).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 10:11:06 2013
From: jira-events at lists.jboss.org (Robert Siebeck (JIRA))
Date: Tue, 12 Nov 2013 10:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11571) rich:extendedDataTable
 inside rich:collapsiblePanel and Google Chrome 12: dissappearing table
In-Reply-To: <JIRA.12449805.1319032826000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12449805.1319032826000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12449805.1319032826000.4295.1384269066331@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-11571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922820#comment-12922820 ] 

Robert Siebeck commented on RF-11571:
-------------------------------------

This problem not only occurs within rich:collapsiblePanel but also with rich:tabPanel and rich:tab.
                
> rich:extendedDataTable inside rich:collapsiblePanel and Google Chrome 12: dissappearing table
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-11571
>                 URL: https://issues.jboss.org/browse/RF-11571
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.1.0.Milestone3
>         Environment: Google Chrome 12.0.742.112
>            Reporter: Jan Papousek
>             Fix For: 5-Tracking
>
>         Attachments: buggy-richfaces-snapshot.zip, google_chrome12-buggy.png
>
>
> Using Google Chrome 12, the rich:extendedDataTable disappears sometimes (see steps to reproduce).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 10:27:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 10:27:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13341) Charts: implements
	AjaxProps
In-Reply-To: <JIRA.12524903.1384269969795@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524903.1384269969795@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524903.1384269969795.4353.1384270025881@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Macko created RF-13341:
--------------------------------

             Summary: Charts: implements AjaxProps
                 Key: RF-13341
                 URL: https://issues.jboss.org/browse/RF-13341
             Project: RichFaces
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: component-output
            Reporter: Luk?? Macko
            Priority: Minor


I think AbstractChart should implements AjaxProps since it uses server-side listeners.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 11:25:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 11:25:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid
 of commons-lang dependency
In-Reply-To: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524849.1384243427000.4571.1384273506061@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922867#comment-12922867 ] 

Luk?? Fry? commented on RF-13335:
---------------------------------

[Agreed on a team meeting|https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2013-11-12]:

{quote}
AGREED: we will expose BaseComponent#getOptions() using defensive copy http://api.jquery.com/jQuery.extend/#jQuery-extend-deep-target-object1-objectN (lfryc, 15:21:38)
{quote}
                
> Page fragments: get rid of commons-lang dependency
> --------------------------------------------------
>
>                 Key: RF-13335
>                 URL: https://issues.jboss.org/browse/RF-13335
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 11:25:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 11:25:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to
	1.10.3
In-Reply-To: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524778.1384177649000.4574.1384273506202@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13334:
----------------------------

    Fix Version/s: 5.0.0.Alpha3
                       (was: 5.0.0.Alpha2)

    
> Upgrade jQuery UI to 1.10.3
> ---------------------------
>
>                 Key: RF-13334
>                 URL: https://issues.jboss.org/browse/RF-13334
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha3
>
>
> RichWidgets issue:
> https://github.com/richwidgets/richwidgets/issues/99

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 11:25:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 11:25:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to
	1.10.3
In-Reply-To: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524778.1384177649000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524778.1384177649000.4583.1384273506931@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922869#comment-12922869 ] 

Luk?? Fry? commented on RF-13334:
---------------------------------

[As greed on team meeting|https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2013-11-12]:

{quote}
AGREED: we will leave jQuery UI 1.10+ upgrade for RichWidgets 0.2 (lfryc, 15:27:43)
{quote}

We don't want to de-stabilize RichFaces 4.5 at this point.
                
> Upgrade jQuery UI to 1.10.3
> ---------------------------
>
>                 Key: RF-13334
>                 URL: https://issues.jboss.org/browse/RF-13334
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha3
>
>
> RichWidgets issue:
> https://github.com/richwidgets/richwidgets/issues/99

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 11:33:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 11:33:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.4621.1384273985857@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922874#comment-12922874 ] 

Luk?? Macko commented on RF-13331:
----------------------------------

I've started to working on moving tests, however there are some problems, tests runs in chrome only at the moment. I'll have fix it before moving to the framework. 
Currently I am not able to run test in sandbox because of the following exception. I understand that sandbox is not priority, so I am thinking: 
* should I report this as an issue or 
* should I just use workaround and temporary move chartBridge.js to sandbox?

{noformat}
16:40:38,682 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-4) JSF1064: Unable to find or serve resource, bridge/output/chartBridge.js, from library, org.richfaces.
16:40:38,683 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-4) Error Rendering View[/examples/events.xhtml]: java.lang.reflect.UndeclaredThrowableException
	at com.sun.proxy.$Proxy68.createResource(Unknown Source)
	at org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:384) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
	at org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:359) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
	at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:342) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
	at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
	at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
	at com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:402) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
	at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source) [:1.7.0_40]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_40]
	at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_40]
	at org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
	... 34 more
Caused by: java.lang.NullPointerException
	at org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
	at org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
	at org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
	at org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT]
	... 38 more
{noformat}
                
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 11:37:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Tue, 12 Nov 2013 11:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13333) Charts: click server
 handlers throws exception
In-Reply-To: <JIRA.12524764.1384173557000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524764.1384173557000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524764.1384173557000.4636.1384274226014@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922876#comment-12922876 ] 

Luk?? Macko commented on RF-13333:
----------------------------------

I've created issue https://issues.jboss.org/browse/RF-13341 to discuss if AbstractChart should implements AjaxProps since it uses server-side listeners.
                
> Charts: click server handlers throws exception
> ----------------------------------------------
>
>                 Key: RF-13333
>                 URL: https://issues.jboss.org/browse/RF-13333
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> Steps to reproduce:
> 1. open r:chart -> Event handling demo
> http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=chart&sample=events&skin=blueSky
> 2. click on one of points on the chart
> FAIL: there is an error in the server console
> {{NoSuchMethodException: Read method for property 'JSONArray' not found}}
> Stack trace:
> {code}
> 13:37:19,467 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-1) Error Rendering View[/richfaces/component-sample.xhtml]: javax.faces.FacesException: Error in conversion Java Object to JavaScript
> 	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:194) [:]
> 	at org.richfaces.javascript.ScriptUtils.toScript(ScriptUtils.java:241) [:]
> 	at org.richfaces.context.AjaxDataSerializerImpl.asString(AjaxDataSerializerImpl.java:32) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.renderExtensions(ExtendedPartialViewContextImpl.java:531) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:327) [:]
> 	at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:222) [:]
> 	at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:391) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:]
> 	at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [:]
> 	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardContextValve.__invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java) [jbossweb-7.0.13.Final.jar:]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> 	at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: java.lang.NoSuchMethodException: Read method for property 'JSONArray' not found
> 	at org.richfaces.javascript.PropertyUtils.readPropertyValue(PropertyUtils.java:74) [:]
> 	at org.richfaces.javascript.ScriptUtils.appendScript(ScriptUtils.java:191) [:]
> 	... 37 more
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 14:50:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 14:50:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4491) pickList doesn't honor
 property 'disabled' of selectItems
In-Reply-To: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12367642.1221658985000.5002.1384285806187@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reopened RF-4491:
-------------------------------

      Assignee:     (was: Nick Belaevski)

    
> pickList doesn't honor property 'disabled' of selectItems
> ---------------------------------------------------------
>
>                 Key: RF-4491
>                 URL: https://issues.jboss.org/browse/RF-4491
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.2
>            Reporter: Martin H?ller
>              Labels: disabled_selectItem, pickList
>
> selectItem components have a property 'disabled' to disable selection of items. The RichFaces component pickList ignores this property. Disabled items can be selected in the source list and added to the target list.
> For documentation of the disabed property see http://java.sun.com/javaee/javaserverfaces/1.1_01/docs/api/javax/faces/model/SelectItem.html#isDisabled()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 14:52:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 14:52:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4491) pickList doesn't honor
 property 'disabled' of selectItems
In-Reply-To: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12367642.1221658985000.5007.1384285925949@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-4491:
------------------------------

    Description: 
_f:selectItem_ components have a 'disabled' property that disables the selection of items. The RichFaces component _pickList_ ignores this property. Disabled items can be selected in the source list and added to the target list.

For documentation of the disabled property see:
https://javaserverfaces.java.net/nonav/docs/2.1/javadocs/javax/faces/model/SelectItem.html#isDisabled()

  was:
selectItem components have a property 'disabled' to disable selection of items. The RichFaces component pickList ignores this property. Disabled items can be selected in the source list and added to the target list.

For documentation of the disabed property see http://java.sun.com/javaee/javaserverfaces/1.1_01/docs/api/javax/faces/model/SelectItem.html#isDisabled()


    
> pickList doesn't honor property 'disabled' of selectItems
> ---------------------------------------------------------
>
>                 Key: RF-4491
>                 URL: https://issues.jboss.org/browse/RF-4491
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.2
>            Reporter: Martin H?ller
>              Labels: disabled_selectItem, pickList
>
> _f:selectItem_ components have a 'disabled' property that disables the selection of items. The RichFaces component _pickList_ ignores this property. Disabled items can be selected in the source list and added to the target list.
> For documentation of the disabled property see:
> https://javaserverfaces.java.net/nonav/docs/2.1/javadocs/javax/faces/model/SelectItem.html#isDisabled()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 14:52:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 14:52:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4491) pickList doesn't honor
 property 'disabled' of selectItems
In-Reply-To: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12367642.1221658985000.5011.1384285926181@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-4491:
------------------------------

    Affects Version/s: 4.3.4

    
> pickList doesn't honor property 'disabled' of selectItems
> ---------------------------------------------------------
>
>                 Key: RF-4491
>                 URL: https://issues.jboss.org/browse/RF-4491
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.2, 4.3.4
>            Reporter: Martin H?ller
>              Labels: disabled_selectItem, pickList
>
> _f:selectItem_ components have a 'disabled' property that disables the selection of items. The RichFaces component _pickList_ ignores this property. Disabled items can be selected in the source list and added to the target list.
> For documentation of the disabled property see:
> https://javaserverfaces.java.net/nonav/docs/2.1/javadocs/javax/faces/model/SelectItem.html#isDisabled()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 14:52:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 14:52:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4491) pickList doesn't honor
 property 'disabled' of selectItems
In-Reply-To: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12367642.1221658985000.5015.1384285926381@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-4491:
------------------------------

    Component/s: component-selects

    
> pickList doesn't honor property 'disabled' of selectItems
> ---------------------------------------------------------
>
>                 Key: RF-4491
>                 URL: https://issues.jboss.org/browse/RF-4491
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 3.2.2, 4.3.4
>            Reporter: Martin H?ller
>              Labels: disabled_selectItem, pickList
>
> _f:selectItem_ components have a 'disabled' property that disables the selection of items. The RichFaces component _pickList_ ignores this property. Disabled items can be selected in the source list and added to the target list.
> For documentation of the disabled property see:
> https://javaserverfaces.java.net/nonav/docs/2.1/javadocs/javax/faces/model/SelectItem.html#isDisabled()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 14:52:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 14:52:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4491) pickList doesn't honor
 property 'disabled' of selectItems
In-Reply-To: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12367642.1221658985000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12367642.1221658985000.5019.1384285926563@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-4491:
------------------------------

    Fix Version/s: 5.0.0.Alpha3

    
> pickList doesn't honor property 'disabled' of selectItems
> ---------------------------------------------------------
>
>                 Key: RF-4491
>                 URL: https://issues.jboss.org/browse/RF-4491
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 3.2.2, 4.3.4
>            Reporter: Martin H?ller
>              Labels: disabled_selectItem, pickList
>             Fix For: 5.0.0.Alpha3
>
>
> _f:selectItem_ components have a 'disabled' property that disables the selection of items. The RichFaces component _pickList_ ignores this property. Disabled items can be selected in the source list and added to the target list.
> For documentation of the disabled property see:
> https://javaserverfaces.java.net/nonav/docs/2.1/javadocs/javax/faces/model/SelectItem.html#isDisabled()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 14:58:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 14:58:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13341) Charts: implement
	AjaxProps
In-Reply-To: <JIRA.12524903.1384269969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524903.1384269969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524903.1384269969000.5025.1384286285829@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13341:
-------------------------------

    Summary: Charts: implement AjaxProps  (was: Charts: implements AjaxProps)

    
> Charts: implement AjaxProps
> ---------------------------
>
>                 Key: RF-13341
>                 URL: https://issues.jboss.org/browse/RF-13341
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>            Priority: Minor
>
> I think AbstractChart should implements AjaxProps since it uses server-side listeners.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 15:21:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 15:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13341) Charts: implement
	AjaxProps
In-Reply-To: <JIRA.12524903.1384269969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524903.1384269969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524903.1384269969000.5058.1384287665832@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922948#comment-12922948 ] 

Brian Leathem commented on RF-13341:
------------------------------------

[AjaxProps|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/attribute/AjaxProps.java] defines the attributes:

* execute
* render
* limitRender
* status
* data

So by implementing this interface, users would be able to initiate an ajax execute/render from the chart component tag.  This would be instead of nesting the AJAX behaviour in the chart component to achieve the same results.

IMO nesting the ajax behaviour provides a nice encapsulation of the AJAX attributes, and I can't see a strong use case for adding this functionality directly into the chart component.

[~lukindo] do you have any use cases in mind?
                
> Charts: implement AjaxProps
> ---------------------------
>
>                 Key: RF-13341
>                 URL: https://issues.jboss.org/browse/RF-13341
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>            Priority: Minor
>
> I think AbstractChart should implements AjaxProps since it uses server-side listeners.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 15:23:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 15:23:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of some attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.5060.1384287785833@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13340:
----------------------------------

    Assignee: Brian Leathem

    
> orderingList - setting of some attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style
> * valueChangeListener

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 15:23:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 15:23:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13339) orderingList: ordered
 values are reset after submit
In-Reply-To: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524863.1384255087000.5062.1384287785926@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13339:
----------------------------------

    Assignee: Brian Leathem

    
> orderingList: ordered values are reset after submit
> ---------------------------------------------------
>
>                 Key: RF-13339
>                 URL: https://issues.jboss.org/browse/RF-13339
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 15:27:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 15:27:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13337) Page fragments: get rid
 of typetools dependency
In-Reply-To: <JIRA.12524851.1384243549000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524851.1384243549000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524851.1384243549000.5083.1384288025870@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reopened RF-13337:
--------------------------------



IMO shading is overkill for inclusion of a single class.  Let's instead simply copy the source into our source tree (preserving the ASL header) and updating the repositories NOTICE.txt:

https://github.com/richfaces/richfaces/blob/master/NOTICE.txt
                
> Page fragments: get rid of typetools dependency
> -----------------------------------------------
>
>                 Key: RF-13337
>                 URL: https://issues.jboss.org/browse/RF-13337
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 15:29:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 15:29:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13336) Page fragments: get rid
 of json-simple dependency
In-Reply-To: <JIRA.12524850.1384243485000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524850.1384243485000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524850.1384243485000.5094.1384288145800@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922952#comment-12922952 ] 

Brian Leathem commented on RF-13336:
------------------------------------

[~lfryc] I cannot find any commits referencing this issue.  What code changes were involved in resolving this issue?
                
> Page fragments: get rid of json-simple dependency
> -------------------------------------------------
>
>                 Key: RF-13336
>                 URL: https://issues.jboss.org/browse/RF-13336
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 15:31:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 15:31:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.5097.1384288265809@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922953#comment-12922953 ] 

Brian Leathem commented on RF-13331:
------------------------------------

I suggest moving the tests to the framework and mark them with _ at Category(Failing.class)_ until they are passing.
                
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 15:33:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 15:33:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.5099.1384288385812@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13330:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 15:54:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 15:54:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.5137.1384289646384@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13323:
----------------------------------

    Assignee: Ji?? ?tefek  (was: Brian Leathem)


Just to be sure, can you try with a standalone sample?
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 12 15:57:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 15:57:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: initialize
 value from DOM (was: ignored API call .setValue(''))
In-Reply-To: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509251.1383279199000.5140.1384289825831@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922959#comment-12922959 ] 

Brian Leathem commented on RF-13306:
------------------------------------

[~alixey] are you interested in preparing a github pull request with this fix?
https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA

You'll have to first sign the CLA:
https://cla.jboss.org/index.seam
                
> Autocomplete: initialize value from DOM (was: ignored API call .setValue(''))
> -----------------------------------------------------------------------------
>
>                 Key: RF-13306
>                 URL: https://issues.jboss.org/browse/RF-13306
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>             Fix For: 4.3.5
>
>
> All described here https://community.jboss.org/thread/233973
> I have this autocomplete component:
> {code}
> <table>   
>    <tr>   
>       <td>   
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"   
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"   
>                             autofill="false"   
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"   
>                             layout="table" value="#{autocomplete.providerName}" >   
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />   
>             <h:column>   
>                <h:outputText style="display:none;" value="#{s.id}"/>   
>                <h:outputText style="display:none;" value="#{s.realName}"/>   
>             </h:column>   
>             <h:column>   
>                <h:outputText value="#{s.name}" escape="false"/>   
>             </h:column>   
>          </rich:autocomplete>   
>       </td>   
>       <td>   
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"   
>                          alt=""/>   
>          <h:graphicImage value="/img/cancel.png"   
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"   
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>   
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>   
>       </td>   
>    </tr>   
> </table>
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And a problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
>  
> I think i found a solution
> AutocompleteBase.js has this code:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = "";  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
> i replace this code by this:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = $(rf.getDomElement(fieldId)).val();  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> and it works!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 16:01:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 16:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13292) Autocomplete: up and
 down arrow keys not working in Opera!
In-Reply-To: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508918.1383023336000.5148.1384290066354@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922961#comment-12922961 ] 

Brian Leathem commented on RF-13292:
------------------------------------

Nice work [~michpetrov].  We should backport this fix to 4.3.4 (re-opening).
                
> Autocomplete: up and down arrow keys not working in Opera!
> ----------------------------------------------------------
>
>                 Key: RF-13292
>                 URL: https://issues.jboss.org/browse/RF-13292
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4, 5.0.0.Alpha2
>            Reporter: alexey plotnikov
>            Assignee: Michal Petrov
>             Fix For: 4.5-Tracking
>
>
> Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 16:01:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 16:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13292) Autocomplete: up and
 down arrow keys not working in Opera!
In-Reply-To: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508918.1383023336000.5151.1384290066479@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reopened RF-13292:
--------------------------------

      Assignee:     (was: Michal Petrov)

    
> Autocomplete: up and down arrow keys not working in Opera!
> ----------------------------------------------------------
>
>                 Key: RF-13292
>                 URL: https://issues.jboss.org/browse/RF-13292
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4, 5.0.0.Alpha2
>            Reporter: alexey plotnikov
>             Fix For: 4.5-Tracking
>
>
> Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 16:01:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 16:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13292) Autocomplete: up and
 down arrow keys not working in Opera!
In-Reply-To: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508918.1383023336000.5154.1384290066645@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13292:
-------------------------------

    Fix Version/s: 4.3.5
                       (was: 4.5-Tracking)

    
> Autocomplete: up and down arrow keys not working in Opera!
> ----------------------------------------------------------
>
>                 Key: RF-13292
>                 URL: https://issues.jboss.org/browse/RF-13292
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4, 5.0.0.Alpha2
>            Reporter: alexey plotnikov
>             Fix For: 4.3.5
>
>
> Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 16:01:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 16:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13292) Autocomplete: up and
 down arrow keys not working in Opera!
In-Reply-To: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508918.1383023336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508918.1383023336000.5157.1384290066790@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922961#comment-12922961 ] 

Brian Leathem edited comment on RF-13292 at 11/12/13 3:59 PM:
--------------------------------------------------------------

Nice work [~michpetrov].  We should backport this fix to 4.3.x (re-opening).
                
      was (Author: bleathem):
    Nice work [~michpetrov].  We should backport this fix to 4.3.4 (re-opening).
                  
> Autocomplete: up and down arrow keys not working in Opera!
> ----------------------------------------------------------
>
>                 Key: RF-13292
>                 URL: https://issues.jboss.org/browse/RF-13292
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4, 5.0.0.Alpha2
>            Reporter: alexey plotnikov
>             Fix For: 4.3.5
>
>
> Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 16:03:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 16:03:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11570) rich:extendedDataTable
 inside rich:collapsiblePanel and IE 8: disappearing header
In-Reply-To: <JIRA.12449798.1319031314000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12449798.1319031314000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12449798.1319031314000.5173.1384290186678@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-11570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reopened RF-11570:
--------------------------------


    
> rich:extendedDataTable inside rich:collapsiblePanel and IE 8: disappearing header
> ---------------------------------------------------------------------------------
>
>                 Key: RF-11570
>                 URL: https://issues.jboss.org/browse/RF-11570
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.1.0.Milestone3
>         Environment: IE 8 (strict mode)
>            Reporter: Jan Papousek
>         Attachments: buggy-richfaces-snapshot.zip, ie8_compatibilty-buggy.png, ie8_strict-buggy.png
>
>
> Using IE 8 in strict mode, the rich:extendedDataTable header disappears sometimes (see steps to reproduce).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 16:18:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 12 Nov 2013 16:18:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11570) rich:extendedDataTable
 inside rich:collapsiblePanel and IE 8: disappearing header
In-Reply-To: <JIRA.12449798.1319031314000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12449798.1319031314000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12449798.1319031314000.5178.1384291086454@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-11570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-11570:
-------------------------------

    Fix Version/s: 5-Tracking

    
> rich:extendedDataTable inside rich:collapsiblePanel and IE 8: disappearing header
> ---------------------------------------------------------------------------------
>
>                 Key: RF-11570
>                 URL: https://issues.jboss.org/browse/RF-11570
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.1.0.Milestone3
>         Environment: IE 8 (strict mode)
>            Reporter: Jan Papousek
>             Fix For: 5-Tracking
>
>         Attachments: buggy-richfaces-snapshot.zip, ie8_compatibilty-buggy.png, ie8_strict-buggy.png
>
>
> Using IE 8 in strict mode, the rich:extendedDataTable header disappears sometimes (see steps to reproduce).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 12 22:47:05 2013
From: jira-events at lists.jboss.org (alexey plotnikov (JIRA))
Date: Tue, 12 Nov 2013 22:47:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13306) Autocomplete: initialize
 value from DOM (was: ignored API call .setValue(''))
In-Reply-To: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509251.1383279199000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509251.1383279199000.5456.1384314425809@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922995#comment-12922995 ] 

alexey plotnikov commented on RF-13306:
---------------------------------------

Brian, i'll try do it today.
                
> Autocomplete: initialize value from DOM (was: ignored API call .setValue(''))
> -----------------------------------------------------------------------------
>
>                 Key: RF-13306
>                 URL: https://issues.jboss.org/browse/RF-13306
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>             Fix For: 4.3.5
>
>
> All described here https://community.jboss.org/thread/233973
> I have this autocomplete component:
> {code}
> <table>   
>    <tr>   
>       <td>   
>          <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"   
>                             minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"   
>                             autofill="false"   
>                             onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"   
>                             layout="table" value="#{autocomplete.providerName}" >   
>             <a4j:queue requestDelay="500" ignoreDupResponses="true" />   
>             <h:column>   
>                <h:outputText style="display:none;" value="#{s.id}"/>   
>                <h:outputText style="display:none;" value="#{s.realName}"/>   
>             </h:column>   
>             <h:column>   
>                <h:outputText value="#{s.name}" escape="false"/>   
>             </h:column>   
>          </rich:autocomplete>   
>       </td>   
>       <td>   
>          <h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"   
>                          alt=""/>   
>          <h:graphicImage value="/img/cancel.png"   
>                          onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"   
>                          alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>   
>          <h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>   
>       </td>   
>    </tr>   
> </table>
> {code}
> as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
> I use JavaScript function "autocompleteChangeProvider" for extract selected id.
> I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
>  
> And a problem:
> if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
>  
> I think i found a solution
> AutocompleteBase.js has this code:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = "";  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
> i replace this code by this:
> {code}
> rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {  
>         // call constructor of parent class  
>         $super.constructor.call(this, componentId);  
>         this.selectId = selectId;  
>         this.fieldId = fieldId;  
>         this.options = $.extend({}, defaultOptions, options);  
>         this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);  
>         this.currentValue = $(rf.getDomElement(fieldId)).val();  
>         this.tempValue = this.getValue();  
>         this.isChanged = this.tempValue.length != 0;  
>         bindEventHandlers.call(this);  
>     };
> {code}
> and it works!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 13 02:50:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 02:50:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.5599.1384329005930@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13323:
-----------------------------

    Attachment: RF-13323.zip


Attached simple project.
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 03:12:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 03:12:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.5625.1384330326362@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923021#comment-12923021 ] 

Ji?? ?tefek commented on RF-13323:
----------------------------------

I've attached here a simple project with 2 samples, one is using @SessionScoped and the second @ViewScoped bean. Both backing beans work correctly. Tried it on GlassFish 3.1.2.2, AS 7.1 with Chrome 30 and Firefox 25. So unless [~wish79] could give us a sample project, i cannot reproduce it.

----

But one thing I've noticed, when you place _fileUpload_ in the ajax rendered _outputPanel_ just like this:
{code}
<a4j:outputPanel ajaxRendered="true">
<rich:fileUpload listener="#{listener}"/>
</a4j:outputPanel>
{code}
and you will upload a file, then the components list of uploaded/toBeUploaded files disappears after each upload (doesn't matter which backing bean is used). [~bleathem] is this an intention? Or should we file an issue?
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 03:12:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 03:12:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.5627.1384330326534@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923021#comment-12923021 ] 

Ji?? ?tefek edited comment on RF-13323 at 11/13/13 3:11 AM:
------------------------------------------------------------

I've attached here a simple project with 2 samples, one is using @SessionScoped and the second @ViewScoped bean. Both backing beans work correctly. Tried it on GlassFish 3.1.2.2, AS 7.1 with Chrome 30 and Firefox 25. So unless [~wish79] could give us a sample project, i cannot reproduce it.

----

But one thing I've noticed, when you place _fileUpload_ in the ajax rendered _outputPanel_ just like this:
{code}
<a4j:outputPanel ajaxRendered="true">
<rich:fileUpload listener="#{listener}"/>
</a4j:outputPanel>
{code}
and you will upload a file, then the components list of uploaded files disappears after each upload (doesn't matter which backing bean is used). [~bleathem] is this an intention? Or should we file an issue?
                
      was (Author: jstefek):
    I've attached here a simple project with 2 samples, one is using @SessionScoped and the second @ViewScoped bean. Both backing beans work correctly. Tried it on GlassFish 3.1.2.2, AS 7.1 with Chrome 30 and Firefox 25. So unless [~wish79] could give us a sample project, i cannot reproduce it.

----

But one thing I've noticed, when you place _fileUpload_ in the ajax rendered _outputPanel_ just like this:
{code}
<a4j:outputPanel ajaxRendered="true">
<rich:fileUpload listener="#{listener}"/>
</a4j:outputPanel>
{code}
and you will upload a file, then the components list of uploaded/toBeUploaded files disappears after each upload (doesn't matter which backing bean is used). [~bleathem] is this an intention? Or should we file an issue?
                  
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 03:14:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 03:14:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.5630.1384330445891@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923021#comment-12923021 ] 

Ji?? ?tefek edited comment on RF-13323 at 11/13/13 3:13 AM:
------------------------------------------------------------

I've attached here a simple project with 2 samples, one is using @SessionScoped and the second @ViewScoped bean. Both samples work correctly. Tried it on GlassFish 3.1.2.2, AS 7.1 with Chrome 30 and Firefox 25. So unless [~wish79] could give us a sample project, i cannot reproduce it.

----

But one thing I've noticed, when you place _fileUpload_ in the ajax rendered _outputPanel_ just like this:
{code}
<a4j:outputPanel ajaxRendered="true">
<rich:fileUpload listener="#{listener}"/>
</a4j:outputPanel>
{code}
and you will upload a file, then the components list of uploaded files disappears after each upload (doesn't matter which backing bean is used). [~bleathem] is this an intention? Or should we file an issue?
                
      was (Author: jstefek):
    I've attached here a simple project with 2 samples, one is using @SessionScoped and the second @ViewScoped bean. Both backing beans work correctly. Tried it on GlassFish 3.1.2.2, AS 7.1 with Chrome 30 and Firefox 25. So unless [~wish79] could give us a sample project, i cannot reproduce it.

----

But one thing I've noticed, when you place _fileUpload_ in the ajax rendered _outputPanel_ just like this:
{code}
<a4j:outputPanel ajaxRendered="true">
<rich:fileUpload listener="#{listener}"/>
</a4j:outputPanel>
{code}
and you will upload a file, then the components list of uploaded files disappears after each upload (doesn't matter which backing bean is used). [~bleathem] is this an intention? Or should we file an issue?
                  
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 03:28:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 03:28:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13341) Charts: implement
	AjaxProps
In-Reply-To: <JIRA.12524903.1384269969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524903.1384269969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524903.1384269969000.5665.1384331286057@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923026#comment-12923026 ] 

Luk?? Fry? commented on RF-13341:
---------------------------------

Brian, the problem here is that Chart implements server-side handlers,

as a response to the listener, you want to do something (e.g. re-render part of the page).

----

In fact, the component supports those attributes as of now:

https://github.com/richfaces/richfaces/blob/94a1060abddf5512eed89e17518a125027b802bf/framework/src/main/java/org/richfaces/context/RenderComponentCallback.java#L77

The ExtendedPartialViewContextImpl collects Ajax-attributes from Activator component (component that activated the request) without asking whether component implements AjaxProps. (Note that this may also be a bug)
                
> Charts: implement AjaxProps
> ---------------------------
>
>                 Key: RF-13341
>                 URL: https://issues.jboss.org/browse/RF-13341
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>            Priority: Minor
>
> I think AbstractChart should implements AjaxProps since it uses server-side listeners.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 03:32:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 03:32:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13336) Page fragments: get rid
 of json-simple dependency
In-Reply-To: <JIRA.12524850.1384243485000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524850.1384243485000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524850.1384243485000.5670.1384331525984@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923028#comment-12923028 ] 

Luk?? Fry? commented on RF-13336:
---------------------------------

I used the parent issue (RF-13300) to link commits.

This issue will be fully resolved with RF-13335
                
> Page fragments: get rid of json-simple dependency
> -------------------------------------------------
>
>                 Key: RF-13336
>                 URL: https://issues.jboss.org/browse/RF-13336
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of [JSR-353|https://jsonp.java.net/index.html].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 03:34:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 03:34:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.5677.1384331645933@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923030#comment-12923030 ] 

Luk?? Fry? commented on RF-13331:
---------------------------------

Lukas, a first problem is caused by bridgeBase.js renamed to bridge-base.js.

The second issue is more interesting as it is relevant to newly introduced programatic Resource Mapping.
Could you please report that separately with a link to reproducer / steps to reproduce?
                
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 08:02:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 08:02:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13342) archetype-simpleapp:
 facelet with name 'title' is not defined in template,
 but it is used in the sample
In-Reply-To: <JIRA.12524983.1384347681433@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524983.1384347681433@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524983.1384347681433.6747.1384347725826@jira02.app.mwc.hst.phx2.redhat.com>

Ji?? ?tefek created RF-13342:
--------------------------------

             Summary: archetype-simpleapp: facelet with name 'title' is not defined in template, but it is used in the sample
                 Key: RF-13342
                 URL: https://issues.jboss.org/browse/RF-13342
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: archetype
    Affects Versions: 5.0.0.Alpha1, 4.3.4
            Reporter: Ji?? ?tefek
            Assignee: Ji?? ?tefek
            Priority: Trivial




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 09:50:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 09:50:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.7154.1384354206732@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13327:
-----------------------------

    Description: 
Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).

*Buttons text*
* addAllText
* addText
* removeAllText
* removeText
* downBottomText
* downText
* upText
* upTopText

*List style*
* maxListHeight
* minListHeight
* style
* columnClasses

*Other RW options*
* switchByClick
* switchByDblClick

*Callbacks*
* onremoveitems
* onadditems
* value
* valueChangeListener

I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

  was:
Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).

*Buttons text*
* addAllText
* addText
* removeAllText
* removeText
* downBottomText
* downText
* upText
* upTopText

*List style*
* maxListHeight
* minListHeight
* style
* columnClasses

*Other RW options*
* switchByClick
* switchByDblClick

*Callbacks*
* onremoveitems
* value
* valueChangeListener

I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?


    
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:17:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:17:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13337) Page fragments: get rid
 of typetools dependency
In-Reply-To: <JIRA.12524851.1384243549000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524851.1384243549000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524851.1384243549000.7228.1384355825974@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13337.
-----------------------------

    Resolution: Done

    
> Page fragments: get rid of typetools dependency
> -----------------------------------------------
>
>                 Key: RF-13337
>                 URL: https://issues.jboss.org/browse/RF-13337
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13337) Page fragments: get rid
 of typetools dependency
In-Reply-To: <JIRA.12524851.1384243549000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524851.1384243549000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524851.1384243549000.7230.1384355826082@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923219#comment-12923219 ] 

Luk?? Fry? commented on RF-13337:
---------------------------------

Committed: https://github.com/richfaces/richfaces/commit/bdcb987dcbf27bd923b59982b6c86b668d7db07d
                
> Page fragments: get rid of typetools dependency
> -----------------------------------------------
>
>                 Key: RF-13337
>                 URL: https://issues.jboss.org/browse/RF-13337
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider [shading it|http://maven.apache.org/plugins/maven-shade-plugin/].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:17:06 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Wed, 13 Nov 2013 10:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13287) rich:extendedDataTable
 column resizing with ajax loading not working properly
In-Reply-To: <JIRA.12508686.1382616678000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508686.1382616678000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508686.1382616678000.7233.1384355826249@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov reassigned RF-13287:
----------------------------------

    Assignee: Michal Petrov

    
> rich:extendedDataTable column resizing with ajax loading not working properly
> -----------------------------------------------------------------------------
>
>                 Key: RF-13287
>                 URL: https://issues.jboss.org/browse/RF-13287
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.4
>         Environment: Glassfish 3.1.2.2, Mojarra 2.1.26, IE10, IE8, Chrome 30,
>            Reporter: Andreas G
>            Assignee: Michal Petrov
>              Labels: testcase_provided
>             Fix For: 5-Tracking
>
>
> In a rich:extendedDataTable with ajax loading turned on: When you resize a column and scroll down (load data), the size of the columns reset to their original value. Only the header keeps its size. The header and the data are not matching anymore.
> Reproducible in the 4.3.4 showcase!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 13 10:33:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid
 of commons-lang dependency
In-Reply-To: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524849.1384243427000.7406.1384356786130@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923225#comment-12923225 ] 

Luk?? Fry? commented on RF-13335:
---------------------------------

The options variable is directly exposed on a component object as follows:

{code}
RichFaces.component("j_idt143:j_idt147").options
{code}
                
> Page fragments: get rid of commons-lang dependency
> --------------------------------------------------
>
>                 Key: RF-13335
>                 URL: https://issues.jboss.org/browse/RF-13335
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:33:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid
 of commons-lang dependency
In-Reply-To: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524849.1384243427000.7409.1384356786313@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923225#comment-12923225 ] 

Luk?? Fry? edited comment on RF-13335 at 11/13/13 10:31 AM:
------------------------------------------------------------

The {{options}} variable is directly exposed on a component object as follows:

{code}
RichFaces.component("j_idt143:j_idt147").options
{code}
                
      was (Author: lfryc):
    The options variable is directly exposed on a component object as follows:

{code}
RichFaces.component("j_idt143:j_idt147").options
{code}
                  
> Page fragments: get rid of commons-lang dependency
> --------------------------------------------------
>
>                 Key: RF-13335
>                 URL: https://issues.jboss.org/browse/RF-13335
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:41:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:41:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195077@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195077@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195077.7453.1384357265860@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13343:
-------------------------------

             Summary: Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
                 Key: RF-13343
                 URL: https://issues.jboss.org/browse/RF-13343
             Project: RichFaces
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: page-fragments
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?


As we have discussed in RF-13335, we have two options available for accessing component options:

* component uses {{BaseComponent}} (RF4 components)

{code}
RichFaces.component("j_idt108").options
{code}

* component uses {{jQuery UI Widget Factory}} (RF5 components)

{code}
$(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
{code}

We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:41:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:41:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.7455.1384357265986@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923233#comment-12923233 ] 

Luk?? Fry? commented on RF-13343:
---------------------------------

We need to remove {{getJsonValue()}} methods()
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:41:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:41:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.7456.1384357266030@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13343:
----------------------------

    Component/s: qe

    
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:43:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:43:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.7459.1384357385962@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923234#comment-12923234 ] 

Luk?? Fry? commented on RF-13343:
---------------------------------

Note that Page Fragments can be used without {{setupFragmentFromWidget()}} method,

it just makes Page Fragment use configuration-less.
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:43:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:43:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.7461.1384357386054@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923235#comment-12923235 ] 

Luk?? Fry? commented on RF-13343:
---------------------------------

I think we can leave this option unsupported and re-implement it once it is needed by QE, wdyt [~ppitonak]?
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:43:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:43:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.7465.1384357386247@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923235#comment-12923235 ] 

Luk?? Fry? edited comment on RF-13343 at 11/13/13 10:42 AM:
------------------------------------------------------------

I think we can leave this option unsupported and re-implement it once it is needed by Framework/Metamer tests, wdyt [~ppitonak]?
                
      was (Author: lfryc):
    I think we can leave this option unsupported and re-implement it once it is needed by QE, wdyt [~ppitonak]?
                  
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:45:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:45:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13335) Page fragments: get rid
 of commons-lang dependency
In-Reply-To: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524849.1384243427000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524849.1384243427000.7468.1384357507502@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923236#comment-12923236 ] 

Luk?? Fry? commented on RF-13335:
---------------------------------

I have opened RF-13343 to address this issue.
                
> Page fragments: get rid of commons-lang dependency
> --------------------------------------------------
>
>                 Key: RF-13335
>                 URL: https://issues.jboss.org/browse/RF-13335
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few [suggestions for dependency free Java-unescaping|http://stackoverflow.com/questions/3537706/howto-unescape-a-java-string-literal-in-java].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:51:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:51:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13342) archetype-simpleapp:
 facelet with name 'title' is not defined in template,
 but it is used in the sample
In-Reply-To: <JIRA.12524983.1384347681000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524983.1384347681000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524983.1384347681000.7496.1384357865880@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13342:
-------------------------------

    Assignee: Luk?? Fry?  (was: Ji?? ?tefek)

    
> archetype-simpleapp: facelet with name 'title' is not defined in template, but it is used in the sample
> -------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13342
>                 URL: https://issues.jboss.org/browse/RF-13342
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: archetype
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>            Priority: Trivial
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:51:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:51:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13342) archetype-simpleapp:
 facelet with name 'title' is not defined in template,
 but it is used in the sample
In-Reply-To: <JIRA.12524983.1384347681000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524983.1384347681000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524983.1384347681000.7499.1384357866027@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13342:
----------------------------

    Assignee:     (was: Luk?? Fry?)

    
> archetype-simpleapp: facelet with name 'title' is not defined in template, but it is used in the sample
> -------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13342
>                 URL: https://issues.jboss.org/browse/RF-13342
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: archetype
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Ji?? ?tefek
>            Priority: Trivial
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 10:53:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 13 Nov 2013 10:53:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13342) archetype-simpleapp:
 facelet with name 'title' is not defined in template,
 but it is used in the sample
In-Reply-To: <JIRA.12524983.1384347681000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524983.1384347681000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524983.1384347681000.7506.1384357986055@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923238#comment-12923238 ] 

Luk?? Fry? commented on RF-13342:
---------------------------------

You are right, we could either use {{title}} in the page, or better, use {{<ui:param name="title" />}}.
                
> archetype-simpleapp: facelet with name 'title' is not defined in template, but it is used in the sample
> -------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13342
>                 URL: https://issues.jboss.org/browse/RF-13342
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: archetype
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Ji?? ?tefek
>            Priority: Trivial
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 14:39:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 13 Nov 2013 14:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13341) Charts: implement
	AjaxProps
In-Reply-To: <JIRA.12524903.1384269969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524903.1384269969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524903.1384269969000.7875.1384371546024@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923284#comment-12923284 ] 

Brian Leathem commented on RF-13341:
------------------------------------

What's the advantage of the chart component implementing server-side events instead of simply relying on nested ajax behaviours?  Are server-side listeners that common a use case that the user benefits from the cluttered API?
                
> Charts: implement AjaxProps
> ---------------------------
>
>                 Key: RF-13341
>                 URL: https://issues.jboss.org/browse/RF-13341
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>            Priority: Minor
>
> I think AbstractChart should implements AjaxProps since it uses server-side listeners.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 15:17:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 13 Nov 2013 15:17:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.7921.1384373825822@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923289#comment-12923289 ] 

Brian Leathem commented on RF-13343:
------------------------------------

Why not use the JSON library already shipped with RichFaces?

https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/json/
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 15:21:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 13 Nov 2013 15:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.7924.1384374065954@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923290#comment-12923290 ] 

Brian Leathem commented on RF-13323:
------------------------------------

Thanks for the investigations [~jstefek].  Please file a new issue addressing the nesting of a fileUpload component in a ajaxRendered outputPanel.
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 15:21:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 13 Nov 2013 15:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.7927.1384374066124@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13323.
--------------------------------

    Resolution: Cannot Reproduce Bug

    
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 15:21:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 13 Nov 2013 15:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.7930.1384374066246@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923291#comment-12923291 ] 

Brian Leathem commented on RF-13323:
------------------------------------

[~wish79] feel free to re-open this issue with instruction on how to reproduce.
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 23:44:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 13 Nov 2013 23:44:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.8299.1384404245837@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923362#comment-12923362 ] 

Brian Leathem commented on RF-13325:
------------------------------------

Is this different than the RichFaces 4 picklist behaviour?  From the jQuery docs this is the expected behaviour for onmouseout:

{quote}
mouseout fires when the pointer moves out of the child element as well
{quote}

Note: There is the _mouseleave_ jQuery event that we could expose as well.  This may be more useful.
                
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 13 23:46:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 13 Nov 2013 23:46:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.8302.1384404365959@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13325:
----------------------------------

    Assignee: Juraj H?ska  (was: Brian Leathem)

    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 01:02:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 01:02:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.8334.1384408925916@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923372#comment-12923372 ] 

Brian Leathem commented on RF-13327:
------------------------------------

Corrected the pick and order buttons' text.
                
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 01:02:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 01:02:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.8335.1384408925978@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923373#comment-12923373 ] 

Brian Leathem commented on RF-13327:
------------------------------------

_maxListHeight_ and _minListHeight_ work for me.  Note: you must include the units in the string, eg: "200px".  If this is a change in behaviour, please file a new issue and we can discussion a resolution there.
                
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 01:08:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 01:08:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.8379.1384409285854@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923374#comment-12923374 ] 

Brian Leathem commented on RF-13327:
------------------------------------

_columnClasses_ works for me with a space separated list.
                
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 02:52:05 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Thu, 14 Nov 2013 02:52:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.8527.1384415525843@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mohammad Weshah updated RF-13323:
---------------------------------

    Attachment: TestRichFacesWebProject.war

    
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 02:56:05 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Thu, 14 Nov 2013 02:56:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.8530.1384415765859@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923394#comment-12923394 ] 

Mohammad Weshah commented on RF-13323:
--------------------------------------

Sorry for being delay , please find the attached war file , please add your jar file ,and test the following URL :
http://localhost:8888/TestRichFacesWebProject/fileu/addDepartment.xhtml

i test it on view scope it is not work.

Regards
Wish79
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 03:12:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 03:12:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13281) orderingList: ordering
 button's text overflows the button on Firefox
In-Reply-To: <JIRA.12508466.1382449117000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508466.1382449117000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508466.1382449117000.8545.1384416726500@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13281.
--------------------------------

    Resolution: Done


Resolved upstream in richwidgets.
                
> orderingList: ordering button's text overflows the button on Firefox
> --------------------------------------------------------------------
>
>                 Key: RF-13281
>                 URL: https://issues.jboss.org/browse/RF-13281
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Firefox 24
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: OL.png
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> The ordering button's text overflows the button.
> Works in Chrome.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 03:21:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 03:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.8563.1384417265984@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13327.
--------------------------------

    Resolution: Done


[~jhuska] if the value change listener still does not work, please file a new issue for it.  All other attributes are expected to be working now.
                
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 03:25:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 03:25:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13299) Page Fragments: added
 license headers to all sources
In-Reply-To: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509045.1383079873000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509045.1383079873000.8578.1384417505992@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13299.
--------------------------------

    Resolution: Done

    
> Page Fragments: added license headers to all sources
> ----------------------------------------------------
>
>                 Key: RF-13299
>                 URL: https://issues.jboss.org/browse/RF-13299
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Issue mentioned during impl review:
> https://github.com/richfaces/richfaces/pull/55

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 03:28:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 03:28:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13326) pickList - caption
 attribute is not rendered in to its faces-config
In-Reply-To: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524612.1383916208000.8582.1384417686285@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13326.
--------------------------------

    Resolution: Done

    
> pickList - caption attribute is not rendered in to its faces-config
> -------------------------------------------------------------------
>
>                 Key: RF-13326
>                 URL: https://issues.jboss.org/browse/RF-13326
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> There should be attribute {{caption}} in the {{pickList}} faces-config. It is not.
> The attribute is defined in [AbstractOrderingList|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/orderingList/AbstractOrderingList.java], which is the ancestor of {{AbstractPickList}}.
> Is it caused because {{orderingList}} has also that attribute and it is somehow overriden as {{pickList}} consists from {{orderingLists}} ? - bit weird
> Note that {{orderingList}} has generated {{caption}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 03:36:06 2013
From: jira-events at lists.jboss.org (Pavel Slegr (JIRA))
Date: Thu, 14 Nov 2013 03:36:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13172) rich:toolbarGroup
 location="right" doesn't work if toolbarGroup location="left" contains not
 rendered values
In-Reply-To: <JIRA.12500222.1378479644000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500222.1378479644000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500222.1378479644000.8598.1384418166519@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Slegr reassigned RF-13172:
--------------------------------

    Assignee: Pavel Slegr

    
> rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13172
>                 URL: https://issues.jboss.org/browse/RF-13172
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-menu
>    Affects Versions: 4.3.3
>            Reporter: Sergey Zubarev
>            Assignee: Pavel Slegr
>              Labels: low_hanging_fruit
>             Fix For: 5-Tracking
>
>
> {code}
> <rich:toolbar itemSeparator="line" id="repairWorkToolbar">
>   <rich:toolbarGroup>
>     <a4j:commandLink value="btn1"/>
>     <a4j:commandLink value="btn2"/>
>     <a4j:commandLink value="btn3" *rendered="false"*/>
>   </rich:toolbarGroup>
>   <rich:toolbarGroup location="right">
>     <a4j:commandLink value="btn_right"/>
>   </rich:toolbarGroup>
> ...
> {code}
> In this case location="right" doesn't work : it displayed left. When I remove rendered="false" from btn3 all works fine.
> Html debug shows, that code produced one extra element in colgroup tag when using rendered="false".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 14 03:42:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 03:42:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.8618.1384418526417@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923409#comment-12923409 ] 

Juraj H?ska commented on RF-13325:
----------------------------------

It is the same in RF4 pickList.

Should I crete JIRA for {{mouseleave}} ?
                
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 03:42:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 03:42:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.8620.1384418526538@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13325:
-----------------------------

    Assignee: Brian Leathem  (was: Juraj H?ska)

    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 03:42:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 03:42:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.8626.1384418526811@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923409#comment-12923409 ] 

Juraj H?ska edited comment on RF-13325 at 11/14/13 3:41 AM:
------------------------------------------------------------

It is the same in RF4 pickList.

Should I create JIRA for {{mouseleave}} ?
                
      was (Author: jhuska):
    It is the same in RF4 pickList.

Should I crete JIRA for {{mouseleave}} ?
                  
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 04:08:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 04:08:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13344) pickList - maxListHeight
 & minListHeight need to have set units along with number to work
In-Reply-To: <JIRA.12525076.1384420028296@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525076.1384420028296@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525076.1384420028296.8713.1384420085893@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13344:
--------------------------------

             Summary: pickList - maxListHeight & minListHeight need to have set units along with number to work
                 Key: RF-13344
                 URL: https://issues.jboss.org/browse/RF-13344
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska


{{pickList}} attributes:
* {{minListHeight}} and {{maxListHeight}}

need to have set units along with the number value (e.g. 200px) in order to work correctly.

In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 04:10:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 04:10:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.8718.1384420207480@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923423#comment-12923423 ] 

Juraj H?ska commented on RF-13327:
----------------------------------

Created RF-13344 for {{maxListHeight}} and {{minListHeight}}, as it is different than in RF4.
                
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 04:14:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 04:14:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.8730.1384420445949@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923426#comment-12923426 ] 

Ji?? ?tefek commented on RF-13323:
----------------------------------

Hi [~wish79],
I can't deploy the _war_ without a manipulation. Could you, please, attach a simple and buildable project with sources, so I can check them? The best way could be using [richfaces archetypes|https://github.com/richfaces/richfaces-archetypes/tree/4.3.x/simpleapp].

Thanks,
js
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 04:36:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 04:36:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13345) FileUpload: behaves
 incorrectly when placed in ajax rendered outputPanel
In-Reply-To: <JIRA.12525080.1384421762314@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525080.1384421762314@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525080.1384421762314.8830.1384421766387@jira02.app.mwc.hst.phx2.redhat.com>

Ji?? ?tefek created RF-13345:
--------------------------------

             Summary: FileUpload: behaves incorrectly when placed in ajax rendered outputPanel
                 Key: RF-13345
                 URL: https://issues.jboss.org/browse/RF-13345
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-input
    Affects Versions: 5.0.0.Alpha1, 4.3.4
         Environment: EAP 6.1
Chrome 30, Firefox 22
            Reporter: Ji?? ?tefek


When fileUpload is placed in ajaxRendered outputPanel, just like this:
{code}
<a4j:outputPanel ajaxRendered="true">
    <rich:fileUpload fileUploadListener="#{richBean.listener}"/>
</a4j:outputPanel>
{code}
then it behaves incorrectly.

With RF 5:
the list of uploaded/to upload files is reset after each upload.

With RF 4:
* cannot manipulate with item(s) which was firstly uploaded
* the upload button is not rendered after first upload performed, but you can still add files and manipulate with them (delete them)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 04:44:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 04:44:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13345) FileUpload: behaves
 incorrectly when placed in ajax rendered outputPanel
In-Reply-To: <JIRA.12525080.1384421762000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525080.1384421762000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525080.1384421762000.8851.1384422247536@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13345:
-----------------------------

    Attachment: RF-13345-RF5-reproducer.zip
                RF-13345-RF4-reproducer.zip


attached reproducers
                
> FileUpload: behaves incorrectly when placed in ajax rendered outputPanel
> ------------------------------------------------------------------------
>
>                 Key: RF-13345
>                 URL: https://issues.jboss.org/browse/RF-13345
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>         Environment: EAP 6.1
> Chrome 30, Firefox 22
>            Reporter: Ji?? ?tefek
>         Attachments: RF-13345-RF4-reproducer.zip, RF-13345-RF5-reproducer.zip
>
>
> When fileUpload is placed in ajaxRendered outputPanel, just like this:
> {code}
> <a4j:outputPanel ajaxRendered="true">
>     <rich:fileUpload fileUploadListener="#{richBean.listener}"/>
> </a4j:outputPanel>
> {code}
> then it behaves incorrectly.
> With RF 5:
> the list of uploaded/to upload files is reset after each upload.
> With RF 4:
> * cannot manipulate with item(s) which was firstly uploaded
> * the upload button is not rendered after first upload performed, but you can still add files and manipulate with them (delete them)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 05:06:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Thu, 14 Nov 2013 05:06:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.9019.1384423566326@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923468#comment-12923468 ] 

Pavol Pitonak commented on RF-13343:
------------------------------------

[~jhuska], [~jstefek],

do we currently use setupFragmentFromWidget() in our test suite?
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 05:23:06 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Thu, 14 Nov 2013 05:23:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.9041.1384424586228@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923479#comment-12923479 ] 

Mohammad Weshah commented on RF-13323:
--------------------------------------

I attached the sources but without the jar file, please check.
Note: Appserver Jboss 7.1

Thanks
Wish79
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 05:23:06 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Thu, 14 Nov 2013 05:23:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.9042.1384424586318@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923479#comment-12923479 ] 

Mohammad Weshah edited comment on RF-13323 at 11/14/13 5:22 AM:
----------------------------------------------------------------

Hi JS,
I attached the sources but without the jar file, please check.
Note: Appserver Jboss 7.1

Thanks
Wish79
                
      was (Author: wish79):
    I attached the sources but without the jar file, please check.
Note: Appserver Jboss 7.1

Thanks
Wish79
                  
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 05:23:05 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Thu, 14 Nov 2013 05:23:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.9038.1384424585922@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mohammad Weshah updated RF-13323:
---------------------------------

    Attachment: TestRichFacesWebProject.rar

    
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 05:29:09 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Thu, 14 Nov 2013 05:29:09 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13287) rich:extendedDataTable
 column resizing with ajax loading not working properly
In-Reply-To: <JIRA.12508686.1382616678000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508686.1382616678000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508686.1382616678000.9053.1384424949340@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov resolved RF-13287.
--------------------------------

    Fix Version/s: 4.3.5
                       (was: 5-Tracking)
       Resolution: Done

    
> rich:extendedDataTable column resizing with ajax loading not working properly
> -----------------------------------------------------------------------------
>
>                 Key: RF-13287
>                 URL: https://issues.jboss.org/browse/RF-13287
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.4
>         Environment: Glassfish 3.1.2.2, Mojarra 2.1.26, IE10, IE8, Chrome 30,
>            Reporter: Andreas G
>            Assignee: Michal Petrov
>              Labels: testcase_provided
>             Fix For: 4.3.5
>
>
> In a rich:extendedDataTable with ajax loading turned on: When you resize a column and scroll down (load data), the size of the columns reset to their original value. Only the header keeps its size. The header and the data are not matching anymore.
> Reproducible in the 4.3.4 showcase!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 14 05:51:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 05:51:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194831@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194831@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194831.9112.1384426266081@jira02.app.mwc.hst.phx2.redhat.com>

Ji?? ?tefek created RF-13346:
--------------------------------

             Summary: orderingList - maxListHeight & minListHeight need to have set units along with number to work
                 Key: RF-13346
                 URL: https://issues.jboss.org/browse/RF-13346
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Ji?? ?tefek


{{pickList}} attributes:
* {{minListHeight}} and {{maxListHeight}}

need to have set units along with the number value (e.g. 200px) in order to work correctly.

In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 05:53:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 05:53:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13347) pickList:
	switchByDblClick does not work
In-Reply-To: <JIRA.12525090.1384426336096@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525090.1384426336096@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525090.1384426336096.9118.1384426386426@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13347:
--------------------------------

             Summary: pickList: switchByDblClick does not work
                 Key: RF-13347
                 URL: https://issues.jboss.org/browse/RF-13347
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska


Setting of {{pickList}} attribute {{switchByDblClick}} to {{true}} does not work.

Note that {{switchByClick}} works as expected.

It seems that attribute is set in render template. I can not found any mention in pick list bridge if that can be the case ? (there is no mention of {{switchByClick}} neither and it works).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 06:09:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Thu, 14 Nov 2013 06:09:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13290) Push framework tests
 fail after upgrade to 1.0.17 (probably Warp issue)
In-Reply-To: <JIRA.12508820.1382713860000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508820.1382713860000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508820.1382713860000.9162.1384427346014@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923503#comment-12923503 ] 

Pavol Pitonak commented on RF-13290:
------------------------------------

No, we didn't run them for Alpha1 release but we plan to do it for all following releases.
                
> Push framework tests fail after upgrade to 1.0.17 (probably Warp issue)
> -----------------------------------------------------------------------
>
>                 Key: RF-13290
>                 URL: https://issues.jboss.org/browse/RF-13290
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll, tests - functional 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> The push is correctly using 'long-polling' technique,
> the request is sent, but the response is never sent back,
> that's why I believe the Warp server-side handling fails.
> ----
> Note that I have tried to upgrade to 1.0.18 and it didn't help.
> ----
> I'm marking those tests as {{Failing}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 06:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 06:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.9192.1384427826695@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923517#comment-12923517 ] 

Juraj H?ska commented on RF-13327:
----------------------------------

Created RF-13347 for not working {{switchByDblClick}}.
                
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 06:45:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 06:45:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.9313.1384429506842@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923533#comment-12923533 ] 

Luk?? Macko commented on RF-13331:
----------------------------------

The second issue was probably also related to renamed resources. I renamed bridgeBase.js and chartBridge.js to correct names and now I am not able to reproduce the issue.
                
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 07:11:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 07:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019684@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019684@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019684.9433.1384431066300@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13348:
--------------------------------

             Summary: pickList - columnClass attribute behaves differently than in RF4
                 Key: RF-13348
                 URL: https://issues.jboss.org/browse/RF-13348
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska


{{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:

Suppose a {{pickList}}, which items consist from _three_ columns.
* if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
* if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected

In *RF4*, it was different though:
* it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.

The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 07:43:05 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Thu, 14 Nov 2013 07:43:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.9598.1384432985845@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov reassigned RF-13346:
----------------------------------

    Assignee: Michal Petrov

    
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 07:55:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 07:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.9623.1384433706160@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13323:
-----------------------------

    Attachment: RF-13323-2.zip

    
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 08:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 08:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.9701.1384435026340@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923597#comment-12923597 ] 

Ji?? ?tefek commented on RF-13323:
----------------------------------

[~bleathem], I have found that the issue with MediaOutput, mentioned in [this comment|https://issues.jboss.org/browse/RF-13323?focusedCommentId=12922655&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12922655], is already reported here -- [RF-11585|https://issues.jboss.org/browse/RF-11585].

[~wish79], sorry, I still can't reproduce it. Got the same result, which you can see on screenshots. 
I've attached another maven project from archetypes with your code.
Could you try it? Just build with maven (_mvn package_) and deploy on container and open http://localhost:8080/RF13323/ . 


                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 08:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 08:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.9706.1384435026632@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923598#comment-12923598 ] 

Ji?? ?tefek commented on RF-13323:
----------------------------------

Sorry, just now I've noticed that you have upgraded JSF version of your container. I'll try that with your version.
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 08:19:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 08:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.9710.1384435145823@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923599#comment-12923599 ] 

Juraj H?ska commented on RF-13327:
----------------------------------

All other attributes (value change listener as well), are working now.
                
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 08:39:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 08:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.9771.1384436346150@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923605#comment-12923605 ] 

Luk?? Fry? commented on RF-13343:
---------------------------------

Brian, we don't need any JSON parsing, that's I'm advocating avoiding JSON library.

The RichFaces component bootstrap is not even strict JSON, so I consider the implementation quite fragile.
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 08:41:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 08:41:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.9781.1384436466322@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923608#comment-12923608 ] 

Ji?? ?tefek commented on RF-13323:
----------------------------------

[~wish79] what version of JSF-API are you using?
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 08:55:06 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Thu, 14 Nov 2013 08:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.9821.1384437306350@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923614#comment-12923614 ] 

Michal Petrov commented on RF-13346:
------------------------------------

The issue is with jQuery, and it's strange that it's not being handled. The problem is here:
{code}
_setHeightMin: function(height) {
    this.selectList.find('.scroll-box').css('min-height', height);
}
{code}

it doesn't work when height is just a number in string form, i.e.
* {{200}} - works
* {{"200px"}} - works
* {{"200"}} - does not work

I'm guessing in RichWidgets the value is autocast to number, but in CDK string will remain a string. This will be an issue for every component. I will look for a workaround but I think the easiest way is to keep a list of options for each component and and parse them in the Bridge.
                
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 09:09:05 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Thu, 14 Nov 2013 09:09:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.9863.1384438145891@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923614#comment-12923614 ] 

Michal Petrov edited comment on RF-13346 at 11/14/13 9:08 AM:
--------------------------------------------------------------

The issue is with jQuery, and it's strange that it's not being handled. The problem is here:
{code}
_setHeightMin: function(height) {
    this.selectList.find('.scroll-box').css('min-height', height);
}
{code}

it doesn't work when height is just a number in string form, i.e.
* {{200}} - works
* {{"200px"}} - works
* {{"200"}} - does not work; yet it works for {{height}}

I'm guessing in RichWidgets the value is autocast to number, but in CDK string will remain a string. This will be an issue for every component. I will look for a workaround but I think the easiest way is to keep a list of options for each component and and parse them in the Bridge.
                
      was (Author: michpetrov):
    The issue is with jQuery, and it's strange that it's not being handled. The problem is here:
{code}
_setHeightMin: function(height) {
    this.selectList.find('.scroll-box').css('min-height', height);
}
{code}

it doesn't work when height is just a number in string form, i.e.
* {{200}} - works
* {{"200px"}} - works
* {{"200"}} - does not work

I'm guessing in RichWidgets the value is autocast to number, but in CDK string will remain a string. This will be an issue for every component. I will look for a workaround but I think the easiest way is to keep a list of options for each component and and parse them in the Bridge.
                  
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 09:15:08 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 09:15:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.9891.1384438508363@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923623#comment-12923623 ] 

Ji?? ?tefek commented on RF-13346:
----------------------------------

Hi [~mpetrov], here is the [widget issue|https://github.com/richwidgets/richwidgets/issues/75].
                
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 09:15:08 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 09:15:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.9896.1384438508654@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923623#comment-12923623 ] 

Ji?? ?tefek edited comment on RF-13346 at 11/14/13 9:14 AM:
------------------------------------------------------------

Hi [~michpetrov], here is the [widget issue|https://github.com/richwidgets/richwidgets/issues/75].
                
      was (Author: jstefek):
    Hi [~mpetrov], here is the [widget issue|https://github.com/richwidgets/richwidgets/issues/75].
                  
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 09:19:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Thu, 14 Nov 2013 09:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.9904.1384438746023@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923625#comment-12923625 ] 

Juraj H?ska commented on RF-13348:
----------------------------------

Now I can see that it is similar to
https://github.com/richwidgets/richwidgets/issues/124

Should be this one closed as it is expected with JSF 2.1 ?
                
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 09:31:08 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Thu, 14 Nov 2013 09:31:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.10023.1384439468148@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923640#comment-12923640 ] 

Michal Petrov commented on RF-13346:
------------------------------------

Ah right, we have two tracking system now :)
                
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 09:31:08 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Thu, 14 Nov 2013 09:31:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.10028.1384439468426@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923640#comment-12923640 ] 

Michal Petrov edited comment on RF-13346 at 11/14/13 9:30 AM:
--------------------------------------------------------------

Ah right, we have two tracking systems now :)
                
      was (Author: michpetrov):
    Ah right, we have two tracking system now :)
                  
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 09:33:08 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Thu, 14 Nov 2013 09:33:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.10085.1384439588096@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov updated RF-13346:
-------------------------------

    Assignee:     (was: Michal Petrov)

    
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 13:10:05 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Thu, 14 Nov 2013 13:10:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.10677.1384452605925@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923736#comment-12923736 ] 

Mohammad Weshah commented on RF-13323:
--------------------------------------

as i mention on the Bug attribute 2.1.9 , but i tried it on the default  Jboss 7.1 API (2.1.7) , same problem.
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 16:39:06 2013
From: jira-events at lists.jboss.org (Chasidy McMaster (JIRA))
Date: Thu, 14 Nov 2013 16:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-8275) Memory leak with extended
 data table after repeated rerender
In-Reply-To: <JIRA.12402476.1263983958000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12402476.1263983958000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12402476.1263983958000.11011.1384465146075@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-8275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923801#comment-12923801 ] 

Chasidy McMaster commented on RF-8275:
--------------------------------------

We are also seeing similar behavior in 3.3.3 Final.  Has this issue been resolved?
                        (Restricted to jira-users group)
            
> Memory leak with extended data table after repeated rerender
> ------------------------------------------------------------
>
>                 Key: RF-8275
>                 URL: https://issues.jboss.org/browse/RF-8275
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 3.3.2.SR1
>         Environment: Windows xp and AIX, Firefox and Internet Explorer 7
>            Reporter: Manuele Piastra
>            Assignee: Andrey Markhel
>            Priority: Critical
>              Labels: extended_datatable, memory_leak, rerender
>             Fix For: 3.3.3.CR1
>
>         Attachments: index.xhtml
>
>
> After each rerender of the extended data table the memory allocated to the process iexplorer.exe keeps growing and it is never released. The same test with simple datatable doesn't show this problem.
> Snippet code used for the test
> <?xml version='1.0' encoding='UTF-8' ?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="1.2"
>  xmlns="http://www.w3.org/1999/xhtml"
>  xmlns:h="http://java.sun.com/jsf/html"
>  xmlns:f="http://java.sun.com/jsf/core"
>  xmlns:ui="http://java.sun.com/jsf/facelets"
>  xmlns:rich="http://richfaces.org/rich"
>  xmlns:a4j="http://richfaces.org/a4j">
>  <html>
>  <head>
>  <title>RichFaces DataTable</title>
>   </head>
>  <body>
>  <f:view>
>   <h:form>
>    <a4j:jsFunction name="rerenderTable" reRender="finderList"></a4j:jsFunction>
>    <rich:dataTable value="#{provaTableBean.list}" var="elem"
>     id="finderList" width="200px" >
>     <rich:column id="id" width="50" label="Id">
>      <f:facet name="header">
>       <h:outputText value="Id" />
>      </f:facet>
>      <h:outputText value="#{elem.id}" />
>     </rich:column>
>     <rich:column id="nome" width="150" label="Nome">
>      <f:facet name="header">
>       <h:outputText value="Nome" />
>      </f:facet>
>      <h:outputText value="#{elem.nome}" />
>     </rich:column>
>    </rich:dataTable>
>   </h:form>
>  </f:view>
>  <script>
>  setInterval(rerenderTable, 10000);
>  </script>
>  </body>
>  </html>
> </jsp:root>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 14 18:45:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 18:45:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-8275) Memory leak with extended
 data table after repeated rerender
In-Reply-To: <JIRA.12402476.1263983958000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12402476.1263983958000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12402476.1263983958000.11101.1384472707373@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-8275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923813#comment-12923813 ] 

Brian Leathem commented on RF-8275:
-----------------------------------

Do you see this in RichFaces 4?  Likely the fix has been applied there.
                
> Memory leak with extended data table after repeated rerender
> ------------------------------------------------------------
>
>                 Key: RF-8275
>                 URL: https://issues.jboss.org/browse/RF-8275
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 3.3.2.SR1
>         Environment: Windows xp and AIX, Firefox and Internet Explorer 7
>            Reporter: Manuele Piastra
>            Assignee: Andrey Markhel
>            Priority: Critical
>              Labels: extended_datatable, memory_leak, rerender
>             Fix For: 3.3.3.CR1
>
>         Attachments: index.xhtml
>
>
> After each rerender of the extended data table the memory allocated to the process iexplorer.exe keeps growing and it is never released. The same test with simple datatable doesn't show this problem.
> Snippet code used for the test
> <?xml version='1.0' encoding='UTF-8' ?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="1.2"
>  xmlns="http://www.w3.org/1999/xhtml"
>  xmlns:h="http://java.sun.com/jsf/html"
>  xmlns:f="http://java.sun.com/jsf/core"
>  xmlns:ui="http://java.sun.com/jsf/facelets"
>  xmlns:rich="http://richfaces.org/rich"
>  xmlns:a4j="http://richfaces.org/a4j">
>  <html>
>  <head>
>  <title>RichFaces DataTable</title>
>   </head>
>  <body>
>  <f:view>
>   <h:form>
>    <a4j:jsFunction name="rerenderTable" reRender="finderList"></a4j:jsFunction>
>    <rich:dataTable value="#{provaTableBean.list}" var="elem"
>     id="finderList" width="200px" >
>     <rich:column id="id" width="50" label="Id">
>      <f:facet name="header">
>       <h:outputText value="Id" />
>      </f:facet>
>      <h:outputText value="#{elem.id}" />
>     </rich:column>
>     <rich:column id="nome" width="150" label="Nome">
>      <f:facet name="header">
>       <h:outputText value="Nome" />
>      </f:facet>
>      <h:outputText value="#{elem.nome}" />
>     </rich:column>
>    </rich:dataTable>
>   </h:form>
>  </f:view>
>  <script>
>  setInterval(rerenderTable, 10000);
>  </script>
>  </body>
>  </html>
> </jsp:root>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 14 21:52:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 21:52:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13329) Delete old 4.x and below
 pickList and orderingList resources from RF5
In-Reply-To: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524633.1383925284000.11254.1384483925904@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13329:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> Delete old 4.x and below pickList and orderingList resources from RF5
> ---------------------------------------------------------------------
>
>                 Key: RF-13329
>                 URL: https://issues.jboss.org/browse/RF-13329
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Now it should be safe to delete the old resources for {{pickList}} and {{orderingList}}.
> I mean {{.js}} and {{.ecss}} files from this folder:
> https://github.com/richfaces/richfaces/tree/master/framework/src/main/resources/META-INF/resources/org.richfaces/select

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 21:52:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 21:52:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.11256.1384483925984@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13330:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 21:52:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 21:52:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.11260.1384483926157@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13330:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 21:52:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 21:52:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13339) orderingList: ordered
 values are reset after submit
In-Reply-To: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524863.1384255087000.11258.1384483926095@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13339:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> orderingList: ordered values are reset after submit
> ---------------------------------------------------
>
>                 Key: RF-13339
>                 URL: https://issues.jboss.org/browse/RF-13339
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 21:52:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 21:52:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.11265.1384483926348@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923831#comment-12923831 ] 

Brian Leathem commented on RF-13325:
------------------------------------

Let's leave it for a user to request the feature.
                
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 21:52:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 21:52:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13339) orderingList: ordered
 values are reset after submit
In-Reply-To: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524863.1384255087000.11264.1384483926320@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13339:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> orderingList: ordered values are reset after submit
> ---------------------------------------------------
>
>                 Key: RF-13339
>                 URL: https://issues.jboss.org/browse/RF-13339
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 21:52:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 21:52:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13329) Delete old 4.x and below
 pickList and orderingList resources from RF5
In-Reply-To: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524633.1383925284000.11262.1384483926256@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13329:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5

    
> Delete old 4.x and below pickList and orderingList resources from RF5
> ---------------------------------------------------------------------
>
>                 Key: RF-13329
>                 URL: https://issues.jboss.org/browse/RF-13329
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Now it should be safe to delete the old resources for {{pickList}} and {{orderingList}}.
> I mean {{.js}} and {{.ecss}} files from this folder:
> https://github.com/richfaces/richfaces/tree/master/framework/src/main/resources/META-INF/resources/org.richfaces/select

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 21:54:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 21:54:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.11268.1384484045873@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13325.
--------------------------------

    Fix Version/s:     (was: 5.0.0.Alpha2)
       Resolution: Rejected

    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 21:54:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 21:54:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.11270.1384484045970@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13330:
----------------------------------

    Assignee: Brian Leathem

    
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 21:54:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 21:54:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13329) Delete old 4.x and below
 pickList and orderingList resources from RF5
In-Reply-To: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524633.1383925284000.11272.1384484046058@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13329:
----------------------------------

    Assignee: Brian Leathem

    
> Delete old 4.x and below pickList and orderingList resources from RF5
> ---------------------------------------------------------------------
>
>                 Key: RF-13329
>                 URL: https://issues.jboss.org/browse/RF-13329
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Now it should be safe to delete the old resources for {{pickList}} and {{orderingList}}.
> I mean {{.js}} and {{.ecss}} files from this folder:
> https://github.com/richfaces/richfaces/tree/master/framework/src/main/resources/META-INF/resources/org.richfaces/select

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 14 22:16:06 2013
From: jira-events at lists.jboss.org (alexey plotnikov (JIRA))
Date: Thu, 14 Nov 2013 22:16:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13349) a4j:queue must be first
 child for rich:autocomplete
In-Reply-To: <JIRA.12525196.1384485297716@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525196.1384485297716@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525196.1384485297716.11276.1384485366740@jira02.app.mwc.hst.phx2.redhat.com>

alexey plotnikov created RF-13349:
-------------------------------------

             Summary: a4j:queue must be first child for rich:autocomplete
                 Key: RF-13349
                 URL: https://issues.jboss.org/browse/RF-13349
             Project: RichFaces
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.3.4
            Reporter: alexey plotnikov


All described here https://community.jboss.org/message/845845 but i'll repeat.
In this example:
{code}
<rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}"  
                   minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion"  
                   autofill="false"  
                   onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;"  
                   layout="table" value="#{autocomplete.legalName}"  
                   required="true">  
                   <h:column>  
                      <h:outputText style="display:none;" value="#{s.id}"/>  
                      <h:outputText style="display:none;" value="#{s.realName}"/>  
                   </h:column>  
                   <h:column>  
                      <h:outputText value="#{s.name}" escape="false"/>  
                   </h:column>  
                   <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
</rich:autocomplete>
{code}
a4j:queue - is *ignored!*
But here
{code}
<rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}"  
                   minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion"  
                   autofill="false"  
                   onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;"  
                   layout="table" value="#{autocomplete.legalName}"  
                   required="true">  
                   <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
                   <h:column>  
                      <h:outputText style="display:none;" value="#{s.id}"/>  
                      <h:outputText style="display:none;" value="#{s.realName}"/>  
                   </h:column>  
                   <h:column>  
                      <h:outputText value="#{s.name}" escape="false"/>  
                   </h:column>  
</rich:autocomplete>
{code}
a4j:queue *not ignored*. So a4j:queue must be first child for autocomplete.

For another components a4j:queue can be any child(first or last).
For example this code:
{code}
<h:selectOneMenu value="#{agentMenuMassList.menuProfile}">  
    <s:selectItems noSelectionLabel="#{messages['pages.noSelect']}" value="#{agentMenuMassList.menuProfiles}" var="m" label="#{m.name}"/>  
    <s:convertEntity/>  
    <a4j:ajax event="change" render="editPanel,menuPanel" listener="#{agentMenuMassList.change}"/>  
    <a4j:queue requestDelay="5000" />  
</h:selectOneMenu>
{code}
*not* ignoring a4j:queue

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 14 22:32:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 14 Nov 2013 22:32:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13329) Delete old 4.x and below
 pickList and orderingList resources from RF5
In-Reply-To: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524633.1383925284000.11280.1384486325815@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13329.
--------------------------------

    Resolution: Done

    
> Delete old 4.x and below pickList and orderingList resources from RF5
> ---------------------------------------------------------------------
>
>                 Key: RF-13329
>                 URL: https://issues.jboss.org/browse/RF-13329
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Now it should be safe to delete the old resources for {{pickList}} and {{orderingList}}.
> I mean {{.js}} and {{.ecss}} files from this folder:
> https://github.com/richfaces/richfaces/tree/master/framework/src/main/resources/META-INF/resources/org.richfaces/select

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 01:03:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 01:03:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13339) orderingList: ordered
 values are reset after submit
In-Reply-To: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524863.1384255087000.11320.1384495385840@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13339.
--------------------------------

    Fix Version/s:     (was: 5.0.0.Alpha2)
       Resolution: Out of Date


This works with the latest master.
                
> orderingList: ordered values are reset after submit
> ---------------------------------------------------
>
>                 Key: RF-13339
>                 URL: https://issues.jboss.org/browse/RF-13339
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>            Priority: Blocker
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 01:05:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 01:05:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of some attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.11326.1384495506595@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13340:
----------------------------------

    Assignee: Ji?? ?tefek  (was: Brian Leathem)


I suspect this is out of date with recent fixes.  [~jstefek] can you please confirm?
                
> orderingList - setting of some attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style
> * valueChangeListener

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 01:08:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 01:08:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13349) a4j:queue must be first
 child for rich:autocomplete
In-Reply-To: <JIRA.12525196.1384485297000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525196.1384485297000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525196.1384485297000.11328.1384495685879@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13349:
----------------------------------

    Assignee: Pavol Pitonak


QE, please verify
                
> a4j:queue must be first child for rich:autocomplete
> ---------------------------------------------------
>
>                 Key: RF-13349
>                 URL: https://issues.jboss.org/browse/RF-13349
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Pavol Pitonak
>
> All described here https://community.jboss.org/message/845845 but i'll repeat.
> In this example:
> {code}
> <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}"  
>                    minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion"  
>                    autofill="false"  
>                    onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;"  
>                    layout="table" value="#{autocomplete.legalName}"  
>                    required="true">  
>                    <h:column>  
>                       <h:outputText style="display:none;" value="#{s.id}"/>  
>                       <h:outputText style="display:none;" value="#{s.realName}"/>  
>                    </h:column>  
>                    <h:column>  
>                       <h:outputText value="#{s.name}" escape="false"/>  
>                    </h:column>  
>                    <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
> </rich:autocomplete>
> {code}
> a4j:queue - is *ignored!*
> But here
> {code}
> <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}"  
>                    minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion"  
>                    autofill="false"  
>                    onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;"  
>                    layout="table" value="#{autocomplete.legalName}"  
>                    required="true">  
>                    <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
>                    <h:column>  
>                       <h:outputText style="display:none;" value="#{s.id}"/>  
>                       <h:outputText style="display:none;" value="#{s.realName}"/>  
>                    </h:column>  
>                    <h:column>  
>                       <h:outputText value="#{s.name}" escape="false"/>  
>                    </h:column>  
> </rich:autocomplete>
> {code}
> a4j:queue *not ignored*. So a4j:queue must be first child for autocomplete.
> For another components a4j:queue can be any child(first or last).
> For example this code:
> {code}
> <h:selectOneMenu value="#{agentMenuMassList.menuProfile}">  
>     <s:selectItems noSelectionLabel="#{messages['pages.noSelect']}" value="#{agentMenuMassList.menuProfiles}" var="m" label="#{m.name}"/>  
>     <s:convertEntity/>  
>     <a4j:ajax event="change" render="editPanel,menuPanel" listener="#{agentMenuMassList.change}"/>  
>     <a4j:queue requestDelay="5000" />  
> </h:selectOneMenu>
> {code}
> *not* ignoring a4j:queue

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 01:10:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 01:10:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.11332.1384495805977@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923847#comment-12923847 ] 

Brian Leathem commented on RF-13348:
------------------------------------

Good question [~jhuska].  We have a conflict of compatibilities here.  To be compatible with RF 4, or compatible with JSF.  Would you mind raising this for discussion on richfaces-dev?  We'll hash it out there, then come back and update this issue.
                
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 01:24:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 01:24:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13347) pickList:
	switchByDblClick does not work
In-Reply-To: <JIRA.12525090.1384426336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525090.1384426336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525090.1384426336000.11334.1384496645827@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923848#comment-12923848 ] 

Brian Leathem commented on RF-13347:
------------------------------------

It does not work because the default value in the component is true:

{code}
    @Attribute(defaultValue = "true")
    public abstract boolean isSwitchByDblClick();
{code}

The cdk does not set the option value if it is equal to the default value.  In this case the default value in the component does not match the default value in the widget.

I'll change the default in the widget to match.
I will change the default value in the widget to match.
                
> pickList: switchByDblClick does not work
> ----------------------------------------
>
>                 Key: RF-13347
>                 URL: https://issues.jboss.org/browse/RF-13347
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> Setting of {{pickList}} attribute {{switchByDblClick}} to {{true}} does not work.
> Note that {{switchByClick}} works as expected.
> It seems that attribute is set in render template. I can not found any mention in pick list bridge if that can be the case ? (there is no mention of {{switchByClick}} neither and it works).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 01:40:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 01:40:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13347) pickList:
	switchByDblClick does not work
In-Reply-To: <JIRA.12525090.1384426336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525090.1384426336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525090.1384426336000.11347.1384497605998@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13347.
--------------------------------

    Resolution: Done

    
> pickList: switchByDblClick does not work
> ----------------------------------------
>
>                 Key: RF-13347
>                 URL: https://issues.jboss.org/browse/RF-13347
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> Setting of {{pickList}} attribute {{switchByDblClick}} to {{true}} does not work.
> Note that {{switchByClick}} works as expected.
> It seems that attribute is set in render template. I can not found any mention in pick list bridge if that can be the case ? (there is no mention of {{switchByClick}} neither and it works).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 01:40:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 01:40:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13347) pickList:
	switchByDblClick does not work
In-Reply-To: <JIRA.12525090.1384426336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525090.1384426336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525090.1384426336000.11349.1384497606108@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13347:
----------------------------------

    Assignee: Brian Leathem

    
> pickList: switchByDblClick does not work
> ----------------------------------------
>
>                 Key: RF-13347
>                 URL: https://issues.jboss.org/browse/RF-13347
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>
> Setting of {{pickList}} attribute {{switchByDblClick}} to {{true}} does not work.
> Note that {{switchByClick}} works as expected.
> It seems that attribute is set in render template. I can not found any mention in pick list bridge if that can be the case ? (there is no mention of {{switchByClick}} neither and it works).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 01:40:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 01:40:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13347) pickList:
	switchByDblClick does not work
In-Reply-To: <JIRA.12525090.1384426336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525090.1384426336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525090.1384426336000.11351.1384497606260@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13347:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> pickList: switchByDblClick does not work
> ----------------------------------------
>
>                 Key: RF-13347
>                 URL: https://issues.jboss.org/browse/RF-13347
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> Setting of {{pickList}} attribute {{switchByDblClick}} to {{true}} does not work.
> Note that {{switchByClick}} works as expected.
> It seems that attribute is set in render template. I can not found any mention in pick list bridge if that can be the case ? (there is no mention of {{switchByClick}} neither and it works).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:03:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:03:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.11360.1384498985862@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923853#comment-12923853 ] 

Brian Leathem commented on RF-13346:
------------------------------------

While in [#75](https://github.com/richwidgets/richwidgets/issues/75#issuecomment-27821682) we agreed to follow the CSS behaviour and have:

# Integer values default to px units
# String values require units

However, as [~michpetrov] pointed out, all facelet attribute values are strings, and so the unit is always required.  While I don't advocate changing the RichWidget behaviour, I do feel we can safely add units in either the js bridge, or in the Renderer.  I suspect it is most _clean_ to intercept the option in the bridge and add the units if they are missing.
                
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:05:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:05:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.11363.1384499106446@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13346:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:07:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:07:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13345) FileUpload: behaves
 incorrectly when placed in ajax rendered outputPanel
In-Reply-To: <JIRA.12525080.1384421762000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525080.1384421762000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525080.1384421762000.11365.1384499225847@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13345:
-------------------------------

    Fix Version/s: 5-Tracking

    
> FileUpload: behaves incorrectly when placed in ajax rendered outputPanel
> ------------------------------------------------------------------------
>
>                 Key: RF-13345
>                 URL: https://issues.jboss.org/browse/RF-13345
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>         Environment: EAP 6.1
> Chrome 30, Firefox 22
>            Reporter: Ji?? ?tefek
>             Fix For: 5-Tracking
>
>         Attachments: RF-13345-RF4-reproducer.zip, RF-13345-RF5-reproducer.zip
>
>
> When fileUpload is placed in ajaxRendered outputPanel, just like this:
> {code}
> <a4j:outputPanel ajaxRendered="true">
>     <rich:fileUpload fileUploadListener="#{richBean.listener}"/>
> </a4j:outputPanel>
> {code}
> then it behaves incorrectly.
> With RF 5:
> the list of uploaded/to upload files is reset after each upload.
> With RF 4:
> * cannot manipulate with item(s) which was firstly uploaded
> * the upload button is not rendered after first upload performed, but you can still add files and manipulate with them (delete them)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:07:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:07:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13344) pickList - maxListHeight
 & minListHeight need to have set units along with number to work
In-Reply-To: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525076.1384420028000.11366.1384499225883@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923854#comment-12923854 ] 

Brian Leathem commented on RF-13344:
------------------------------------

See the discussion in RF-13346.
                
> pickList - maxListHeight & minListHeight need to have set units along with number to work
> -----------------------------------------------------------------------------------------
>
>                 Key: RF-13344
>                 URL: https://issues.jboss.org/browse/RF-13344
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:07:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:07:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13344) pickList - maxListHeight
 & minListHeight need to have set units along with number to work
In-Reply-To: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525076.1384420028000.11369.1384499226028@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13344:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> pickList - maxListHeight & minListHeight need to have set units along with number to work
> -----------------------------------------------------------------------------------------
>
>                 Key: RF-13344
>                 URL: https://issues.jboss.org/browse/RF-13344
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:09:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:09:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.11371.1384499345793@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923855#comment-12923855 ] 

Brian Leathem commented on RF-13327:
------------------------------------

Thanks [~jhuska]
                
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:13:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:13:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13290) Push framework tests
 fail after upgrade to 1.0.17 (probably Warp issue)
In-Reply-To: <JIRA.12508820.1382713860000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508820.1382713860000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508820.1382713860000.11375.1384499585912@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13290:
-------------------------------

    Fix Version/s: 5.0.0.Alpha3

    
> Push framework tests fail after upgrade to 1.0.17 (probably Warp issue)
> -----------------------------------------------------------------------
>
>                 Key: RF-13290
>                 URL: https://issues.jboss.org/browse/RF-13290
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll, tests - functional 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha3
>
>
> The push is correctly using 'long-polling' technique,
> the request is sent, but the response is never sent back,
> that's why I believe the Warp server-side handling fails.
> ----
> Note that I have tried to upgrade to 1.0.18 and it didn't help.
> ----
> I'm marking those tests as {{Failing}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:13:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:13:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13287) rich:extendedDataTable
 column resizing with ajax loading not working properly
In-Reply-To: <JIRA.12508686.1382616678000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508686.1382616678000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508686.1382616678000.11377.1384499586007@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13287:
-------------------------------

    Labels: needs-qe testcase_provided  (was: testcase_provided)

    
> rich:extendedDataTable column resizing with ajax loading not working properly
> -----------------------------------------------------------------------------
>
>                 Key: RF-13287
>                 URL: https://issues.jboss.org/browse/RF-13287
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.4
>         Environment: Glassfish 3.1.2.2, Mojarra 2.1.26, IE10, IE8, Chrome 30,
>            Reporter: Andreas G
>            Assignee: Michal Petrov
>              Labels: needs-qe, testcase_provided
>             Fix For: 4.3.5
>
>
> In a rich:extendedDataTable with ajax loading turned on: When you resize a column and scroll down (load data), the size of the columns reset to their original value. Only the header keeps its size. The header and the data are not matching anymore.
> Reproducible in the 4.3.4 showcase!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 02:15:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:15:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13287) rich:extendedDataTable
 column resizing with ajax loading not working properly
In-Reply-To: <JIRA.12508686.1382616678000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508686.1382616678000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508686.1382616678000.11381.1384499707001@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923857#comment-12923857 ] 

Brian Leathem commented on RF-13287:
------------------------------------

Thanks for resolving this [~michpetrov].  Would you mind porting the fix to the 4.5 and 5.0 branches as well?  this way we will get the fix out ASAP.
                
> rich:extendedDataTable column resizing with ajax loading not working properly
> -----------------------------------------------------------------------------
>
>                 Key: RF-13287
>                 URL: https://issues.jboss.org/browse/RF-13287
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.4
>         Environment: Glassfish 3.1.2.2, Mojarra 2.1.26, IE10, IE8, Chrome 30,
>            Reporter: Andreas G
>            Assignee: Michal Petrov
>              Labels: needs-qe, testcase_provided
>             Fix For: 4.3.5
>
>
> In a rich:extendedDataTable with ajax loading turned on: When you resize a column and scroll down (load data), the size of the columns reset to their original value. Only the header keeps its size. The header and the data are not matching anymore.
> Reproducible in the 4.3.4 showcase!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 02:19:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13206) Failure to reset
 ClassLoader when AWT Initialization errors
In-Reply-To: <JIRA.12501140.1379705166000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501140.1379705166000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501140.1379705166000.11384.1384499945894@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923858#comment-12923858 ] 

Brian Leathem commented on RF-13206:
------------------------------------

[~oakesville] would you like to formulate a pull request with a fix for this issue?

https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA
                
> Failure to reset ClassLoader when AWT Initialization errors
> -----------------------------------------------------------
>
>                 Key: RF-13206
>                 URL: https://issues.jboss.org/browse/RF-13206
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: core
>    Affects Versions: 4.3.3
>         Environment: ServiceMix
>            Reporter: Donald Oakes
>            Priority: Minor
>
> In org.richfaces.application.InitializationListener.AWTInitializer, the initalize() method can fail to reset the context ClassLoader despite the finally block that should do that (from line 195):
> {code:title=org.richfaces.application.InitializationListener.AWTInitializer#195}
>             } finally {
>                 if (testStream != null) {
>                     try {
>                         testStream.close();
>                     } catch (IOException e) {
>                         LOGGER.error(e.getMessage(), e);
>                     }
>                 }
>                 thread.setContextClassLoader(initialTCCL);
>             }
> {code}
> In my OSGi environment, the testStream.close() invocation throws the NoClassDefFoundError pasted below.  This circumvents the subsequent intention to restore the context ClassLoader.  In effect, if AWT initialization fails the context ClassLoader is left in a bad state that prevents future ServiceTracker processing and hoses up the Faces initialization.
> {code}
> java.lang.NoClassDefFoundError: javax/imageio/stream/ImageInputStream
>         at org.richfaces.application.InitializationListener$AWTInitializer.initialize(InitializationListener.java:198)
>         at org.richfaces.application.InitializationListener.initializeAWT(InitializationListener.java:94)
>         at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:78)
>         at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:152)
>         at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43)
>         at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2471)
>         at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:120)
>         at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2662)
>         at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:601)
>         at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:286)
>         at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:154)
>         at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 02:19:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13206) Failure to reset
 ClassLoader when AWT Initialization errors
In-Reply-To: <JIRA.12501140.1379705166000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501140.1379705166000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501140.1379705166000.11387.1384499946030@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13206:
-------------------------------

    Fix Version/s: 5-Tracking

    
> Failure to reset ClassLoader when AWT Initialization errors
> -----------------------------------------------------------
>
>                 Key: RF-13206
>                 URL: https://issues.jboss.org/browse/RF-13206
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: core
>    Affects Versions: 4.3.3
>         Environment: ServiceMix
>            Reporter: Donald Oakes
>            Priority: Minor
>             Fix For: 5-Tracking
>
>
> In org.richfaces.application.InitializationListener.AWTInitializer, the initalize() method can fail to reset the context ClassLoader despite the finally block that should do that (from line 195):
> {code:title=org.richfaces.application.InitializationListener.AWTInitializer#195}
>             } finally {
>                 if (testStream != null) {
>                     try {
>                         testStream.close();
>                     } catch (IOException e) {
>                         LOGGER.error(e.getMessage(), e);
>                     }
>                 }
>                 thread.setContextClassLoader(initialTCCL);
>             }
> {code}
> In my OSGi environment, the testStream.close() invocation throws the NoClassDefFoundError pasted below.  This circumvents the subsequent intention to restore the context ClassLoader.  In effect, if AWT initialization fails the context ClassLoader is left in a bad state that prevents future ServiceTracker processing and hoses up the Faces initialization.
> {code}
> java.lang.NoClassDefFoundError: javax/imageio/stream/ImageInputStream
>         at org.richfaces.application.InitializationListener$AWTInitializer.initialize(InitializationListener.java:198)
>         at org.richfaces.application.InitializationListener.initializeAWT(InitializationListener.java:94)
>         at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:78)
>         at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:152)
>         at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43)
>         at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2471)
>         at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:120)
>         at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2662)
>         at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:601)
>         at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:286)
>         at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:154)
>         at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 02:19:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13206) Failure to reset
 ClassLoader when AWT Initialization errors
In-Reply-To: <JIRA.12501140.1379705166000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501140.1379705166000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501140.1379705166000.11390.1384499946242@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13206:
-------------------------------

    Labels: low_hanging_fruit  (was: )

    
> Failure to reset ClassLoader when AWT Initialization errors
> -----------------------------------------------------------
>
>                 Key: RF-13206
>                 URL: https://issues.jboss.org/browse/RF-13206
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: core
>    Affects Versions: 4.3.3
>         Environment: ServiceMix
>            Reporter: Donald Oakes
>            Priority: Minor
>              Labels: low_hanging_fruit
>             Fix For: 5-Tracking
>
>
> In org.richfaces.application.InitializationListener.AWTInitializer, the initalize() method can fail to reset the context ClassLoader despite the finally block that should do that (from line 195):
> {code:title=org.richfaces.application.InitializationListener.AWTInitializer#195}
>             } finally {
>                 if (testStream != null) {
>                     try {
>                         testStream.close();
>                     } catch (IOException e) {
>                         LOGGER.error(e.getMessage(), e);
>                     }
>                 }
>                 thread.setContextClassLoader(initialTCCL);
>             }
> {code}
> In my OSGi environment, the testStream.close() invocation throws the NoClassDefFoundError pasted below.  This circumvents the subsequent intention to restore the context ClassLoader.  In effect, if AWT initialization fails the context ClassLoader is left in a bad state that prevents future ServiceTracker processing and hoses up the Faces initialization.
> {code}
> java.lang.NoClassDefFoundError: javax/imageio/stream/ImageInputStream
>         at org.richfaces.application.InitializationListener$AWTInitializer.initialize(InitializationListener.java:198)
>         at org.richfaces.application.InitializationListener.initializeAWT(InitializationListener.java:94)
>         at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:78)
>         at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:152)
>         at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43)
>         at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2471)
>         at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:120)
>         at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2662)
>         at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:601)
>         at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:286)
>         at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:154)
>         at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 02:21:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13207) Table having multiple
 sub-rows within a main row in extended datatable
In-Reply-To: <JIRA.12501169.1379921283000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501169.1379921283000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501169.1379921283000.11397.1384500066170@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13207:
-------------------------------

    Labels: waiting_on_user  (was: )

    
> Table having multiple sub-rows within a main row in extended datatable
> ----------------------------------------------------------------------
>
>                 Key: RF-13207
>                 URL: https://issues.jboss.org/browse/RF-13207
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: cdk, component-tables
>    Affects Versions: 4.3.1
>         Environment: windows 7 , JRE 7 
>            Reporter: sathiyan venkatesh
>              Labels: waiting_on_user
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 02:21:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13209) RichTree JS
 onselectionchange() with a4jregion template
In-Reply-To: <JIRA.12501179.1379927682000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501179.1379927682000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501179.1379927682000.11399.1384500066243@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13209:
-------------------------------

    Fix Version/s: 5-Tracking

    
> RichTree JS onselectionchange() with a4jregion template
> -------------------------------------------------------
>
>                 Key: RF-13209
>                 URL: https://issues.jboss.org/browse/RF-13209
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.2.3.Final, 4.3.3, 4.3.4
>            Reporter: Matej Novotny
>             Fix For: 5-Tracking
>
>
> There is a bug when using onselectionchange() JS API in RichTree component using A4jRegion template (rest of the templates cause no problems).
> The event will be called twice - in my case I tested it with simple alert("text") in Metamer using JBoss AS 7.1.
> This bug appears in older version as well, so far I have tested it with 4.3.4, 4.3.3 and 4.2.3 Final builds all of which caused the same double event.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 02:21:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.11401.1384500066347@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13210:
----------------------------------

    Assignee: Luk?? Fry?


[~lfryc] is this now out of date?
                
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:23:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:23:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13216) PoupPanel doesn't
 disappear when rendered="false" and rerender it.
In-Reply-To: <JIRA.12501363.1380018548000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501363.1380018548000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501363.1380018548000.11407.1384500186584@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923860#comment-12923860 ] 

Brian Leathem commented on RF-13216:
------------------------------------

[~tkonishi] can we close this issue?
                
> PoupPanel doesn't disappear when rendered="false" and rerender it.
> ------------------------------------------------------------------
>
>                 Key: RF-13216
>                 URL: https://issues.jboss.org/browse/RF-13216
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 4.3.3
>            Reporter: Takayuki Konishi
>              Labels: gss
>         Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip
>
>
> If you use the richfaces popupPanel in the default  domElementAttachment="body" mode it will not disappear under specific conditions.
> {code:xml} 
>     <h:body title="page 1">
>         <a4j:outputPanel id="myPanel">
>             <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}">
>                 <h:form>
>                     <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/>
>                 </h:form>
>             </rich:popupPanel>
>             <h:form>
>                 <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/>
>             </h:form>
>         </a4j:outputPanel>
>     </h:body>
> {code} 
> In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. 
> Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final.
> Note:
> In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 02:23:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:23:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13216) PoupPanel doesn't
 disappear when rendered="false" and rerender it.
In-Reply-To: <JIRA.12501363.1380018548000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501363.1380018548000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501363.1380018548000.11413.1384500186872@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13216:
-------------------------------

    Labels: gss waiting_on_user  (was: gss)

    
> PoupPanel doesn't disappear when rendered="false" and rerender it.
> ------------------------------------------------------------------
>
>                 Key: RF-13216
>                 URL: https://issues.jboss.org/browse/RF-13216
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 4.3.3
>            Reporter: Takayuki Konishi
>              Labels: gss, waiting_on_user
>         Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip
>
>
> If you use the richfaces popupPanel in the default  domElementAttachment="body" mode it will not disappear under specific conditions.
> {code:xml} 
>     <h:body title="page 1">
>         <a4j:outputPanel id="myPanel">
>             <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}">
>                 <h:form>
>                     <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/>
>                 </h:form>
>             </rich:popupPanel>
>             <h:form>
>                 <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/>
>             </h:form>
>         </a4j:outputPanel>
>     </h:body>
> {code} 
> In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view. 
> Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final.
> Note:
> In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 02:23:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:23:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13221) Incorrect XML encoding
	in AJAX response
In-Reply-To: <JIRA.12501466.1380105464000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501466.1380105464000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501466.1380105464000.11417.1384500187128@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13221.
--------------------------------

    Resolution: Rejected


Upstream issue.
                
> Incorrect XML encoding in AJAX response
> ---------------------------------------
>
>                 Key: RF-13221
>                 URL: https://issues.jboss.org/browse/RF-13221
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: Jon?? Trantina
>              Labels: gss
>
> Consider the following example:
> {noformat}
> <h:form>
> <a4j:commandButton render="@form" value="rerender me"/>
> <script src="path_to_some_script?param=asd&amp;important=param"></script>
> </h:form>
> {noformat}
> when commandButton is clicked, the form is rerendered and the response looks like this:
> {noformat}
> <partial-response><changes><update id="someID"><![CDATA[
>    ...
>   <script src="path_to_some_script?param=asd&amp;important=param"></script>
> ]]</ ... >
> {noformat}
> But this is wrong. Because script tag is already in CDATA, so there is no need for XML encoding for '&' entity.
> This further causes script loading to fail (performed by jsf.js), whenever parameters are needed (e.g. portal environment), 
> because script is downloaded from {noformat}"path_to_some_script?param=asd&amp;important=param" {noformat}
> instead of {noformat}"path_to_some_script?param=asd&important=param"{noformat}.
> Another very similar issue is when CDATA element is present in a re-rendered fragment. Example:
> {noformat}
> <h:form>
> <a4j:commandButton render="@form" value="rerender me"/>
> <style type="text/css">
> /* <![CDATA[ */
>       .somecssclass {...}
> /* ]] */
> </style>
> </h:form>
> {noformat}
> The AJAX response then looks like so:
> {noformat}
> <partial-response><changes><update id="someID"><![CDATA[
> ...
>    <![CDATA[
>       ...
>   ]]
> ...
> ]]</ ... >
> {noformat}
> And this is incorrect XML, since CDATA cannot contain ']]', so the response is discarded.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:23:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:23:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13244) StyleProps and
 StyleClassProps should be merged to one interface
In-Reply-To: <JIRA.12502201.1380888528000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502201.1380888528000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502201.1380888528000.11419.1384500187212@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13244.
--------------------------------

    Resolution: Rejected

    
> StyleProps and StyleClassProps should be merged to one interface
> ----------------------------------------------------------------
>
>                 Key: RF-13244
>                 URL: https://issues.jboss.org/browse/RF-13244
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> It doesn't make sense to have several style-realted interface since style and styleClass appears togetger.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:25:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:25:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support
 complex components like rich:autocomplete
In-Reply-To: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502430.1381226839000.11422.1384500306052@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13251:
----------------------------------

    Assignee: Luk?? Fry?


@lfryc please assess and schedule accordingly
                
> FocusManager to support complex components like rich:autocomplete
> -----------------------------------------------------------------
>
>                 Key: RF-13251
>                 URL: https://issues.jboss.org/browse/RF-13251
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.3.4
>            Reporter: Immo Benjes
>            Assignee: Luk?? Fry?
>            Priority: Minor
>
> Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete.
> It would be good if FocusManager could support complex components or 'real' Ids as generated for that page.
> The use case for the support on autocomplete is like this:
> User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:25:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:25:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13257) PhotoAlbum bugs
In-Reply-To: <JIRA.12502772.1381491871000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502772.1381491871000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502772.1381491871000.11424.1384500306226@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13257:
-------------------------------

    Fix Version/s: 4.3.5

    
> PhotoAlbum bugs
> ---------------
>
>                 Key: RF-13257
>                 URL: https://issues.jboss.org/browse/RF-13257
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: Ji?? ?tefek
>             Fix For: 4.3.5
>
>
> PhotoAlbum 4.3.x known bugs:
> * uploading file to album (image isn't saved to DB)
> * deleting uploaded file (cannot delete not existing file, but the image is present in album even after relog)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:31:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:31:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13344) pickList - maxListHeight
 & minListHeight need to have set units along with number to work
In-Reply-To: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525076.1384420028000.11440.1384500666028@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13344:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> pickList - maxListHeight & minListHeight need to have set units along with number to work
> -----------------------------------------------------------------------------------------
>
>                 Key: RF-13344
>                 URL: https://issues.jboss.org/browse/RF-13344
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:31:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:31:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.11443.1384500666235@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13346:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:33:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:33:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of some attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.11445.1384500785931@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13340:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> orderingList - setting of some attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style
> * valueChangeListener

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:33:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.11448.1384500786058@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13331:
-------------------------------

     Original Estimate: 1 hour
    Remaining Estimate: 1 hour

    
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:33:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.11452.1384500786235@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13330:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5, 5.0.0.Alpha2 - Sprint 6  (was: 5.0.0.Alpha2 - Sprint 5)

    
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:33:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of some attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.11456.1384500786403@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13340:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5, 5.0.0.Alpha2 - Sprint 6  (was: 5.0.0.Alpha2 - Sprint 5)

    
> orderingList - setting of some attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style
> * valueChangeListener

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:33:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.11459.1384500786540@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13331:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 5, 5.0.0.Alpha2 - Sprint 6  (was: 5.0.0.Alpha2 - Sprint 5)

    
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:33:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.11462.1384500786697@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13346:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 02:33:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 02:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13344) pickList - maxListHeight
 & minListHeight need to have set units along with number to work
In-Reply-To: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525076.1384420028000.11464.1384500786766@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13344:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> pickList - maxListHeight & minListHeight need to have set units along with number to work
> -----------------------------------------------------------------------------------------
>
>                 Key: RF-13344
>                 URL: https://issues.jboss.org/browse/RF-13344
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 03:00:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 03:00:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13344) pickList - maxListHeight
 & minListHeight need to have set units along with number to work
In-Reply-To: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525076.1384420028000.11537.1384502406825@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13344:
----------------------------------

    Assignee: Brian Leathem

    
> pickList - maxListHeight & minListHeight need to have set units along with number to work
> -----------------------------------------------------------------------------------------
>
>                 Key: RF-13344
>                 URL: https://issues.jboss.org/browse/RF-13344
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 03:00:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 03:00:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.11540.1384502407030@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13346:
----------------------------------

    Assignee: Brian Leathem

    
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 03:55:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 03:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13344) pickList - maxListHeight
 & minListHeight need to have set units along with number to work
In-Reply-To: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525076.1384420028000.11654.1384505706748@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13344.
--------------------------------

    Resolution: Done


Added a _addUnitsIfRequired method to bridge-base and used it in the pick and ordering lists to add units to numerical height values
                
> pickList - maxListHeight & minListHeight need to have set units along with number to work
> -----------------------------------------------------------------------------------------
>
>                 Key: RF-13344
>                 URL: https://issues.jboss.org/browse/RF-13344
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 03:57:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 03:57:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13346) orderingList -
 maxListHeight & minListHeight need to have set units along with number to
 work
In-Reply-To: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525089.1384426194000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525089.1384426194000.11661.1384505825900@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13346.
--------------------------------

    Resolution: Done


Added a _addUnitsIfRequired method to bridge-base and used it in the pick and ordering lists to add units to numerical height values
                
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13346
>                 URL: https://issues.jboss.org/browse/RF-13346
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 04:13:05 2013
From: jira-events at lists.jboss.org (Pavel Slegr (JIRA))
Date: Fri, 15 Nov 2013 04:13:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13172) rich:toolbarGroup
 location="right" doesn't work if toolbarGroup location="left" contains not
 rendered values
In-Reply-To: <JIRA.12500222.1378479644000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500222.1378479644000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500222.1378479644000.11701.1384506785905@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923900#comment-12923900 ] 

Pavel Slegr commented on RF-13172:
----------------------------------

Brian, your suggestion was basically correct, additionally there is also getCountSeparators method, where the same thing (using rendered child's only) had to be fixed
pull request sent ... against RF4/components repo
                
> rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13172
>                 URL: https://issues.jboss.org/browse/RF-13172
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-menu
>    Affects Versions: 4.3.3
>            Reporter: Sergey Zubarev
>            Assignee: Pavel Slegr
>              Labels: low_hanging_fruit
>             Fix For: 5-Tracking
>
>
> {code}
> <rich:toolbar itemSeparator="line" id="repairWorkToolbar">
>   <rich:toolbarGroup>
>     <a4j:commandLink value="btn1"/>
>     <a4j:commandLink value="btn2"/>
>     <a4j:commandLink value="btn3" *rendered="false"*/>
>   </rich:toolbarGroup>
>   <rich:toolbarGroup location="right">
>     <a4j:commandLink value="btn_right"/>
>   </rich:toolbarGroup>
> ...
> {code}
> In this case location="right" doesn't work : it displayed left. When I remove rendered="false" from btn3 all works fine.
> Html debug shows, that code produced one extra element in colgroup tag when using rendered="false".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 05:34:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 15 Nov 2013 05:34:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.11857.1384511646334@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923923#comment-12923923 ] 

Juraj H?ska commented on RF-13348:
----------------------------------

Created https://community.jboss.org/message/845869#845869
                
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 06:19:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 15 Nov 2013 06:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.12034.1384514346910@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923943#comment-12923943 ] 

Juraj H?ska commented on RF-13343:
----------------------------------

[~ppitonak] : Afaik and Mr. grep as well think that the only usage is to setup hotkey selector in one test.

I have switched it to manual setting in this commit:
https://github.com/richfaces/richfaces-qa/commit/06183063b37bc7b71388b8104860691c14c66625
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 06:32:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 15 Nov 2013 06:32:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.12109.1384515125895@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923949#comment-12923949 ] 

Luk?? Fry? commented on RF-13331:
---------------------------------

Lukas, please use / introduce the category FailingOnFirefox alongside the Failing category.

We also need to introduce it into richfaces5/pom.xml to integration-tests profile so that tests will be driven by that.
Let's open an RFPL (QA component) issue to adress test compatiblity.
                
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 06:34:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 15 Nov 2013 06:34:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.12117.1384515246353@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923951#comment-12923951 ] 

Luk?? Fry? commented on RF-13210:
---------------------------------

Note, it's not, we should move RichFaces Core JS resources such as richfaces.js to org.richfaces resource library and re-configure resource packaging.
                
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 06:36:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 15 Nov 2013 06:36:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.12119.1384515365847@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923951#comment-12923951 ] 

Luk?? Fry? edited comment on RF-13210 at 11/15/13 6:34 AM:
-----------------------------------------------------------

No, it's not, we should move RichFaces Core JS resources such as richfaces.js to org.richfaces resource library and re-configure resource packaging.
                
      was (Author: lfryc):
    Note, it's not, we should move RichFaces Core JS resources such as richfaces.js to org.richfaces resource library and re-configure resource packaging.
                  
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 07:50:07 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 15 Nov 2013 07:50:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13349) a4j:queue must be first
 child for rich:autocomplete
In-Reply-To: <JIRA.12525196.1384485297000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525196.1384485297000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525196.1384485297000.12303.1384519807970@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923969#comment-12923969 ] 

Pavol Pitonak commented on RF-13349:
------------------------------------

I could not reproduce with RichFaces 4.3.4.Final.

Alexey, could you please provide me more information about your environment, such as OS, browser, JSF version and which app server are you deploying to?
                
> a4j:queue must be first child for rich:autocomplete
> ---------------------------------------------------
>
>                 Key: RF-13349
>                 URL: https://issues.jboss.org/browse/RF-13349
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Pavol Pitonak
>
> All described here https://community.jboss.org/message/845845 but i'll repeat.
> In this example:
> {code}
> <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}"  
>                    minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion"  
>                    autofill="false"  
>                    onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;"  
>                    layout="table" value="#{autocomplete.legalName}"  
>                    required="true">  
>                    <h:column>  
>                       <h:outputText style="display:none;" value="#{s.id}"/>  
>                       <h:outputText style="display:none;" value="#{s.realName}"/>  
>                    </h:column>  
>                    <h:column>  
>                       <h:outputText value="#{s.name}" escape="false"/>  
>                    </h:column>  
>                    <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
> </rich:autocomplete>
> {code}
> a4j:queue - is *ignored!*
> But here
> {code}
> <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}"  
>                    minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion"  
>                    autofill="false"  
>                    onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;"  
>                    layout="table" value="#{autocomplete.legalName}"  
>                    required="true">  
>                    <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
>                    <h:column>  
>                       <h:outputText style="display:none;" value="#{s.id}"/>  
>                       <h:outputText style="display:none;" value="#{s.realName}"/>  
>                    </h:column>  
>                    <h:column>  
>                       <h:outputText value="#{s.name}" escape="false"/>  
>                    </h:column>  
> </rich:autocomplete>
> {code}
> a4j:queue *not ignored*. So a4j:queue must be first child for autocomplete.
> For another components a4j:queue can be any child(first or last).
> For example this code:
> {code}
> <h:selectOneMenu value="#{agentMenuMassList.menuProfile}">  
>     <s:selectItems noSelectionLabel="#{messages['pages.noSelect']}" value="#{agentMenuMassList.menuProfiles}" var="m" label="#{m.name}"/>  
>     <s:convertEntity/>  
>     <a4j:ajax event="change" render="editPanel,menuPanel" listener="#{agentMenuMassList.change}"/>  
>     <a4j:queue requestDelay="5000" />  
> </h:selectOneMenu>
> {code}
> *not* ignoring a4j:queue

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 07:50:08 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 15 Nov 2013 07:50:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13349) a4j:queue must be first
 child for rich:autocomplete
In-Reply-To: <JIRA.12525196.1384485297000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525196.1384485297000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525196.1384485297000.12307.1384519808342@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13349:
-------------------------------

    Labels: waiting_on_user  (was: )

    
> a4j:queue must be first child for rich:autocomplete
> ---------------------------------------------------
>
>                 Key: RF-13349
>                 URL: https://issues.jboss.org/browse/RF-13349
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Pavol Pitonak
>              Labels: waiting_on_user
>
> All described here https://community.jboss.org/message/845845 but i'll repeat.
> In this example:
> {code}
> <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}"  
>                    minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion"  
>                    autofill="false"  
>                    onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;"  
>                    layout="table" value="#{autocomplete.legalName}"  
>                    required="true">  
>                    <h:column>  
>                       <h:outputText style="display:none;" value="#{s.id}"/>  
>                       <h:outputText style="display:none;" value="#{s.realName}"/>  
>                    </h:column>  
>                    <h:column>  
>                       <h:outputText value="#{s.name}" escape="false"/>  
>                    </h:column>  
>                    <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
> </rich:autocomplete>
> {code}
> a4j:queue - is *ignored!*
> But here
> {code}
> <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}"  
>                    minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion"  
>                    autofill="false"  
>                    onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;"  
>                    layout="table" value="#{autocomplete.legalName}"  
>                    required="true">  
>                    <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
>                    <h:column>  
>                       <h:outputText style="display:none;" value="#{s.id}"/>  
>                       <h:outputText style="display:none;" value="#{s.realName}"/>  
>                    </h:column>  
>                    <h:column>  
>                       <h:outputText value="#{s.name}" escape="false"/>  
>                    </h:column>  
> </rich:autocomplete>
> {code}
> a4j:queue *not ignored*. So a4j:queue must be first child for autocomplete.
> For another components a4j:queue can be any child(first or last).
> For example this code:
> {code}
> <h:selectOneMenu value="#{agentMenuMassList.menuProfile}">  
>     <s:selectItems noSelectionLabel="#{messages['pages.noSelect']}" value="#{agentMenuMassList.menuProfiles}" var="m" label="#{m.name}"/>  
>     <s:convertEntity/>  
>     <a4j:ajax event="change" render="editPanel,menuPanel" listener="#{agentMenuMassList.change}"/>  
>     <a4j:queue requestDelay="5000" />  
> </h:selectOneMenu>
> {code}
> *not* ignoring a4j:queue

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 11:39:06 2013
From: jira-events at lists.jboss.org (Chasidy McMaster (JIRA))
Date: Fri, 15 Nov 2013 11:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-8275) Memory leak with extended
 data table after repeated rerender
In-Reply-To: <JIRA.12402476.1263983958000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12402476.1263983958000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12402476.1263983958000.13391.1384533546041@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-8275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924106#comment-12924106 ] 

Chasidy McMaster commented on RF-8275:
--------------------------------------

>From what I read, RichFaces 4.0 requires JSF 2.0 and we aren't ready to make that leap quite yet. 
                
> Memory leak with extended data table after repeated rerender
> ------------------------------------------------------------
>
>                 Key: RF-8275
>                 URL: https://issues.jboss.org/browse/RF-8275
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 3.3.2.SR1
>         Environment: Windows xp and AIX, Firefox and Internet Explorer 7
>            Reporter: Manuele Piastra
>            Assignee: Andrey Markhel
>            Priority: Critical
>              Labels: extended_datatable, memory_leak, rerender
>             Fix For: 3.3.3.CR1
>
>         Attachments: index.xhtml
>
>
> After each rerender of the extended data table the memory allocated to the process iexplorer.exe keeps growing and it is never released. The same test with simple datatable doesn't show this problem.
> Snippet code used for the test
> <?xml version='1.0' encoding='UTF-8' ?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="1.2"
>  xmlns="http://www.w3.org/1999/xhtml"
>  xmlns:h="http://java.sun.com/jsf/html"
>  xmlns:f="http://java.sun.com/jsf/core"
>  xmlns:ui="http://java.sun.com/jsf/facelets"
>  xmlns:rich="http://richfaces.org/rich"
>  xmlns:a4j="http://richfaces.org/a4j">
>  <html>
>  <head>
>  <title>RichFaces DataTable</title>
>   </head>
>  <body>
>  <f:view>
>   <h:form>
>    <a4j:jsFunction name="rerenderTable" reRender="finderList"></a4j:jsFunction>
>    <rich:dataTable value="#{provaTableBean.list}" var="elem"
>     id="finderList" width="200px" >
>     <rich:column id="id" width="50" label="Id">
>      <f:facet name="header">
>       <h:outputText value="Id" />
>      </f:facet>
>      <h:outputText value="#{elem.id}" />
>     </rich:column>
>     <rich:column id="nome" width="150" label="Nome">
>      <f:facet name="header">
>       <h:outputText value="Nome" />
>      </f:facet>
>      <h:outputText value="#{elem.nome}" />
>     </rich:column>
>    </rich:dataTable>
>   </h:form>
>  </f:view>
>  <script>
>  setInterval(rerenderTable, 10000);
>  </script>
>  </body>
>  </html>
> </jsp:root>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 11:59:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 15 Nov 2013 11:59:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13350) pickList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525335.1384534676351@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525335.1384534676351@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525335.1384534676351.13457.1384534747686@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13350:
--------------------------------

             Summary: pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
                 Key: RF-13350
                 URL: https://issues.jboss.org/browse/RF-13350
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska


Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.

The {{styleClass}} is included just in {{passThrough}}  attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml#L65].

Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L33-34] in autocomplate render base ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 12:04:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 12:04:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13172) rich:toolbarGroup
 location="right" doesn't work if toolbarGroup location="left" contains not
 rendered values
In-Reply-To: <JIRA.12500222.1378479644000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500222.1378479644000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500222.1378479644000.13478.1384535045865@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13172:
-------------------------------

    Fix Version/s: 4.3.5
                       (was: 5-Tracking)

    
> rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13172
>                 URL: https://issues.jboss.org/browse/RF-13172
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-menu
>    Affects Versions: 4.3.3
>            Reporter: Sergey Zubarev
>            Assignee: Pavel Slegr
>              Labels: low_hanging_fruit
>             Fix For: 4.3.5
>
>
> {code}
> <rich:toolbar itemSeparator="line" id="repairWorkToolbar">
>   <rich:toolbarGroup>
>     <a4j:commandLink value="btn1"/>
>     <a4j:commandLink value="btn2"/>
>     <a4j:commandLink value="btn3" *rendered="false"*/>
>   </rich:toolbarGroup>
>   <rich:toolbarGroup location="right">
>     <a4j:commandLink value="btn_right"/>
>   </rich:toolbarGroup>
> ...
> {code}
> In this case location="right" doesn't work : it displayed left. When I remove rendered="false" from btn3 all works fine.
> Html debug shows, that code produced one extra element in colgroup tag when using rendered="false".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 12:04:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 12:04:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13172) rich:toolbarGroup
 location="right" doesn't work if toolbarGroup location="left" contains not
 rendered values
In-Reply-To: <JIRA.12500222.1378479644000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500222.1378479644000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500222.1378479644000.13481.1384535045994@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13172:
-------------------------------

    Labels: low_hanging_fruit needs-qe  (was: low_hanging_fruit)

    
> rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13172
>                 URL: https://issues.jboss.org/browse/RF-13172
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-menu
>    Affects Versions: 4.3.3
>            Reporter: Sergey Zubarev
>            Assignee: Pavel Slegr
>              Labels: low_hanging_fruit, needs-qe
>             Fix For: 4.3.5
>
>
> {code}
> <rich:toolbar itemSeparator="line" id="repairWorkToolbar">
>   <rich:toolbarGroup>
>     <a4j:commandLink value="btn1"/>
>     <a4j:commandLink value="btn2"/>
>     <a4j:commandLink value="btn3" *rendered="false"*/>
>   </rich:toolbarGroup>
>   <rich:toolbarGroup location="right">
>     <a4j:commandLink value="btn_right"/>
>   </rich:toolbarGroup>
> ...
> {code}
> In this case location="right" doesn't work : it displayed left. When I remove rendered="false" from btn3 all works fine.
> Html debug shows, that code produced one extra element in colgroup tag when using rendered="false".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 15 12:08:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 12:08:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13350) pickList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525335.1384534676000.13488.1384535285932@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924121#comment-12924121 ] 

Brian Leathem commented on RF-13350:
------------------------------------

Since we have no need to concatenate classes on that element we can simply use the CDK attribute mapping syntax in the pass through:
{code}
class:styleClass
{code}
                
> pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
> -------------------------------------------------------------------------------------------
>
>                 Key: RF-13350
>                 URL: https://issues.jboss.org/browse/RF-13350
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>
> Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.
> The {{styleClass}} is included just in {{passThrough}}  attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml#L65].
> Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L33-34] in autocomplate render base ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 12:08:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 12:08:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13350) pickList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525335.1384534676000.13491.1384535286099@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13350:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
> -------------------------------------------------------------------------------------------
>
>                 Key: RF-13350
>                 URL: https://issues.jboss.org/browse/RF-13350
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.
> The {{styleClass}} is included just in {{passThrough}}  attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml#L65].
> Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L33-34] in autocomplate render base ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 12:10:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 12:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.13497.1384535406023@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13210:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 12:39:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 12:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.13604.1384537146037@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13348:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 14:57:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 14:57:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.13800.1384545427135@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924167#comment-12924167 ] 

Brian Leathem commented on RF-13348:
------------------------------------

The _columnClasses_ attribute doc describes the fix implemented:

{quote}
_columnClasses_ specifies a comma-delimited list of CSS style classes to apply to each column.
A space separated list of classes may be specified for an individual column.

If the number of classes in this list is less than the number of column children, then no class will be
applied to the columns greater than the number of classes.  If however the final class in the list is the `*`
character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order
the class in this list.

If there are more class names than columns, the overflow ones are ignored.
{quote}
                
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 14:57:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 14:57:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.13805.1384545427296@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13348.
--------------------------------

      Assignee: Brian Leathem
    Resolution: Done

    
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 14:57:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 14:57:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13350) pickList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525335.1384534676000.13807.1384545427361@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13350:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
> -------------------------------------------------------------------------------------------
>
>                 Key: RF-13350
>                 URL: https://issues.jboss.org/browse/RF-13350
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.
> The {{styleClass}} is included just in {{passThrough}}  attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml#L65].
> Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L33-34] in autocomplate render base ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 14:57:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 14:57:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.13809.1384545427450@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13210:
-------------------------------

     Original Estimate: 1 hour
    Remaining Estimate: 1 hour

    
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 14:59:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 14:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13350) pickList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525335.1384534676000.13811.1384545546278@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13350:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
> -------------------------------------------------------------------------------------------
>
>                 Key: RF-13350
>                 URL: https://issues.jboss.org/browse/RF-13350
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.
> The {{styleClass}} is included just in {{passThrough}}  attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml#L65].
> Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L33-34] in autocomplate render base ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 14:59:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 14:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.13813.1384545546360@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13210:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 15:04:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 15:04:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13350) pickList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525335.1384534676000.13821.1384545845890@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13350:
----------------------------------

    Assignee: Brian Leathem

    
> pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
> -------------------------------------------------------------------------------------------
>
>                 Key: RF-13350
>                 URL: https://issues.jboss.org/browse/RF-13350
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.
> The {{styleClass}} is included just in {{passThrough}}  attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml#L65].
> Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L33-34] in autocomplate render base ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 15:12:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 15:12:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13350) pickList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525335.1384534676000.13861.1384546326059@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13350.
--------------------------------

    Resolution: Done

    
> pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
> -------------------------------------------------------------------------------------------
>
>                 Key: RF-13350
>                 URL: https://issues.jboss.org/browse/RF-13350
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.
> The {{styleClass}} is included just in {{passThrough}}  attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml#L65].
> Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L33-34] in autocomplate render base ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 17:20:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 15 Nov 2013 17:20:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11284) rich:autocomplete on
 Mojarra doesn't handle suggestions/selection correctly
In-Reply-To: <JIRA.12444076.1312983789000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12444076.1312983789000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12444076.1312983789000.13976.1384554006007@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-11284:
-------------------------------

    Assignee:     (was: Brian Leathem)

    
> rich:autocomplete on Mojarra doesn't handle suggestions/selection correctly
> ---------------------------------------------------------------------------
>
>                 Key: RF-11284
>                 URL: https://issues.jboss.org/browse/RF-11284
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 4.1.0.Milestone1
>         Environment: RichFaces 4.1.0.20110805-M1 r.10246d45dddd1d2aa2034317d5a832394cc919f9
> Metamer 4.1.0.20110805-M1 r.22604
> Mojarra 2.0.3-
> JBoss AS 6.0.0.Final
> Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
> Chrome 12.0.742.112 @ Linux i686, IE7, 
>            Reporter: J?n Jamrich
>             Fix For: 5-Tracking
>
>
> In the contrary with rich:autocomplete with MyFaces, there is not working suggestions or suggestion selection for autocomplete.
> Common case is type some keys into autocomplete input, e.g. "al" and wait for display suggestions, in this case "Alabama, Alaska". Then pick one of them, and this item should appear in autocomplete input instead of typed characters (so that value start with upper case and so on), and this value appears in output element.
> It is working correctly with autocomplete example without any changes (just open page faces/components/richAutocomplete/autocomplete.xhtml).
> But when set any attribute value (such as layout to div, or minChars to 2 or something else), selection from autocomplete suggestions stop work.
> Then is not possible to select item from suggestion, but when click (or select by narrovs and press enter) on an item, then suggestions disappears, but autocomplete input remain empty not the output is updated by selected value.
> The workaround is invalidate session, but it causes clean attribute value (so then is not minChars or layout attribute set to any value).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 15 19:44:06 2013
From: jira-events at lists.jboss.org (Val Blant (JIRA))
Date: Fri, 15 Nov 2013 19:44:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4308) rich:pickList: keep sort
 order of source list after add/remove operations
In-Reply-To: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12366369.1219836667000.14042.1384562646336@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924210#comment-12924210 ] 

Val Blant commented on RF-4308:
-------------------------------

I have an easy fix for this problem that seems to work pretty well. Just include this _orderedPickListFix.js_ in your app, and the pickLists should start behaving.

{code:javascript|title=orderedPickListFix.js|borderStyle=solid}
/**
 * This is an extension to the RichFaces PickList that preserves the original order of items in the source list
 * 
 * @author Val Blant
 */
if ( typeof window.RichFaces.ui.List != 'undefined' && !window.PickListExtension ) {
	
	window.PickListExtension = {};
	
	
	if ( typeof window.RichFaces.ui.PickList != 'undefined' ) {

		/**
		 * Overriding original constructor found in "org.richfaces/pickList.js" resource
		 */
		window.RichFaces.ui.PickList = function(oldPickListConstructor) {
			return function(id, options) {
				// Instantiate the original PickList
				//
				var pickList = new oldPickListConstructor(id, options);
				
				// Assign item indecies to each item in the source list to preserve original order
				//
				pickList.sourceList.items.each(function( index ) {
					this.itemIndex = index;
				});
				
				return pickList;
			};
		}(window.RichFaces.ui.PickList);
		
	}
	
	
	
	/**
	 * Original code taken from "org.richfaces/list.js" resource
	 */
	(function($, rf, list) {

	   /**
	    * Insert items into a pick list according to their original order stored in 'itemIndex' attribute
	    */
	    list.prototype.addItems = function(items) {
               var parentContainer = this.scrollContainer;
               
               items.each(function() { 
                   if ( parentContainer.children().length < this.itemIndex ) {
                   	parentContainer.append(this);
                   }
                   else {
                	itemAtOurIndex = parentContainer.children()[this.itemIndex];
                	jQuery(this).insertBefore( itemAtOurIndex );
                   }
               });
            
               this.__updateItemsList();
               rf.Event.fire(this, "additems", items);			
  	   };
	
     }(jQuery, window.RichFaces, window.RichFaces.ui.List));
}
{code} 
                
> rich:pickList: keep sort order of source list after add/remove operations
> -------------------------------------------------------------------------
>
>                 Key: RF-4308
>                 URL: https://issues.jboss.org/browse/RF-4308
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.2
>            Reporter: Martin H?ller
>              Labels: order, picklist, sort
>             Fix For: 3.Future
>
>
> When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user.
> My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sat Nov 16 05:44:05 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Sat, 16 Nov 2013 05:44:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.14123.1384598645911@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924222#comment-12924222 ] 

Mohammad Weshah commented on RF-13323:
--------------------------------------

Hello Ji?? ?tefek
 Any update ?

Regards
Wish79
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 17 06:16:06 2013
From: jira-events at lists.jboss.org (Salvo Isaja (JIRA))
Date: Sun, 17 Nov 2013 06:16:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12682) extendedDataTable render
 issue with rich:tabPanel
In-Reply-To: <JIRA.12481662.1356024824000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12481662.1356024824000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12481662.1356024824000.14266.1384686966800@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924253#comment-12924253 ] 

Salvo Isaja commented on RF-12682:
----------------------------------

Hello Brian,
unfortunately I'm hitting this issue with 4.3.4. I'm using the tab panel of Bootstrap 3, though, not RichFaces'. When switching tabs, the height of the extendedDataTable seems to drop to zero (the headers are not visible too, everything is grayed out in Firebug) and the table is blank. This even happens without switching tabs, but just opening Firebug (but not just resizing the browser window). Tested on Firefox 25.
Any help is appreciated.
Thanks,
   Salvo
                
> extendedDataTable render issue with rich:tabPanel
> -------------------------------------------------
>
>                 Key: RF-12682
>                 URL: https://issues.jboss.org/browse/RF-12682
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final
>            Reporter: Kaveh A.
>              Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided
>         Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip
>
>
> This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time).
> In this particular case if we load a page with two tabs.  Furthermore if we have one extendedDataTable in each tab  (the first tab shows and the second tab is not shown at first).  In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly.  A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue.
> https://community.jboss.org/message/783787

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Sun Nov 17 06:18:06 2013
From: jira-events at lists.jboss.org (Salvo Isaja (JIRA))
Date: Sun, 17 Nov 2013 06:18:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12193) rich:extendedDataTable
	is blank on show
In-Reply-To: <JIRA.12464804.1335212251000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12464804.1335212251000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12464804.1335212251000.14274.1384687086157@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924254#comment-12924254 ] 

Salvo Isaja commented on RF-12193:
----------------------------------

Seems to be still present as of 4.3.4, please see my comment on issue 12682. Thanks.
                
> rich:extendedDataTable is blank on show
> ---------------------------------------
>
>                 Key: RF-12193
>                 URL: https://issues.jboss.org/browse/RF-12193
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.2.1.Final
>         Environment: Firefox 11, Internet Explorer 8
>            Reporter: Nick Dev
>            Assignee: Brian Leathem
>             Fix For: 4.3.2, 5.0.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> rich:extendedDataTable is blank when shown after it was hidden.
> Firefox: complete table is blank.
> IE: table header is not displayed.
> Table is shown after resizing the window.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Sun Nov 17 22:13:06 2013
From: jira-events at lists.jboss.org (alexey plotnikov (JIRA))
Date: Sun, 17 Nov 2013 22:13:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13349) a4j:queue must be first
 child for rich:autocomplete
In-Reply-To: <JIRA.12525196.1384485297000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525196.1384485297000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525196.1384485297000.14508.1384744386664@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924291#comment-12924291 ] 

alexey plotnikov commented on RF-13349:
---------------------------------------

Hmmm, i can not reproduce too :(. But this bug was produced on some page(i don't remember page name). I'll try find this page.
                
> a4j:queue must be first child for rich:autocomplete
> ---------------------------------------------------
>
>                 Key: RF-13349
>                 URL: https://issues.jboss.org/browse/RF-13349
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: alexey plotnikov
>            Assignee: Pavol Pitonak
>              Labels: waiting_on_user
>
> All described here https://community.jboss.org/message/845845 but i'll repeat.
> In this example:
> {code}
> <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}"  
>                    minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion"  
>                    autofill="false"  
>                    onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;"  
>                    layout="table" value="#{autocomplete.legalName}"  
>                    required="true">  
>                    <h:column>  
>                       <h:outputText style="display:none;" value="#{s.id}"/>  
>                       <h:outputText style="display:none;" value="#{s.realName}"/>  
>                    </h:column>  
>                    <h:column>  
>                       <h:outputText value="#{s.name}" escape="false"/>  
>                    </h:column>  
>                    <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
> </rich:autocomplete>
> {code}
> a4j:queue - is *ignored!*
> But here
> {code}
> <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}"  
>                    minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion"  
>                    autofill="false"  
>                    onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;"  
>                    layout="table" value="#{autocomplete.legalName}"  
>                    required="true">  
>                    <a4j:queue requestDelay="500" ignoreDupResponses="true" />  
>                    <h:column>  
>                       <h:outputText style="display:none;" value="#{s.id}"/>  
>                       <h:outputText style="display:none;" value="#{s.realName}"/>  
>                    </h:column>  
>                    <h:column>  
>                       <h:outputText value="#{s.name}" escape="false"/>  
>                    </h:column>  
> </rich:autocomplete>
> {code}
> a4j:queue *not ignored*. So a4j:queue must be first child for autocomplete.
> For another components a4j:queue can be any child(first or last).
> For example this code:
> {code}
> <h:selectOneMenu value="#{agentMenuMassList.menuProfile}">  
>     <s:selectItems noSelectionLabel="#{messages['pages.noSelect']}" value="#{agentMenuMassList.menuProfiles}" var="m" label="#{m.name}"/>  
>     <s:convertEntity/>  
>     <a4j:ajax event="change" render="editPanel,menuPanel" listener="#{agentMenuMassList.change}"/>  
>     <a4j:queue requestDelay="5000" />  
> </h:selectOneMenu>
> {code}
> *not* ignoring a4j:queue

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 01:52:05 2013
From: jira-events at lists.jboss.org (Pavel Slegr (JIRA))
Date: Mon, 18 Nov 2013 01:52:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13317)
 ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState
 id in startUpdate()
In-Reply-To: <JIRA.12518007.1383648996000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12518007.1383648996000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12518007.1383648996000.14555.1384757525886@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Slegr reassigned RF-13317:
--------------------------------

    Assignee: Pavel Slegr

    
> ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13317
>                 URL: https://issues.jboss.org/browse/RF-13317
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>         Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1
>            Reporter: Matti Bickel
>            Assignee: Pavel Slegr
>            Priority: Critical
>              Labels: jsf22
>             Fix For: 4.3.5
>
>
> I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests:
> When the response comes back, the data is fine but I get a JSF error saying
> bq. During update: javax.faces.ViewState not found
> Following that, no componentData is available to the Autocomplete component and no suggestions get displayed.
> For reference the javadoc for ResponseStateManager.VIEW_STATE_PARAM says:
> {quote}
> Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 02:43:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 02:43:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13339) orderingList: ordered
 values are reset after submit
In-Reply-To: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524863.1384255087000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524863.1384255087000.14581.1384760585821@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924307#comment-12924307 ] 

Ji?? ?tefek commented on RF-13339:
----------------------------------

Verified, it works.
                
> orderingList: ordered values are reset after submit
> ---------------------------------------------------
>
>                 Key: RF-13339
>                 URL: https://issues.jboss.org/browse/RF-13339
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>            Priority: Blocker
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 03:01:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 03:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13351) orderingList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525395.1384761556962@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525395.1384761556962@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525395.1384761556962.14585.1384761666369@jira02.app.mwc.hst.phx2.redhat.com>

Ji?? ?tefek created RF-13351:
--------------------------------

             Summary: orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
                 Key: RF-13351
                 URL: https://issues.jboss.org/browse/RF-13351
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Ji?? ?tefek
            Assignee: Brian Leathem
             Fix For: 5.0.0.Alpha2


Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.

The {{styleClass}} is included just in {{passThrough}}  attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml#L65].

Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L33-34] in autocomplate render base ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 03:01:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 03:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13351) orderingList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525395.1384761556000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525395.1384761556000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525395.1384761556000.14586.1384761666448@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13351:
-----------------------------

    Description: Setting of {{styleClass}} attribute to the {{orderingList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.  (was: Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.

The {{styleClass}} is included just in {{passThrough}}  attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml#L65].

Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L33-34] in autocomplate render base ?)

    
> orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13351
>                 URL: https://issues.jboss.org/browse/RF-13351
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of {{styleClass}} attribute to the {{orderingList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 03:03:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 03:03:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13351) orderingList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525395.1384761556000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525395.1384761556000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525395.1384761556000.14589.1384761785901@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924309#comment-12924309 ] 

Ji?? ?tefek commented on RF-13351:
----------------------------------

I'll send a PR.
                
> orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13351
>                 URL: https://issues.jboss.org/browse/RF-13351
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of {{styleClass}} attribute to the {{orderingList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 03:21:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 03:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13351) orderingList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525395.1384761556000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525395.1384761556000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525395.1384761556000.14595.1384762865869@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek reassigned RF-13351:
--------------------------------

    Assignee: Ji?? ?tefek  (was: Brian Leathem)

    
> orderingList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13351
>                 URL: https://issues.jboss.org/browse/RF-13351
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of {{styleClass}} attribute to the {{orderingList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 03:29:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 03:29:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of some attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.14603.1384763346585@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek reassigned RF-13340:
--------------------------------

    Assignee: Brian Leathem  (was: Ji?? ?tefek)


Yes, [~bleathem], it is out of date now .
                
> orderingList - setting of some attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style
> * valueChangeListener

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 04:11:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 04:11:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13341) Charts: implement
	AjaxProps
In-Reply-To: <JIRA.12524903.1384269969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524903.1384269969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524903.1384269969000.14704.1384765867805@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924331#comment-12924331 ] 

Luk?? Macko commented on RF-13341:
----------------------------------

I think the advantage of the custom chart server-side listener/event is that event.data can be propagated to the server. It will not be the most common use case probably, however it might be useful e.g to show some additional information related to a value clicked in a chart, in my opinion.
                
> Charts: implement AjaxProps
> ---------------------------
>
>                 Key: RF-13341
>                 URL: https://issues.jboss.org/browse/RF-13341
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>            Priority: Minor
>
> I think AbstractChart should implements AjaxProps since it uses server-side listeners.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 05:37:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 05:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.15079.1384771026160@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924415#comment-12924415 ] 

Ji?? ?tefek commented on RF-13323:
----------------------------------

[~wish79], tried this:
- vanilla JBoss AS 7.1.1.Final: impl: _jsf-impl-2.1.7-jbossorg-2_ and apis: _jboss-jsf-api_2.1_spec-2.0.1.Final_ , works.
- JBoss AS 7.1.1.Final with updated impl to: _jsf-impl-2.1.9-jbossorg-1_ , works.
- JBoss AS 7.1.1.Final with updated impl to: _jsf-impl-2.1.9-jbossorg-1_ + updated apis to:  _jboss-jsf-api_2.1_spec-2.0.9.Final_ , works.

What apis/impls are you using? Do you replace them as in this [comment|http://stackoverflow.com/a/11495699]? Or are you using the Oracle ones?

System? JDK? 64bit?
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 06:35:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 06:35:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.15414.1384774506471@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? moved RFPL-3055 to RF-13352:
---------------------------------------

        Project: RichFaces  (was: RichFaces Planning)
            Key: RF-13352  (was: RFPL-3055)
     Issue Type: Enhancement  (was: Feature Request)
    Component/s: tests - functional 
                     (was: build)
                     (was: jsf-test)

    
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Fry?
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 06:37:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 06:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.15426.1384774626239@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924450#comment-12924450 ] 

Luk?? Fry? commented on RF-13352:
---------------------------------

Hey Lukas, you are right.

Could you please give a try to implement it?

Hints:
configure a profile {{browser-firefox}} to setup appropriate category: here is the default value:
https://github.com/richfaces/richfaces/blob/master/pom.xml#L446
                
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Fry?
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 06:39:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 18 Nov 2013 06:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.15433.1384774746404@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13352:
----------------------------

    Assignee: Luk?? Macko  (was: Luk?? Fry?)

    
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Macko
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 08:00:08 2013
From: jira-events at lists.jboss.org (Immo Benjes (JIRA))
Date: Mon, 18 Nov 2013 08:00:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13353) Javascript callbacks on
 global queue are not called
In-Reply-To: <JIRA.12525446.1384779581549@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525446.1384779581549@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525446.1384779581549.15772.1384779608876@jira02.app.mwc.hst.phx2.redhat.com>

Immo Benjes created RF-13353:
--------------------------------

             Summary: Javascript callbacks on global queue are not called
                 Key: RF-13353
                 URL: https://issues.jboss.org/browse/RF-13353
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.3.4
            Reporter: Immo Benjes


Only two of the javascript callbacks on a:queue are actually functional:

{code}
<a:queue name="org.richfaces.queue.global" requestDelay="300" ignoreDupResponce="true" onrequestqueue="log('onrequestqueue')" onsubmit="log('onsubmit')" oncomplete="log('oncomplete')" onrequestdequeue="log('onrequestdequeue')" onbeforedomupdate="log('onbeforedom')"/>
{code}

When doing an ajax request only onrequestqueue and onrequestdequeue are called. onsubmit, oncomplete and onbeforedomupdate are not called.

Please note: log('xx') is a wrapper around console.log()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 09:09:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 18 Nov 2013 09:09:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13354) Autocomplete:
 suggestions stay visible after input is cleared
In-Reply-To: <JIRA.12525458.1384783692646@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525458.1384783692646@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525458.1384783692646.15909.1384783745823@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13354:
----------------------------------

             Summary: Autocomplete: suggestions stay visible after input is cleared
                 Key: RF-13354
                 URL: https://issues.jboss.org/browse/RF-13354
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-input, regression
    Affects Versions: 5.0.0.Alpha2
         Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
EAP 6.1.1
Mojarra 2.1.19
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 31.0.1650.57 @ Linux x86_64
            Reporter: Pavol Pitonak


# deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
# type "ala" into input (several suggestions will appear)
# clear input, e.g. by using backspace key

result:
* the list with all available suggestions is displayed
* in 4.3.4.Final, the suggestions are *not* displayed when input is empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 09:39:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 18 Nov 2013 09:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13355) Upgrade Mojarra to 2.1.26
In-Reply-To: <JIRA.12525466.1384785440213@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525466.1384785440213@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525466.1384785440213.15976.1384785546001@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13355:
----------------------------------

             Summary: Upgrade Mojarra to 2.1.26
                 Key: RF-13355
                 URL: https://issues.jboss.org/browse/RF-13355
             Project: RichFaces
          Issue Type: Component  Upgrade
      Security Level: Public (Everyone can see)
          Components: third-party
    Affects Versions: 5.0.0.Alpha2
            Reporter: Pavol Pitonak


RichFaces 5 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.

[1] https://github.com/richfaces/richfaces/blob/master/build/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 09:39:06 2013
From: jira-events at lists.jboss.org (Anton Bogoslavskyi (JIRA))
Date: Mon, 18 Nov 2013 09:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) RF-8602 Reproduced in
	4.3.3.Final
In-Reply-To: <JIRA.12525467.1384785454764@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454764@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454764.15978.1384785546234@jira02.app.mwc.hst.phx2.redhat.com>

Anton Bogoslavskyi created RF-13356:
---------------------------------------

             Summary: RF-8602 Reproduced in 4.3.3.Final
                 Key: RF-13356
                 URL: https://issues.jboss.org/browse/RF-13356
             Project: RichFaces
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: regression
    Affects Versions: 4.3.3
            Reporter: Anton Bogoslavskyi
             Fix For: 4.3.5


The same as in the parent issue:

Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 11:51:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 11:51:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) RF-8602 Reproduced in
	4.3.3.Final
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.16504.1384793465870@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13356:
-------------------------------

        Parent:     (was: RF-8602)
    Issue Type: Bug  (was: Sub-task)

    
> RF-8602 Reproduced in 4.3.3.Final
> ---------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: regression
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>             Fix For: 4.3.5
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 11:51:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 11:51:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) RF-8602 Reproduced in
	4.3.3.Final
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.16506.1384793465938@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13356:
-------------------------------

    Fix Version/s:     (was: 4.3.5)

    
> RF-8602 Reproduced in 4.3.3.Final
> ---------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: regression
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 11:53:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 11:53:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.16508.1384793586359@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13356:
-------------------------------

    Summary: ExtendedDataTable: row height strechted to 100% of the table height  (was: RF-8602 Reproduced in 4.3.3.Final)

    
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: regression
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 11:53:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 11:53:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.16510.1384793586460@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13356:
-------------------------------

    Component/s: component-tables
                     (was: regression)

    
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 11:53:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 11:53:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.16516.1384793586754@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13356:
----------------------------------

    Assignee: Pavol Pitonak


QE, can you please try to reproduce in RF 4.3.latest this issue that was previously resolved in RF 3?
                
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>            Assignee: Pavol Pitonak
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 11:57:05 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Mon, 18 Nov 2013 11:57:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.16524.1384793825849@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924588#comment-12924588 ] 

Mohammad Weshah commented on RF-13323:
--------------------------------------

default Jboss AS 7.1 jsf API (2.1.7) 
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 11:59:06 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Mon, 18 Nov 2013 11:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.16528.1384793946318@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924588#comment-12924588 ] 

Mohammad Weshah edited comment on RF-13323 at 11/18/13 11:57 AM:
-----------------------------------------------------------------

default Jboss AS 7.1 jsf API (2.1.7) 
Java 1.6.0_24-b07
64bit
                
      was (Author: wish79):
    default Jboss AS 7.1 jsf API (2.1.7) 
                  
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 12:34:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 12:34:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.16576.1384796045861@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13352:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 12:40:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 12:40:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4308) rich:pickList: keep sort
 order of source list after add/remove operations
In-Reply-To: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12366369.1219836667000.16606.1384796407456@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-4308:
------------------------------

    Fix Version/s: 5-Tracking
                       (was: 3.Future)

    
> rich:pickList: keep sort order of source list after add/remove operations
> -------------------------------------------------------------------------
>
>                 Key: RF-4308
>                 URL: https://issues.jboss.org/browse/RF-4308
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.2
>            Reporter: Martin H?ller
>              Labels: order, picklist, sort
>             Fix For: 5-Tracking
>
>
> When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user.
> My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 13:17:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 13:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4308) rich:pickList: keep sort
 order of source list after add/remove operations
In-Reply-To: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12366369.1219836667000.16692.1384798626933@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924613#comment-12924613 ] 

Brian Leathem commented on RF-4308:
-----------------------------------

If we resolve RichWidget issue [#137|https://github.com/richwidgets/richwidgets/issues/137] with the proposed javascript callback method, then the RichFaces 5 picklist CDK template could define a _data-index_ attribute, and the widget-bridge could implement a sort callback that sorted on that _data-index_ attribute.

Using this sort would be activated by setting the _orderable = false_ facelet attribute.
                
> rich:pickList: keep sort order of source list after add/remove operations
> -------------------------------------------------------------------------
>
>                 Key: RF-4308
>                 URL: https://issues.jboss.org/browse/RF-4308
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.2
>            Reporter: Martin H?ller
>              Labels: order, picklist, sort
>             Fix For: 5-Tracking
>
>
> When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user.
> My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 18:03:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 18:03:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4308) rich:pickList: keep sort
 order of source list after add/remove operations
In-Reply-To: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12366369.1219836667000.17117.1384815786373@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924687#comment-12924687 ] 

Brian Leathem commented on RF-4308:
-----------------------------------

RichWidget issue [#137|https://github.com/richwidgets/richwidgets/issues/137] has been resoloved; the client-side hook is now in place.  Further work required to resolve this issue involves:

# Extending [ClientSelectItem|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/ClientSelectItem.java] to track the sequence number of the Selectitem in the pick list
# Adding a _data-rf-index_ attribute to the items in the pick list [CDK template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml]
# Adding a _sortFunction_ option to the pick-list widget invocation in the [pick-list-bridge|https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/bridge/select/pick-list-bridge.js]

----

In the mean time, a workaround would be to implement your own pick list widget _sortFunction_ by listening for the widget _create_ event:
{code}
$('<my-selector>').on('picklist', 'create', function(a, b) {
   return ...
});
{code}

A concrete example of this looks like:
{code}
$('#list').on('picklistcreate', function(event, ui) {
  $('#list').pickList('option', 'sortFunction', function(a, b) {
    return $(a).data('key') - $(b).data('key');
  });
});
{code}
                
> rich:pickList: keep sort order of source list after add/remove operations
> -------------------------------------------------------------------------
>
>                 Key: RF-4308
>                 URL: https://issues.jboss.org/browse/RF-4308
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.2
>            Reporter: Martin H?ller
>              Labels: order, picklist, sort
>             Fix For: 5-Tracking
>
>
> When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user.
> My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 18:05:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 18:05:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4308) rich:pickList: keep sort
 order of source list after add/remove operations
In-Reply-To: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12366369.1219836667000.17132.1384815907063@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-4308:
------------------------------

    Affects Version/s: 5.0.0.Alpha1
                       4.3.4

    
> rich:pickList: keep sort order of source list after add/remove operations
> -------------------------------------------------------------------------
>
>                 Key: RF-4308
>                 URL: https://issues.jboss.org/browse/RF-4308
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.2, 4.3.4, 5.0.0.Alpha1
>            Reporter: Martin H?ller
>              Labels: order, picklist, sort
>             Fix For: 5-Tracking
>
>
> When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user.
> My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 18:05:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 18:05:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4308) rich:pickList: keep sort
 order of source list after add/remove operations
In-Reply-To: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12366369.1219836667000.17147.1384815907965@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-4308:
------------------------------

    Component/s: component-selects

    
> rich:pickList: keep sort order of source list after add/remove operations
> -------------------------------------------------------------------------
>
>                 Key: RF-4308
>                 URL: https://issues.jboss.org/browse/RF-4308
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 3.2.2, 4.3.4, 5.0.0.Alpha1
>            Reporter: Martin H?ller
>              Labels: order, picklist, sort
>             Fix For: 5-Tracking
>
>
> When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user.
> My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 18:05:08 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 18:05:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-4308) rich:pickList: keep sort
 order of source list after add/remove operations
In-Reply-To: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12366369.1219836667000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12366369.1219836667000.17162.1384815908734@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-4308:
------------------------------

    Labels: low_hanging_fruit order picklist sort  (was: order picklist sort)

    
> rich:pickList: keep sort order of source list after add/remove operations
> -------------------------------------------------------------------------
>
>                 Key: RF-4308
>                 URL: https://issues.jboss.org/browse/RF-4308
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 3.2.2, 4.3.4, 5.0.0.Alpha1
>            Reporter: Martin H?ller
>              Labels: low_hanging_fruit, order, picklist, sort
>             Fix For: 5-Tracking
>
>
> When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user.
> My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 18:09:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 18:09:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13355) Upgrade Mojarra
In-Reply-To: <JIRA.12525466.1384785440000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525466.1384785440000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525466.1384785440000.17164.1384816145824@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13355:
-------------------------------

    Summary: Upgrade Mojarra  (was: Upgrade Mojarra to 2.1.26)


RichFaces 5 Alphas should track WildFly, and hence update to JSF 2.2.
                
> Upgrade Mojarra
> ---------------
>
>                 Key: RF-13355
>                 URL: https://issues.jboss.org/browse/RF-13355
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Pavol Pitonak
>
> RichFaces 5 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.
> [1] https://github.com/richfaces/richfaces/blob/master/build/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 18:09:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 18:09:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13355) Upgrade Mojarra
In-Reply-To: <JIRA.12525466.1384785440000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525466.1384785440000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525466.1384785440000.17166.1384816145899@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13355:
-------------------------------

    Fix Version/s: 5.0.0.Alpha3

    
> Upgrade Mojarra
> ---------------
>
>                 Key: RF-13355
>                 URL: https://issues.jboss.org/browse/RF-13355
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha3
>
>
> RichFaces 5 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.
> [1] https://github.com/richfaces/richfaces/blob/master/build/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 18:09:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 18:09:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13354) Autocomplete:
 suggestions stay visible after input is cleared
In-Reply-To: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525458.1384783692000.17168.1384816146006@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13354:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Autocomplete: suggestions stay visible after input is cleared
> -------------------------------------------------------------
>
>                 Key: RF-13354
>                 URL: https://issues.jboss.org/browse/RF-13354
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # type "ala" into input (several suggestions will appear)
> # clear input, e.g. by using backspace key
> result:
> * the list with all available suggestions is displayed
> * in 4.3.4.Final, the suggestions are *not* displayed when input is empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 18:11:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 18:11:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13353) Javascript callbacks on
 global queue are not called
In-Reply-To: <JIRA.12525446.1384779581000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525446.1384779581000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525446.1384779581000.17175.1384816267872@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13353.
--------------------------------

    Resolution: Duplicate Issue

    
> Javascript callbacks on global queue are not called
> ---------------------------------------------------
>
>                 Key: RF-13353
>                 URL: https://issues.jboss.org/browse/RF-13353
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.4
>            Reporter: Immo Benjes
>              Labels: a:queue
>
> Only two of the javascript callbacks on a:queue are actually functional:
> {code}
> <a:queue name="org.richfaces.queue.global" requestDelay="300" ignoreDupResponce="true" onrequestqueue="log('onrequestqueue')" onsubmit="log('onsubmit')" oncomplete="log('oncomplete')" onrequestdequeue="log('onrequestdequeue')" onbeforedomupdate="log('onbeforedom')"/>
> {code}
> When doing an ajax request only onrequestqueue and onrequestdequeue are called. onsubmit, oncomplete and onbeforedomupdate are not called.
> Please note: log('xx') is a wrapper around console.log()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 18 18:21:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 18:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13340) orderingList - setting
 of some attributes does not have any effect on the component
In-Reply-To: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524867.1384257806000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524867.1384257806000.17178.1384816865809@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13340.
--------------------------------

         Assignee:     (was: Brian Leathem)
    Fix Version/s:     (was: 5.0.0.Alpha2)
       Resolution: Out of Date

    
> orderingList - setting of some attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13340
>                 URL: https://issues.jboss.org/browse/RF-13340
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of these attributes on a {{orderingList}} has no effect on the rendered component
> * style
> * valueChangeListener

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 18 18:25:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 18 Nov 2013 18:25:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12682) extendedDataTable render
 issue with rich:tabPanel
In-Reply-To: <JIRA.12481662.1356024824000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12481662.1356024824000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12481662.1356024824000.17192.1384817106062@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924692#comment-12924692 ] 

Brian Leathem commented on RF-12682:
------------------------------------

[~salvois] would you please file a new issue (referencing this one) with appropriate re-producer code attached?
                
> extendedDataTable render issue with rich:tabPanel
> -------------------------------------------------
>
>                 Key: RF-12682
>                 URL: https://issues.jboss.org/browse/RF-12682
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final
>            Reporter: Kaveh A.
>              Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided
>         Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip
>
>
> This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time).
> In this particular case if we load a page with two tabs.  Furthermore if we have one extendedDataTable in each tab  (the first tab shows and the second tab is not shown at first).  In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly.  A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue.
> https://community.jboss.org/message/783787

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 02:25:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 02:25:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13357) Switch RichFaces to use
 dist branch of RichWidgets to avoid a need for compiling own version
In-Reply-To: <JIRA.12525517.1384845803710@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525517.1384845803710@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525517.1384845803710.17390.1384845905868@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13357:
-------------------------------

             Summary: Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version
                 Key: RF-13357
                 URL: https://issues.jboss.org/browse/RF-13357
             Project: RichFaces
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
          Components: component
            Reporter: Luk?? Fry?
             Fix For: 5.0.0.Alpha2




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 02:58:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 02:58:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.17402.1384847885866@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924738#comment-12924738 ] 

Ji?? ?tefek commented on RF-13323:
----------------------------------

Sorry, even with yours JVM I can't reproduce it.
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 03:00:06 2013
From: jira-events at lists.jboss.org (Pavel Slegr (JIRA))
Date: Tue, 19 Nov 2013 03:00:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12813) rich:panelMenuItem
 executes action even if disabled attribute evaluates to true
In-Reply-To: <JIRA.12486095.1362189003000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12486095.1362189003000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12486095.1362189003000.17405.1384848006832@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Slegr reassigned RF-12813:
--------------------------------

    Assignee: Pavel Slegr

    
> rich:panelMenuItem executes action even if disabled attribute evaluates to true
> -------------------------------------------------------------------------------
>
>                 Key: RF-12813
>                 URL: https://issues.jboss.org/browse/RF-12813
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-menu
>    Affects Versions: 4.3.0.Final
>            Reporter: Andrey Zhemoytuk
>            Assignee: Pavel Slegr
>             Fix For: 4.3.5
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> org.richfaces.renderkit.html.PanelMenuItemRenderer#doDecode does not check 'disabled' attribute (how usually do other components before executing action) which may cause security issues.
> Initially reported on:
> http://stackoverflow.com/questions/15130807/richfaces-panelmenuitem-reevaluating-disabled-not-working

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 03:49:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 03:49:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13355) Upgrade Mojarra
In-Reply-To: <JIRA.12525466.1384785440000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525466.1384785440000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525466.1384785440000.17480.1384850945927@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924751#comment-12924751 ] 

Pavol Pitonak commented on RF-13355:
------------------------------------

My bad... should i create a new issue for upgrading RF 4.3 to Mojarra 2.1.26?
                
> Upgrade Mojarra
> ---------------
>
>                 Key: RF-13355
>                 URL: https://issues.jboss.org/browse/RF-13355
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha3
>
>
> RichFaces 5 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.
> [1] https://github.com/richfaces/richfaces/blob/master/build/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 03:57:06 2013
From: jira-events at lists.jboss.org (Immo Benjes (JIRA))
Date: Tue, 19 Nov 2013 03:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11711) a4j:queue - review usage
 of attributes onsubmit, oncomplete, onevent, onbeforedomupdate and onerror
In-Reply-To: <JIRA.12452390.1321455049000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12452390.1321455049000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12452390.1321455049000.17507.1384851426331@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-11711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924754#comment-12924754 ] 

Immo Benjes commented on RF-11711:
----------------------------------

I would prefer that the onsubmit and oncomplete are being fixed and not simply dropped. I used these callbacks in RF 3.x. I now have to work around this by using a:status components, however I have several different status components and I need the onsubmit and oncomplete javascript callbacks on every ajax request. If you have it on the queue you only have to worry about one place. If you have named status components (e.g. a little spinner next to an entry field) you will have to add the onsubmit/oncomplete on every single status component!
                
> a4j:queue - review usage of attributes onsubmit, oncomplete, onevent, onbeforedomupdate and onerror
> ---------------------------------------------------------------------------------------------------
>
>                 Key: RF-11711
>                 URL: https://issues.jboss.org/browse/RF-11711
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 4.1.0.CR1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Minor
>             Fix For: 5-Tracking
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 04:34:05 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Tue, 19 Nov 2013 04:34:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13287) rich:extendedDataTable
 column resizing with ajax loading not working properly
In-Reply-To: <JIRA.12508686.1382616678000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508686.1382616678000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508686.1382616678000.17577.1384853645877@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924769#comment-12924769 ] 

Michal Petrov commented on RF-13287:
------------------------------------

Done.
                
> rich:extendedDataTable column resizing with ajax loading not working properly
> -----------------------------------------------------------------------------
>
>                 Key: RF-13287
>                 URL: https://issues.jboss.org/browse/RF-13287
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.4
>         Environment: Glassfish 3.1.2.2, Mojarra 2.1.26, IE10, IE8, Chrome 30,
>            Reporter: Andreas G
>            Assignee: Michal Petrov
>              Labels: needs-qe, testcase_provided
>             Fix For: 4.3.5
>
>
> In a rich:extendedDataTable with ajax loading turned on: When you resize a column and scroll down (load data), the size of the columns reset to their original value. Only the header keeps its size. The header and the data are not matching anymore.
> Reproducible in the 4.3.4 showcase!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 05:28:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 05:28:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.17751.1384856885824@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13210:
----------------------------

    Fix Version/s: 4.5.0.Alpha1

    
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 06:43:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 06:43:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11302) Subtable: column sorting
	doesn't work
In-Reply-To: <JIRA.12444467.1313149423000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12444467.1313149423000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12444467.1313149423000.17929.1384861385861@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-11302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak resolved RF-11302.
--------------------------------

    Resolution: Out of Date


Closing this issue because I cannot reproduce anymore on neither 4.3.4.Final nor 5.0.0-SNAPSHOT.
                
> Subtable: column sorting doesn't work
> -------------------------------------
>
>                 Key: RF-11302
>                 URL: https://issues.jboss.org/browse/RF-11302
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: base functionality, component-tables
>    Affects Versions: 4.1.0.Milestone1
>         Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc
> Metamer 4.1.0-SNAPSHOT r.22616
> Mojarra 2.1.2-FCS
> Apache Tomcat 7.0.19
> OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
> Chrome 13.0.782.112 @ Linux i686
>            Reporter: Pavol Pitonak
>              Labels: ci_issue
>             Fix For: 5-Tracking
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richCollapsibleSubTable/sorting-using-column.xhtml
> # click on header "Name"
> result:
> subtables are not sorted, second click on the same header sorts both subtables

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 07:35:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 07:35:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466435@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466435@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466435.18104.1384864506857@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13359:
----------------------------------

             Summary: Showcase: several components don't work
                 Key: RF-13359
                 URL: https://issues.jboss.org/browse/RF-13359
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 5.0.0.Alpha2
         Environment: Showcase 5.0.0-SNAPSHOT
            Reporter: Pavol Pitonak
            Priority: Blocker


# deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
# open browser console
# click on "Start Process" button

result:
* this message appears in browser console 
{quote}
event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
{quote}
* progress bar is rendered wrongly
* the same message is displayed on these pages (and these components are broken too)
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 08:09:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 08:09:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13360) Pick list: buttons have
	two icons
In-Reply-To: <JIRA.12525559.1384866543443@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525559.1384866543443@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525559.1384866543443.18236.1384866546701@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13360:
----------------------------------

             Summary: Pick list: buttons have two icons
                 Key: RF-13360
                 URL: https://issues.jboss.org/browse/RF-13360
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
         Environment: RichFaces 5.0.0-SNAPSHOT
            Reporter: Pavol Pitonak


# open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=pickList&skin=blueSky

result:
* all buttons have two icons, see attached screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 08:13:07 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 08:13:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13360) Pick list: buttons have
	two icons
In-Reply-To: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525559.1384866543000.18281.1384866787452@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13360:
-------------------------------

    Attachment: picklist.png

    
> Pick list: buttons have two icons
> ---------------------------------
>
>                 Key: RF-13360
>                 URL: https://issues.jboss.org/browse/RF-13360
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>         Attachments: picklist.png
>
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=pickList&skin=blueSky
> result:
> * all buttons have two icons, see attached screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 08:21:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 08:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside
	calendar is not rendered
In-Reply-To: <JIRA.12525562.1384867150939@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525562.1384867150939@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525562.1384867150939.18307.1384867265875@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13361:
----------------------------------

             Summary: Placeholder inside calendar is not rendered
                 Key: RF-13361
                 URL: https://issues.jboss.org/browse/RF-13361
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-input
    Affects Versions: 5.0.0.Alpha2
         Environment: RichFaces 5.0.0-SNAPSHOT
            Reporter: Pavol Pitonak


# open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
# open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky

result:
* in Showcase 4 calendar component has a placeholder text
* in Showcase 5 placeholder in calendar is missing, see screenshot 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 08:27:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 08:27:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside
	calendar is not rendered
In-Reply-To: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525562.1384867150000.18329.1384867626365@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13361:
-------------------------------

    Attachment: placeholder1.png

    
> Placeholder inside calendar is not rendered
> -------------------------------------------
>
>                 Key: RF-13361
>                 URL: https://issues.jboss.org/browse/RF-13361
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>         Attachments: placeholder1.png
>
>
> # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> result:
> * in Showcase 4 calendar component has a placeholder text
> * in Showcase 5 placeholder in calendar is missing, see screenshot 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 08:33:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 08:33:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.18363.1384867985843@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13359:
-------------------------------

    Description: 
# deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
# open browser console
# click on "Start Process" button

result:
* this message appears in browser console 
{quote}
event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
{quote}
* progress bar is rendered wrongly
* the same message is displayed on these pages (and these components are broken too)
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

  was:
# deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
# open browser console
# click on "Start Process" button

result:
* this message appears in browser console 
{quote}
event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
{quote}
* progress bar is rendered wrongly
* the same message is displayed on these pages (and these components are broken too)
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky


    
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Blocker
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 08:56:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 08:56:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.18481.1384869366290@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13356:
-------------------------------

    Attachment: edt.png

    
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>            Assignee: Pavol Pitonak
>         Attachments: edt.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 08:58:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 08:58:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.18486.1384869485974@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak reassigned RF-13356:
----------------------------------

    Assignee: Brian Leathem  (was: Pavol Pitonak)


In RichFaces 4.3.4.Final, rows are *not* stretched to 100% (see attached screenshot).
                
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>            Assignee: Brian Leathem
>         Attachments: edt.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 09:12:06 2013
From: jira-events at lists.jboss.org (Alexander Fox (JIRA))
Date: Tue, 19 Nov 2013 09:12:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12759) rich:hotkey doesn't
 handle Ctrl+A key binding
In-Reply-To: <JIRA.12483538.1359140693000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12483538.1359140693000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12483538.1359140693000.18529.1384870326145@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924900#comment-12924900 ] 

Alexander Fox commented on RF-12759:
------------------------------------

Here is a better workaround that doesn't need <rich:element> with hard coded element id. Hard coded element IDs are not usable.

            <rich:hotKey selector="#mySelector" key="return"
                onkeydown="jQuery(document.getElementById('#{rich:clientId('myComponentId')}')).click();" enabledInInput="true"/>

                
> rich:hotkey doesn't handle Ctrl+A key binding
> ---------------------------------------------
>
>                 Key: RF-12759
>                 URL: https://issues.jboss.org/browse/RF-12759
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.2.3.Final
>         Environment: Linux Fedora 16 x64, NetBeans 7.2, GlassFish 3.1.1, CDI/Weld/CODI, JSF2, RichFaces4.2.3, Hibernate3.2.5, Firebird 2.5.1
>            Reporter: Edilmar Alves
>            Assignee: Luk?? Fry?
>              Labels: hotkey
>             Fix For: 5-Tracking
>
>         Attachments: test.java, test.xhtml
>
>
> When I try to use rich:hotkey with a4j:commandButton, it doesn't work. A detailed explanation about this is in the forum.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 09:28:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 09:28:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13362) ajax.reslib and
 base-component.reslib conflicts with RF 5.0 versions
In-Reply-To: <JIRA.12525577.1384871238787@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525577.1384871238787@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525577.1384871238787.18636.1384871286390@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13362:
-------------------------------

             Summary: ajax.reslib and base-component.reslib conflicts with RF 5.0 versions
                 Key: RF-13362
                 URL: https://issues.jboss.org/browse/RF-13362
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component
    Affects Versions: 4.5.0.Alpha1
            Reporter: Luk?? Fry?
             Fix For: 4.5.0.Alpha1




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 09:28:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 09:28:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13362) ajax.reslib and
 base-component.reslib conflicts with RF 5.0 versions
In-Reply-To: <JIRA.12525577.1384871238000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525577.1384871238000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525577.1384871238000.18637.1384871286452@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13362:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> ajax.reslib and base-component.reslib conflicts with RF 5.0 versions
> --------------------------------------------------------------------
>
>                 Key: RF-13362
>                 URL: https://issues.jboss.org/browse/RF-13362
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 09:28:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 09:28:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13357) Switch RichFaces to use
 dist branch of RichWidgets to avoid a need for compiling own version
In-Reply-To: <JIRA.12525517.1384845803000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525517.1384845803000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525517.1384845803000.18640.1384871286615@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13357:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version
> --------------------------------------------------------------------------------------------
>
>                 Key: RF-13357
>                 URL: https://issues.jboss.org/browse/RF-13357
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 09:30:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 09:30:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13362) ajax.reslib and
 base-component.reslib conflicts with RF 5.0 versions
In-Reply-To: <JIRA.12525577.1384871238000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525577.1384871238000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525577.1384871238000.18642.1384871405914@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13362:
-------------------------------

    Assignee: Luk?? Fry?

    
> ajax.reslib and base-component.reslib conflicts with RF 5.0 versions
> --------------------------------------------------------------------
>
>                 Key: RF-13362
>                 URL: https://issues.jboss.org/browse/RF-13362
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 09:53:09 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 09:53:09 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13363) Sync latest page
 fragments changes from RF-qa repository to RF repository
In-Reply-To: <JIRA.12525345.1384537307000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525345.1384537307000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525345.1384537307000.18723.1384872789198@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? moved RFPL-3054 to RF-13363:
---------------------------------------

              Project: RichFaces  (was: RichFaces Planning)
                  Key: RF-13363  (was: RFPL-3054)
    Affects Version/s: 5.0.0.Alpha2
                           (was: 5.0.0.Alpha2)
          Component/s: page-fragments
                           (was: QE)
        Fix Version/s: 5.0.0.Alpha2
                           (was: 5.0.0.Alpha2)

    
> Sync latest page fragments changes from RF-qa repository to RF repository
> -------------------------------------------------------------------------
>
>                 Key: RF-13363
>                 URL: https://issues.jboss.org/browse/RF-13363
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> After porting all changes delete the page-fragments submodule from richfaces-qa repository.
> Make it depended on the RF's page fragments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 09:55:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 09:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13363) Sync latest page
 fragments changes from RF-qa repository to RF repository
In-Reply-To: <JIRA.12525345.1384537307000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525345.1384537307000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525345.1384537307000.18732.1384872906444@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924924#comment-12924924 ] 

Luk?? Fry? commented on RF-13363:
---------------------------------

I have moved issue to RF / page-fragments issue tracker.
                
> Sync latest page fragments changes from RF-qa repository to RF repository
> -------------------------------------------------------------------------
>
>                 Key: RF-13363
>                 URL: https://issues.jboss.org/browse/RF-13363
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> After porting all changes delete the page-fragments submodule from richfaces-qa repository.
> Make it depended on the RF's page fragments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:01:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 10:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.18766.1384873266694@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13331:
-------------------------------

    Assignee: Luk?? Fry?  (was: Luk?? Macko)

    
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:01:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 10:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.18768.1384873266807@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13210.
-----------------------------

    Resolution: Done

    
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:03:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 10:03:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13362) ajax.reslib and
 base-component.reslib conflicts with RF 5.0 versions
In-Reply-To: <JIRA.12525577.1384871238000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525577.1384871238000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525577.1384871238000.18770.1384873385884@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13362.
-----------------------------

    Resolution: Done

    
> ajax.reslib and base-component.reslib conflicts with RF 5.0 versions
> --------------------------------------------------------------------
>
>                 Key: RF-13362
>                 URL: https://issues.jboss.org/browse/RF-13362
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:11:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 19 Nov 2013 10:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.18818.1384873866626@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924942#comment-12924942 ] 

Pavol Pitonak commented on RF-13210:
------------------------------------

[~manovotn], please verify that this fix didn't break anything.
                
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:11:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 10:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.18823.1384873866856@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924944#comment-12924944 ] 

Luk?? Fry? commented on RF-13352:
---------------------------------

Could you please send an update to https://github.com/richfaces/richfaces/pull/62 once implemented?
                
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:11:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 10:11:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.18827.1384873867019@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924944#comment-12924944 ] 

Luk?? Fry? edited comment on RF-13352 at 11/19/13 10:10 AM:
------------------------------------------------------------

Could you please send an update to https://github.com/richfaces/richfaces/pull/62 once you implement this?
                
      was (Author: lfryc):
    Could you please send an update to https://github.com/richfaces/richfaces/pull/62 once implemented?
                  
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:15:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 10:15:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.18850.1384874106815@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924954#comment-12924954 ] 

Luk?? Fry? commented on RF-13331:
---------------------------------

Waiting for RF-13352 before we can merge this.
                
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 10:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.18857.1384874226686@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924957#comment-12924957 ] 

Luk?? Macko commented on RF-13352:
----------------------------------

I will.
                
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 10:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.18862.1384874226966@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13331:
----------------------------

    Assignee: Luk?? Macko  (was: Luk?? Fry?)

    
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:19:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 10:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.18875.1384874345962@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13352:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:19:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 10:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13354) Autocomplete:
 suggestions stay visible after input is cleared
In-Reply-To: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525458.1384783692000.18877.1384874346077@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13354:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> Autocomplete: suggestions stay visible after input is cleared
> -------------------------------------------------------------
>
>                 Key: RF-13354
>                 URL: https://issues.jboss.org/browse/RF-13354
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # type "ala" into input (several suggestions will appear)
> # clear input, e.g. by using backspace key
> result:
> * the list with all available suggestions is displayed
> * in 4.3.4.Final, the suggestions are *not* displayed when input is empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 10:19:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 10:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.18880.1384874346250@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13352:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:19:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 10:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13354) Autocomplete:
 suggestions stay visible after input is cleared
In-Reply-To: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525458.1384783692000.18882.1384874346334@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13354:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> Autocomplete: suggestions stay visible after input is cleared
> -------------------------------------------------------------
>
>                 Key: RF-13354
>                 URL: https://issues.jboss.org/browse/RF-13354
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # type "ala" into input (several suggestions will appear)
> # clear input, e.g. by using backspace key
> result:
> * the list with all available suggestions is displayed
> * in 4.3.4.Final, the suggestions are *not* displayed when input is empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 10:28:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 10:28:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13354) Autocomplete:
 suggestions stay visible after input is cleared
In-Reply-To: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525458.1384783692000.18910.1384874886158@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13354:
-------------------------------

    Assignee: Luk?? Fry?

    
> Autocomplete: suggestions stay visible after input is cleared
> -------------------------------------------------------------
>
>                 Key: RF-13354
>                 URL: https://issues.jboss.org/browse/RF-13354
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # type "ala" into input (several suggestions will appear)
> # clear input, e.g. by using backspace key
> result:
> * the list with all available suggestions is displayed
> * in 4.3.4.Final, the suggestions are *not* displayed when input is empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 10:36:09 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 10:36:09 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.18934.1384875369025@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13359:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 10:50:07 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Tue, 19 Nov 2013 10:50:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.19029.1384876207427@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924983#comment-12924983 ] 

Michal Petrov commented on RF-13359:
------------------------------------

The warning messages are generated by the browser and the issue is in jQuery, I don't think it's soimething we directly use in RichFaces.

See [http://bugs.jquery.com/ticket/14282].
                
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 11:04:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 11:04:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.19076.1384877045974@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13359:
-------------------------------

     Original Estimate: 1 hour
    Remaining Estimate: 1 hour

    
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 11:04:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 11:04:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.19079.1384877046172@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13359:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 11:04:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 11:04:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13357) Switch RichFaces to use
 dist branch of RichWidgets to avoid a need for compiling own version
In-Reply-To: <JIRA.12525517.1384845803000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525517.1384845803000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525517.1384845803000.19081.1384877046288@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13357:
----------------------------------

    Assignee: Brian Leathem

    
> Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version
> --------------------------------------------------------------------------------------------
>
>                 Key: RF-13357
>                 URL: https://issues.jboss.org/browse/RF-13357
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 11:04:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 11:04:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13357) Switch RichFaces to use
 dist branch of RichWidgets to avoid a need for compiling own version
In-Reply-To: <JIRA.12525517.1384845803000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525517.1384845803000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525517.1384845803000.19083.1384877046414@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13357:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version
> --------------------------------------------------------------------------------------------
>
>                 Key: RF-13357
>                 URL: https://issues.jboss.org/browse/RF-13357
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 11:44:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 11:44:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.19201.1384879446029@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924998#comment-12924998 ] 

Luk?? Fry? commented on RF-13352:
---------------------------------

Lukas, few implementation notes:

<groups> and <exlucededGroups> is used to match what categories we want to run:
http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#groups
(note that <groups> should be rather named categories, but <groups> settings drives both, TestNG and JUnit tests, that's why maven-surefire-plugin follows TestNG naming conventions)


The idea is that if you turn on profile, it can append boolean conditions as the suffix of <groups> selector.

But I found that there is specific impl detail, which is not evident from first sight.
During prototyping I have used <groups> together with <excludedGroups>, but platform-specific configuration (e.g.  affects <groups>. That's why {{${testCategory.excluded.browser}}} needs to be setup as:

{code}
<testCategory.excluded.browser>AND NOT category.FailingFirefox</testCategory.excluded.browser>
{code}

You can use my prototype as a reference impl:
https://github.com/lfryc/surefire-and-junit-categories/blob/master/pom.xml#L175

                
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 11:44:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Nov 2013 11:44:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.19208.1384879446362@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924998#comment-12924998 ] 

Luk?? Fry? edited comment on RF-13352 at 11/19/13 11:42 AM:
------------------------------------------------------------

Lukas, few implementation notes:

<groups> and <exlucededGroups> is used to match what categories we want to run:
http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#groups
(note that <groups> should be rather named categories, but <groups> settings drives both, TestNG and JUnit tests, that's why maven-surefire-plugin follows TestNG naming conventions)


The idea is that if you turn on profile, it can append boolean conditions as the suffix of <groups> selector.

But I found that there is specific impl detail, which is not evident from first sight.
During prototyping I have used <groups> together with <excludedGroups>, but platform-specific configuration (e.g.  affects <groups>. That's why {{${testCategory.excluded.browser}}} needs to be setup as:

{code}
<testCategory.excluded.browser>AND NOT category.FailingOnFirefox</testCategory.excluded.browser>
{code}

You can use my prototype as a reference impl:
https://github.com/lfryc/surefire-and-junit-categories/blob/master/pom.xml#L175

                
      was (Author: lfryc):
    Lukas, few implementation notes:

<groups> and <exlucededGroups> is used to match what categories we want to run:
http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#groups
(note that <groups> should be rather named categories, but <groups> settings drives both, TestNG and JUnit tests, that's why maven-surefire-plugin follows TestNG naming conventions)


The idea is that if you turn on profile, it can append boolean conditions as the suffix of <groups> selector.

But I found that there is specific impl detail, which is not evident from first sight.
During prototyping I have used <groups> together with <excludedGroups>, but platform-specific configuration (e.g.  affects <groups>. That's why {{${testCategory.excluded.browser}}} needs to be setup as:

{code}
<testCategory.excluded.browser>AND NOT category.FailingFirefox</testCategory.excluded.browser>
{code}

You can use my prototype as a reference impl:
https://github.com/lfryc/surefire-and-junit-categories/blob/master/pom.xml#L175

                  
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 13:51:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 13:51:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside
	calendar is not rendered
In-Reply-To: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525562.1384867150000.19541.1384887065903@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13361:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Placeholder inside calendar is not rendered
> -------------------------------------------
>
>                 Key: RF-13361
>                 URL: https://issues.jboss.org/browse/RF-13361
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: placeholder1.png
>
>
> # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> result:
> * in Showcase 4 calendar component has a placeholder text
> * in Showcase 5 placeholder in calendar is missing, see screenshot 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 13:51:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 13:51:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13360) Pick list: buttons have
	two icons
In-Reply-To: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525559.1384866543000.19543.1384887065985@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13360:
-------------------------------

    Priority: Trivial  (was: Major)

    
> Pick list: buttons have two icons
> ---------------------------------
>
>                 Key: RF-13360
>                 URL: https://issues.jboss.org/browse/RF-13360
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Trivial
>         Attachments: picklist.png
>
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=pickList&skin=blueSky
> result:
> * all buttons have two icons, see attached screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 13:51:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 13:51:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13360) Pick list: buttons have
	two icons
In-Reply-To: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525559.1384866543000.19547.1384887066195@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925041#comment-12925041 ] 

Brian Leathem commented on RF-13360:
------------------------------------

The default value for the button text needs to be removed:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/AbstractPickList.java#L73
                
> Pick list: buttons have two icons
> ---------------------------------
>
>                 Key: RF-13360
>                 URL: https://issues.jboss.org/browse/RF-13360
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Trivial
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: picklist.png
>
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=pickList&skin=blueSky
> result:
> * all buttons have two icons, see attached screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 13:51:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 13:51:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13360) Pick list: buttons have
	two icons
In-Reply-To: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525559.1384866543000.19545.1384887066099@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13360:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Pick list: buttons have two icons
> ---------------------------------
>
>                 Key: RF-13360
>                 URL: https://issues.jboss.org/browse/RF-13360
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Trivial
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: picklist.png
>
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=pickList&skin=blueSky
> result:
> * all buttons have two icons, see attached screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 13:59:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 13:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.19581.1384887546789@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13356.
--------------------------------

    Resolution: Cannot Reproduce Bug


We are unable to re-produce this issue.  Perhaps you have some [~uhim] perhaps you have some conflicting CSS in your application?  If you can provide a self-contained (simple) re-producer, feel free to re-open this issue.
                
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>            Assignee: Brian Leathem
>         Attachments: edt.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 13:59:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 13:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13355) Upgrade Mojarra
In-Reply-To: <JIRA.12525466.1384785440000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525466.1384785440000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525466.1384785440000.19582.1384887546841@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925044#comment-12925044 ] 

Brian Leathem commented on RF-13355:
------------------------------------

+1, please create the additional issue.
                
> Upgrade Mojarra
> ---------------
>
>                 Key: RF-13355
>                 URL: https://issues.jboss.org/browse/RF-13355
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha3
>
>
> RichFaces 5 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.
> [1] https://github.com/richfaces/richfaces/blob/master/build/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 14:07:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 14:07:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.19612.1384888026395@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925048#comment-12925048 ] 

Brian Leathem commented on RF-13323:
------------------------------------

[~wish79] have you tried running the standalone sample [~jstefek] shared?  Do you notice your issue with that sample app?
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 14:11:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 14:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11711) a4j:queue - review usage
 of attributes onsubmit, oncomplete, onevent, onbeforedomupdate and onerror
In-Reply-To: <JIRA.12452390.1321455049000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12452390.1321455049000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12452390.1321455049000.19626.1384888266434@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-11711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925049#comment-12925049 ] 

Brian Leathem commented on RF-11711:
------------------------------------

thanks for sharing your use case [~ibenjes]
                
> a4j:queue - review usage of attributes onsubmit, oncomplete, onevent, onbeforedomupdate and onerror
> ---------------------------------------------------------------------------------------------------
>
>                 Key: RF-11711
>                 URL: https://issues.jboss.org/browse/RF-11711
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 4.1.0.CR1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Minor
>             Fix For: 5-Tracking
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 14:45:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 14:45:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13358) rich:panelMenuGroup
 allowing actions executions even if originally disabled
In-Reply-To: <JIRA.12525535.1384858189000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525535.1384858189000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525535.1384858189000.19775.1384890305879@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13358:
-------------------------------

    Security: Public  (was: JBoss Internal)

    
> rich:panelMenuGroup allowing actions executions even if originally disabled
> ---------------------------------------------------------------------------
>
>                 Key: RF-13358
>                 URL: https://issues.jboss.org/browse/RF-13358
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-menu
>    Affects Versions: 4.3.4
>         Environment: Linux, AS 7.1.1 Brontes, FF 25 with FireBug addOn
>            Reporter: Pavel Slegr
>            Assignee: Pavel Slegr
>            Priority: Critical
>             Fix For: 4.3.5
>
>
> related to https://issues.jboss.org/browse/RF-12813
> This can be possibly a security hole, as the second component piece is discovered to allow tampering actions through JS.
> I suggest to try out on other components as well !!!
> with following example
> {code}
> {
>                 <rich:panelMenuGroup id="group4" label="Group 4" expanded="false">
>                     <rich:panelMenuItem id="item41" label="Item 4.1" />
>                     <rich:panelMenuItem id="item42" label="Item 4.2" disabled="true" />
>                     <rich:panelMenuGroup id="group43" label="Group 4.1" disabled="true">
>                         <rich:panelMenuItem id="item431" label="Item 4.1.1" />
>                     </rich:panelMenuGroup>
>                 </rich:panelMenuGroup>
> }
> {code}
> the group43 element is intended to be disabled and thus not allowing any actions execution on it
> Once tampered with 
> {code}
> {
> new RichFaces.ui.PanelMenuGroup("f:group43",{"collapseEvent":"click","unselectable":false,"selectable":false,"name":"group43","ajax":{"incId":"1"} ,"stylePrefix":"rf\u002Dpm\u002Dgr","expanded":false,"expandEvent":"click","disabled":false,"mode":"client"} )
> }
> {code}
> It is possible to expand the group and execute further actions on its children elements

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 15:35:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 15:35:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13360) Pick list: buttons have
	two icons
In-Reply-To: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525559.1384866543000.19807.1384893306390@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13360:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> Pick list: buttons have two icons
> ---------------------------------
>
>                 Key: RF-13360
>                 URL: https://issues.jboss.org/browse/RF-13360
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Trivial
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: picklist.png
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=pickList&skin=blueSky
> result:
> * all buttons have two icons, see attached screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 15:35:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 15:35:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside
	calendar is not rendered
In-Reply-To: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525562.1384867150000.19809.1384893306499@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13361:
-------------------------------

     Original Estimate: 30 minutes
    Remaining Estimate: 30 minutes

    
> Placeholder inside calendar is not rendered
> -------------------------------------------
>
>                 Key: RF-13361
>                 URL: https://issues.jboss.org/browse/RF-13361
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: placeholder1.png
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> result:
> * in Showcase 4 calendar component has a placeholder text
> * in Showcase 5 placeholder in calendar is missing, see screenshot 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 15:35:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 15:35:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13360) Pick list: buttons have
	two icons
In-Reply-To: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525559.1384866543000.19811.1384893306618@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13360:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> Pick list: buttons have two icons
> ---------------------------------
>
>                 Key: RF-13360
>                 URL: https://issues.jboss.org/browse/RF-13360
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Trivial
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: picklist.png
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=pickList&skin=blueSky
> result:
> * all buttons have two icons, see attached screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 15:35:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 15:35:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside
	calendar is not rendered
In-Reply-To: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525562.1384867150000.19813.1384893306675@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13361:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> Placeholder inside calendar is not rendered
> -------------------------------------------
>
>                 Key: RF-13361
>                 URL: https://issues.jboss.org/browse/RF-13361
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: placeholder1.png
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> result:
> * in Showcase 4 calendar component has a placeholder text
> * in Showcase 5 placeholder in calendar is missing, see screenshot 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 15:37:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 15:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13301) Favor use of Page
 Fragments in Framework Tests
In-Reply-To: <JIRA.12509047.1383080150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12509047.1383080150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12509047.1383080150000.19817.1384893426028@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13301:
-------------------------------

    Fix Version/s: 5.0.0.Alpha3
                       (was: 5.0.0.Alpha2)

    
> Favor use of Page Fragments in Framework Tests
> ----------------------------------------------
>
>                 Key: RF-13301
>                 URL: https://issues.jboss.org/browse/RF-13301
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Pavol Pitonak
>             Fix For: 5.0.0.Alpha3
>
>
> Since we have introduced Page Fragments in Alpha2, we could favor their usage in fragment tests.
> We could start to refactor tests for  components rewritten in Alpha2 and continue as we rewrite other components.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 15:37:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 15:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13357) Switch RichFaces to use
 dist branch of RichWidgets to avoid a need for compiling own version
In-Reply-To: <JIRA.12525517.1384845803000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525517.1384845803000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525517.1384845803000.19824.1384893426484@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13357.
--------------------------------

    Resolution: Done

    
> Switch RichFaces to use dist branch of RichWidgets to avoid a need for compiling own version
> --------------------------------------------------------------------------------------------
>
>                 Key: RF-13357
>                 URL: https://issues.jboss.org/browse/RF-13357
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 19 15:37:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 15:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13360) Pick list: buttons have
	two icons
In-Reply-To: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525559.1384866543000.19826.1384893426540@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13360:
----------------------------------

    Assignee: Brian Leathem

    
> Pick list: buttons have two icons
> ---------------------------------
>
>                 Key: RF-13360
>                 URL: https://issues.jboss.org/browse/RF-13360
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Trivial
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: picklist.png
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=pickList&skin=blueSky
> result:
> * all buttons have two icons, see attached screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 19 16:54:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 19 Nov 2013 16:54:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13360) Pick list: buttons have
	two icons
In-Reply-To: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525559.1384866543000.19894.1384898045820@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13360.
--------------------------------

    Resolution: Done

    
> Pick list: buttons have two icons
> ---------------------------------
>
>                 Key: RF-13360
>                 URL: https://issues.jboss.org/browse/RF-13360
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Trivial
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: picklist.png
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=pickList&skin=blueSky
> result:
> * all buttons have two icons, see attached screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 03:28:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 03:28:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.20485.1384936085997@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925205#comment-12925205 ] 

Brian Leathem commented on RF-13359:
------------------------------------

I dug into the progressBar not working.  It doesn't seem to be a resource mapping issue; all resources are correctly mapped and retrieved.  In comparing the RF 4 showcase to the RF 5 one, I did notice that the following line is not being called in the case of the RF 5 showcase:

https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/output/progressBar/progressBar.js#L87

It seems that the event.componentData is null.  Comparing the AJAX response body did not show any difference.  But I suspect the problem will be uncovered by a more careful comparison of the AJAX responses (between the RF 4 and RF 5 showcases).
                
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 04:31:05 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Wed, 20 Nov 2013 04:31:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.20879.1384939865938@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925243#comment-12925243 ] 

Mohammad Weshah commented on RF-13323:
--------------------------------------

Dear Brian,
 Sorry for being delay , i test the RF-13323-2 it works fine without a4j:mediaOutput , but when i add it , the list not reset the image do not display, but the strange thing is i copy all lib from RF-13323-2 to my test application the list is still disappear (without adding a4j:mediaOutput).

Regards
Wish79
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 04:39:05 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Wed, 20 Nov 2013 04:39:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.20911.1384940345890@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925243#comment-12925243 ] 

Mohammad Weshah edited comment on RF-13323 at 11/20/13 4:37 AM:
----------------------------------------------------------------

Dear Brian,
 Sorry for being delay , i test the RF-13323-2 it works fine without a4j:mediaOutput , but when i add the a4j:mediaOutput the list not reset the image do not display , but the strange thing is i copy all lib from RF-13323-2 to my test application the list is still disappear in my app (without adding a4j:mediaOutput).

Regards
Wish79
                
      was (Author: wish79):
    Dear Brian,
 Sorry for being delay , i test the RF-13323-2 it works fine without a4j:mediaOutput , but when i add it , the list not reset the image do not display, but the strange thing is i copy all lib from RF-13323-2 to my test application the list is still disappear (without adding a4j:mediaOutput).

Regards
Wish79
                  
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 04:53:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 04:53:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13289) inputspinner : setting
 the value to empty/null
In-Reply-To: <JIRA.12508761.1382687176000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508761.1382687176000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508761.1382687176000.20972.1384941186694@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925254#comment-12925254 ] 

Juraj H?ska commented on RF-13289:
----------------------------------

I tried to reproduce it with metamer and it is so as reported.

It is not possible to set the value to be empty. {{inputNumberSpinner}} is supposing to have attribute {{value}} to be bound to {{double/Double}}, setting of {{null}} does not help.
                
>  inputspinner : setting the value to empty/null
> -----------------------------------------------
>
>                 Key: RF-13289
>                 URL: https://issues.jboss.org/browse/RF-13289
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.3
>            Reporter: liumin hu
>            Assignee: Juraj H?ska
>
>  can put empty/null value in a spinner, everytime the spinner changes empty to 0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 04:53:08 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 04:53:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13289) inputspinner : setting
 the value to empty/null
In-Reply-To: <JIRA.12508761.1382687176000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508761.1382687176000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508761.1382687176000.20994.1384941188002@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13289:
-----------------------------

    Assignee:     (was: Juraj H?ska)

    
>  inputspinner : setting the value to empty/null
> -----------------------------------------------
>
>                 Key: RF-13289
>                 URL: https://issues.jboss.org/browse/RF-13289
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.3
>            Reporter: liumin hu
>
>  can put empty/null value in a spinner, everytime the spinner changes empty to 0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 04:55:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 04:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13289) inputspinner : setting
 the value to empty/null
In-Reply-To: <JIRA.12508761.1382687176000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508761.1382687176000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508761.1382687176000.20997.1384941306136@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13289:
-----------------------------

    Affects Version/s: 5.0.0.Alpha2

    
>  inputspinner : setting the value to empty/null
> -----------------------------------------------
>
>                 Key: RF-13289
>                 URL: https://issues.jboss.org/browse/RF-13289
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.3, 5.0.0.Alpha2
>            Reporter: liumin hu
>
>  can put empty/null value in a spinner, everytime the spinner changes empty to 0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 04:55:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 04:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to
	2.1.26 in RichFaces 4
In-Reply-To: <JIRA.12525674.1384941255874@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525674.1384941255874@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525674.1384941255874.21004.1384941306566@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13364:
----------------------------------

             Summary: Upgrade Mojarra to 2.1.26 in RichFaces 4
                 Key: RF-13364
                 URL: https://issues.jboss.org/browse/RF-13364
             Project: RichFaces
          Issue Type: Component  Upgrade
      Security Level: Public (Everyone can see)
          Components: third-party
    Affects Versions: 5.0.0.Alpha2
            Reporter: Pavol Pitonak
             Fix For: 5.0.0.Alpha3


RichFaces 5 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.

[1] https://github.com/richfaces/richfaces/blob/master/build/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 04:55:07 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 04:55:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to
	2.1.26 in RichFaces 4
In-Reply-To: <JIRA.12525674.1384941255000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525674.1384941255000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525674.1384941255000.21013.1384941307153@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13364:
-------------------------------

    Description: 
RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.

[1] https://github.com/richfaces4/build/blob/master/bom/pom.xml

  was:
RichFaces 5 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.

[1] https://github.com/richfaces/richfaces/blob/master/build/pom.xml


    
> Upgrade Mojarra to 2.1.26 in RichFaces 4
> ----------------------------------------
>
>                 Key: RF-13364
>                 URL: https://issues.jboss.org/browse/RF-13364
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha3
>
>
> RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.
> [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 04:57:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 04:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to
	2.1.26 in RichFaces 4
In-Reply-To: <JIRA.12525674.1384941255000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525674.1384941255000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525674.1384941255000.21019.1384941426197@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13364:
-------------------------------

    Affects Version/s: 4.3.4
                           (was: 5.0.0.Alpha2)

    
> Upgrade Mojarra to 2.1.26 in RichFaces 4
> ----------------------------------------
>
>                 Key: RF-13364
>                 URL: https://issues.jboss.org/browse/RF-13364
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 4.3.4
>            Reporter: Pavol Pitonak
>             Fix For: 5.0.0.Alpha3
>
>
> RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.
> [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 04:57:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 04:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to
	2.1.26 in RichFaces 4
In-Reply-To: <JIRA.12525674.1384941255000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525674.1384941255000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525674.1384941255000.21022.1384941426373@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13364:
-------------------------------

    Fix Version/s:     (was: 5.0.0.Alpha3)

    
> Upgrade Mojarra to 2.1.26 in RichFaces 4
> ----------------------------------------
>
>                 Key: RF-13364
>                 URL: https://issues.jboss.org/browse/RF-13364
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 4.3.4
>            Reporter: Pavol Pitonak
>
> RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.
> [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 04:57:06 2013
From: jira-events at lists.jboss.org (Anton Bogoslavskyi (JIRA))
Date: Wed, 20 Nov 2013 04:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.21026.1384941426637@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton Bogoslavskyi updated RF-13356:
------------------------------------

    Attachment: screen1.png
                screen2.png
                extended-screen1.png
                extended-screen2.png


screen1 and screen2 are with dataTable.
two others represent extendedDataTable.

difference:
tables on the screens 1 have:
#alarmList {
    height: 500px;
}
                
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>            Assignee: Brian Leathem
>         Attachments: edt.png, extended-screen1.png, extended-screen2.png, screen1.png, screen2.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 05:05:06 2013
From: jira-events at lists.jboss.org (Anton Bogoslavskyi (JIRA))
Date: Wed, 20 Nov 2013 05:05:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.21045.1384941906421@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925260#comment-12925260 ] 

Anton Bogoslavskyi commented on RF-13356:
-----------------------------------------

Sorry, my bad. Streching reproduced for simple dataTable. But that actually doesn't solve my problem. 

What I see in your screenshot actually doesn't seem to look OK. Yes, the rows are not streched, but why the footer is in the middle of the control?
So what I really need from this control is that the height should be constant (the footer is always on the same place) while the rows are not streched to fill all the space between header and footer.
Why:
I have pagination control in footer and I expect it not to jump when I click the "next page" button.

I just apologize for wasting your time reproducing strech issue for extendedDataTable. I might reopen this issue for dataTable. Or create another one for extendedDataTable to place footer on the right place. Or both. Which way is preferable for you?

PS: my screenshots are both 4.3.3, do not have time to migrate to 4.3.4 yet/
                
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>            Assignee: Brian Leathem
>         Attachments: edt.png, extended-screen1.png, extended-screen2.png, screen1.png, screen2.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 05:20:07 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 05:20:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13360) Pick list: buttons have
	two icons
In-Reply-To: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525559.1384866543000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525559.1384866543000.21098.1384942807279@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13360.
------------------------------



Verified
                
> Pick list: buttons have two icons
> ---------------------------------
>
>                 Key: RF-13360
>                 URL: https://issues.jboss.org/browse/RF-13360
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Trivial
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: picklist.png
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=pickList&skin=blueSky
> result:
> * all buttons have two icons, see attached screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 05:26:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 05:26:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.21111.1384943166100@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak reopened RF-13356:
--------------------------------



I could reproduce with data table.
                
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>            Assignee: Brian Leathem
>         Attachments: edt.png, extended-screen1.png, extended-screen2.png, screen1.png, screen2.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 05:26:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 05:26:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.21120.1384943166486@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13356:
-------------------------------

    Affects Version/s: 5.0.0.Alpha1

    
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3, 5.0.0.Alpha1
>            Reporter: Anton Bogoslavskyi
>            Assignee: Brian Leathem
>         Attachments: edt.png, extended-screen1.png, extended-screen2.png, screen1.png, screen2.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 05:26:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 05:26:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) ExtendedDataTable: row
 height strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.21124.1384943166680@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925266#comment-12925266 ] 

Pavol Pitonak commented on RF-13356:
------------------------------------

[~uhim], please create a new issue for EDT footer issue.
                
> ExtendedDataTable: row height strechted to 100% of the table height
> -------------------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3, 5.0.0.Alpha1
>            Reporter: Anton Bogoslavskyi
>            Assignee: Brian Leathem
>         Attachments: edt.png, extended-screen1.png, extended-screen2.png, screen1.png, screen2.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 05:26:07 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 05:26:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) DataTable: row height
 strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.21131.1384943167054@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13356:
-------------------------------

    Summary: DataTable: row height strechted to 100% of the table height  (was: ExtendedDataTable: row height strechted to 100% of the table height)

    
> DataTable: row height strechted to 100% of the table height
> -----------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3, 5.0.0.Alpha1
>            Reporter: Anton Bogoslavskyi
>            Assignee: Brian Leathem
>         Attachments: edt.png, extended-screen1.png, extended-screen2.png, screen1.png, screen2.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 06:55:06 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Wed, 20 Nov 2013 06:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside
	calendar is not rendered
In-Reply-To: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525562.1384867150000.21332.1384948506068@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov reassigned RF-13361:
----------------------------------

    Assignee: Michal Petrov

    
> Placeholder inside calendar is not rendered
> -------------------------------------------
>
>                 Key: RF-13361
>                 URL: https://issues.jboss.org/browse/RF-13361
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Michal Petrov
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: placeholder1.png
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> result:
> * in Showcase 4 calendar component has a placeholder text
> * in Showcase 5 placeholder in calendar is missing, see screenshot 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 07:01:06 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Wed, 20 Nov 2013 07:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside
	calendar is not rendered
In-Reply-To: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525562.1384867150000.21347.1384948866397@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925297#comment-12925297 ] 

Michal Petrov commented on RF-13361:
------------------------------------

Well, that's a weird one. The {{":input"}} selector doesn't seem to work properly in RF 5.

Trying this in console:
{code}
$("<form><input/></form>").find(":input")
{code}
works in RF 4 but not in RF 5, even though both are using jQuery v1.8.3.
                
> Placeholder inside calendar is not rendered
> -------------------------------------------
>
>                 Key: RF-13361
>                 URL: https://issues.jboss.org/browse/RF-13361
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Michal Petrov
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: placeholder1.png
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> result:
> * in Showcase 4 calendar component has a placeholder text
> * in Showcase 5 placeholder in calendar is missing, see screenshot 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 07:53:06 2013
From: jira-events at lists.jboss.org (Gustavo Ehrhardt (JIRA))
Date: Wed, 20 Nov 2013 07:53:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12092) a4j:poll : a4j:status
	never clears
In-Reply-To: <JIRA.12462470.1332784893000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12462470.1332784893000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12462470.1332784893000.21502.1384951986457@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925314#comment-12925314 ] 

Gustavo Ehrhardt commented on RF-12092:
---------------------------------------

Just another workaround:

Move the "a4j:status" to inside of "f:view" but outside of "h:form".
This workaround doesn't require to change the commandLink call.
                
> a4j:poll : a4j:status never clears
> ----------------------------------
>
>                 Key: RF-12092
>                 URL: https://issues.jboss.org/browse/RF-12092
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 4.2.0.Final, 4.2.1.Final
>            Reporter: Robert Gary
>             Fix For: 5-Tracking
>
>         Attachments: a4jPollIssue.war
>
>
> When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete.
> <a4j:poll id="ajaxPoll" interval="5000" enabled="true" action="#{faces$DiscoveryStatus.poll}"
>            render="#{faces$DiscoveryStatus.reRenderStr}"/>
>             <a4j:status id="a4jstatus">
>                 <f:facet name="start">
>                     <img src='/images/ajax-loader.gif'/>
>                 </f:facet>
>                 <!--<f:facet name="stop">-->
>                 <!--<img src="/appiq/images/minor_icon.gif"/>-->
>                 <!--</f:facet>-->
>             </a4j:status>
> This code works correctly in RF 3.3.3.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 08:12:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 08:12:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090549@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090549@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090549.21544.1384953125874@jira02.app.mwc.hst.phx2.redhat.com>

Ji?? ?tefek created RF-13365:
--------------------------------

             Summary: push: cannot be disabled with ajax request
                 Key: RF-13365
                 URL: https://issues.jboss.org/browse/RF-13365
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-a4j-core
    Affects Versions: 5.0.0.Alpha2
         Environment: EAP 6.1, Glassfish 3.1.2.2
FF 25, Chrome 31
            Reporter: Ji?? ?tefek


Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 08:24:05 2013
From: jira-events at lists.jboss.org (Anton Bogoslavskyi (JIRA))
Date: Wed, 20 Nov 2013 08:24:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13366) ExtendedDataTable:
 footer is in the middle of the control if the height is constant
In-Reply-To: <JIRA.12525699.1384953843049@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525699.1384953843049@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525699.1384953843049.21569.1384953845924@jira02.app.mwc.hst.phx2.redhat.com>

Anton Bogoslavskyi created RF-13366:
---------------------------------------

             Summary: ExtendedDataTable: footer is in the middle of the control if the height is constant
                 Key: RF-13366
                 URL: https://issues.jboss.org/browse/RF-13366
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-tables
    Affects Versions: 4.3.3
            Reporter: Anton Bogoslavskyi


Reproduce:
Define class and assign it to your extendedDataTable:
.table_style {
    height: 500px;
}

Prepare the test data to have minimum rows (not fill the whole table with data).

Expected:
Table height is 500px. Footer is on the bottom of the table and won't change place when rows amount changes.
The whitespace is between the last row and the footer

Actual:
Table height is 500px. Footer is right under the last row and jumps each time the amount of rows changes.
The whitespace is under the footer and surrounded by the table border.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 08:30:06 2013
From: jira-events at lists.jboss.org (Anton Bogoslavskyi (JIRA))
Date: Wed, 20 Nov 2013 08:30:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13366) ExtendedDataTable:
 footer is in the middle of the control if the height is constant
In-Reply-To: <JIRA.12525699.1384953843000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525699.1384953843000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525699.1384953843000.21591.1384954206168@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton Bogoslavskyi updated RF-13366:
------------------------------------

    Attachment: edt[1].png

    
> ExtendedDataTable: footer is in the middle of the control if the height is constant
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13366
>                 URL: https://issues.jboss.org/browse/RF-13366
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>         Attachments: edt[1].png
>
>
> Reproduce:
> Define class and assign it to your extendedDataTable:
> .table_style {
>     height: 500px;
> }
> Prepare the test data to have minimum rows (not fill the whole table with data).
> Expected:
> Table height is 500px. Footer is on the bottom of the table and won't change place when rows amount changes.
> The whitespace is between the last row and the footer
> Actual:
> Table height is 500px. Footer is right under the last row and jumps each time the amount of rows changes.
> The whitespace is under the footer and surrounded by the table border.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 09:05:06 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Wed, 20 Nov 2013 09:05:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside
	calendar is not rendered
In-Reply-To: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525562.1384867150000.21740.1384956306347@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925334#comment-12925334 ] 

Michal Petrov commented on RF-13361:
------------------------------------

Fix [pushed|https://github.com/richfaces/richfaces/commit/177d138dbf3de18fe9d2ea691e821aea6212f4ec].
                
> Placeholder inside calendar is not rendered
> -------------------------------------------
>
>                 Key: RF-13361
>                 URL: https://issues.jboss.org/browse/RF-13361
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Michal Petrov
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: placeholder1.png
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> result:
> * in Showcase 4 calendar component has a placeholder text
> * in Showcase 5 placeholder in calendar is missing, see screenshot 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 09:05:06 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Wed, 20 Nov 2013 09:05:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside
	calendar is not rendered
In-Reply-To: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525562.1384867150000.21747.1384956306664@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov resolved RF-13361.
--------------------------------

    Resolution: Done

    
> Placeholder inside calendar is not rendered
> -------------------------------------------
>
>                 Key: RF-13361
>                 URL: https://issues.jboss.org/browse/RF-13361
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Michal Petrov
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: placeholder1.png
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> result:
> * in Showcase 4 calendar component has a placeholder text
> * in Showcase 5 placeholder in calendar is missing, see screenshot 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 09:07:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 09:07:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13367) pickList nested in
 accordion has clipped ordering buttons
In-Reply-To: <JIRA.12525704.1384956330702@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525704.1384956330702@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525704.1384956330702.21750.1384956425956@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13367:
--------------------------------

             Summary: pickList nested in accordion has clipped ordering buttons
                 Key: RF-13367
                 URL: https://issues.jboss.org/browse/RF-13367
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska
         Attachments: pickListInAccordion.png

When using {{pickList}} inside of {{accordion}}, then pickList ordering buttons are clipped. One has to scroll the view to the right in order to see it fully.

Please see the attached screenshot. IMHO the pickList should adapt its size to its parent container.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 09:07:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 09:07:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13367) pickList nested in
 accordion has clipped ordering buttons
In-Reply-To: <JIRA.12525704.1384956330000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525704.1384956330000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525704.1384956330000.21759.1384956426422@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13367:
-----------------------------

    Attachment: pickListInAccordion.png

    
> pickList nested in accordion has clipped ordering buttons
> ---------------------------------------------------------
>
>                 Key: RF-13367
>                 URL: https://issues.jboss.org/browse/RF-13367
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListInAccordion.png
>
>
> When using {{pickList}} inside of {{accordion}}, then pickList ordering buttons are clipped. One has to scroll the view to the right in order to see it fully.
> Please see the attached screenshot. IMHO the pickList should adapt its size to its parent container.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 09:09:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 09:09:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13367) pickList nested in
 accordion has clipped ordering buttons
In-Reply-To: <JIRA.12525704.1384956330000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525704.1384956330000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525704.1384956330000.21768.1384956545831@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13367:
-----------------------------

    Steps to Reproduce: 
# Build and load metamer
# access http://localhost:8080/metamer/faces/components/richPickList/simple.xhtml
# switch to the accordion template
# see that pickList is clipped

    
> pickList nested in accordion has clipped ordering buttons
> ---------------------------------------------------------
>
>                 Key: RF-13367
>                 URL: https://issues.jboss.org/browse/RF-13367
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListInAccordion.png
>
>
> When using {{pickList}} inside of {{accordion}}, then pickList ordering buttons are clipped. One has to scroll the view to the right in order to see it fully.
> Please see the attached screenshot. IMHO the pickList should adapt its size to its parent container.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 09:13:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 09:13:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13368) pickList nested in
 collapsiblePanel overflow it
In-Reply-To: <JIRA.12525706.1384956741850@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525706.1384956741850@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525706.1384956741850.21804.1384956786516@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13368:
--------------------------------

             Summary: pickList nested in collapsiblePanel overflow it
                 Key: RF-13368
                 URL: https://issues.jboss.org/browse/RF-13368
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska


When {{pickList}} is nested in {{collapsiblePanel}}, then it overflows it.

Please see the attached screenshot.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 09:15:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 09:15:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13368) pickList nested in
 collapsiblePanel overflow it
In-Reply-To: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525706.1384956741000.21808.1384956907092@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13368:
-----------------------------

    Attachment: pickListAndCollapsiblePanel.png

    
> pickList nested in collapsiblePanel overflow it
> -----------------------------------------------
>
>                 Key: RF-13368
>                 URL: https://issues.jboss.org/browse/RF-13368
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListAndCollapsiblePanel.png
>
>
> When {{pickList}} is nested in {{collapsiblePanel}}, then it overflows it.
> Please see the attached screenshot.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 09:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 09:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13368) pickList nested in
 collapsiblePanel overflows it
In-Reply-To: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525706.1384956741000.21810.1384957026322@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13368:
-----------------------------

    Summary: pickList nested in collapsiblePanel overflows it  (was: pickList nested in collapsiblePanel overflow it)

    
> pickList nested in collapsiblePanel overflows it
> ------------------------------------------------
>
>                 Key: RF-13368
>                 URL: https://issues.jboss.org/browse/RF-13368
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListAndCollapsiblePanel.png
>
>
> When {{pickList}} is nested in {{collapsiblePanel}}, then it overflows it.
> Please see the attached screenshot.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 09:21:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 09:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13368) pickList nested in
 collapsiblePanel overflows it
In-Reply-To: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525706.1384956741000.21837.1384957266471@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13368:
-----------------------------

    Description: 
When {{pickList}} is nested in {{collapsiblePanel}}, then it overflows it.

Please see the attached screenshot.

It also overflows other components:
* {{r:panel}}, 
* {{r:tabPanel}}
but I guess its related ? Tell me if you feel like there should be separated JIRA for each.

  was:
When {{pickList}} is nested in {{collapsiblePanel}}, then it overflows it.

Please see the attached screenshot.


    
> pickList nested in collapsiblePanel overflows it
> ------------------------------------------------
>
>                 Key: RF-13368
>                 URL: https://issues.jboss.org/browse/RF-13368
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListAndCollapsiblePanel.png
>
>
> When {{pickList}} is nested in {{collapsiblePanel}}, then it overflows it.
> Please see the attached screenshot.
> It also overflows other components:
> * {{r:panel}}, 
> * {{r:tabPanel}}
> but I guess its related ? Tell me if you feel like there should be separated JIRA for each.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 09:54:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 09:54:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside
	calendar is not rendered
In-Reply-To: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525562.1384867150000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525562.1384867150000.22070.1384959246824@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13361.
------------------------------



Verified
                
> Placeholder inside calendar is not rendered
> -------------------------------------------
>
>                 Key: RF-13361
>                 URL: https://issues.jboss.org/browse/RF-13361
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Michal Petrov
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: placeholder1.png
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky
> result:
> * in Showcase 4 calendar component has a placeholder text
> * in Showcase 5 placeholder in calendar is missing, see screenshot 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 10:14:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 20 Nov 2013 10:14:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13200) Tree: Uncaught
 TypeError: Object #<Object> has no method '$'
In-Reply-To: <JIRA.12500915.1379512164000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500915.1379512164000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500915.1379512164000.22211.1384960446771@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13200.
------------------------------



Verified
                
> Tree: Uncaught TypeError: Object #<Object> has no method '$'
> ------------------------------------------------------------
>
>                 Key: RF-13200
>                 URL: https://issues.jboss.org/browse/RF-13200
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tree
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> JBoss Application Server: Weld Integration 7.2.1.Final-redhat-10
> JBoss AS 7.2.1.Final-redhat-10
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 29.0.1547.65 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> # deploy Metamer and open http://127.0.0.1:8080/metamer/faces/components/richTree/treeAdaptors.xhtml?templates=plain
> # open node R-1
> # open node R-1.1
> # click on node R-1.1-M-V-1
> expected result:
> * node should be selected
> actual:
> * exception in browser console: Uncaught TypeError: Object #<Object> has no method '$'
> reason:
> * response to Ajax request contains this code
> {code}
> RichFaces.$(&quot;form:richTree&quot;).__updateSelectionFromInput();
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 11:26:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 11:26:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13368) pickList nested in
 collapsiblePanel overflows it
In-Reply-To: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525706.1384956741000.22534.1384964765928@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925413#comment-12925413 ] 

Brian Leathem commented on RF-13368:
------------------------------------

this should have been resolved with a recent richwidget fix.  I'll double check the fix was pulled in to RichFaces.
                
> pickList nested in collapsiblePanel overflows it
> ------------------------------------------------
>
>                 Key: RF-13368
>                 URL: https://issues.jboss.org/browse/RF-13368
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListAndCollapsiblePanel.png
>
>
> When {{pickList}} is nested in {{collapsiblePanel}}, then it overflows it.
> Please see the attached screenshot.
> It also overflows other components:
> * {{r:panel}}, 
> * {{r:tabPanel}}
> but I guess its related ? Tell me if you feel like there should be separated JIRA for each.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 11:44:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 11:44:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13366) ExtendedDataTable:
 footer is in the middle of the control if the height is constant
In-Reply-To: <JIRA.12525699.1384953843000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525699.1384953843000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525699.1384953843000.22646.1384965846157@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13366:
-------------------------------

    Description: 
Reproduce:
Define class and assign it to your extendedDataTable:

{code}
.table_style {
    height: 500px;
}
{code}

Prepare the test data to have minimum rows (not fill the whole table with data).

Expected:
Table height is 500px. Footer is on the bottom of the table and won't change place when rows amount changes.
The whitespace is between the last row and the footer

Actual:
Table height is 500px. Footer is right under the last row and jumps each time the amount of rows changes.
The whitespace is under the footer and surrounded by the table border.


  was:
Reproduce:
Define class and assign it to your extendedDataTable:
.table_style {
    height: 500px;
}

Prepare the test data to have minimum rows (not fill the whole table with data).

Expected:
Table height is 500px. Footer is on the bottom of the table and won't change place when rows amount changes.
The whitespace is between the last row and the footer

Actual:
Table height is 500px. Footer is right under the last row and jumps each time the amount of rows changes.
The whitespace is under the footer and surrounded by the table border.



    
> ExtendedDataTable: footer is in the middle of the control if the height is constant
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13366
>                 URL: https://issues.jboss.org/browse/RF-13366
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>         Attachments: edt[1].png
>
>
> Reproduce:
> Define class and assign it to your extendedDataTable:
> {code}
> .table_style {
>     height: 500px;
> }
> {code}
> Prepare the test data to have minimum rows (not fill the whole table with data).
> Expected:
> Table height is 500px. Footer is on the bottom of the table and won't change place when rows amount changes.
> The whitespace is between the last row and the footer
> Actual:
> Table height is 500px. Footer is right under the last row and jumps each time the amount of rows changes.
> The whitespace is under the footer and surrounded by the table border.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 12:18:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 12:18:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13366) ExtendedDataTable:
 footer is in the middle of the control if the height is constant
In-Reply-To: <JIRA.12525699.1384953843000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525699.1384953843000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525699.1384953843000.22741.1384967885974@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13366.
--------------------------------

    Resolution: Won't Fix


The table footer is intended to be after the final row of the table.  It would be unintuitive to have whitespace between the footer an the table rows, they would appear to be disconnected.

Try placing an additional element/component underneath your table to achieve the layout you are looking for.
                
> ExtendedDataTable: footer is in the middle of the control if the height is constant
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13366
>                 URL: https://issues.jboss.org/browse/RF-13366
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3
>            Reporter: Anton Bogoslavskyi
>         Attachments: edt[1].png
>
>
> Reproduce:
> Define class and assign it to your extendedDataTable:
> {code}
> .table_style {
>     height: 500px;
> }
> {code}
> Prepare the test data to have minimum rows (not fill the whole table with data).
> Expected:
> Table height is 500px. Footer is on the bottom of the table and won't change place when rows amount changes.
> The whitespace is between the last row and the footer
> Actual:
> Table height is 500px. Footer is right under the last row and jumps each time the amount of rows changes.
> The whitespace is under the footer and surrounded by the table border.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 12:21:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 12:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.22747.1384968065830@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13365:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 12:21:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 12:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to
	2.1.26 in RichFaces 4
In-Reply-To: <JIRA.12525674.1384941255000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525674.1384941255000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525674.1384941255000.22749.1384968065905@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13364:
-------------------------------

    Fix Version/s: 4.3.5

    
> Upgrade Mojarra to 2.1.26 in RichFaces 4
> ----------------------------------------
>
>                 Key: RF-13364
>                 URL: https://issues.jboss.org/browse/RF-13364
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 4.3.4
>            Reporter: Pavol Pitonak
>             Fix For: 4.3.5
>
>
> RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26.
> [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 12:26:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 12:26:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.22754.1384968365936@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925444#comment-12925444 ] 

Brian Leathem commented on RF-13323:
------------------------------------

[~wish79] can you take [~jstefek]'s sample as a starting point and modify it to be more like you application to reproduce the failure you describe?  Doing this will help tremendously on isolating the root cause and put us on a path to a resolution of the issue.
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 12:28:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 12:28:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13289) inputspinner : setting
 the value to empty/null
In-Reply-To: <JIRA.12508761.1382687176000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508761.1382687176000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508761.1382687176000.22757.1384968485989@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13289:
-------------------------------

    Fix Version/s: 5-Tracking

    
>  inputspinner : setting the value to empty/null
> -----------------------------------------------
>
>                 Key: RF-13289
>                 URL: https://issues.jboss.org/browse/RF-13289
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.3, 5.0.0.Alpha2
>            Reporter: liumin hu
>             Fix For: 5-Tracking
>
>
>  can put empty/null value in a spinner, everytime the spinner changes empty to 0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 12:28:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 12:28:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12092) a4j:poll : a4j:status
	never clears
In-Reply-To: <JIRA.12462470.1332784893000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12462470.1332784893000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12462470.1332784893000.22768.1384968486511@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-12092:
-------------------------------

    Description: 
When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete.

{code}
<a4j:poll id="ajaxPoll" interval="5000" enabled="true" action="#{faces$DiscoveryStatus.poll}"
           render="#{faces$DiscoveryStatus.reRenderStr}"/>


            <a4j:status id="a4jstatus">

                <f:facet name="start">
                    <img src='/images/ajax-loader.gif'/>
                </f:facet>
                <!--<f:facet name="stop">-->
                <!--<img src="/appiq/images/minor_icon.gif"/>-->
                <!--</f:facet>-->
            </a4j:status>
{code}

This code works correctly in RF 3.3.3.

  was:
When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete.


<a4j:poll id="ajaxPoll" interval="5000" enabled="true" action="#{faces$DiscoveryStatus.poll}"
           render="#{faces$DiscoveryStatus.reRenderStr}"/>


            <a4j:status id="a4jstatus">

                <f:facet name="start">
                    <img src='/images/ajax-loader.gif'/>
                </f:facet>
                <!--<f:facet name="stop">-->
                <!--<img src="/appiq/images/minor_icon.gif"/>-->
                <!--</f:facet>-->
            </a4j:status>


This code works correctly in RF 3.3.3.


    
> a4j:poll : a4j:status never clears
> ----------------------------------
>
>                 Key: RF-12092
>                 URL: https://issues.jboss.org/browse/RF-12092
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 4.2.0.Final, 4.2.1.Final
>            Reporter: Robert Gary
>             Fix For: 5-Tracking
>
>         Attachments: a4jPollIssue.war
>
>
> When a4j:poll fires a4j:status correctly displays the request is in progress. However, it never shows it complete. Using any other a4j component will correctly update the a4j:status. So if the a4j:status is stuck showing its waiting because of an a4j:poll if you click on an a4j:commandButton the a4j:status will correctly show its now complete.
> {code}
> <a4j:poll id="ajaxPoll" interval="5000" enabled="true" action="#{faces$DiscoveryStatus.poll}"
>            render="#{faces$DiscoveryStatus.reRenderStr}"/>
>             <a4j:status id="a4jstatus">
>                 <f:facet name="start">
>                     <img src='/images/ajax-loader.gif'/>
>                 </f:facet>
>                 <!--<f:facet name="stop">-->
>                 <!--<img src="/appiq/images/minor_icon.gif"/>-->
>                 <!--</f:facet>-->
>             </a4j:status>
> {code}
> This code works correctly in RF 3.3.3.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 12:32:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 12:32:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13368) pickList nested in
 collapsiblePanel overflows it
In-Reply-To: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525706.1384956741000.22787.1384968725907@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925449#comment-12925449 ] 

Brian Leathem commented on RF-13368:
------------------------------------

this issue seems out-of-date to me, I was unable to reproduce the issue without pulling in any additional richwidget changes.
                
> pickList nested in collapsiblePanel overflows it
> ------------------------------------------------
>
>                 Key: RF-13368
>                 URL: https://issues.jboss.org/browse/RF-13368
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListAndCollapsiblePanel.png
>
>
> When {{pickList}} is nested in {{collapsiblePanel}}, then it overflows it.
> Please see the attached screenshot.
> It also overflows other components:
> * {{r:panel}}, 
> * {{r:tabPanel}}
> but I guess its related ? Tell me if you feel like there should be separated JIRA for each.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 12:32:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 12:32:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13367) pickList nested in
 accordion has clipped ordering buttons
In-Reply-To: <JIRA.12525704.1384956330000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525704.1384956330000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525704.1384956330000.22791.1384968726070@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13367.
--------------------------------

    Resolution: Out of Date

    
> pickList nested in accordion has clipped ordering buttons
> ---------------------------------------------------------
>
>                 Key: RF-13367
>                 URL: https://issues.jboss.org/browse/RF-13367
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListInAccordion.png
>
>
> When using {{pickList}} inside of {{accordion}}, then pickList ordering buttons are clipped. One has to scroll the view to the right in order to see it fully.
> Please see the attached screenshot. IMHO the pickList should adapt its size to its parent container.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 12:32:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 12:32:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13368) pickList nested in
 collapsiblePanel overflows it
In-Reply-To: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525706.1384956741000.22790.1384968726038@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13368.
--------------------------------

    Resolution: Out of Date

    
> pickList nested in collapsiblePanel overflows it
> ------------------------------------------------
>
>                 Key: RF-13368
>                 URL: https://issues.jboss.org/browse/RF-13368
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListAndCollapsiblePanel.png
>
>
> When {{pickList}} is nested in {{collapsiblePanel}}, then it overflows it.
> Please see the attached screenshot.
> It also overflows other components:
> * {{r:panel}}, 
> * {{r:tabPanel}}
> but I guess its related ? Tell me if you feel like there should be separated JIRA for each.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 12:45:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 12:45:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13368) pickList nested in
 collapsiblePanel overflows it
In-Reply-To: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525706.1384956741000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525706.1384956741000.22851.1384969505987@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13368.
----------------------------


    
> pickList nested in collapsiblePanel overflows it
> ------------------------------------------------
>
>                 Key: RF-13368
>                 URL: https://issues.jboss.org/browse/RF-13368
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListAndCollapsiblePanel.png
>
>
> When {{pickList}} is nested in {{collapsiblePanel}}, then it overflows it.
> Please see the attached screenshot.
> It also overflows other components:
> * {{r:panel}}, 
> * {{r:tabPanel}}
> but I guess its related ? Tell me if you feel like there should be separated JIRA for each.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 12:45:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 20 Nov 2013 12:45:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13367) pickList nested in
 accordion has clipped ordering buttons
In-Reply-To: <JIRA.12525704.1384956330000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525704.1384956330000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525704.1384956330000.22855.1384969506173@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13367.
----------------------------


    
> pickList nested in accordion has clipped ordering buttons
> ---------------------------------------------------------
>
>                 Key: RF-13367
>                 URL: https://issues.jboss.org/browse/RF-13367
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>         Attachments: pickListInAccordion.png
>
>
> When using {{pickList}} inside of {{accordion}}, then pickList ordering buttons are clipped. One has to scroll the view to the right in order to see it fully.
> Please see the attached screenshot. IMHO the pickList should adapt its size to its parent container.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 13:55:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 13:55:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.23080.1384973705987@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13359:
----------------------------------

    Assignee: Brian Leathem

    
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 15:09:05 2013
From: jira-events at lists.jboss.org (Mohammad Weshah (JIRA))
Date: Wed, 20 Nov 2013 15:09:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13323) FileUploadEvent listener
 reset the list value with Viewscope
In-Reply-To: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524556.1383900080000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524556.1383900080000.23182.1384978145829@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925495#comment-12925495 ] 

Mohammad Weshah commented on RF-13323:
--------------------------------------

when i add my code to Jira project it works .but when i add Jira lib to my project my code dose not works, conclusion it seem the problem with my project setting .

Thanks for all
                
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
>                 Key: RF-13323
>                 URL: https://issues.jboss.org/browse/RF-13323
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>  
>            Reporter: Mohammad Weshah
>            Assignee: Ji?? ?tefek
>              Labels: rich:fileUpload
>         Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>  
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();  
>   
> public void FileUploadlistener(FileUploadEvent event) throws Exception {  
>         UploadedFile item = event.getUploadedFile();  
>         UploadedImage file = new UploadedImage();  
>         file.setLength(item.getData().length);  
>         file.setName(item.getName());  
>         file.setData(item.getData());  
>          
>         files.add(file);  
>       }  
> {code}
>  
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>  
> Regards
> Wish79

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 20 15:41:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 20 Nov 2013 15:41:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.23234.1384980066246@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925503#comment-12925503 ] 

Brian Leathem commented on RF-13359:
------------------------------------

Further investigation has shown that the progressBar component works when resource optimisation is disabled, and fails when resource optimisation is enabled.  

This failing behaviour began with this commit: [633da4|https://github.com/richfaces/richfaces/commit/633da455d5a301437c2b5eb9d3316ffde2e5e23e]
                
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 20 15:57:05 2013
From: jira-events at lists.jboss.org (Joao Granado (JIRA))
Date: Wed, 20 Nov 2013 15:57:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13369) autocomplete problem in
 glassfish 4 with jsf 2.2
In-Reply-To: <JIRA.12525764.1384980989999@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525764.1384980989999@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525764.1384980989999.23248.1384981025990@jira02.app.mwc.hst.phx2.redhat.com>

Joao Granado created RF-13369:
---------------------------------

             Summary: autocomplete problem in glassfish 4 with jsf 2.2
                 Key: RF-13369
                 URL: https://issues.jboss.org/browse/RF-13369
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-input
    Affects Versions: 4.3.4
         Environment: glassfish4 with JSF2.2, ubunto 12.04
            Reporter: Joao Granado


autocomplete: the pop-up list always appears empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 02:34:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 02:34:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13369) autocomplete problem in
 glassfish 4 with jsf 2.2
In-Reply-To: <JIRA.12525764.1384980989000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525764.1384980989000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525764.1384980989000.23793.1385019246085@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13369:
-------------------------------

    Fix Version/s: 4.3.5

    
> autocomplete problem in glassfish 4 with jsf 2.2
> ------------------------------------------------
>
>                 Key: RF-13369
>                 URL: https://issues.jboss.org/browse/RF-13369
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: glassfish4 with JSF2.2, ubunto 12.04
>            Reporter: Joao Granado
>              Labels: jsf22
>             Fix For: 4.3.5
>
>
> autocomplete: the pop-up list always appears empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 02:34:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 02:34:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13369) autocomplete problem in
 glassfish 4 with jsf 2.2
In-Reply-To: <JIRA.12525764.1384980989000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525764.1384980989000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525764.1384980989000.23791.1385019245900@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13369:
-------------------------------

    Labels: jsf22  (was: richfaces)

    
> autocomplete problem in glassfish 4 with jsf 2.2
> ------------------------------------------------
>
>                 Key: RF-13369
>                 URL: https://issues.jboss.org/browse/RF-13369
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.3.4
>         Environment: glassfish4 with JSF2.2, ubunto 12.04
>            Reporter: Joao Granado
>              Labels: jsf22
>
> autocomplete: the pop-up list always appears empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 04:12:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 04:12:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.23911.1385025125989@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925626#comment-12925626 ] 

Brian Leathem commented on RF-13359:
------------------------------------

It took a while, but I isolated the single offending line:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/push.js#L259

{code}
      $(document).on('cleanDom.RICH', function(event, ui) {
        if ($.contains(ui.target, widget.element)) {
          widget._destroy();
        }
      });
{code}

[~lfryc] It's not clear to me what you are trying to achieve here, but the end result seems to be that the destroy call is too aggressive.  Can you re-visit this please?

{panel:title=Note:|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
The isolation was difficult, as the file in question should have nothing to do with the progressBar component.  Hence why the effect was observed only had an effect when included via resource packaging.
{panel}
                
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 04:14:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 04:14:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.23925.1385025246264@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925629#comment-12925629 ] 

Brian Leathem commented on RF-13359:
------------------------------------

The above problem only seems to affect the progressBar.  The other components listed are still broken despite commenting out the offending line.
                
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 04:14:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 04:14:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.23931.1385025246828@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13359:
----------------------------------

    Assignee: Luk?? Fry?  (was: Brian Leathem)

    
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 05:47:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 21 Nov 2013 05:47:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.24314.1385030826388@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925674#comment-12925674 ] 

Matej Novotny commented on RF-13210:
------------------------------------

I went through Jenkins jobs to verify this and I also tried to deploy Metamer and manually check for some resource problems (for both RF 5 and 4.5). Everything seems to work correctly.
                
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 05:59:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 21 Nov 2013 05:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.24330.1385031546403@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925674#comment-12925674 ] 

Matej Novotny edited comment on RF-13210 at 11/21/13 5:58 AM:
--------------------------------------------------------------

I went through Jenkins jobs to verify this and I also tried to deploy Metamer and manually check for some resource problems (for both RF 5 and 4.5). Everything seems to work correctly.

EDIT: I was asked to post this result on dev forum [here| https://community.jboss.org/message/846672] is the link.
                
      was (Author: manovotn):
    I went through Jenkins jobs to verify this and I also tried to deploy Metamer and manually check for some resource problems (for both RF 5 and 4.5). Everything seems to work correctly.
                  
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 07:12:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 07:12:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side
In-Reply-To: <JIRA.12525807.1385035920887@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525807.1385035920887@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525807.1385035920887.24531.1385035926207@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Macko created RF-13370:
--------------------------------

             Summary: Charts - server-side
                 Key: RF-13370
                 URL: https://issues.jboss.org/browse/RF-13370
             Project: RichFaces
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: component-output
            Reporter: Luk?? Macko


* rename attribute *clickListener* in chart and series tag to *plotClickListner*
* send request to server only if a server-side listener is attached 
* particular series server-side listeners (called only for particular series events)
* server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 07:18:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 07:18:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side
In-Reply-To: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525807.1385035920000.24566.1385036285807@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925705#comment-12925705 ] 

Luk?? Macko commented on RF-13370:
----------------------------------

I've already done the first and the second item in a [branch | https://github.com/Lukindo/richfaces/commits/chart-server-side].
                
> Charts - server-side
> --------------------
>
>                 Key: RF-13370
>                 URL: https://issues.jboss.org/browse/RF-13370
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>
> * rename attribute *clickListener* in chart and series tag to *plotClickListner*
> * send request to server only if a server-side listener is attached 
> * particular series server-side listeners (called only for particular series events)
> * server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 08:56:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 08:56:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13371) Refactored Push destroy
 logic is too aggresive and causes ProgressBar to fail
In-Reply-To: <JIRA.12525811.1385042093703@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525811.1385042093703@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525811.1385042093703.24749.1385042167304@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13371:
-------------------------------

             Summary: Refactored Push destroy logic is too aggresive and causes ProgressBar to fail
                 Key: RF-13371
                 URL: https://issues.jboss.org/browse/RF-13371
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Luk?? Fry?


>From RF-13359:

{quote}
It took a while, but I isolated the single offending line:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/push.js#L259

{code}
      $(document).on('cleanDom.RICH', function(event, ui) {
        if ($.contains(ui.target, widget.element)) {
          widget._destroy();
        }
      });
{code}

[~lfryc] It's not clear to me what you are trying to achieve here, but the end result seems to be that the destroy call is too aggressive.  Can you re-visit this please?

{panel:title=Note:|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
The isolation was difficult, as the file in question should have nothing to do with the progressBar component.  Hence why the effect was observed only had an effect when included via resource packaging.
{panel}
{quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 08:56:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 08:56:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13371) Refactored Push destroy
 logic is too aggresive and causes ProgressBar to fail
In-Reply-To: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525811.1385042093000.24751.1385042167414@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13371:
----------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Refactored Push destroy logic is too aggresive and causes ProgressBar to fail
> -----------------------------------------------------------------------------
>
>                 Key: RF-13371
>                 URL: https://issues.jboss.org/browse/RF-13371
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> From RF-13359:
> {quote}
> It took a while, but I isolated the single offending line:
> https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/push.js#L259
> {code}
>       $(document).on('cleanDom.RICH', function(event, ui) {
>         if ($.contains(ui.target, widget.element)) {
>           widget._destroy();
>         }
>       });
> {code}
> [~lfryc] It's not clear to me what you are trying to achieve here, but the end result seems to be that the destroy call is too aggressive.  Can you re-visit this please?
> {panel:title=Note:|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
> The isolation was difficult, as the file in question should have nothing to do with the progressBar component.  Hence why the effect was observed only had an effect when included via resource packaging.
> {panel}
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 08:56:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 08:56:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13371) Refactored Push destroy
 logic is too aggresive and causes ProgressBar to fail
In-Reply-To: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525811.1385042093000.24753.1385042167618@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13371:
----------------------------

    Priority: Critical  (was: Major)

    
> Refactored Push destroy logic is too aggresive and causes ProgressBar to fail
> -----------------------------------------------------------------------------
>
>                 Key: RF-13371
>                 URL: https://issues.jboss.org/browse/RF-13371
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> From RF-13359:
> {quote}
> It took a while, but I isolated the single offending line:
> https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/push.js#L259
> {code}
>       $(document).on('cleanDom.RICH', function(event, ui) {
>         if ($.contains(ui.target, widget.element)) {
>           widget._destroy();
>         }
>       });
> {code}
> [~lfryc] It's not clear to me what you are trying to achieve here, but the end result seems to be that the destroy call is too aggressive.  Can you re-visit this please?
> {panel:title=Note:|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
> The isolation was difficult, as the file in question should have nothing to do with the progressBar component.  Hence why the effect was observed only had an effect when included via resource packaging.
> {panel}
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 08:56:08 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 08:56:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.24761.1385042168277@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925738#comment-12925738 ] 

Luk?? Fry? commented on RF-13359:
---------------------------------

Nice catch, Brian! I have created RF-13371 to investigate and added it to Alpha2 sprint.
                
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 08:58:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 08:58:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13371) Refactored Push destroy
 logic is too aggresive and causes ProgressBar to fail
In-Reply-To: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525811.1385042093000.24777.1385042286941@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13371:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> Refactored Push destroy logic is too aggresive and causes ProgressBar to fail
> -----------------------------------------------------------------------------
>
>                 Key: RF-13371
>                 URL: https://issues.jboss.org/browse/RF-13371
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> From RF-13359:
> {quote}
> It took a while, but I isolated the single offending line:
> https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/push.js#L259
> {code}
>       $(document).on('cleanDom.RICH', function(event, ui) {
>         if ($.contains(ui.target, widget.element)) {
>           widget._destroy();
>         }
>       });
> {code}
> [~lfryc] It's not clear to me what you are trying to achieve here, but the end result seems to be that the destroy call is too aggressive.  Can you re-visit this please?
> {panel:title=Note:|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
> The isolation was difficult, as the file in question should have nothing to do with the progressBar component.  Hence why the effect was observed only had an effect when included via resource packaging.
> {panel}
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 08:58:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 08:58:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13371) Refactored Push destroy
 logic is too aggresive and causes ProgressBar to fail
In-Reply-To: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525811.1385042093000.24778.1385042287033@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13371:
-------------------------------

    Assignee: Luk?? Fry?

    
> Refactored Push destroy logic is too aggresive and causes ProgressBar to fail
> -----------------------------------------------------------------------------
>
>                 Key: RF-13371
>                 URL: https://issues.jboss.org/browse/RF-13371
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> From RF-13359:
> {quote}
> It took a while, but I isolated the single offending line:
> https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/push.js#L259
> {code}
>       $(document).on('cleanDom.RICH', function(event, ui) {
>         if ($.contains(ui.target, widget.element)) {
>           widget._destroy();
>         }
>       });
> {code}
> [~lfryc] It's not clear to me what you are trying to achieve here, but the end result seems to be that the destroy call is too aggressive.  Can you re-visit this please?
> {panel:title=Note:|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
> The isolation was difficult, as the file in question should have nothing to do with the progressBar component.  Hence why the effect was observed only had an effect when included via resource packaging.
> {panel}
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 09:02:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 09:02:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.24784.1385042525974@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925742#comment-12925742 ] 

Luk?? Fry? commented on RF-13210:
---------------------------------

Great job, Matej! Thanks for checking.
                
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 09:02:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 09:02:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.24791.1385042526310@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925744#comment-12925744 ] 

Luk?? Fry? commented on RF-13331:
---------------------------------

The pull request was linked again:
https://github.com/richfaces/richfaces/pull/62
                
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 09:04:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 09:04:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.24794.1385042645929@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13331:
-------------------------------

    Assignee: Luk?? Fry?  (was: Luk?? Macko)

    
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 09:07:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 09:07:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.24801.1385042825923@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13352:
-------------------------------

    Assignee: Luk?? Fry?  (was: Luk?? Macko)

    
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 10:30:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 10:30:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13372) togglePanel does not
 work with toggleControl
In-Reply-To: <JIRA.12525839.1385047782205@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525839.1385047782205@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525839.1385047782205.25003.1385047806836@jira02.app.mwc.hst.phx2.redhat.com>

Ji?? ?tefek created RF-13372:
--------------------------------

             Summary: togglePanel does not work with toggleControl
                 Key: RF-13372
                 URL: https://issues.jboss.org/browse/RF-13372
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 5.0.0.Alpha2
         Environment: GlassFish 3.1.2.2, AS 7.1.1
            Reporter: Ji?? ?tefek


Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 10:32:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 10:32:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13372) togglePanel does not
 work with toggleControl
In-Reply-To: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525839.1385047782000.25011.1385047926077@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13372:
-----------------------------

    Steps to Reproduce: 
# deploy metamer and open [this|http://localhost:8080/metamer/faces/components/richTogglePanel/simple.xhtml]
# try to toggle item with any of the links
# have: page is reloaded and item is not switched
# expected: panel is switched by ajax to the chosen item

  was:
# deploy metamer and open 
# try to toggle item with any of the links
# have: page is reloaded and item is not switched
# expected: panel is switched by ajax to the chosen item


    
> togglePanel does not work with toggleControl
> --------------------------------------------
>
>                 Key: RF-13372
>                 URL: https://issues.jboss.org/browse/RF-13372
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: GlassFish 3.1.2.2, AS 7.1.1
>            Reporter: Ji?? ?tefek
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 10:32:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 10:32:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13372) togglePanel does not
 work with toggleControl
In-Reply-To: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525839.1385047782000.25013.1385047926195@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13372:
-----------------------------

    Priority: Blocker  (was: Major)

    
> togglePanel does not work with toggleControl
> --------------------------------------------
>
>                 Key: RF-13372
>                 URL: https://issues.jboss.org/browse/RF-13372
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: GlassFish 3.1.2.2, AS 7.1.1
>            Reporter: Ji?? ?tefek
>            Priority: Blocker
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 10:34:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 10:34:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13372) togglePanel does not
 work with toggleControl
In-Reply-To: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525839.1385047782000.25038.1385048046647@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13372:
-----------------------------

    Workaround Description: The content can be switched by {code}RichFaces.component('id').$JS-API-function{code}

    
> togglePanel does not work with toggleControl
> --------------------------------------------
>
>                 Key: RF-13372
>                 URL: https://issues.jboss.org/browse/RF-13372
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: GlassFish 3.1.2.2, AS 7.1.1
>            Reporter: Ji?? ?tefek
>            Priority: Blocker
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 10:34:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 10:34:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13372) togglePanel does not
 work with toggleControl
In-Reply-To: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525839.1385047782000.25049.1385048047285@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13372:
-----------------------------

    Workaround Description: The content can be switched by {code}RichFaces.component('id').$JS-API-function(){code}  (was: The content can be switched by {code}RichFaces.component('id').$JS-API-function{code})

    
> togglePanel does not work with toggleControl
> --------------------------------------------
>
>                 Key: RF-13372
>                 URL: https://issues.jboss.org/browse/RF-13372
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: GlassFish 3.1.2.2, AS 7.1.1
>            Reporter: Ji?? ?tefek
>            Priority: Blocker
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 11:08:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 11:08:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13293) accordion: JS API: bugs
 of function switchTo()
In-Reply-To: <JIRA.12508933.1383040097000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508933.1383040097000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508933.1383040097000.25194.1385050085953@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925808#comment-12925808 ] 

Ji?? ?tefek commented on RF-13293:
----------------------------------

Same for TogglePanel. Imho for all switchables.
                
> accordion: JS API: bugs of function switchTo()
> ----------------------------------------------
>
>                 Key: RF-13293
>                 URL: https://issues.jboss.org/browse/RF-13293
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Ji?? ?tefek
>             Fix For: 4.5-Tracking
>
>
> Bug #1 -- @cycledSwitching
> Cannot switch to next item, when there is a disabled item in the way when @cycledSwitching=false.
> E.g.:When you use function _switchTo(nextItem())_
> * it switches to next item, but
> ** if you use @cycledSwitching=false, then it cannot switch to an item after a disabled item.
> ** if you use @cycledSwitching=true, then it switches to next available item after a disabled item (plus it can cycle through items from beginning).
> ----
> Bug #2 -- result of function _switchTo()_ can be used without params
> Function _switchTo_ can be used without parameters and this behaviour is undocumented. When you use it without parameters (or null)  it simply switches to next item.
> The catch: When you use _switchTo(previousItem())_ , you use @cycledSwitching=false and you have first item active, then it switches to next item instead of doing nothing (the _previousItem()_ returns null).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 11:08:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 11:08:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13293) accordion: JS API: bugs
 of function switchTo()
In-Reply-To: <JIRA.12508933.1383040097000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508933.1383040097000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508933.1383040097000.25198.1385050086148@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925808#comment-12925808 ] 

Ji?? ?tefek edited comment on RF-13293 at 11/21/13 11:07 AM:
-------------------------------------------------------------

Same with TogglePanel. Imho with all switchables.
                
      was (Author: jstefek):
    Same for TogglePanel. Imho for all switchables.
                  
> accordion: JS API: bugs of function switchTo()
> ----------------------------------------------
>
>                 Key: RF-13293
>                 URL: https://issues.jboss.org/browse/RF-13293
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Ji?? ?tefek
>             Fix For: 4.5-Tracking
>
>
> Bug #1 -- @cycledSwitching
> Cannot switch to next item, when there is a disabled item in the way when @cycledSwitching=false.
> E.g.:When you use function _switchTo(nextItem())_
> * it switches to next item, but
> ** if you use @cycledSwitching=false, then it cannot switch to an item after a disabled item.
> ** if you use @cycledSwitching=true, then it switches to next available item after a disabled item (plus it can cycle through items from beginning).
> ----
> Bug #2 -- result of function _switchTo()_ can be used without params
> Function _switchTo_ can be used without parameters and this behaviour is undocumented. When you use it without parameters (or null)  it simply switches to next item.
> The catch: When you use _switchTo(previousItem())_ , you use @cycledSwitching=false and you have first item active, then it switches to next item instead of doing nothing (the _previousItem()_ returns null).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 11:24:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 11:24:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13372) togglePanel does not
 work with toggleControl
In-Reply-To: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525839.1385047782000.25285.1385051046043@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13372:
-----------------------------

    Steps to Reproduce: 
# deploy metamer and open [this|http://localhost:8080/metamer/faces/components/richTogglePanel/rf-13372.xhtml]
# try to toggle item with any of the links
# have: page is reloaded and item is not switched
# expected: panel is switched by ajax to the chosen item

  was:
# deploy metamer and open [this|http://localhost:8080/metamer/faces/components/richTogglePanel/simple.xhtml]
# try to toggle item with any of the links
# have: page is reloaded and item is not switched
# expected: panel is switched by ajax to the chosen item


    
> togglePanel does not work with toggleControl
> --------------------------------------------
>
>                 Key: RF-13372
>                 URL: https://issues.jboss.org/browse/RF-13372
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: GlassFish 3.1.2.2, AS 7.1.1
>            Reporter: Ji?? ?tefek
>            Priority: Blocker
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 12:55:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 12:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.25543.1385056506309@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13359:
----------------------------------

    Assignee: Brian Leathem  (was: Luk?? Fry?)

    
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 13:33:05 2013
From: jira-events at lists.jboss.org (H G (JIRA))
Date: Thu, 21 Nov 2013 13:33:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10756) collapsibleSubtable: id
 set to tbody differs from component id and break rendering.
In-Reply-To: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12432840.1300178676000.25699.1385058785957@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925888#comment-12925888 ] 

H G commented on RF-10756:
--------------------------

DataTable is one of the most important frequently used components. CollapsibleSubtable adds very nice functionality but is practically useless because of several bugs related to partial updates, breaks filters, etc... All this bugs are very old and targeted to 5-Future. I'd like to see the fixes in the comings releases of RF 5 (alpha 2,3).
                
> collapsibleSubtable: id set to tbody differs from component id and break rendering.
> -----------------------------------------------------------------------------------
>
>                 Key: RF-10756
>                 URL: https://issues.jboss.org/browse/RF-10756
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.0.0.Final
>            Reporter: Ilya Shaikovsky
>            Assignee: Nick Belaevski
>             Fix For: 5-Future
>
>
> added to richfaces-showcase code:
> 			<rich:column colspan="6">
> 				<rich:collapsibleSubTableToggler for="sbtbl" />
> 				<h:outputText value="#{list.vendor}" />
> 				<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
> 				</a4j:commandButton>
> 			</rich:column>
> 			<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
> 				expandMode="client">
> 				<rich:column>
> 					<h:outputText value="#{item.daysLive}" />
> 				</rich:column>
> and 
>     public void incDaysLive(){
>         for (InventoryVendorList vendor : inventoryVendorLists) {
>             for (InventoryVendorItem item : vendor.getVendorItems()) {
>                 item.setDaysLive(item.getDaysLive()+1);
>             }
>             
>         }
>     }
> do not see values updated before refreshing the browser.
> According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 16:06:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 16:06:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13373) The toggle control
	renderer is not invoked
In-Reply-To: <JIRA.12525880.1385067960518@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525880.1385067960518@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525880.1385067960518.26016.1385067965739@jira02.app.mwc.hst.phx2.redhat.com>

Brian Leathem created RF-13373:
----------------------------------

             Summary: The toggle control renderer is not invoked
                 Key: RF-13373
                 URL: https://issues.jboss.org/browse/RF-13373
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-output
    Affects Versions: 5.0.0.Alpha2
            Reporter: Brian Leathem
            Assignee: Brian Leathem
             Fix For: 5.0.0.Alpha2


The toggle control broke because the value returned by the [ToggleControl#getRendererType|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/toggle/toggleControl/ToggleControl.java#L145] method does not match the renderer defined in the [@JsfBehavior annotation|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/toggle/toggleControl/ToggleControl.java#L48].

This descrepency was introduced with this commit: [42fc56|https://github.com/richfaces/richfaces/commit/42fc5626a02a1826e29ce8980aba18152a2bca19]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 16:08:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 16:08:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.26020.1385068085960@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925919#comment-12925919 ] 

Brian Leathem commented on RF-13359:
------------------------------------

The toggle control broke because the value returned by the [ToggleControl#getRendererType|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/toggle/toggleControl/ToggleControl.java#L145] method does not match the renderer defined in the [@JsfBehavior annotation|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/toggle/toggleControl/ToggleControl.java#L48].

This descrepency was introduced with this commit: [42fc56|https://github.com/richfaces/richfaces/commit/42fc5626a02a1826e29ce8980aba18152a2bca19]

I have filed RF-13373 to track the resolution of this issue.
                
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 16:10:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 16:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13373) The toggle control
	renderer is not invoked
In-Reply-To: <JIRA.12525880.1385067960000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525880.1385067960000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525880.1385067960000.26023.1385068206084@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13373:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> The toggle control renderer is not invoked
> ------------------------------------------
>
>                 Key: RF-13373
>                 URL: https://issues.jboss.org/browse/RF-13373
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Brian Leathem
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> The toggle control broke because the value returned by the [ToggleControl#getRendererType|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/toggle/toggleControl/ToggleControl.java#L145] method does not match the renderer defined in the [@JsfBehavior annotation|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/toggle/toggleControl/ToggleControl.java#L48].
> This descrepency was introduced with this commit: [42fc56|https://github.com/richfaces/richfaces/commit/42fc5626a02a1826e29ce8980aba18152a2bca19]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 16:16:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 16:16:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13373) The toggle control
	renderer is not invoked
In-Reply-To: <JIRA.12525880.1385067960000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525880.1385067960000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525880.1385067960000.26049.1385068566653@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13373.
--------------------------------

    Resolution: Done

    
> The toggle control renderer is not invoked
> ------------------------------------------
>
>                 Key: RF-13373
>                 URL: https://issues.jboss.org/browse/RF-13373
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Brian Leathem
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> The toggle control broke because the value returned by the [ToggleControl#getRendererType|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/toggle/toggleControl/ToggleControl.java#L145] method does not match the renderer defined in the [@JsfBehavior annotation|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/toggle/toggleControl/ToggleControl.java#L48].
> This descrepency was introduced with this commit: [42fc56|https://github.com/richfaces/richfaces/commit/42fc5626a02a1826e29ce8980aba18152a2bca19]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 16:18:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 16:18:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.26053.1385068686103@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13359:
-------------------------------

     Original Estimate: 2 days  (was: 1 hour)
    Remaining Estimate: 2 days  (was: 1 hour)

    
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 16:39:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 16:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.26109.1385069946064@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925926#comment-12925926 ] 

Brian Leathem commented on RF-13359:
------------------------------------

With the resolution of RF-13373 the togglePanel now works, but only for the first 2 toggles.  On the third toggle a javascript error is thrown:
{quote}
Uncaught TypeError: Cannot read property 'disabled' of undefined 
{quote}

This error is not present when resource optimisation is disabled.
                
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 17:11:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 17:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13374) RichFaces push
 registered as $.fn.push overrides jQuery function
In-Reply-To: <JIRA.12525883.1385071792092@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525883.1385071792092@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525883.1385071792092.26114.1385071866459@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13374:
-------------------------------

             Summary: RichFaces push registered as $.fn.push overrides jQuery function
                 Key: RF-13374
                 URL: https://issues.jboss.org/browse/RF-13374
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-push/poll
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
            Priority: Blocker
             Fix For: 5.0.0.Alpha2


The real cause of an issue mentioned in RF-13359 isn't an invalid implementation of _destroy method (RF-13371), but rather conflict caused by registering $.fn.push function.

The solution is to rename that jQuery function, e.g. {{$.fn.richfacespush}} or namespace it in other way (e.g. {{$.fn.rf.push}} - question is how it would be called then). Let's investigate further how we can namespace our jQuery plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 17:13:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 17:13:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13374) RichFaces push
 registered as $.fn.push overrides jQuery function
In-Reply-To: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525883.1385071792000.26126.1385071986004@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13374:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> RichFaces push registered as $.fn.push overrides jQuery function
> ----------------------------------------------------------------
>
>                 Key: RF-13374
>                 URL: https://issues.jboss.org/browse/RF-13374
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>
> The real cause of an issue mentioned in RF-13359 isn't an invalid implementation of _destroy method (RF-13371), but rather conflict caused by registering $.fn.push function.
> The solution is to rename that jQuery function, e.g. {{$.fn.richfacespush}} or namespace it in other way (e.g. {{$.fn.rf.push}} - question is how it would be called then). Let's investigate further how we can namespace our jQuery plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 17:13:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 17:13:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13374) RichFaces push
 registered as $.fn.push overrides jQuery function
In-Reply-To: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525883.1385071792000.26129.1385071986182@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13374:
-------------------------------

    Assignee: Luk?? Fry?

    
> RichFaces push registered as $.fn.push overrides jQuery function
> ----------------------------------------------------------------
>
>                 Key: RF-13374
>                 URL: https://issues.jboss.org/browse/RF-13374
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>
> The real cause of an issue mentioned in RF-13359 isn't an invalid implementation of _destroy method (RF-13371), but rather conflict caused by registering $.fn.push function.
> The solution is to rename that jQuery function, e.g. {{$.fn.richfacespush}} or namespace it in other way (e.g. {{$.fn.rf.push}} - question is how it would be called then). Let's investigate further how we can namespace our jQuery plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 17:15:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 17:15:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13354) Autocomplete:
 suggestions stay visible after input is cleared
In-Reply-To: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525458.1384783692000.26137.1385072107253@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925928#comment-12925928 ] 

Luk?? Fry? commented on RF-13354:
---------------------------------

As we have discussed offline with Brian and Pavol, Autocomplete specifies default value of {{minChars=1}}. This satisfies a behavior that doesn't show suggestion list when {{input.value.length < 1}}.

However in Pavol's case, he used {{minChars = 0}} that makes sure auto-completion works even for {{0}} characters in an input.

I believe the behavior is correct and compatible with RF 4.3 implementation.
                
> Autocomplete: suggestions stay visible after input is cleared
> -------------------------------------------------------------
>
>                 Key: RF-13354
>                 URL: https://issues.jboss.org/browse/RF-13354
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # type "ala" into input (several suggestions will appear)
> # clear input, e.g. by using backspace key
> result:
> * the list with all available suggestions is displayed
> * in 4.3.4.Final, the suggestions are *not* displayed when input is empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 17:15:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 17:15:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13354) Autocomplete:
 suggestions stay visible after input is cleared
In-Reply-To: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525458.1384783692000.26140.1385072107390@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13354.
-----------------------------

    Fix Version/s:     (was: 5.0.0.Alpha2)
       Resolution: Rejected

    
> Autocomplete: suggestions stay visible after input is cleared
> -------------------------------------------------------------
>
>                 Key: RF-13354
>                 URL: https://issues.jboss.org/browse/RF-13354
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # type "ala" into input (several suggestions will appear)
> # clear input, e.g. by using backspace key
> result:
> * the list with all available suggestions is displayed
> * in 4.3.4.Final, the suggestions are *not* displayed when input is empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 17:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 17:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13371) Refactored Push destroy
 logic is too aggresive and causes ProgressBar to fail
In-Reply-To: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525811.1385042093000.26142.1385072226250@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925929#comment-12925929 ] 

Luk?? Fry? commented on RF-13371:
---------------------------------

I have put a breakpoint into debugger and I can't see this component destroyed more than once or any other issues with the logic.

But I will double-check and make sure that the code is properly documented as it's not obvious.
                
> Refactored Push destroy logic is too aggresive and causes ProgressBar to fail
> -----------------------------------------------------------------------------
>
>                 Key: RF-13371
>                 URL: https://issues.jboss.org/browse/RF-13371
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> From RF-13359:
> {quote}
> It took a while, but I isolated the single offending line:
> https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/push.js#L259
> {code}
>       $(document).on('cleanDom.RICH', function(event, ui) {
>         if ($.contains(ui.target, widget.element)) {
>           widget._destroy();
>         }
>       });
> {code}
> [~lfryc] It's not clear to me what you are trying to achieve here, but the end result seems to be that the destroy call is too aggressive.  Can you re-visit this please?
> {panel:title=Note:|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
> The isolation was difficult, as the file in question should have nothing to do with the progressBar component.  Hence why the effect was observed only had an effect when included via resource packaging.
> {panel}
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 17:19:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 17:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13374) RichFaces push
 registered as $.fn.push overrides jQuery function
In-Reply-To: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525883.1385071792000.26145.1385072345855@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925930#comment-12925930 ] 

Brian Leathem commented on RF-13374:
------------------------------------

+1 for _richpush_
                
> RichFaces push registered as $.fn.push overrides jQuery function
> ----------------------------------------------------------------
>
>                 Key: RF-13374
>                 URL: https://issues.jboss.org/browse/RF-13374
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>
> The real cause of an issue mentioned in RF-13359 isn't an invalid implementation of _destroy method (RF-13371), but rather conflict caused by registering $.fn.push function.
> The solution is to rename that jQuery function, e.g. {{$.fn.richfacespush}} or namespace it in other way (e.g. {{$.fn.rf.push}} - question is how it would be called then). Let's investigate further how we can namespace our jQuery plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 17:49:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 17:49:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13374) RichFaces push
 registered as $.fn.push overrides jQuery function
In-Reply-To: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525883.1385071792000.26192.1385074145905@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13374.
-----------------------------

    Resolution: Done

    
> RichFaces push registered as $.fn.push overrides jQuery function
> ----------------------------------------------------------------
>
>                 Key: RF-13374
>                 URL: https://issues.jboss.org/browse/RF-13374
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>
> The real cause of an issue mentioned in RF-13359 isn't an invalid implementation of _destroy method (RF-13371), but rather conflict caused by registering $.fn.push function.
> The solution is to rename that jQuery function, e.g. {{$.fn.richfacespush}} or namespace it in other way (e.g. {{$.fn.rf.push}} - question is how it would be called then). Let's investigate further how we can namespace our jQuery plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 17:59:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 17:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.26214.1385074746410@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925942#comment-12925942 ] 

Luk?? Fry? commented on RF-13359:
---------------------------------

All issues with demos mentioned in a issue description cannot be reproduced anymore.
                
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 18:01:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 18:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.26218.1385074866913@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925942#comment-12925942 ] 

Luk?? Fry? edited comment on RF-13359 at 11/21/13 5:59 PM:
-----------------------------------------------------------

All issues with demos mentioned in the issue description cannot be reproduced anymore.
                
      was (Author: lfryc):
    All issues with demos mentioned in a issue description cannot be reproduced anymore.
                  
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 18:01:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 21 Nov 2013 18:01:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.26222.1385074867076@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13359.
-----------------------------

    Resolution: Done

    
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 18:10:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 18:10:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.26228.1385075405924@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13365:
-------------------------------

     Original Estimate: 1 hour
    Remaining Estimate: 1 hour

    
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 18:10:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 18:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.26231.1385075406229@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13365:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 19:17:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 19:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13252) a4j:ajax includes jsf.js
	script twice
In-Reply-To: <JIRA.12502662.1381395391000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502662.1381395391000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502662.1381395391000.26306.1385079426338@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925957#comment-12925957 ] 

Brian Leathem commented on RF-13252:
------------------------------------

The workaround suggested in RF-13042 is as follows:

Add the following code snippet anywhere on the page, outside of the region participating in the ajax refresh:

{quote}
<h:inputText rendered="false">
    <f:ajax />
</h:inputText>
{quote}

[~ppitonak] would you please verify the above workaround?  We should include it in the WFK release notes if so.
                
> a4j:ajax includes jsf.js script twice
> -------------------------------------
>
>                 Key: RF-13252
>                 URL: https://issues.jboss.org/browse/RF-13252
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 4.3.4
>            Reporter: Jon?? Trantina
>             Fix For: 4.3.5
>
>         Attachments: reproducer.zip
>
>
> When a4j:script is used in the page like so:
> {noformat}
> <h:commandLink value="Click me ">
>     <a4j:ajax event="click" render="@form"/>
> </h:commandLink>
> {noformat}
> Then two script tags pointing to jsf.js are added to the page, once in the head by the inclusion of @ResourceDependency [1], and once again by Overriding the ClientBehaviorRenderer#getScript method [2,3].
> Note, that according to Brian, resolving this without introducing any functional regressions may require the resolution of RF-12270 [4].
> [1] https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/ajax/ajax/AjaxBehaviorRenderer.java#L53
> [2] https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/ajax/ajax/AjaxBehaviorRenderer.java#L123
> [3] https://github.com/jboss/mojarra/blob/2.1.21-jbossorg-1/jsf-api/src/main/java/javax/faces/render/ClientBehaviorRenderer.java#L95
> [4] https://issues.jboss.org/browse/RF-12270

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 19:23:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 19:23:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10756) collapsibleSubtable: id
 set to tbody differs from component id and break rendering.
In-Reply-To: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12432840.1300178676000.26314.1385079787814@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-10756:
-------------------------------

    Description: 
added to richfaces-showcase code:

{code}
			<rich:column colspan="6">
				<rich:collapsibleSubTableToggler for="sbtbl" />
				<h:outputText value="#{list.vendor}" />
				<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
				</a4j:commandButton>
			</rich:column>
			<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
				expandMode="client">
				<rich:column>
					<h:outputText value="#{item.daysLive}" />
				</rich:column>
{code}

and 

{code}
    public void incDaysLive(){
        for (InventoryVendorList vendor : inventoryVendorLists) {
            for (InventoryVendorItem item : vendor.getVendorItems()) {
                item.setDaysLive(item.getDaysLive()+1);
            }
            
        }
    }
{code}

do not see values updated before refreshing the browser.

According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.

  was:
added to richfaces-showcase code:

			<rich:column colspan="6">
				<rich:collapsibleSubTableToggler for="sbtbl" />
				<h:outputText value="#{list.vendor}" />
				<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
				</a4j:commandButton>
			</rich:column>
			<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
				expandMode="client">
				<rich:column>
					<h:outputText value="#{item.daysLive}" />
				</rich:column>

and 
    public void incDaysLive(){
        for (InventoryVendorList vendor : inventoryVendorLists) {
            for (InventoryVendorItem item : vendor.getVendorItems()) {
                item.setDaysLive(item.getDaysLive()+1);
            }
            
        }
    }

do not see values updated before refreshing the browser.

According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.


    
> collapsibleSubtable: id set to tbody differs from component id and break rendering.
> -----------------------------------------------------------------------------------
>
>                 Key: RF-10756
>                 URL: https://issues.jboss.org/browse/RF-10756
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.0.0.Final
>            Reporter: Ilya Shaikovsky
>            Assignee: Nick Belaevski
>             Fix For: 5-Future
>
>
> added to richfaces-showcase code:
> {code}
> 			<rich:column colspan="6">
> 				<rich:collapsibleSubTableToggler for="sbtbl" />
> 				<h:outputText value="#{list.vendor}" />
> 				<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
> 				</a4j:commandButton>
> 			</rich:column>
> 			<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
> 				expandMode="client">
> 				<rich:column>
> 					<h:outputText value="#{item.daysLive}" />
> 				</rich:column>
> {code}
> and 
> {code}
>     public void incDaysLive(){
>         for (InventoryVendorList vendor : inventoryVendorLists) {
>             for (InventoryVendorItem item : vendor.getVendorItems()) {
>                 item.setDaysLive(item.getDaysLive()+1);
>             }
>             
>         }
>     }
> {code}
> do not see values updated before refreshing the browser.
> According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 19:23:08 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 19:23:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10756) collapsibleSubtable: id
 set to tbody differs from component id and break rendering.
In-Reply-To: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12432840.1300178676000.26330.1385079788800@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-10756:
----------------------------------

    Assignee: Pavol Pitonak  (was: Nick Belaevski)


QE, please verify this issue.
                
> collapsibleSubtable: id set to tbody differs from component id and break rendering.
> -----------------------------------------------------------------------------------
>
>                 Key: RF-10756
>                 URL: https://issues.jboss.org/browse/RF-10756
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.0.0.Final
>            Reporter: Ilya Shaikovsky
>            Assignee: Pavol Pitonak
>
> added to richfaces-showcase code:
> {code}
> 			<rich:column colspan="6">
> 				<rich:collapsibleSubTableToggler for="sbtbl" />
> 				<h:outputText value="#{list.vendor}" />
> 				<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
> 				</a4j:commandButton>
> 			</rich:column>
> 			<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
> 				expandMode="client">
> 				<rich:column>
> 					<h:outputText value="#{item.daysLive}" />
> 				</rich:column>
> {code}
> and 
> {code}
>     public void incDaysLive(){
>         for (InventoryVendorList vendor : inventoryVendorLists) {
>             for (InventoryVendorItem item : vendor.getVendorItems()) {
>                 item.setDaysLive(item.getDaysLive()+1);
>             }
>             
>         }
>     }
> {code}
> do not see values updated before refreshing the browser.
> According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 19:23:08 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 19:23:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10756) collapsibleSubtable: id
 set to tbody differs from component id and break rendering.
In-Reply-To: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12432840.1300178676000.26322.1385079788360@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-10756:
-------------------------------

    Fix Version/s:     (was: 5-Future)

    
> collapsibleSubtable: id set to tbody differs from component id and break rendering.
> -----------------------------------------------------------------------------------
>
>                 Key: RF-10756
>                 URL: https://issues.jboss.org/browse/RF-10756
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.0.0.Final
>            Reporter: Ilya Shaikovsky
>            Assignee: Nick Belaevski
>
> added to richfaces-showcase code:
> {code}
> 			<rich:column colspan="6">
> 				<rich:collapsibleSubTableToggler for="sbtbl" />
> 				<h:outputText value="#{list.vendor}" />
> 				<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
> 				</a4j:commandButton>
> 			</rich:column>
> 			<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
> 				expandMode="client">
> 				<rich:column>
> 					<h:outputText value="#{item.daysLive}" />
> 				</rich:column>
> {code}
> and 
> {code}
>     public void incDaysLive(){
>         for (InventoryVendorList vendor : inventoryVendorLists) {
>             for (InventoryVendorItem item : vendor.getVendorItems()) {
>                 item.setDaysLive(item.getDaysLive()+1);
>             }
>             
>         }
>     }
> {code}
> do not see values updated before refreshing the browser.
> According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 21 19:27:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 19:27:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side
In-Reply-To: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525807.1385035920000.26332.1385080025823@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925960#comment-12925960 ] 

Brian Leathem commented on RF-13370:
------------------------------------

[~lukindo] woudl you like these fixes included in 5.0.0.Alpha2 or Alpha3?  If they fixes are ready, we should consider including them in Alpha2.
                
> Charts - server-side
> --------------------
>
>                 Key: RF-13370
>                 URL: https://issues.jboss.org/browse/RF-13370
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>
> * rename attribute *clickListener* in chart and series tag to *plotClickListner*
> * send request to server only if a server-side listener is attached 
> * particular series server-side listeners (called only for particular series events)
> * server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 19:29:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 19:29:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13372) togglePanel does not
 work with toggleControl
In-Reply-To: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525839.1385047782000.26334.1385080146231@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925961#comment-12925961 ] 

Brian Leathem commented on RF-13372:
------------------------------------

The fix for RF-13373 is already committed, so I'm marking this one as the duplicate issue.
                
> togglePanel does not work with toggleControl
> --------------------------------------------
>
>                 Key: RF-13372
>                 URL: https://issues.jboss.org/browse/RF-13372
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: GlassFish 3.1.2.2, AS 7.1.1
>            Reporter: Ji?? ?tefek
>            Priority: Blocker
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 19:29:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 19:29:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13372) togglePanel does not
 work with toggleControl
In-Reply-To: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525839.1385047782000.26336.1385080146318@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13372.
--------------------------------

    Resolution: Duplicate Issue

    
> togglePanel does not work with toggleControl
> --------------------------------------------
>
>                 Key: RF-13372
>                 URL: https://issues.jboss.org/browse/RF-13372
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: GlassFish 3.1.2.2, AS 7.1.1
>            Reporter: Ji?? ?tefek
>            Priority: Blocker
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 21 19:34:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 21 Nov 2013 19:34:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.26340.1385080445944@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13365:
----------------------------------

    Assignee: Luk?? Fry?

    
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 02:32:06 2013
From: jira-events at lists.jboss.org (J W (JIRA))
Date: Fri, 22 Nov 2013 02:32:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11088) rich:select modify
 manualInput behavior to avoid single item scoped item list popup when
 editing value
In-Reply-To: <JIRA.12440702.1309245969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12440702.1309245969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12440702.1309245969000.26489.1385105526425@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-11088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925981#comment-12925981 ] 

J W commented on RF-11088:
--------------------------

I fixed the errors in the mentioned pull request.
                
> rich:select modify manualInput behavior to avoid single item scoped item list popup when editing value
> ------------------------------------------------------------------------------------------------------
>
>                 Key: RF-11088
>                 URL: https://issues.jboss.org/browse/RF-11088
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 4.0.0.Final, 4.0.1.Milestone1, 4.1.0.Milestone1
>            Reporter: Justin Wyer
>              Labels: rich:select
>             Fix For: 4.5-Tracking
>
>
> rich:select has usability issues when using enableManualInput="true" this will address the issues discussed in the forum post. My current idea is to attempt to display the full item list and auto highlight the input's value.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 02:39:06 2013
From: jira-events at lists.jboss.org (J W (JIRA))
Date: Fri, 22 Nov 2013 02:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11088) rich:select modify
 manualInput behavior to avoid single item scoped item list popup when
 editing value
In-Reply-To: <JIRA.12440702.1309245969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12440702.1309245969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12440702.1309245969000.26505.1385105946371@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-11088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925981#comment-12925981 ] 

J W edited comment on RF-11088 at 11/22/13 2:38 AM:
----------------------------------------------------

I fixed the errors in the mentioned pull request.

https://github.com/richfaces/richfaces/pull/42
                
      was (Author: jigg4):
    I fixed the errors in the mentioned pull request.
                  
> rich:select modify manualInput behavior to avoid single item scoped item list popup when editing value
> ------------------------------------------------------------------------------------------------------
>
>                 Key: RF-11088
>                 URL: https://issues.jboss.org/browse/RF-11088
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 4.0.0.Final, 4.0.1.Milestone1, 4.1.0.Milestone1
>            Reporter: Justin Wyer
>              Labels: rich:select
>             Fix For: 4.5-Tracking
>
>
> rich:select has usability issues when using enableManualInput="true" this will address the issues discussed in the forum post. My current idea is to attempt to display the full item list and auto highlight the input's value.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 02:41:06 2013
From: jira-events at lists.jboss.org (J W (JIRA))
Date: Fri, 22 Nov 2013 02:41:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13101) rich:select Method
 getSelectInputLabel is not working when using objects
In-Reply-To: <JIRA.12496870.1374222203000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12496870.1374222203000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12496870.1374222203000.26513.1385106066750@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925984#comment-12925984 ] 

J W commented on RF-13101:
--------------------------

i have fixed the pull request: https://github.com/richfaces/richfaces/pull/42
                
> rich:select Method getSelectInputLabel is not working when using objects
> ------------------------------------------------------------------------
>
>                 Key: RF-13101
>                 URL: https://issues.jboss.org/browse/RF-13101
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, component-selects
>    Affects Versions: 4.3.2, 5.0.0.Alpha1
>            Reporter: J W
>              Labels: rich:select, select
>             Fix For: 4.5-Tracking
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> The condition of the if-statement in org.richfaces.renderkit.SelectHelper.getSelectInputLabel(FacesContext facesContext, UIComponent component) is not working with the string-representations of the items. If using cloned objects the equals method will return false, even if the items are the same, because the IDs are different.
> The method should use only the strings of the objects, similiar to how MyFaces has solved this (check workarround).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 02:41:07 2013
From: jira-events at lists.jboss.org (J W (JIRA))
Date: Fri, 22 Nov 2013 02:41:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11021) rich:select should show
 first item in list if defaultLabel is not set
In-Reply-To: <JIRA.12438620.1306850914000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12438620.1306850914000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12438620.1306850914000.26520.1385106067065@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-11021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925985#comment-12925985 ] 

J W commented on RF-11021:
--------------------------

pls check the pull request again, as i have fixed the errors: https://github.com/richfaces/richfaces/pull/42
                
> rich:select should show first item in list if defaultLabel is not set
> ---------------------------------------------------------------------
>
>                 Key: RF-11021
>                 URL: https://issues.jboss.org/browse/RF-11021
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.0.0.Final
>         Environment: GAE, Win7-64
>            Reporter: Ara Minosian
>              Labels: richfaces
>             Fix For: 4.5-Tracking
>
>
> This code does not display first value. Id displays emty item.
> {code:xml} 
> <rich:select id="unitSelect" value="#{editBean.paramEditor1.unitKeyWithRange}" selectFirst="true">
>     <f:selectItems value="#{editBean.paramEditor1.availableUnits}"/>
> </rich:select>
> {code} 
> This code dispays first value
> {code:xml} 
> <h:selectOneMenu id="unitSelect" value="#{editBean.paramEditor1.unitKeyWithRange}">
>     <f:selectItems value="#{editBean.paramEditor1.availableUnits}"/>
> </h:selectOneMenu>
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 02:43:06 2013
From: jira-events at lists.jboss.org (J W (JIRA))
Date: Fri, 22 Nov 2013 02:43:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12613) rich:select with
 enablemanualinput selects wrong items
In-Reply-To: <JIRA.12479359.1353061335000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12479359.1353061335000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12479359.1353061335000.26526.1385106186118@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925986#comment-12925986 ] 

J W commented on RF-12613:
--------------------------

Fixed the Pull request: https://github.com/richfaces/richfaces/pull/42
                
> rich:select with enablemanualinput selects wrong items
> ------------------------------------------------------
>
>                 Key: RF-12613
>                 URL: https://issues.jboss.org/browse/RF-12613
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.1.0.Final, 4.3.0.M2
>            Reporter: geert olaerts
>             Fix For: 4.5-Tracking
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> When using rich:select with enablemanualinput = "true", the wrong item might be selected. If the list of possible items is (in this order): "test test" and "test" and the user selects "test" richfaces will select "test test" as input. The same happens if the user types "test". If the list is "test" and "test test" and the user selects or types "test" the correct item is selected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 04:47:06 2013
From: jira-events at lists.jboss.org (J W (JIRA))
Date: Fri, 22 Nov 2013 04:47:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10131) Improve SelectItem(s)
 handling compatibility with JSF 2.0
In-Reply-To: <JIRA.12427446.1294236532000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12427446.1294236532000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12427446.1294236532000.26636.1385113626349@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926002#comment-12926002 ] 

J W commented on RF-10131:
--------------------------

Is this already finished?
Whenever i try to add an Item with f:selectItem with itemDisabled="true", the item will be always treated like every other item.
                
> Improve SelectItem(s) handling compatibility with JSF 2.0
> ---------------------------------------------------------
>
>                 Key: RF-10131
>                 URL: https://issues.jboss.org/browse/RF-10131
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: compatibility
>         Environment: myfaces 2.0.3, richfaces 4.0 trunk rev. 20883
>            Reporter: Martin Ko??
>            Assignee: Gleb Galkin
>             Fix For: 4.0.0.Milestone6
>
>
> 1) JSF 2.0 specifies new attributes itemLabel, itemDescription and itemDisabled for f:selectItem(s). Unfortunately those attributes are not part of public API but every renderkit must reimplement it again in own code base. RichFaces org.richfaces.component.util.SelectUtils.getSelectItems(FacesContext, UIComponent) currently support only old JSF 1.2 style (SelectItem instances are obtained from value="#{}"). 
> Implement support for f:selectItems value="#{}" var="variable" 
> 							itemLabel="#{...}" itemValue="#{...}"/>
> 2) null or empty SelectItems handling: o.j.rf.SelectUtils throws an exception if no SelectItem(s) are available. If think this is too agressive and not very useful for user. I suggest to use myfaces-like solution: a warning in development stage like:
> WARNING: ValueExpression #{de.bier.humpen} of UISelectItems with component-path {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /X500Form.xhtml][Class: javax.faces.component.html.HtmlBody,    ...  ][Class: javax.faces.component.UISelectItems,Id: selectItemsId} does not reference an Object of type SelectItem, array, Iterable or Map, but of type: null

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 04:49:07 2013
From: jira-events at lists.jboss.org (J W (JIRA))
Date: Fri, 22 Nov 2013 04:49:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10131) Improve SelectItem(s)
 handling compatibility with JSF 2.0
In-Reply-To: <JIRA.12427446.1294236532000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12427446.1294236532000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12427446.1294236532000.26666.1385113747351@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926002#comment-12926002 ] 

J W edited comment on RF-10131 at 11/22/13 4:49 AM:
----------------------------------------------------

Is this already finished?
Whenever i try to add an Item with f:selectItem with itemDisabled="true", the item will be always treated like every other item.
I am using RF 4.3.1
                
      was (Author: jigg4):
    Is this already finished?
Whenever i try to add an Item with f:selectItem with itemDisabled="true", the item will be always treated like every other item.
                  
> Improve SelectItem(s) handling compatibility with JSF 2.0
> ---------------------------------------------------------
>
>                 Key: RF-10131
>                 URL: https://issues.jboss.org/browse/RF-10131
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: compatibility
>         Environment: myfaces 2.0.3, richfaces 4.0 trunk rev. 20883
>            Reporter: Martin Ko??
>            Assignee: Gleb Galkin
>             Fix For: 4.0.0.Milestone6
>
>
> 1) JSF 2.0 specifies new attributes itemLabel, itemDescription and itemDisabled for f:selectItem(s). Unfortunately those attributes are not part of public API but every renderkit must reimplement it again in own code base. RichFaces org.richfaces.component.util.SelectUtils.getSelectItems(FacesContext, UIComponent) currently support only old JSF 1.2 style (SelectItem instances are obtained from value="#{}"). 
> Implement support for f:selectItems value="#{}" var="variable" 
> 							itemLabel="#{...}" itemValue="#{...}"/>
> 2) null or empty SelectItems handling: o.j.rf.SelectUtils throws an exception if no SelectItem(s) are available. If think this is too agressive and not very useful for user. I suggest to use myfaces-like solution: a warning in development stage like:
> WARNING: ValueExpression #{de.bier.humpen} of UISelectItems with component-path {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /X500Form.xhtml][Class: javax.faces.component.html.HtmlBody,    ...  ][Class: javax.faces.component.UISelectItems,Id: selectItemsId} does not reference an Object of type SelectItem, array, Iterable or Map, but of type: null

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 04:55:07 2013
From: jira-events at lists.jboss.org (J W (JIRA))
Date: Fri, 22 Nov 2013 04:55:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-6678) RichFaces Select
 components: implement disabled state support for selectItem
In-Reply-To: <JIRA.12383309.1238663780000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12383309.1238663780000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12383309.1238663780000.26717.1385114107198@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926011#comment-12926011 ] 

J W commented on RF-6678:
-------------------------

Shouldnt this have be done in this issue already? https://issues.jboss.org/browse/RF-10131
                
> RichFaces Select components: implement disabled state support for selectItem
> ----------------------------------------------------------------------------
>
>                 Key: RF-6678
>                 URL: https://issues.jboss.org/browse/RF-6678
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 4.0.0.Milestone5
>            Reporter: Ilya Shaikovsky
>             Fix For: 5-Tracking
>
>
> components:
> inplaceSelect
> select
> In future we should support the same in:
> listShuttle
> orderingList
> note: s:selectItems disabled attribute should also works fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 05:03:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 05:03:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13375) Bridge Base: components
 can't be destroyed because they listens for non-existing event cleanDom
In-Reply-To: <JIRA.12525898.1385114555913@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525898.1385114555913@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525898.1385114555913.26759.1385114586540@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13375:
-------------------------------

             Summary: Bridge Base: components can't be destroyed because they listens for non-existing event cleanDom
                 Key: RF-13375
                 URL: https://issues.jboss.org/browse/RF-13375
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
            Assignee: Luk?? Fry?
             Fix For: 5.0.0.Alpha2


richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 05:03:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 05:03:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13371) Clarify and fix Push
	destroy logic
In-Reply-To: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525811.1385042093000.26762.1385114586706@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13371:
----------------------------

        Summary: Clarify and fix Push destroy logic  (was: Refactored Push destroy logic is too aggresive and causes ProgressBar to fail)
    Description: 
I need to commend on the approach I take for destroying Push component which follows approximately what Widget Factory does.

I have also found that the widget _destro method isn't called at all, because there is no such event as {{cleanDom}}.

richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

  was:
>From RF-13359:

{quote}
It took a while, but I isolated the single offending line:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/push.js#L259

{code}
      $(document).on('cleanDom.RICH', function(event, ui) {
        if ($.contains(ui.target, widget.element)) {
          widget._destroy();
        }
      });
{code}

[~lfryc] It's not clear to me what you are trying to achieve here, but the end result seems to be that the destroy call is too aggressive.  Can you re-visit this please?

{panel:title=Note:|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
The isolation was difficult, as the file in question should have nothing to do with the progressBar component.  Hence why the effect was observed only had an effect when included via resource packaging.
{panel}
{quote}


    
> Clarify and fix Push destroy logic
> ----------------------------------
>
>                 Key: RF-13371
>                 URL: https://issues.jboss.org/browse/RF-13371
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> I need to commend on the approach I take for destroying Push component which follows approximately what Widget Factory does.
> I have also found that the widget _destro method isn't called at all, because there is no such event as {{cleanDom}}.
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 05:03:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 05:03:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13375) Bridge Base: components
 can't be destroyed because they listens for non-existing event cleanDom
In-Reply-To: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525898.1385114555000.26766.1385114586888@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13375:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> Bridge Base: components can't be destroyed because they listens for non-existing event cleanDom
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13375
>                 URL: https://issues.jboss.org/browse/RF-13375
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 05:05:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 05:05:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13371) Clarify and fix Push
	destroy logic
In-Reply-To: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525811.1385042093000.26769.1385114706543@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13371.
-----------------------------

    Resolution: Done

    
> Clarify and fix Push destroy logic
> ----------------------------------
>
>                 Key: RF-13371
>                 URL: https://issues.jboss.org/browse/RF-13371
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> I need to commend on the approach I take for destroying Push component which follows approximately what Widget Factory does.
> I have also found that the widget _destro method isn't called at all, because there is no such event as {{cleanDom}}.
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 05:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 05:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13375) Bridge Base: components
 can't be destroyed because they listens for non-existing event cleanDom
In-Reply-To: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525898.1385114555000.26819.1385115426320@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926021#comment-12926021 ] 

Luk?? Fry? commented on RF-13375:
---------------------------------

During debugging I haven't found our event handlers in [bridge-base|https://github.com/richfaces/richfaces/blob/0bf739c81460686c839e6cb5c0d43c400150835c/framework/src/main/resources/META-INF/resources/org.richfaces/bridge/bridge-base.js#L19] aren't fired, even though the _destroy for Widget Factory are called.

The reason is that richfaces.js calls {{$.cleanData}}:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/richfaces.js#L155

Then jquery.ui.widget.js fires {{remove}} event when cleanData is called:
https://github.com/jquery/jquery-ui/blob/1.10.3/ui/jquery.ui.widget.js#L19

Then this event is observed and this.destroy() method is fired which calls _destroy() method in widget impls:
https://github.com/jquery/jquery-ui/blob/1.10.3/ui/jquery.ui.widget.js#L241

----

We could depend on this Widget Factory cleaning logic or, in order to make sure the method is called, we could introduce own one.
                
> Bridge Base: components can't be destroyed because they listens for non-existing event cleanDom
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13375
>                 URL: https://issues.jboss.org/browse/RF-13375
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 05:17:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 05:17:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13375) Bridge Base: components
 can't be destroyed because they listens for non-existing event cleanDom
In-Reply-To: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525898.1385114555000.26842.1385115427536@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13375:
-------------------------------

    Assignee: Brian Leathem  (was: Luk?? Fry?)


Wdyt [~bleathem] ?
                
> Bridge Base: components can't be destroyed because they listens for non-existing event cleanDom
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13375
>                 URL: https://issues.jboss.org/browse/RF-13375
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 05:31:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 05:31:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.26874.1385116265944@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13365:
----------------------------

    Labels: regression  (was: )

    
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>              Labels: regression
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:29:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:29:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13374) RichFaces push
 registered as $.fn.push overrides jQuery function
In-Reply-To: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525883.1385071792000.27094.1385123346570@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reopened RF-13374:
-----------------------------



I need to update RF 4.5
                
> RichFaces push registered as $.fn.push overrides jQuery function
> ----------------------------------------------------------------
>
>                 Key: RF-13374
>                 URL: https://issues.jboss.org/browse/RF-13374
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>
> The real cause of an issue mentioned in RF-13359 isn't an invalid implementation of _destroy method (RF-13371), but rather conflict caused by registering $.fn.push function.
> The solution is to rename that jQuery function, e.g. {{$.fn.richfacespush}} or namespace it in other way (e.g. {{$.fn.rf.push}} - question is how it would be called then). Let's investigate further how we can namespace our jQuery plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:43:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:43:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Updated to RW with RCUE
 theme: fonts aren't loaded correctly
In-Reply-To: <JIRA.12525909.1385124185290@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185290@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185290.27148.1385124185907@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13376:
-------------------------------

             Summary: Updated to RW with RCUE theme: fonts aren't loaded correctly
                 Key: RF-13376
                 URL: https://issues.jboss.org/browse/RF-13376
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component, examples, showcase
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
             Fix For: 5.0.0.Alpha2




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:45:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:45:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Updated to RW with RCUE
 theme: fonts aren't loaded correctly
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.27151.1385124305890@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Description: The issue is visible on a component-demo or showcase.

    
> Updated to RW with RCUE theme: fonts aren't loaded correctly
> ------------------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> The issue is visible on a component-demo or showcase.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:55:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Updated to RW with RCUE
 theme: fonts aren't loaded correctly
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.27161.1385124906013@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 6

    
> Updated to RW with RCUE theme: fonts aren't loaded correctly
> ------------------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> The issue is visible on a component-demo or showcase.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:57:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:57:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Updated to RW with RCUE
 theme: fonts aren't loaded correctly
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.27165.1385125025984@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Description: 
The issue is visible on a component-demo.

I can't reproduce issue in Showcase.

----

Additionally we should review demos that they all still look correctly.

----

I would suggest disable default controls (buttons/inputs/...) skinning so that

  was:
The issue is visible on a component-demo.

I can't reproduce issue in Showcase.

----

Additionally we should review demos that they all still look correctly.


    
> Updated to RW with RCUE theme: fonts aren't loaded correctly
> ------------------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> The issue is visible on a component-demo.
> I can't reproduce issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I would suggest disable default controls (buttons/inputs/...) skinning so that

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:57:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:57:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Updated to RW with RCUE
 theme: fonts aren't loaded correctly
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.27164.1385125025917@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Description: 
The issue is visible on a component-demo.

I can't reproduce issue in Showcase.

----

Additionally we should review demos that they all still look correctly.

  was:The issue is visible on a component-demo or showcase.


    
> Updated to RW with RCUE theme: fonts aren't loaded correctly
> ------------------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> The issue is visible on a component-demo.
> I can't reproduce issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:57:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Issues when updated to
	RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.27168.1385125026180@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Summary: Issues when updated to RW with RCUE theme  (was: Updated to RW with RCUE theme: fonts aren't loaded correctly)

    
> Issues when updated to RW with RCUE theme
> -----------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> The issue is visible on a component-demo.
> I can't reproduce issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I would suggest disable default controls (buttons/inputs/...) skinning so that

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:57:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Visual issues when
 updated to RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.27169.1385125026220@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Summary: Visual issues when updated to RW with RCUE theme  (was: Issues when updated to RW with RCUE theme)

    
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> The issue is visible on a component-demo.
> I can't reproduce issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I would suggest disable default controls (buttons/inputs/...) skinning so that

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:57:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Visual issues when
 updated to RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.27171.1385125026314@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Description: 
Fonts {{Open Sans}} can't be loadedin the component-demo.

I can't reproduce this issue in Showcase.

----

Additionally we should review demos that they all still look correctly.

----

I would suggest disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

  was:
The issue is visible on a component-demo.

I can't reproduce issue in Showcase.

----

Additionally we should review demos that they all still look correctly.

----

I would suggest disable default controls (buttons/inputs/...) skinning so that


    
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> Fonts {{Open Sans}} can't be loadedin the component-demo.
> I can't reproduce this issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I would suggest disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:59:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Visual issues when
 updated to RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.27181.1385125146715@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Description: 
Fonts {{Open Sans}} can't be loadedin the component-demo.

I can't reproduce this issue in Showcase.

----

Additionally we should review demos that they all still look correctly.

----

I would suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

  was:
Fonts {{Open Sans}} can't be loadedin the component-demo.

I can't reproduce this issue in Showcase.

----

Additionally we should review demos that they all still look correctly.

----

I would suggest disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.


    
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> Fonts {{Open Sans}} can't be loadedin the component-demo.
> I can't reproduce this issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I would suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 07:59:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 07:59:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Visual issues when
 updated to RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.27184.1385125147098@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Description: 
Fonts {{Open Sans}} can't be loadedin the component-demo.

I can't reproduce this issue in Showcase.

----

Additionally we should review demos that they all still look correctly.

----

I suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

  was:
Fonts {{Open Sans}} can't be loadedin the component-demo.

I can't reproduce this issue in Showcase.

----

Additionally we should review demos that they all still look correctly.

----

I would suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.


    
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> Fonts {{Open Sans}} can't be loadedin the component-demo.
> I can't reproduce this issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 08:14:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 08:14:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.27226.1385126045879@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926064#comment-12926064 ] 

Luk?? Fry? commented on RF-13365:
---------------------------------

Disabling now works fine as can be seen in commited dev sample in push-demo.

However it takes time before the Push start to work again - I believe this issue might be related to RF-12543.
                
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>              Labels: regression
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 08:16:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 08:16:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.27230.1385126166898@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926064#comment-12926064 ] 

Luk?? Fry? edited comment on RF-13365 at 11/22/13 8:14 AM:
-----------------------------------------------------------

Disabling now works fine as can be seen in commited dev sample in push-demo (the inability to function correctly was caused by wrong destroy logic - RF-13371)

However it takes time before the Push start to work again - I believe this issue might be related to RF-12543.
                
      was (Author: lfryc):
    Disabling now works fine as can be seen in commited dev sample in push-demo.

However it takes time before the Push start to work again - I believe this issue might be related to RF-12543.
                  
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>              Labels: regression
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 08:16:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 08:16:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.27232.1385126166980@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926065#comment-12926065 ] 

Luk?? Fry? commented on RF-13365:
---------------------------------

[~jstefek], could you please try to reproduce with RF 4.3 whether it was the issue as well?
                
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>              Labels: regression
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 08:18:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 08:18:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.27251.1385126286456@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13365.
-----------------------------

    Resolution: Done


I believe the original issue is resolved now. Let's higher the priority of RF-12543 to get a fix for re-rendered Push.
                
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>              Labels: regression
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 08:20:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 08:20:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.27253.1385126405901@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reopened RF-13330:
-----------------------------



Brian, I believe this needs to be fixed for RF 4.5 as well.
                
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 08:20:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 08:20:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13374) RichFaces push
 registered as $.fn.push overrides jQuery function
In-Reply-To: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525883.1385071792000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525883.1385071792000.27260.1385126406249@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13374.
-----------------------------

    Resolution: Done

    
> RichFaces push registered as $.fn.push overrides jQuery function
> ----------------------------------------------------------------
>
>                 Key: RF-13374
>                 URL: https://issues.jboss.org/browse/RF-13374
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>
> The real cause of an issue mentioned in RF-13359 isn't an invalid implementation of _destroy method (RF-13371), but rather conflict caused by registering $.fn.push function.
> The solution is to rename that jQuery function, e.g. {{$.fn.richfacespush}} or namespace it in other way (e.g. {{$.fn.rf.push}} - question is how it would be called then). Let's investigate further how we can namespace our jQuery plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 08:53:07 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 22 Nov 2013 08:53:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13377) NullPointerException in
 calendar page fragment
In-Reply-To: <JIRA.12525914.1385128343852@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525914.1385128343852@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525914.1385128343852.27455.1385128387508@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13377:
----------------------------------

             Summary: NullPointerException in calendar page fragment
                 Key: RF-13377
                 URL: https://issues.jboss.org/browse/RF-13377
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: page-fragments
    Affects Versions: 5.0.0.Alpha2
         Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
            Reporter: Pavol Pitonak


# run a Metamer test for r:calendar using page fragments, e.g.
{code}
mvn clean verify -P jbossas-managed-7-1 -Dtest=TestCalendarAttributes
{code}

result:
* all tests are skipped because a NPE in calendar page fragment
{quote}
*org.jboss.arquillian.graphene.enricher.exception.PageFragmentInitializationException: java.lang.reflect.InvocationTargetException*
	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:171)
	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.setupPageFragment(PageFragmentEnricher.java:208)
	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.enrich(PageFragmentEnricher.java:85)
	at org.jboss.arquillian.graphene.enricher.GrapheneEnricher.enrich(GrapheneEnricher.java:51)
	at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52)
	at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95)
	at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:613)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
	at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
	at org.testng.TestRunner.privateRun(TestRunner.java:757)
	at org.testng.TestRunner.run(TestRunner.java:608)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
	at org.testng.SuiteRunner.run(SuiteRunner.java:240)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
	at org.testng.TestNG.run(TestNG.java:999)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:91)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:128)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:112)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
*Caused by: java.lang.reflect.InvocationTargetException*
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.instantiate(AbstractSearchContextEnricher.java:174)
	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:144)
	... 76 more
*Caused by: java.lang.NullPointerException: configuration is null - it needs to be setup before starting to use it*
	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext.get(RichFacesPageFragmentsConfigurationContext.java:43)
	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$2.getTarget(RichFacesPageFragmentsConfigurationContext.java:97)
	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$1.invoke(RichFacesPageFragmentsConfigurationContext.java:57)
	at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.intercept(GrapheneProxyHandler.java:92)
	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfiguration$$EnhancerByGraphene$$e41cfe31.isUseJSInteractionStrategy(<generated>)
	at org.richfaces.fragment.calendar.RichFacesCalendar.<init>(RichFacesCalendar.java:52)
	... 82 more
{quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 11:38:05 2013
From: jira-events at lists.jboss.org (David Rawlings (JIRA))
Date: Fri, 22 Nov 2013 11:38:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12533) UIDataAdaptor throws NPE
 with disabled PSS (webflow 2.3)
In-Reply-To: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12476684.1349966061000.27969.1385138285975@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Rawlings updated RF-12533:
--------------------------------

    Attachment: TreeStructureManager.java


I had the same problem, using webflow 2.3.1, myfaces 2.1.12 and RichFaces 4.3.3.Final.  I'm not sure what the 'correct' fix is, but I've implemented the attached patch (spring faces 2.3.1 TreeStructureManager) that seems to work ok.  I've added comments in the attached source to show where the patch starts/finishes.

I'm no myfaces/webflow/RichFaces expert so use at your own risk...
                
> UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
> --------------------------------------------------------
>
>                 Key: RF-12533
>                 URL: https://issues.jboss.org/browse/RF-12533
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.2.2.Final, 4.2.3.CR1, 4.3.0.M1
>         Environment: spring webflow 2.3.1, myfaces-impl 2.1.8
>            Reporter: Anton Zukovskij
>            Priority: Critical
>              Labels: partial_state_saving, spring
>             Fix For: 5-Tracking
>
>         Attachments: log-2.txt, log.txt, swf-rf4.zip, TreeStructureManager.java
>
>
> When partial state saving is disabled(javax.faces.PARTIAL_STATE_SAVING=false), nullpointer exception is thrown during restore state phase of webflow rendered view that contains UIDataAdaptor component. In other words NPE exception is thrown on every page submit of webflow rendered views that contain components that exted UIDataAdaptor. Please see log attached and sample application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 13:11:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 22 Nov 2013 13:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13375) Bridge Base: components
 can't be destroyed because they listens for non-existing event cleanDom
In-Reply-To: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525898.1385114555000.28224.1385143866390@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13375:
-------------------------------

    Assignee: Luk?? Fry?  (was: Brian Leathem)


Agreed: we will depend on Widget Factory's cleanData hook. Let's remove event hooks from bridge-base.js.
                
> Bridge Base: components can't be destroyed because they listens for non-existing event cleanDom
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13375
>                 URL: https://issues.jboss.org/browse/RF-13375
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 13:11:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 22 Nov 2013 13:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13375) Bridge Base: components
 can't be destroyed because they listens for non-existing event cleanDom
In-Reply-To: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525898.1385114555000.28229.1385143866597@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926253#comment-12926253 ] 

Brian Leathem commented on RF-13375:
------------------------------------

Let's add a comment to richfaces.js that this happens and is expected then we can remove the listeners from bridge-base.
                
> Bridge Base: components can't be destroyed because they listens for non-existing event cleanDom
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13375
>                 URL: https://issues.jboss.org/browse/RF-13375
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 13:13:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 22 Nov 2013 13:13:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.28238.1385143985830@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926255#comment-12926255 ] 

Brian Leathem commented on RF-13330:
------------------------------------

+1, let's check RichFaces 4.5 for improper jQuery usage as well.
                
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 13:42:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 22 Nov 2013 13:42:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10131) Improve SelectItem(s)
 handling compatibility with JSF 2.0
In-Reply-To: <JIRA.12427446.1294236532000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12427446.1294236532000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12427446.1294236532000.28277.1385145726002@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926261#comment-12926261 ] 

Brian Leathem commented on RF-10131:
------------------------------------

This issue states it was resolved in the select and inplaceSelect components.  RF-4491 address seeing this impl'ed in the pick and ordering list.
                
> Improve SelectItem(s) handling compatibility with JSF 2.0
> ---------------------------------------------------------
>
>                 Key: RF-10131
>                 URL: https://issues.jboss.org/browse/RF-10131
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: compatibility
>         Environment: myfaces 2.0.3, richfaces 4.0 trunk rev. 20883
>            Reporter: Martin Ko??
>            Assignee: Gleb Galkin
>             Fix For: 4.0.0.Milestone6
>
>
> 1) JSF 2.0 specifies new attributes itemLabel, itemDescription and itemDisabled for f:selectItem(s). Unfortunately those attributes are not part of public API but every renderkit must reimplement it again in own code base. RichFaces org.richfaces.component.util.SelectUtils.getSelectItems(FacesContext, UIComponent) currently support only old JSF 1.2 style (SelectItem instances are obtained from value="#{}"). 
> Implement support for f:selectItems value="#{}" var="variable" 
> 							itemLabel="#{...}" itemValue="#{...}"/>
> 2) null or empty SelectItems handling: o.j.rf.SelectUtils throws an exception if no SelectItem(s) are available. If think this is too agressive and not very useful for user. I suggest to use myfaces-like solution: a warning in development stage like:
> WARNING: ValueExpression #{de.bier.humpen} of UISelectItems with component-path {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /X500Form.xhtml][Class: javax.faces.component.html.HtmlBody,    ...  ][Class: javax.faces.component.UISelectItems,Id: selectItemsId} does not reference an Object of type SelectItem, array, Iterable or Map, but of type: null

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 13:44:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 22 Nov 2013 13:44:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12533) UIDataAdaptor throws NPE
 with disabled PSS (webflow 2.3)
In-Reply-To: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12476684.1349966061000.28281.1385145845872@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926262#comment-12926262 ] 

Brian Leathem commented on RF-12533:
------------------------------------

Is there a corresponding Spring Webflow issue tracking this?
                
> UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
> --------------------------------------------------------
>
>                 Key: RF-12533
>                 URL: https://issues.jboss.org/browse/RF-12533
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.2.2.Final, 4.2.3.CR1, 4.3.0.M1
>         Environment: spring webflow 2.3.1, myfaces-impl 2.1.8
>            Reporter: Anton Zukovskij
>            Priority: Critical
>              Labels: partial_state_saving, spring
>             Fix For: 5-Tracking
>
>         Attachments: log-2.txt, log.txt, swf-rf4.zip, TreeStructureManager.java
>
>
> When partial state saving is disabled(javax.faces.PARTIAL_STATE_SAVING=false), nullpointer exception is thrown during restore state phase of webflow rendered view that contains UIDataAdaptor component. In other words NPE exception is thrown on every page submit of webflow rendered views that contain components that exted UIDataAdaptor. Please see log attached and sample application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 13:46:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 22 Nov 2013 13:46:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13371) Clarify and fix Push
	destroy logic
In-Reply-To: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525811.1385042093000.28289.1385145966600@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13371:
-------------------------------

    Description: 
I need to comment on the approach I took for destroying the Push component which follows approximately what Widget Factory does.

I have also found that the widget _destroy method isn't called at all, because there is no such event as {{cleanDom}}.

richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

  was:
I need to commend on the approach I take for destroying Push component which follows approximately what Widget Factory does.

I have also found that the widget _destro method isn't called at all, because there is no such event as {{cleanDom}}.

richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.


    
> Clarify and fix Push destroy logic
> ----------------------------------
>
>                 Key: RF-13371
>                 URL: https://issues.jboss.org/browse/RF-13371
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> I need to comment on the approach I took for destroying the Push component which follows approximately what Widget Factory does.
> I have also found that the widget _destroy method isn't called at all, because there is no such event as {{cleanDom}}.
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 13:53:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 22 Nov 2013 13:53:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-6678) RichFaces Select
 components: implement disabled state support for selectItem
In-Reply-To: <JIRA.12383309.1238663780000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12383309.1238663780000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12383309.1238663780000.28294.1385146386428@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-6678:
---------------------------------

    Assignee: Pavol Pitonak


QE, would you please confirm one way or another the status of disabled SelectItems in select and inplaceSelect components?
                
> RichFaces Select components: implement disabled state support for selectItem
> ----------------------------------------------------------------------------
>
>                 Key: RF-6678
>                 URL: https://issues.jboss.org/browse/RF-6678
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 4.0.0.Milestone5
>            Reporter: Ilya Shaikovsky
>            Assignee: Pavol Pitonak
>             Fix For: 5-Tracking
>
>
> components:
> inplaceSelect
> select
> In future we should support the same in:
> listShuttle
> orderingList
> note: s:selectItems disabled attribute should also works fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 14:40:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 22 Nov 2013 14:40:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13377) NullPointerException in
 calendar page fragment
In-Reply-To: <JIRA.12525914.1385128343000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525914.1385128343000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525914.1385128343000.28375.1385149206663@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13377:
----------------------------------

    Assignee: Pavol Pitonak


Pavol, page fragments are owned by QE.  Please assess, schedule, and assign this issue as you see fit.
                
> NullPointerException in calendar page fragment
> ----------------------------------------------
>
>                 Key: RF-13377
>                 URL: https://issues.jboss.org/browse/RF-13377
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Pavol Pitonak
>
> # run a Metamer test for r:calendar using page fragments, e.g.
> {code}
> mvn clean verify -P jbossas-managed-7-1 -Dtest=TestCalendarAttributes
> {code}
> result:
> * all tests are skipped because a NPE in calendar page fragment
> {quote}
> *org.jboss.arquillian.graphene.enricher.exception.PageFragmentInitializationException: java.lang.reflect.InvocationTargetException*
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:171)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.setupPageFragment(PageFragmentEnricher.java:208)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.enrich(PageFragmentEnricher.java:85)
> 	at org.jboss.arquillian.graphene.enricher.GrapheneEnricher.enrich(GrapheneEnricher.java:51)
> 	at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52)
> 	at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> 	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> 	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> 	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95)
> 	at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> 	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
> 	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
> 	at org.testng.internal.Invoker.invokeMethod(Invoker.java:613)
> 	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
> 	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
> 	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> 	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> 	at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
> 	at org.testng.TestRunner.privateRun(TestRunner.java:757)
> 	at org.testng.TestRunner.run(TestRunner.java:608)
> 	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> 	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> 	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> 	at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> 	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> 	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> 	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
> 	at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
> 	at org.testng.TestNG.run(TestNG.java:999)
> 	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:91)
> 	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:128)
> 	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:112)
> 	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> 	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> 	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> 	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> *Caused by: java.lang.reflect.InvocationTargetException*
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> 	at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.instantiate(AbstractSearchContextEnricher.java:174)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:144)
> 	... 76 more
> *Caused by: java.lang.NullPointerException: configuration is null - it needs to be setup before starting to use it*
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext.get(RichFacesPageFragmentsConfigurationContext.java:43)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$2.getTarget(RichFacesPageFragmentsConfigurationContext.java:97)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$1.invoke(RichFacesPageFragmentsConfigurationContext.java:57)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.intercept(GrapheneProxyHandler.java:92)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfiguration$$EnhancerByGraphene$$e41cfe31.isUseJSInteractionStrategy(<generated>)
> 	at org.richfaces.fragment.calendar.RichFacesCalendar.<init>(RichFacesCalendar.java:52)
> 	... 82 more
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 22 14:42:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 22 Nov 2013 14:42:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Visual issues when
 updated to RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.28390.1385149327053@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926274#comment-12926274 ] 

Brian Leathem commented on RF-13376:
------------------------------------

[~lfryc] I suggest we address this along with theming in 5.0.0.Alpha3?
                
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> Fonts {{Open Sans}} can't be loadedin the component-demo.
> I can't reproduce this issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 22 14:42:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 22 Nov 2013 14:42:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Visual issues when
 updated to RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.28392.1385149327123@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926274#comment-12926274 ] 

Brian Leathem edited comment on RF-13376 at 11/22/13 2:41 PM:
--------------------------------------------------------------

[~lfryc] I suggest we address this along with theming in 5.0.0.Alpha3.
                
      was (Author: bleathem):
    [~lfryc] I suggest we address this along with theming in 5.0.0.Alpha3?
                  
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> Fonts {{Open Sans}} can't be loadedin the component-demo.
> I can't reproduce this issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sat Nov 23 05:43:05 2013
From: jira-events at lists.jboss.org (Salvo Isaja (JIRA))
Date: Sat, 23 Nov 2013 05:43:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13378) extendedDataTable not
 shown inside Bootstrap tab panel
In-Reply-To: <JIRA.12525973.1385203366104@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525973.1385203366104@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525973.1385203366104.28865.1385203385879@jira02.app.mwc.hst.phx2.redhat.com>

Salvo Isaja created RF-13378:
--------------------------------

             Summary: extendedDataTable not shown inside Bootstrap tab panel
                 Key: RF-13378
                 URL: https://issues.jboss.org/browse/RF-13378
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-tables
    Affects Versions: 4.3.4
         Environment: Tested on Ubuntu 12.04, Firefox 25, JDK 7u45, GlassFish 3.1.2.2
            Reporter: Salvo Isaja


As described in RF-12682, when an extendedDataTable is placed in a parent which is not displayed by default, showing the parent causes the table to be invisible. This was reported to be solved on 4.3.2 for tables inside rich:tabPanel, while this issue is on 4.3.4 for tables inside a tab panel from Bootstrap 3.
Attached a minimal project which demonstrates the issue.
Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Sat Nov 23 05:45:05 2013
From: jira-events at lists.jboss.org (Salvo Isaja (JIRA))
Date: Sat, 23 Nov 2013 05:45:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13378) extendedDataTable not
 shown inside Bootstrap tab panel
In-Reply-To: <JIRA.12525973.1385203366000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525973.1385203366000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525973.1385203366000.28867.1385203505965@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Salvo Isaja updated RF-13378:
-----------------------------

    Attachment: ExtendedDataTableTest.7z


NetBeans project with a facelet that demonstrates the problem. Includes Bootstrap 3.
                
> extendedDataTable not shown inside Bootstrap tab panel
> ------------------------------------------------------
>
>                 Key: RF-13378
>                 URL: https://issues.jboss.org/browse/RF-13378
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.4
>         Environment: Tested on Ubuntu 12.04, Firefox 25, JDK 7u45, GlassFish 3.1.2.2
>            Reporter: Salvo Isaja
>         Attachments: ExtendedDataTableTest.7z
>
>
> As described in RF-12682, when an extendedDataTable is placed in a parent which is not displayed by default, showing the parent causes the table to be invisible. This was reported to be solved on 4.3.2 for tables inside rich:tabPanel, while this issue is on 4.3.4 for tables inside a tab panel from Bootstrap 3.
> Attached a minimal project which demonstrates the issue.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Sat Nov 23 05:45:06 2013
From: jira-events at lists.jboss.org (Salvo Isaja (JIRA))
Date: Sat, 23 Nov 2013 05:45:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12682) extendedDataTable render
 issue with rich:tabPanel
In-Reply-To: <JIRA.12481662.1356024824000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12481662.1356024824000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12481662.1356024824000.28877.1385203506453@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926337#comment-12926337 ] 

Salvo Isaja commented on RF-12682:
----------------------------------

Hi Brian, I've opened RF-13378, thanks.
                
> extendedDataTable render issue with rich:tabPanel
> -------------------------------------------------
>
>                 Key: RF-12682
>                 URL: https://issues.jboss.org/browse/RF-12682
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final
>            Reporter: Kaveh A.
>              Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided
>         Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip
>
>
> This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time).
> In this particular case if we load a page with two tabs.  Furthermore if we have one extendedDataTable in each tab  (the first tab shows and the second tab is not shown at first).  In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly.  A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue.
> https://community.jboss.org/message/783787

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Sun Nov 24 02:49:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 02:49:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Visual issues when
 updated to RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.29025.1385279345821@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926363#comment-12926363 ] 

Luk?? Fry? commented on RF-13376:
---------------------------------

+1, since it doesn't affect Showcase much
                
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> Fonts {{Open Sans}} can't be loadedin the component-demo.
> I can't reproduce this issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 02:51:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 02:51:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Visual issues when
 updated to RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.29027.1385279465936@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926363#comment-12926363 ] 

Luk?? Fry? edited comment on RF-13376 at 11/24/13 2:49 AM:
-----------------------------------------------------------

+1, since it doesn't affect Showcase
                
      was (Author: lfryc):
    +1, since it doesn't affect Showcase much
                  
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> Fonts {{Open Sans}} can't be loadedin the component-demo.
> I can't reproduce this issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 02:51:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 02:51:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Visual issues when
 updated to RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.29029.1385279466175@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Fix Version/s: 5.0.0.Alpha3
                       (was: 5.0.0.Alpha2)

    
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha3
>
>
> Fonts {{Open Sans}} can't be loadedin the component-demo.
> I can't reproduce this issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 02:56:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 02:56:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13375) Bridge Base: components
 can't be destroyed because they listens for non-existing event cleanDom
In-Reply-To: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525898.1385114555000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525898.1385114555000.29031.1385279765819@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13375.
-----------------------------

    Resolution: Done

    
> Bridge Base: components can't be destroyed because they listens for non-existing event cleanDom
> -----------------------------------------------------------------------------------------------
>
>                 Key: RF-13375
>                 URL: https://issues.jboss.org/browse/RF-13375
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 02:58:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 02:58:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13376) Visual issues when
 updated to RW with RCUE theme
In-Reply-To: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525909.1385124185000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525909.1385124185000.29033.1385279885885@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13376:
----------------------------

    Sprint:   (was: 5.0.0.Alpha2 - Sprint 6)

    
> Visual issues when updated to RW with RCUE theme
> ------------------------------------------------
>
>                 Key: RF-13376
>                 URL: https://issues.jboss.org/browse/RF-13376
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component, examples, showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha3
>
>
> Fonts {{Open Sans}} can't be loadedin the component-demo.
> I can't reproduce this issue in Showcase.
> ----
> Additionally we should review demos that they all still look correctly.
> ----
> I suggest to disable default controls (buttons/inputs/...) skinning so that the themes RichFaces/RichWidgets do not conflict.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 03:19:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 03:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.29035.1385281145948@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13330.
-----------------------------

    Resolution: Done


I have replaced occurences of improper $/jQuery usage with RichFaces.jQuery in 4.5.x branch.
                
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 03:19:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 03:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13330) RichFaces.jQuery should
 be used in CDK templates instead of $
In-Reply-To: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524718.1384095223000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524718.1384095223000.29037.1385281146085@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13330:
----------------------------

    Fix Version/s: 4.5.0.Alpha1

    
> RichFaces.jQuery should be used in CDK templates instead of $
> -------------------------------------------------------------
>
>                 Key: RF-13330
>                 URL: https://issues.jboss.org/browse/RF-13330
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Brian Leathem
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> RichFaces make use of non-conflicting jQuery reference to avoid collisions with user-specific use of jQuery.
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L44
> https://github.com/richfaces/richfaces/blob/b7df8b6d5d46e17f47ecc8d099f3441bb81b8b9e/framework/src/main/java/org/richfaces/ui/select/orderingList/ordering-list.template.xml#L92

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 03:21:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 03:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13379) Build on Travis fails
 due to NoClassDefFoundEx.: javax/servlet/Servlet
In-Reply-To: <JIRA.12525985.1385281263567@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525985.1385281263567@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525985.1385281263567.29039.1385281265852@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13379:
-------------------------------

             Summary: Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet
                 Key: RF-13379
                 URL: https://issues.jboss.org/browse/RF-13379
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Luk?? Fry?


https://travis-ci.org/richfaces/richfaces/builds/14381706

{code}
[INFO] <<< exec-maven-plugin:1.2.1:java (static-resources) @ richfaces <<<
[INFO] 
[INFO] --- exec-maven-plugin:1.2.1:java (static-resources) @ richfaces ---
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Nov 24, 2013 8:04:06 AM org.richfaces.resource.optimizer.ResourceGenerator execute
SEVERE: null
java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/Servlet
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:188)
	at org.richfaces.resource.optimizer.ResourceGenerator.execute(ResourceGenerator.java:437)
	at org.richfaces.resource.optimizer.GenerateResourcesMain.main(GenerateResourcesMain.java:39)
	at sun.reflect.NativethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativethodAccessorImpl.invoke(NativethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
	at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.NoClassDefFoundError: javax/servlet/Servlet
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
	at org.richfaces.resource.ResourceFactoryImpl.creatappedResource(ResourceFactoryImpl.java:356)
	at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 03:23:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 03:23:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13379) Build on Travis fails
 due to NoClassDefFoundEx.: javax/servlet/Servlet
In-Reply-To: <JIRA.12525985.1385281263000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525985.1385281263000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525985.1385281263000.29042.1385281386392@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13379:
----------------------------

    Component/s: tests - functional 

    
> Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet
> ----------------------------------------------------------------------
>
>                 Key: RF-13379
>                 URL: https://issues.jboss.org/browse/RF-13379
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Fry?
>
> https://travis-ci.org/richfaces/richfaces/builds/14381706
> {code}
> [INFO] <<< exec-maven-plugin:1.2.1:java (static-resources) @ richfaces <<<
> [INFO] 
> [INFO] --- exec-maven-plugin:1.2.1:java (static-resources) @ richfaces ---
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> Nov 24, 2013 8:04:06 AM org.richfaces.resource.optimizer.ResourceGenerator execute
> SEVERE: null
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> 	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 	at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> 	at org.richfaces.resource.optimizer.ResourceGenerator.execute(ResourceGenerator.java:437)
> 	at org.richfaces.resource.optimizer.GenerateResourcesMain.main(GenerateResourcesMain.java:39)
> 	at sun.reflect.NativethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativethodAccessorImpl.invoke(NativethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> 	at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> 	at java.lang.ClassLoader.defineClass1(Native Method)
> 	at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
> 	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> 	at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
> 	at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> 	at org.richfaces.resource.ResourceFactoryImpl.creatappedResource(ResourceFactoryImpl.java:356)
> 	at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 03:23:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 03:23:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13379) Build on Travis fails
 due to NoClassDefFoundEx.: javax/servlet/Servlet
In-Reply-To: <JIRA.12525985.1385281263000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525985.1385281263000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525985.1385281263000.29044.1385281386564@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13379:
----------------------------

    Component/s: resource handling
                     (was: tests - functional )

    
> Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet
> ----------------------------------------------------------------------
>
>                 Key: RF-13379
>                 URL: https://issues.jboss.org/browse/RF-13379
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: resource handling
>            Reporter: Luk?? Fry?
>
> https://travis-ci.org/richfaces/richfaces/builds/14381706
> {code}
> [INFO] <<< exec-maven-plugin:1.2.1:java (static-resources) @ richfaces <<<
> [INFO] 
> [INFO] --- exec-maven-plugin:1.2.1:java (static-resources) @ richfaces ---
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> Nov 24, 2013 8:04:06 AM org.richfaces.resource.optimizer.ResourceGenerator execute
> SEVERE: null
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> 	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 	at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> 	at org.richfaces.resource.optimizer.ResourceGenerator.execute(ResourceGenerator.java:437)
> 	at org.richfaces.resource.optimizer.GenerateResourcesMain.main(GenerateResourcesMain.java:39)
> 	at sun.reflect.NativethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativethodAccessorImpl.invoke(NativethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> 	at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> 	at java.lang.ClassLoader.defineClass1(Native Method)
> 	at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
> 	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> 	at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
> 	at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> 	at org.richfaces.resource.ResourceFactoryImpl.creatappedResource(ResourceFactoryImpl.java:356)
> 	at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 03:23:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 03:23:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13379) Build on Travis fails
 due to NoClassDefFoundEx.: javax/servlet/Servlet in resource-optimizer
In-Reply-To: <JIRA.12525985.1385281263000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525985.1385281263000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525985.1385281263000.29046.1385281386710@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13379:
----------------------------

    Summary: Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet in resource-optimizer  (was: Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet)

    
> Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet in resource-optimizer
> --------------------------------------------------------------------------------------------
>
>                 Key: RF-13379
>                 URL: https://issues.jboss.org/browse/RF-13379
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: resource handling
>            Reporter: Luk?? Fry?
>
> https://travis-ci.org/richfaces/richfaces/builds/14381706
> {code}
> [INFO] <<< exec-maven-plugin:1.2.1:java (static-resources) @ richfaces <<<
> [INFO] 
> [INFO] --- exec-maven-plugin:1.2.1:java (static-resources) @ richfaces ---
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> Nov 24, 2013 8:04:06 AM org.richfaces.resource.optimizer.ResourceGenerator execute
> SEVERE: null
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> 	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 	at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> 	at org.richfaces.resource.optimizer.ResourceGenerator.execute(ResourceGenerator.java:437)
> 	at org.richfaces.resource.optimizer.GenerateResourcesMain.main(GenerateResourcesMain.java:39)
> 	at sun.reflect.NativethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativethodAccessorImpl.invoke(NativethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> 	at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> 	at java.lang.ClassLoader.defineClass1(Native Method)
> 	at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
> 	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> 	at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
> 	at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> 	at org.richfaces.resource.ResourceFactoryImpl.creatappedResource(ResourceFactoryImpl.java:356)
> 	at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Sun Nov 24 03:23:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Sun, 24 Nov 2013 03:23:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13379) Build on Travis fails
 due to NoClassDefFoundEx.: javax/servlet/Servlet (during framework resource
 optimization)
In-Reply-To: <JIRA.12525985.1385281263000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525985.1385281263000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525985.1385281263000.29047.1385281386778@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13379:
----------------------------

    Summary: Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet (during framework resource optimization)  (was: Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet in resource-optimizer)

    
> Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet (during framework resource optimization)
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13379
>                 URL: https://issues.jboss.org/browse/RF-13379
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: resource handling
>            Reporter: Luk?? Fry?
>
> https://travis-ci.org/richfaces/richfaces/builds/14381706
> {code}
> [INFO] <<< exec-maven-plugin:1.2.1:java (static-resources) @ richfaces <<<
> [INFO] 
> [INFO] --- exec-maven-plugin:1.2.1:java (static-resources) @ richfaces ---
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> Nov 24, 2013 8:04:06 AM org.richfaces.resource.optimizer.ResourceGenerator execute
> SEVERE: null
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> 	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 	at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> 	at org.richfaces.resource.optimizer.ResourceGenerator.execute(ResourceGenerator.java:437)
> 	at org.richfaces.resource.optimizer.GenerateResourcesMain.main(GenerateResourcesMain.java:39)
> 	at sun.reflect.NativethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativethodAccessorImpl.invoke(NativethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> 	at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> 	at java.lang.ClassLoader.defineClass1(Native Method)
> 	at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
> 	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> 	at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
> 	at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> 	at org.richfaces.resource.ResourceFactoryImpl.creatappedResource(ResourceFactoryImpl.java:356)
> 	at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 03:00:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 03:00:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13377) NullPointerException in
 calendar page fragment
In-Reply-To: <JIRA.12525914.1385128343000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525914.1385128343000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525914.1385128343000.29355.1385366406387@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek reassigned RF-13377:
--------------------------------

    Assignee: Ji?? ?tefek  (was: Pavol Pitonak)

    
> NullPointerException in calendar page fragment
> ----------------------------------------------
>
>                 Key: RF-13377
>                 URL: https://issues.jboss.org/browse/RF-13377
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Ji?? ?tefek
>
> # run a Metamer test for r:calendar using page fragments, e.g.
> {code}
> mvn clean verify -P jbossas-managed-7-1 -Dtest=TestCalendarAttributes
> {code}
> result:
> * all tests are skipped because a NPE in calendar page fragment
> {quote}
> *org.jboss.arquillian.graphene.enricher.exception.PageFragmentInitializationException: java.lang.reflect.InvocationTargetException*
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:171)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.setupPageFragment(PageFragmentEnricher.java:208)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.enrich(PageFragmentEnricher.java:85)
> 	at org.jboss.arquillian.graphene.enricher.GrapheneEnricher.enrich(GrapheneEnricher.java:51)
> 	at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52)
> 	at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> 	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> 	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> 	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95)
> 	at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> 	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
> 	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
> 	at org.testng.internal.Invoker.invokeMethod(Invoker.java:613)
> 	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
> 	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
> 	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> 	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> 	at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
> 	at org.testng.TestRunner.privateRun(TestRunner.java:757)
> 	at org.testng.TestRunner.run(TestRunner.java:608)
> 	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> 	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> 	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> 	at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> 	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> 	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> 	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
> 	at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
> 	at org.testng.TestNG.run(TestNG.java:999)
> 	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:91)
> 	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:128)
> 	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:112)
> 	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> 	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> 	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> 	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> *Caused by: java.lang.reflect.InvocationTargetException*
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> 	at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.instantiate(AbstractSearchContextEnricher.java:174)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:144)
> 	... 76 more
> *Caused by: java.lang.NullPointerException: configuration is null - it needs to be setup before starting to use it*
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext.get(RichFacesPageFragmentsConfigurationContext.java:43)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$2.getTarget(RichFacesPageFragmentsConfigurationContext.java:97)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$1.invoke(RichFacesPageFragmentsConfigurationContext.java:57)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.intercept(GrapheneProxyHandler.java:92)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfiguration$$EnhancerByGraphene$$e41cfe31.isUseJSInteractionStrategy(<generated>)
> 	at org.richfaces.fragment.calendar.RichFacesCalendar.<init>(RichFacesCalendar.java:52)
> 	... 82 more
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 03:14:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 03:14:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.29367.1385367246019@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926414#comment-12926414 ] 

Ji?? ?tefek commented on RF-13365:
----------------------------------

[~lfryc], the Metamer sample is working with RF 4.3.x. 

Verified, that it works now with RF 5.

The delay between repeated subscription (time before the Push start to work again) is reported in [RF-12096|https://issues.jboss.org/browse/RF-12096].
                
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>              Labels: regression
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 04:09:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 04:09:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13377) NullPointerException in
 calendar page fragment
In-Reply-To: <JIRA.12525914.1385128343000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525914.1385128343000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525914.1385128343000.29419.1385370546105@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13377:
-----------------------------

    Assignee: Juraj H?ska  (was: Ji?? ?tefek)

    
> NullPointerException in calendar page fragment
> ----------------------------------------------
>
>                 Key: RF-13377
>                 URL: https://issues.jboss.org/browse/RF-13377
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Juraj H?ska
>
> # run a Metamer test for r:calendar using page fragments, e.g.
> {code}
> mvn clean verify -P jbossas-managed-7-1 -Dtest=TestCalendarAttributes
> {code}
> result:
> * all tests are skipped because a NPE in calendar page fragment
> {quote}
> *org.jboss.arquillian.graphene.enricher.exception.PageFragmentInitializationException: java.lang.reflect.InvocationTargetException*
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:171)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.setupPageFragment(PageFragmentEnricher.java:208)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.enrich(PageFragmentEnricher.java:85)
> 	at org.jboss.arquillian.graphene.enricher.GrapheneEnricher.enrich(GrapheneEnricher.java:51)
> 	at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52)
> 	at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> 	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> 	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> 	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95)
> 	at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> 	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
> 	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
> 	at org.testng.internal.Invoker.invokeMethod(Invoker.java:613)
> 	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
> 	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
> 	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> 	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> 	at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
> 	at org.testng.TestRunner.privateRun(TestRunner.java:757)
> 	at org.testng.TestRunner.run(TestRunner.java:608)
> 	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> 	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> 	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> 	at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> 	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> 	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> 	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
> 	at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
> 	at org.testng.TestNG.run(TestNG.java:999)
> 	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:91)
> 	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:128)
> 	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:112)
> 	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> 	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> 	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> 	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> *Caused by: java.lang.reflect.InvocationTargetException*
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> 	at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.instantiate(AbstractSearchContextEnricher.java:174)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:144)
> 	... 76 more
> *Caused by: java.lang.NullPointerException: configuration is null - it needs to be setup before starting to use it*
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext.get(RichFacesPageFragmentsConfigurationContext.java:43)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$2.getTarget(RichFacesPageFragmentsConfigurationContext.java:97)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$1.invoke(RichFacesPageFragmentsConfigurationContext.java:57)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.intercept(GrapheneProxyHandler.java:92)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfiguration$$EnhancerByGraphene$$e41cfe31.isUseJSInteractionStrategy(<generated>)
> 	at org.richfaces.fragment.calendar.RichFacesCalendar.<init>(RichFacesCalendar.java:52)
> 	... 82 more
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 04:55:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 04:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13377) NullPointerException in
 calendar page fragment
In-Reply-To: <JIRA.12525914.1385128343000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525914.1385128343000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525914.1385128343000.29547.1385373306071@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926430#comment-12926430 ] 

Juraj H?ska commented on RF-13377:
----------------------------------

I am linking the pull request which resolves this issue.

The problem was:
Some fragments need Page fragment configuration to be initialized. However, I removed support for it in [this|https://github.com/richfaces/richfaces/commit/d7b47deb404951e93ac8ea05ed5b4ac986b5ea1e] commit for page fragments.

I thought that it should not be Arquillian extension till RF-13343 is resolved. However, it should be, just the configuration from JSON should not be used. It did not work before, because {{META-INF/services/org...}} was not pointing correctly to the page fragments extension class.

In the pull request I am making the Page Fragments extension once again.
                
> NullPointerException in calendar page fragment
> ----------------------------------------------
>
>                 Key: RF-13377
>                 URL: https://issues.jboss.org/browse/RF-13377
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Juraj H?ska
>
> # run a Metamer test for r:calendar using page fragments, e.g.
> {code}
> mvn clean verify -P jbossas-managed-7-1 -Dtest=TestCalendarAttributes
> {code}
> result:
> * all tests are skipped because a NPE in calendar page fragment
> {quote}
> *org.jboss.arquillian.graphene.enricher.exception.PageFragmentInitializationException: java.lang.reflect.InvocationTargetException*
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:171)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.setupPageFragment(PageFragmentEnricher.java:208)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.enrich(PageFragmentEnricher.java:85)
> 	at org.jboss.arquillian.graphene.enricher.GrapheneEnricher.enrich(GrapheneEnricher.java:51)
> 	at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52)
> 	at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> 	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> 	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> 	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95)
> 	at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> 	at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525)
> 	at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
> 	at org.testng.internal.Invoker.invokeMethod(Invoker.java:613)
> 	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
> 	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
> 	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> 	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> 	at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
> 	at org.testng.TestRunner.privateRun(TestRunner.java:757)
> 	at org.testng.TestRunner.run(TestRunner.java:608)
> 	at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> 	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> 	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> 	at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> 	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> 	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> 	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
> 	at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
> 	at org.testng.TestNG.run(TestNG.java:999)
> 	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:91)
> 	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:128)
> 	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:112)
> 	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:113)
> 	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
> 	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
> 	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> *Caused by: java.lang.reflect.InvocationTargetException*
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> 	at org.jboss.arquillian.graphene.enricher.AbstractSearchContextEnricher.instantiate(AbstractSearchContextEnricher.java:174)
> 	at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:144)
> 	... 76 more
> *Caused by: java.lang.NullPointerException: configuration is null - it needs to be setup before starting to use it*
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext.get(RichFacesPageFragmentsConfigurationContext.java:43)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$2.getTarget(RichFacesPageFragmentsConfigurationContext.java:97)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfigurationContext$1.invoke(RichFacesPageFragmentsConfigurationContext.java:57)
> 	at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.intercept(GrapheneProxyHandler.java:92)
> 	at org.richfaces.fragment.configuration.RichFacesPageFragmentsConfiguration$$EnhancerByGraphene$$e41cfe31.isUseJSInteractionStrategy(<generated>)
> 	at org.richfaces.fragment.calendar.RichFacesCalendar.<init>(RichFacesCalendar.java:52)
> 	... 82 more
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 04:57:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 04:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.29572.1385373426268@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926432#comment-12926432 ] 

Juraj H?ska commented on RF-13343:
----------------------------------

[~lfryc], [~bleathem], [~ppitonak]
Do you think guys that those page fragments methods which depend on JSON parsing - aka various {{setupFromWidget}} should throw {{UnsupportedOperationException}} till this issue is resolved ?

IMHO not, as we can quite quickly implement this, right ?
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 05:03:05 2013
From: jira-events at lists.jboss.org (David Rawlings (JIRA))
Date: Mon, 25 Nov 2013 05:03:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12533) UIDataAdaptor throws NPE
 with disabled PSS (webflow 2.3)
In-Reply-To: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12476684.1349966061000.29583.1385373785937@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926435#comment-12926435 ] 

David Rawlings commented on RF-12533:
-------------------------------------

Created SWF-1612 webflow JIRA...

https://jira.springsource.org/browse/SWF-1612
                
> UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
> --------------------------------------------------------
>
>                 Key: RF-12533
>                 URL: https://issues.jboss.org/browse/RF-12533
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.2.2.Final, 4.2.3.CR1, 4.3.0.M1
>         Environment: spring webflow 2.3.1, myfaces-impl 2.1.8
>            Reporter: Anton Zukovskij
>            Priority: Critical
>              Labels: partial_state_saving, spring
>             Fix For: 5-Tracking
>
>         Attachments: log-2.txt, log.txt, swf-rf4.zip, TreeStructureManager.java
>
>
> When partial state saving is disabled(javax.faces.PARTIAL_STATE_SAVING=false), nullpointer exception is thrown during restore state phase of webflow rendered view that contains UIDataAdaptor component. In other words NPE exception is thrown on every page submit of webflow rendered views that contain components that exted UIDataAdaptor. Please see log attached and sample application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 25 05:07:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 25 Nov 2013 05:07:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13252) a4j:ajax includes jsf.js
	script twice
In-Reply-To: <JIRA.12502662.1381395391000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502662.1381395391000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502662.1381395391000.29599.1385374026328@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926437#comment-12926437 ] 

Pavol Pitonak commented on RF-13252:
------------------------------------

The workaround seems to work.
                
> a4j:ajax includes jsf.js script twice
> -------------------------------------
>
>                 Key: RF-13252
>                 URL: https://issues.jboss.org/browse/RF-13252
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 4.3.4
>            Reporter: Jon?? Trantina
>             Fix For: 4.3.5
>
>         Attachments: reproducer.zip
>
>
> When a4j:script is used in the page like so:
> {noformat}
> <h:commandLink value="Click me ">
>     <a4j:ajax event="click" render="@form"/>
> </h:commandLink>
> {noformat}
> Then two script tags pointing to jsf.js are added to the page, once in the head by the inclusion of @ResourceDependency [1], and once again by Overriding the ClientBehaviorRenderer#getScript method [2,3].
> Note, that according to Brian, resolving this without introducing any functional regressions may require the resolution of RF-12270 [4].
> [1] https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/ajax/ajax/AjaxBehaviorRenderer.java#L53
> [2] https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/ajax/ajax/AjaxBehaviorRenderer.java#L123
> [3] https://github.com/jboss/mojarra/blob/2.1.21-jbossorg-1/jsf-api/src/main/java/javax/faces/render/ClientBehaviorRenderer.java#L95
> [4] https://issues.jboss.org/browse/RF-12270

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 05:33:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 05:33:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.29644.1385375585944@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926445#comment-12926445 ] 

Luk?? Fry? commented on RF-13343:
---------------------------------

[~jhuska], let's go ahead and implement it.

As I understand it, It's nothing we rely on, particularly in Alpha2 release.
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 06:11:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 25 Nov 2013 06:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13380) Error 404 not found for
	fonts
In-Reply-To: <JIRA.12526026.1385377814116@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526026.1385377814116@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526026.1385377814116.29770.1385377866368@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13380:
----------------------------------

             Summary: Error 404 not found for fonts
                 Key: RF-13380
                 URL: https://issues.jboss.org/browse/RF-13380
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: base functionality
    Affects Versions: 5.0.0.Alpha2
         Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
            Reporter: Pavol Pitonak
            Priority: Critical


# deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
# see browser console

result:
* several resources are missing
* Chrome console contains these errors:
{quote}
GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
{quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 25 06:15:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 25 Nov 2013 06:15:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13380) Error 404 not found for
	fonts
In-Reply-To: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526026.1385377814000.29779.1385378106897@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13380:
-------------------------------

    Description: 
# deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
# see browser console

result:
* several resources are missing
* Chrome console contains these errors:
{quote}
GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
{quote}
* when deployed to JBoss AS 7.1.1.Final, you can see these warnings in server log
{quote}
12:12:53,342 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
12:12:53,341 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
12:12:53,392 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
12:12:53,393 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
{quote}

  was:
# deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
# see browser console

result:
* several resources are missing
* Chrome console contains these errors:
{quote}
GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
{quote}


    
> Error 404 not found for fonts
> -----------------------------
>
>                 Key: RF-13380
>                 URL: https://issues.jboss.org/browse/RF-13380
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: base functionality
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Critical
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
> # see browser console
> result:
> * several resources are missing
> * Chrome console contains these errors:
> {quote}
> GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
> {quote}
> * when deployed to JBoss AS 7.1.1.Final, you can see these warnings in server log
> {quote}
> 12:12:53,342 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,341 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,392 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,393 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 25 06:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 06:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.29783.1385378226299@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926458#comment-12926458 ] 

Juraj H?ska commented on RF-13343:
----------------------------------

Sorry I was not clear enough.

I think that we do not have to throw {{UnsuportedOperationException}}, because it would be not worth work for Alpha2, as we can easily implement this issue (and then again remove those throws).

Do you agree ?
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 07:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 07:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.29890.1385381826376@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926471#comment-12926471 ] 

Luk?? Fry? commented on RF-13343:
---------------------------------

Hey Juraj, you was pretty clear and my answer is: agree, let's try to fit this to Alpha2 release.
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 07:19:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 25 Nov 2013 07:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13372) togglePanel does not
 work with toggleControl
In-Reply-To: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525839.1385047782000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525839.1385047782000.29898.1385381946220@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13372.
------------------------------



Verified
                
> togglePanel does not work with toggleControl
> --------------------------------------------
>
>                 Key: RF-13372
>                 URL: https://issues.jboss.org/browse/RF-13372
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: GlassFish 3.1.2.2, AS 7.1.1
>            Reporter: Ji?? ?tefek
>            Priority: Blocker
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 07:19:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 25 Nov 2013 07:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13373) The toggle control
	renderer is not invoked
In-Reply-To: <JIRA.12525880.1385067960000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525880.1385067960000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525880.1385067960000.29901.1385381946348@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13373.
------------------------------



Verified
                
> The toggle control renderer is not invoked
> ------------------------------------------
>
>                 Key: RF-13373
>                 URL: https://issues.jboss.org/browse/RF-13373
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Brian Leathem
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> The toggle control broke because the value returned by the [ToggleControl#getRendererType|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/toggle/toggleControl/ToggleControl.java#L145] method does not match the renderer defined in the [@JsfBehavior annotation|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/toggle/toggleControl/ToggleControl.java#L48].
> This descrepency was introduced with this commit: [42fc56|https://github.com/richfaces/richfaces/commit/42fc5626a02a1826e29ce8980aba18152a2bca19]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 25 07:25:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 07:25:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13380) Error 404 not found for
	fonts
In-Reply-To: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526026.1385377814000.29912.1385382305891@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13380:
----------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Error 404 not found for fonts
> -----------------------------
>
>                 Key: RF-13380
>                 URL: https://issues.jboss.org/browse/RF-13380
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: base functionality
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
> # see browser console
> result:
> * several resources are missing
> * Chrome console contains these errors:
> {quote}
> GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
> {quote}
> * when deployed to JBoss AS 7.1.1.Final, you can see these warnings in server log
> {quote}
> 12:12:53,342 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,341 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,392 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,393 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 07:25:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 07:25:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13380) Error 404 not found for
	fonts
In-Reply-To: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526026.1385377814000.29915.1385382306104@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13380:
-------------------------------

    Assignee: Luk?? Fry?

    
> Error 404 not found for fonts
> -----------------------------
>
>                 Key: RF-13380
>                 URL: https://issues.jboss.org/browse/RF-13380
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: base functionality
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
> # see browser console
> result:
> * several resources are missing
> * Chrome console contains these errors:
> {quote}
> GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
> {quote}
> * when deployed to JBoss AS 7.1.1.Final, you can see these warnings in server log
> {quote}
> 12:12:53,342 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,341 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,392 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,393 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 07:39:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 25 Nov 2013 07:39:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13381) Hotkey doesn't work with
	picklist
In-Reply-To: <JIRA.12526035.1385383078284@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526035.1385383078284@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526035.1385383078284.29948.1385383145854@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13381:
----------------------------------

             Summary: Hotkey doesn't work with picklist
                 Key: RF-13381
                 URL: https://issues.jboss.org/browse/RF-13381
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-misc, component-selects, regression
    Affects Versions: 5.0.0.Alpha2
         Environment: Showcase 5.0.0-SNAPSHOT
            Reporter: Pavol Pitonak


# open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
# click on first item in "Available cities" list
# press right arrow key on keyboard
# press End button on keyboard

result:
* nothing happens

expected:
* selected item moves to to righ list after pressing right arrow
* all items from left list should move to the right after pressing End button

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 25 07:53:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 25 Nov 2013 07:53:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13359) Showcase: several
	components don't work
In-Reply-To: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525552.1384864466000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525552.1384864466000.29974.1385383986709@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13359.
------------------------------



Verified. All components but hotkey work fine, I created a new issue for hotkey RF-13381
                
> Showcase: several components don't work
> ---------------------------------------
>
>                 Key: RF-13359
>                 URL: https://issues.jboss.org/browse/RF-13359
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> # deploy Showcase and open http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=progressBar&skin=blueSky
> # open browser console
> # click on "Start Process" button
> result:
> * this message appears in browser console 
> {quote}
> event.returnValue is deprecated. Please use the standard event.preventDefault() instead. 
> {quote}
> * progress bar is rendered wrongly
> * the same message is displayed on these pages (and these components are broken too)
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=togglePanel&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=tabPanel&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=accordion&sample=dynamic&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=panelMenu&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=dragDrop&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> ** http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=focus&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 25 08:15:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 08:15:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13380) Error 404 not found for
	fonts
In-Reply-To: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526026.1385377814000.30003.1385385307066@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926487#comment-12926487 ] 

Luk?? Fry? commented on RF-13380:
---------------------------------

Upstream issue: https://github.com/richwidgets/richwidgets/issues/143
                
> Error 404 not found for fonts
> -----------------------------
>
>                 Key: RF-13380
>                 URL: https://issues.jboss.org/browse/RF-13380
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: base functionality
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
> # see browser console
> result:
> * several resources are missing
> * Chrome console contains these errors:
> {quote}
> GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
> {quote}
> * when deployed to JBoss AS 7.1.1.Final, you can see these warnings in server log
> {quote}
> 12:12:53,342 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,341 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,392 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,393 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 08:50:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 08:50:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13380) Error 404 not found for
	fonts
In-Reply-To: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526026.1385377814000.30112.1385387406368@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13380.
-----------------------------

    Resolution: Done

    
> Error 404 not found for fonts
> -----------------------------
>
>                 Key: RF-13380
>                 URL: https://issues.jboss.org/browse/RF-13380
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: base functionality
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
> # see browser console
> result:
> * several resources are missing
> * Chrome console contains these errors:
> {quote}
> GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
> {quote}
> * when deployed to JBoss AS 7.1.1.Final, you can see these warnings in server log
> {quote}
> 12:12:53,342 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,341 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,392 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,393 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 08:54:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 08:54:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.30149.1385387647372@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926508#comment-12926508 ] 

Juraj H?ska edited comment on RF-13348 at 11/25/13 8:53 AM:
------------------------------------------------------------

I am reopening the issue, because it is not behaving as the doc describes.

IMHO it is a bug and that the doc is correct.

It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns

* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column

Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout.xhtml
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.

My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be applied to the columns greater than the number of classes. If however the final class in the list is the `*` character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order the class in this list.

It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?
                
      was (Author: jhuska):
    I am reopening the issue, because it is not behaving as the doc describes.

IMHO it is a bug and that the doc is correct.

It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns

* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column

Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout.xhtml
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.

My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be
applied to the columns greater than the number of classes. If however the final class in the list is the `*`
character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order
the class in this list.

It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?
                  
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 08:54:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 08:54:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.30144.1385387647159@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska reopened RF-13348:
------------------------------



I am reopening the issue, because it is not behaving as the doc describes.

IMHO it is a bug and that the doc is correct.

It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns

* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column

Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout.xhtml
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.

My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be
applied to the columns greater than the number of classes. If however the final class in the list is the `*`
character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order
the class in this list.

It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?
                
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 08:58:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 08:58:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.30154.1385387885859@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926508#comment-12926508 ] 

Juraj H?ska edited comment on RF-13348 at 11/25/13 8:56 AM:
------------------------------------------------------------

I am reopening the issue, because it is not behaving as the doc describes.

IMHO it is a bug and that the doc is correct.

It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns

* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column

Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout.xhtml
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.

My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be applied to the columns greater than the number of classes. If however the final class in the list is the `*` character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order the class in this list.

It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?

Also if you can confirm it I can reopen [the upstream change|https://github.com/richwidgets/richwidgets/commit/1fc6d73b1a78669dce4b354ca02afd234d12ee9e] which is behind it.
                
      was (Author: jhuska):
    I am reopening the issue, because it is not behaving as the doc describes.

IMHO it is a bug and that the doc is correct.

It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns

* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column

Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout.xhtml
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.

My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be applied to the columns greater than the number of classes. If however the final class in the list is the `*` character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order the class in this list.

It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?
                  
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 09:06:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 09:06:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13325) pickList:
 onmouseout/onmouseover is triggered even when pointer button is not moved
 out/over element
In-Reply-To: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524571.1383904100000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524571.1383904100000.30170.1385388366295@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13325.
----------------------------


    
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RF-13325
>                 URL: https://issues.jboss.org/browse/RF-13325
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 09:08:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 09:08:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13326) pickList - caption
 attribute is not rendered in to its faces-config
In-Reply-To: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524612.1383916208000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524612.1383916208000.30178.1385388486218@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13326.
----------------------------



Verified. Closing
                
> pickList - caption attribute is not rendered in to its faces-config
> -------------------------------------------------------------------
>
>                 Key: RF-13326
>                 URL: https://issues.jboss.org/browse/RF-13326
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> There should be attribute {{caption}} in the {{pickList}} faces-config. It is not.
> The attribute is defined in [AbstractOrderingList|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/orderingList/AbstractOrderingList.java], which is the ancestor of {{AbstractPickList}}.
> Is it caused because {{orderingList}} has also that attribute and it is somehow overriden as {{pickList}} consists from {{orderingLists}} ? - bit weird
> Note that {{orderingList}} has generated {{caption}} attribute.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 09:08:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 09:08:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13327) pickList - setting of
 multiple attributes does not have any effect on the component
In-Reply-To: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524615.1383916680000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524615.1383916680000.30182.1385388486452@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13327.
----------------------------



Verified. Closing.
                
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
>                 Key: RF-13327
>                 URL: https://issues.jboss.org/browse/RF-13327
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pickList.template.xml] ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 09:10:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 09:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13344) pickList - maxListHeight
 & minListHeight need to have set units along with number to work
In-Reply-To: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525076.1384420028000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525076.1384420028000.30188.1385388606000@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13344.
----------------------------



Verified. Closing.
                
> pickList - maxListHeight & minListHeight need to have set units along with number to work
> -----------------------------------------------------------------------------------------
>
>                 Key: RF-13344
>                 URL: https://issues.jboss.org/browse/RF-13344
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 09:10:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 09:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13347) pickList:
	switchByDblClick does not work
In-Reply-To: <JIRA.12525090.1384426336000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525090.1384426336000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525090.1384426336000.30196.1385388606362@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13347.
----------------------------



Verified. Closing.
                
> pickList: switchByDblClick does not work
> ----------------------------------------
>
>                 Key: RF-13347
>                 URL: https://issues.jboss.org/browse/RF-13347
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> Setting of {{pickList}} attribute {{switchByDblClick}} to {{true}} does not work.
> Note that {{switchByClick}} works as expected.
> It seems that attribute is set in render template. I can not found any mention in pick list bridge if that can be the case ? (there is no mention of {{switchByClick}} neither and it works).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 09:12:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 09:12:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13350) pickList: styleClass
 attribute is rendered wrongly as styleclass instead of class attribute
In-Reply-To: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525335.1384534676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525335.1384534676000.30198.1385388725848@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13350.
----------------------------



Verified. Closing.
                
> pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute
> -------------------------------------------------------------------------------------------
>
>                 Key: RF-13350
>                 URL: https://issues.jboss.org/browse/RF-13350
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute.
> The {{styleClass}} is included just in {{passThrough}}  attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/select/pickList/pick-list.template.xml#L65].
> Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/input/autocomplete/autocomplete.template.xml#L33-34] in autocomplate render base ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 09:14:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Mon, 25 Nov 2013 09:14:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13329) Delete old 4.x and below
 pickList and orderingList resources from RF5
In-Reply-To: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524633.1383925284000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524633.1383925284000.30205.1385388845853@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13329.
----------------------------



Verified. Closing.
                
> Delete old 4.x and below pickList and orderingList resources from RF5
> ---------------------------------------------------------------------
>
>                 Key: RF-13329
>                 URL: https://issues.jboss.org/browse/RF-13329
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Now it should be safe to delete the old resources for {{pickList}} and {{orderingList}}.
> I mean {{.js}} and {{.ecss}} files from this folder:
> https://github.com/richfaces/richfaces/tree/master/framework/src/main/resources/META-INF/resources/org.richfaces/select

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 09:33:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Mon, 25 Nov 2013 09:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13380) Error 404 not found for
	fonts
In-Reply-To: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526026.1385377814000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526026.1385377814000.30263.1385389986113@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13380.
------------------------------



Verified
                
> Error 404 not found for fonts
> -----------------------------
>
>                 Key: RF-13380
>                 URL: https://issues.jboss.org/browse/RF-13380
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: base functionality
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
> # see browser console
> result:
> * several resources are missing
> * Chrome console contains these errors:
> {quote}
> GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.woff 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
> {quote}
> * when deployed to JBoss AS 7.1.1.Final, you can see these warnings in server log
> {quote}
> 12:12:53,342 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,341 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.woff.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,392 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,393 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.ttf.  To resolve this, add a mime-type mapping to the applications web.xml.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 13:33:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 25 Nov 2013 13:33:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12533) UIDataAdaptor throws NPE
 with disabled PSS (webflow 2.3)
In-Reply-To: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12476684.1349966061000.31577.1385404385946@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-12533:
-------------------------------

    Labels: partial_state_saving spring upstream  (was: partial_state_saving spring)

    
> UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
> --------------------------------------------------------
>
>                 Key: RF-12533
>                 URL: https://issues.jboss.org/browse/RF-12533
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.2.2.Final, 4.2.3.CR1, 4.3.0.M1
>         Environment: spring webflow 2.3.1, myfaces-impl 2.1.8
>            Reporter: Anton Zukovskij
>            Priority: Critical
>              Labels: partial_state_saving, spring, upstream
>             Fix For: 5-Tracking
>
>         Attachments: log-2.txt, log.txt, swf-rf4.zip, TreeStructureManager.java
>
>
> When partial state saving is disabled(javax.faces.PARTIAL_STATE_SAVING=false), nullpointer exception is thrown during restore state phase of webflow rendered view that contains UIDataAdaptor component. In other words NPE exception is thrown on every page submit of webflow rendered views that contain components that exted UIDataAdaptor. Please see log attached and sample application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 25 13:35:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 25 Nov 2013 13:35:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12533) UIDataAdaptor throws NPE
 with disabled PSS (webflow 2.3)
In-Reply-To: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12476684.1349966061000.31581.1385404506520@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-12533:
-------------------------------

    Component/s: third-party

    
> UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
> --------------------------------------------------------
>
>                 Key: RF-12533
>                 URL: https://issues.jboss.org/browse/RF-12533
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables, third-party
>    Affects Versions: 4.2.2.Final, 4.2.3.CR1, 4.3.0.M1
>         Environment: spring webflow 2.3.1, myfaces-impl 2.1.8
>            Reporter: Anton Zukovskij
>            Priority: Critical
>              Labels: partial_state_saving, spring, upstream
>             Fix For: 5-Tracking
>
>         Attachments: log-2.txt, log.txt, swf-rf4.zip, TreeStructureManager.java
>
>
> When partial state saving is disabled(javax.faces.PARTIAL_STATE_SAVING=false), nullpointer exception is thrown during restore state phase of webflow rendered view that contains UIDataAdaptor component. In other words NPE exception is thrown on every page submit of webflow rendered views that contain components that exted UIDataAdaptor. Please see log attached and sample application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 25 13:35:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 25 Nov 2013 13:35:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12533) UIDataAdaptor throws NPE
 with disabled PSS (webflow 2.3)
In-Reply-To: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12476684.1349966061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12476684.1349966061000.31585.1385404506735@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926596#comment-12926596 ] 

Brian Leathem commented on RF-12533:
------------------------------------

Thanks [~rawlingsd]
                
> UIDataAdaptor throws NPE with disabled PSS (webflow 2.3)
> --------------------------------------------------------
>
>                 Key: RF-12533
>                 URL: https://issues.jboss.org/browse/RF-12533
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables, third-party
>    Affects Versions: 4.2.2.Final, 4.2.3.CR1, 4.3.0.M1
>         Environment: spring webflow 2.3.1, myfaces-impl 2.1.8
>            Reporter: Anton Zukovskij
>            Priority: Critical
>              Labels: partial_state_saving, spring, upstream
>             Fix For: 5-Tracking
>
>         Attachments: log-2.txt, log.txt, swf-rf4.zip, TreeStructureManager.java
>
>
> When partial state saving is disabled(javax.faces.PARTIAL_STATE_SAVING=false), nullpointer exception is thrown during restore state phase of webflow rendered view that contains UIDataAdaptor component. In other words NPE exception is thrown on every page submit of webflow rendered views that contain components that exted UIDataAdaptor. Please see log attached and sample application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 25 13:47:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 25 Nov 2013 13:47:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.31606.1385405226436@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13343:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 13:47:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 25 Nov 2013 13:47:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.31607.1385405226484@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926601#comment-12926601 ] 

Brian Leathem commented on RF-13343:
------------------------------------

+1 Let's include this in 5.0.0.Alpha2, time permitting.
                
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments, qe
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 13:59:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 25 Nov 2013 13:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.31626.1385405946345@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926605#comment-12926605 ] 

Brian Leathem commented on RF-13348:
------------------------------------

[~jhuska] I think you are not interpreting the docs as intended:

{quote}
When table layout is used, _columnClasses_ specifies a comma-delimited list of CSS style classes to apply to each column. A space separated list of classes may be specified for an individual column.
{quote}

What is meant by this is that the comma character is the column delimeter, and the space character spearates multiple classes to be applied to a single column in the iteration over the columns.

Let me demonstrate with an example:
{code}
columnClasses = class1, class2a class2b, class3, *
{code}

Then I expect a table with 5 columns to have the following classes:

|| column || CSS class ||
| column 1 | class1 |
| column 2 | class2a class2b |
| column 3 | class3 |
| column 4 | class1 |
| column 5 | class2a class2b |

This behavior is confirmed with the richwidget tests:
https://github.com/richwidgets/richwidgets/blob/master/test/widgets/select/ordering-list/ordering-list-options.js#L445
https://github.com/richwidgets/richwidgets/blob/master/test/widgets/select/ordering-list/ordering-list-options.js#L500

If you feel the docs are still unclear, please open a new issue addressing the documentation of the _columnClasses_ attribute.
                
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 13:59:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 25 Nov 2013 13:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.31629.1385405946512@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13348.
--------------------------------

    Resolution: Done

    
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Mon Nov 25 14:23:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 25 Nov 2013 14:23:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13381) Hotkey doesn't work with
	picklist
In-Reply-To: <JIRA.12526035.1385383078000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526035.1385383078000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526035.1385383078000.31659.1385407386272@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926608#comment-12926608 ] 

Brian Leathem commented on RF-13381:
------------------------------------

This is rather an issue that _r:componentControl_ doesn't work with pickList.
                
> Hotkey doesn't work with picklist
> ---------------------------------
>
>                 Key: RF-13381
>                 URL: https://issues.jboss.org/browse/RF-13381
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-misc, component-selects, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> # click on first item in "Available cities" list
> # press right arrow key on keyboard
> # press End button on keyboard
> result:
> * nothing happens
> expected:
> * selected item moves to to righ list after pressing right arrow
> * all items from left list should move to the right after pressing End button

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Mon Nov 25 15:35:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Mon, 25 Nov 2013 15:35:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13379) Build on Travis fails
 due to NoClassDefFoundEx.: javax/servlet/Servlet (during framework resource
 optimization)
In-Reply-To: <JIRA.12525985.1385281263000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525985.1385281263000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525985.1385281263000.31711.1385411706316@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13379:
-------------------------------

    Fix Version/s: 5.0.0.Alpha3

    
> Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet (during framework resource optimization)
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13379
>                 URL: https://issues.jboss.org/browse/RF-13379
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: resource handling
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha3
>
>
> https://travis-ci.org/richfaces/richfaces/builds/14381706
> {code}
> [INFO] <<< exec-maven-plugin:1.2.1:java (static-resources) @ richfaces <<<
> [INFO] 
> [INFO] --- exec-maven-plugin:1.2.1:java (static-resources) @ richfaces ---
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> Nov 24, 2013 8:04:06 AM org.richfaces.resource.optimizer.ResourceGenerator execute
> SEVERE: null
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> 	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 	at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> 	at org.richfaces.resource.optimizer.ResourceGenerator.execute(ResourceGenerator.java:437)
> 	at org.richfaces.resource.optimizer.GenerateResourcesMain.main(GenerateResourcesMain.java:39)
> 	at sun.reflect.NativethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativethodAccessorImpl.invoke(NativethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> 	at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> 	at java.lang.ClassLoader.defineClass1(Native Method)
> 	at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
> 	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> 	at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
> 	at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> 	at org.richfaces.resource.ResourceFactoryImpl.creatappedResource(ResourceFactoryImpl.java:356)
> 	at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 02:19:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 02:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13381) ComponentControl doesn't
	work with picklist
In-Reply-To: <JIRA.12526035.1385383078000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526035.1385383078000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526035.1385383078000.31865.1385450345836@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13381:
-------------------------------

    Summary: ComponentControl doesn't work with picklist  (was: Hotkey doesn't work with picklist)

    
> ComponentControl doesn't work with picklist
> -------------------------------------------
>
>                 Key: RF-13381
>                 URL: https://issues.jboss.org/browse/RF-13381
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-misc, component-selects, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> # click on first item in "Available cities" list
> # press right arrow key on keyboard
> # press End button on keyboard
> result:
> * nothing happens
> expected:
> * selected item moves to to righ list after pressing right arrow
> * all items from left list should move to the right after pressing End button

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 02:19:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 02:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13381) ComponentControl doesn't
	work with picklist
In-Reply-To: <JIRA.12526035.1385383078000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526035.1385383078000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526035.1385383078000.31867.1385450345908@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13381.
--------------------------------

         Assignee: Brian Leathem
    Fix Version/s: 5.0.0.Alpha2
       Resolution: Done

    
> ComponentControl doesn't work with picklist
> -------------------------------------------
>
>                 Key: RF-13381
>                 URL: https://issues.jboss.org/browse/RF-13381
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-misc, component-selects, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> # click on first item in "Available cities" list
> # press right arrow key on keyboard
> # press End button on keyboard
> result:
> * nothing happens
> expected:
> * selected item moves to to righ list after pressing right arrow
> * all items from left list should move to the right after pressing End button

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 02:19:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 02:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13381) ComponentControl doesn't
	work with picklist
In-Reply-To: <JIRA.12526035.1385383078000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526035.1385383078000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526035.1385383078000.31869.1385450346016@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13381:
-------------------------------

    Labels: needs-qe  (was: )

    
> ComponentControl doesn't work with picklist
> -------------------------------------------
>
>                 Key: RF-13381
>                 URL: https://issues.jboss.org/browse/RF-13381
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-misc, component-selects, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>              Labels: needs-qe
>             Fix For: 5.0.0.Alpha2
>
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> # click on first item in "Available cities" list
> # press right arrow key on keyboard
> # press End button on keyboard
> result:
> * nothing happens
> expected:
> * selected item moves to to righ list after pressing right arrow
> * all items from left list should move to the right after pressing End button

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 03:51:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 03:51:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13348) pickList - columnClass
 attribute behaves differently than in RF4
In-Reply-To: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525097.1384431019000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525097.1384431019000.31950.1385455867049@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13348.
----------------------------



Thank you for explaining. It was rather my misunderstanding, docs seems to be clear now.

Verified. Closing.
                
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
>                 Key: RF-13348
>                 URL: https://issues.jboss.org/browse/RF-13348
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 04:11:07 2013
From: jira-events at lists.jboss.org (Gabriele Gervasi (JIRA))
Date: Tue, 26 Nov 2013 04:11:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13382) rich:select realign
 options list on window resize
In-Reply-To: <JIRA.12526119.1385457002719@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526119.1385457002719@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526119.1385457002719.31971.1385457067446@jira02.app.mwc.hst.phx2.redhat.com>

Gabriele Gervasi created RF-13382:
-------------------------------------

             Summary: rich:select realign options list on window resize
                 Key: RF-13382
                 URL: https://issues.jboss.org/browse/RF-13382
             Project: RichFaces
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 4.3.4
            Reporter: Gabriele Gervasi
            Priority: Optional


I'm currently developing a web application and i notice that rich:select options   doesn't follow rich:select input on window resize. If it's possible to change this  behaviour it will be really apprentice. I temporarily simply solved hiding on window resize.
<script>
            window.onresize = function(event) {
                document.activeElement.blur();
            }
</script>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 04:13:06 2013
From: jira-events at lists.jboss.org (Gabriele Gervasi (JIRA))
Date: Tue, 26 Nov 2013 04:13:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13382) rich:select realign
 options list on window resize
In-Reply-To: <JIRA.12526119.1385457002000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526119.1385457002000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526119.1385457002000.31982.1385457186014@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriele Gervasi updated RF-13382:
----------------------------------

    Attachment: Schermata 2013-11-25 alle 18.51.03.png
                Schermata 2013-11-25 alle 18.51.30.png

    
> rich:select realign options list on window resize
> -------------------------------------------------
>
>                 Key: RF-13382
>                 URL: https://issues.jboss.org/browse/RF-13382
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 4.3.4
>            Reporter: Gabriele Gervasi
>            Priority: Optional
>         Attachments: Schermata 2013-11-25 alle 18.51.03.png, Schermata 2013-11-25 alle 18.51.30.png
>
>
> I'm currently developing a web application and i notice that rich:select options   doesn't follow rich:select input on window resize. If it's possible to change this  behaviour it will be really apprentice. I temporarily simply solved hiding on window resize.
> <script>
>             window.onresize = function(event) {
>                 document.activeElement.blur();
>             }
> </script>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 05:38:05 2013
From: jira-events at lists.jboss.org (RH Bugzilla Integration (JIRA))
Date: Tue, 26 Nov 2013 05:38:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13154) Upgrade Atmosphere to
 1.0.17 (a4j:push fails with CNFE for
 org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6)
In-Reply-To: <JIRA.12499404.1377547327000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12499404.1377547327000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12499404.1377547327000.32248.1385462285940@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926691#comment-12926691 ] 

RH Bugzilla Integration commented on RF-13154:
----------------------------------------------

Boleslaw Dawidowicz <bdawidow at redhat.com> changed the Status of [bug 1002971|https://bugzilla.redhat.com/show_bug.cgi?id=1002971] from MODIFIED to ON_QA
                
> Upgrade Atmosphere to 1.0.17 (a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6)
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13154
>                 URL: https://issues.jboss.org/browse/RF-13154
>             Project: RichFaces
>          Issue Type: Component  Upgrade
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.3.3
>         Environment: EAP 6.1.1.ER7
>            Reporter: Ken Finnigan
>            Assignee: Brian Leathem
>             Fix For: 4.3.4
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> When accessing a4j:push example in showcase on EAP 6.1.1.ER7 the network tab of the developer console in Chrome shows failed network attempts for richfaces push and the following exception in the server logs:
> {code}
> 15:21:29,295 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[AutoRegisteredPushServlet]] (http-/127.0.0.1:8080-2) JBWEB000236: Servlet.service() for servlet AutoRegisteredPushServlet threw exception: java.lang.ClassNotFoundException: org.apache.coyote.http11.upgrade.UpgradeInbound from [Module "deployment.richfaces-showcase-4.3.3.Final-jbas71.war:main" from Service Module Loader]
> 	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.2.Final-redhat-1]
> 	at org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279) [atmosphere-runtime-1.0.10.jar:1.0.10]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> 	at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {code}
> Running the exact same showcase example war on EAP 6.1.0.GA works fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 07:01:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 26 Nov 2013 07:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13381) ComponentControl doesn't
	work with picklist
In-Reply-To: <JIRA.12526035.1385383078000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526035.1385383078000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526035.1385383078000.32461.1385467266418@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13381.
------------------------------



Verified.
                
> ComponentControl doesn't work with picklist
> -------------------------------------------
>
>                 Key: RF-13381
>                 URL: https://issues.jboss.org/browse/RF-13381
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-misc, component-selects, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: Showcase 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Brian Leathem
>              Labels: needs-qe
>             Fix For: 5.0.0.Alpha2
>
>
> # open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=hotKey&skin=blueSky
> # click on first item in "Available cities" list
> # press right arrow key on keyboard
> # press End button on keyboard
> result:
> * nothing happens
> expected:
> * selected item moves to to righ list after pressing right arrow
> * all items from left list should move to the right after pressing End button

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 07:21:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 07:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side
In-Reply-To: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525807.1385035920000.32504.1385468465833@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926723#comment-12926723 ] 

Luk?? Macko commented on RF-13370:
----------------------------------

Three of them can be part of Alpha2. The last one will probably take some time, I expect Alpha 3.
                
> Charts - server-side
> --------------------
>
>                 Key: RF-13370
>                 URL: https://issues.jboss.org/browse/RF-13370
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>
> * rename attribute *clickListener* in chart and series tag to *plotClickListner*
> * send request to server only if a server-side listener is attached 
> * particular series server-side listeners (called only for particular series events)
> * server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 07:27:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 07:27:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13178) RichFaces CDI Push fails
 with NoSuchElementException in OWB
In-Reply-To: <JIRA.12500327.1378747327000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500327.1378747327000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500327.1378747327000.32528.1385468825911@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926725#comment-12926725 ] 

Luk?? Fry? commented on RF-13178:
---------------------------------

This issue may be resolved by leveraging event handling improvements in CDI, see RF-11455.
                
> RichFaces CDI Push fails with NoSuchElementException in OWB
> -----------------------------------------------------------
>
>                 Key: RF-13178
>                 URL: https://issues.jboss.org/browse/RF-13178
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 4.3.3
>         Environment: Tomee 1.5.2 (Apache Tomcat (TomEE)/7.0.37))
>            Reporter: Brian Leathem
>              Labels: cdi, cdi11, owb
>             Fix For: 5.0.0.Alpha3
>
>
> RichFaces push fails with a NoSuchElementException:
> {code}
> SEVERE: Servlet.service() for servlet [FacesServlet] in context with path [] threw exception [javax.el.ELException: java.util.NoSuchElementException] with root cause
> java.util.NoSuchElementException
>         at java.util.HashMap$HashIterator.nextEntry(HashMap.java:897)
>         at java.util.HashMap$KeyIterator.next(HashMap.java:928)
>         at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.getBeanReference(PushCDIExtension.java:172)
>         at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:140)
>         at org.apache.webbeans.event.NotificationManager.fireEvent(NotificationManager.java:429)
>         at org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:484)
>         at org.apache.webbeans.event.EventImpl.fire(EventImpl.java:75)
>         at ca.bleathem.sample.PushCdiBean.sendMessage(PushCdiBean.java:31)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
>         at org.apache.webbeans.intercept.InterceptorHandler.invoke(InterceptorHandler.java:322)
>         at org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:117)
>         at org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:108)
>         at ca.bleathem.sample.PushCdiBean_$$_javassist_2.sendMessage(PushCdiBean_$$_javassist_2.java)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
>         at org.apache.el.parser.AstValue.invoke(AstValue.java:278)
>         at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:274)
>         at org.apache.myfaces.view.facelets.el.ContextAwareTagMethodExpression.invoke(ContextAwareTagMethodExpression.java:96)
>         at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:68)
>         at javax.faces.component.UICommand.broadcast(UICommand.java:120)
>         at javax.faces.component.UIViewRoot._broadcastAll(UIViewRoot.java:1028)
>         at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:286)
>         at javax.faces.component.UIViewRoot._process(UIViewRoot.java:1375)
>         at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
>         at org.apache.myfaces.lifecycle.InvokeApplicationExecutor.execute(InvokeApplicationExecutor.java:38)
>         at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:170)
>         at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
>         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>         at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>         at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>         at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>         at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:722)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 07:27:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 07:27:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13178) RichFaces CDI Push fails
 with NoSuchElementException in OWB
In-Reply-To: <JIRA.12500327.1378747327000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500327.1378747327000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500327.1378747327000.32530.1385468825971@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926725#comment-12926725 ] 

Luk?? Fry? edited comment on RF-13178 at 11/26/13 7:26 AM:
-----------------------------------------------------------

This issue may be resolved by leveraging event handling improvements in CDI 1.1 that allows to access event qualifiers, see RF-11455.
                
      was (Author: lfryc):
    This issue may be resolved by leveraging event handling improvements in CDI, see RF-11455.
                  
> RichFaces CDI Push fails with NoSuchElementException in OWB
> -----------------------------------------------------------
>
>                 Key: RF-13178
>                 URL: https://issues.jboss.org/browse/RF-13178
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 4.3.3
>         Environment: Tomee 1.5.2 (Apache Tomcat (TomEE)/7.0.37))
>            Reporter: Brian Leathem
>              Labels: cdi, cdi11, owb
>             Fix For: 5.0.0.Alpha3
>
>
> RichFaces push fails with a NoSuchElementException:
> {code}
> SEVERE: Servlet.service() for servlet [FacesServlet] in context with path [] threw exception [javax.el.ELException: java.util.NoSuchElementException] with root cause
> java.util.NoSuchElementException
>         at java.util.HashMap$HashIterator.nextEntry(HashMap.java:897)
>         at java.util.HashMap$KeyIterator.next(HashMap.java:928)
>         at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.getBeanReference(PushCDIExtension.java:172)
>         at org.richfaces.cdi.push.PushCDIExtension$PushObserverMethod.notify(PushCDIExtension.java:140)
>         at org.apache.webbeans.event.NotificationManager.fireEvent(NotificationManager.java:429)
>         at org.apache.webbeans.container.BeanManagerImpl.fireEvent(BeanManagerImpl.java:484)
>         at org.apache.webbeans.event.EventImpl.fire(EventImpl.java:75)
>         at ca.bleathem.sample.PushCdiBean.sendMessage(PushCdiBean.java:31)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
>         at org.apache.webbeans.intercept.InterceptorHandler.invoke(InterceptorHandler.java:322)
>         at org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:117)
>         at org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.invoke(NormalScopedBeanInterceptorHandler.java:108)
>         at ca.bleathem.sample.PushCdiBean_$$_javassist_2.sendMessage(PushCdiBean_$$_javassist_2.java)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
>         at org.apache.el.parser.AstValue.invoke(AstValue.java:278)
>         at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:274)
>         at org.apache.myfaces.view.facelets.el.ContextAwareTagMethodExpression.invoke(ContextAwareTagMethodExpression.java:96)
>         at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:68)
>         at javax.faces.component.UICommand.broadcast(UICommand.java:120)
>         at javax.faces.component.UIViewRoot._broadcastAll(UIViewRoot.java:1028)
>         at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:286)
>         at javax.faces.component.UIViewRoot._process(UIViewRoot.java:1375)
>         at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
>         at org.apache.myfaces.lifecycle.InvokeApplicationExecutor.execute(InvokeApplicationExecutor.java:38)
>         at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:170)
>         at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
>         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>         at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
>         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>         at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>         at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>         at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:722)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 08:09:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 26 Nov 2013 08:09:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13383) Select and CSV doesn't
 work: UndeclaredThrowableException in ResourceFactoryImpl
In-Reply-To: <JIRA.12526143.1385471286369@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526143.1385471286369@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526143.1385471286369.32625.1385471346286@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13383:
----------------------------------

             Summary: Select and CSV doesn't work: UndeclaredThrowableException in ResourceFactoryImpl
                 Key: RF-13383
                 URL: https://issues.jboss.org/browse/RF-13383
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-input, component-validators, regression
    Affects Versions: 5.0.0.Alpha2
         Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
EAP 6.1.1
Mojarra 2.1.19
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 31.0.1650.57 @ Linux x86_64
            Reporter: Pavol Pitonak


# deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13999.xhtml

result:
{quote}
java.lang.reflect.UndeclaredThrowableException
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
JBWEB000071: root cause

java.lang.reflect.InvocationTargetException
	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
JBWEB000071: root cause

java.lang.NullPointerException
	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
{quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 08:11:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 26 Nov 2013 08:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13383) Select and CSV doesn't
 work: UndeclaredThrowableException in ResourceFactoryImpl
In-Reply-To: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526143.1385471286000.32639.1385471466571@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13383:
-------------------------------

    Description: 
# deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml

result:
* UndeclaredThrowableException is thrown
* works fine when you replace r:select with r:inplaceSelect

{quote}
java.lang.reflect.UndeclaredThrowableException
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
JBWEB000071: root cause

java.lang.reflect.InvocationTargetException
	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
JBWEB000071: root cause

java.lang.NullPointerException
	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
{quote}

  was:
# deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13999.xhtml

result:
{quote}
java.lang.reflect.UndeclaredThrowableException
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
JBWEB000071: root cause

java.lang.reflect.InvocationTargetException
	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
JBWEB000071: root cause

java.lang.NullPointerException
	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
{quote}


    
> Select and CSV doesn't work: UndeclaredThrowableException in ResourceFactoryImpl
> --------------------------------------------------------------------------------
>
>                 Key: RF-13383
>                 URL: https://issues.jboss.org/browse/RF-13383
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, component-validators, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>
> # deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml
> result:
> * UndeclaredThrowableException is thrown
> * works fine when you replace r:select with r:inplaceSelect
> {quote}
> java.lang.reflect.UndeclaredThrowableException
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.reflect.InvocationTargetException
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.NullPointerException
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
> 	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 08:11:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 26 Nov 2013 08:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13383) Select and CSV doesn't
 work: UndeclaredThrowableException in ResourceFactoryImpl
In-Reply-To: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526143.1385471286000.32642.1385471466769@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13383:
-------------------------------

    Priority: Critical  (was: Major)

    
> Select and CSV doesn't work: UndeclaredThrowableException in ResourceFactoryImpl
> --------------------------------------------------------------------------------
>
>                 Key: RF-13383
>                 URL: https://issues.jboss.org/browse/RF-13383
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, component-validators, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Priority: Critical
>
> # deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml
> result:
> * UndeclaredThrowableException is thrown
> * works fine when you replace r:select with r:inplaceSelect
> {quote}
> java.lang.reflect.UndeclaredThrowableException
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.reflect.InvocationTargetException
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.NullPointerException
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
> 	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 08:57:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 08:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224064@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224064@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224064.32873.1385474226392@jira02.app.mwc.hst.phx2.redhat.com>

Matej Novotny created RF-13384:
----------------------------------

             Summary: Showcase for 4.5.x - richfaces-event.js problem
                 Key: RF-13384
                 URL: https://issues.jboss.org/browse/RF-13384
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.5.0.Alpha1
            Reporter: Matej Novotny
             Fix For: 4.5.0.Alpha1


The showcase application shows following warning in server console when accessing nearly any component. 

{code}
14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
{code}

The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:01:09 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 09:01:09 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224000.32899.1385474469698@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny updated RF-13384:
-------------------------------

    Description: 
The showcase application shows following warning in server console when accessing nearly any component. 

{code}
14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
{code}

The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).

May be related to [this issue|https://issues.jboss.org/browse/RF-13186].

  was:
The showcase application shows following warning in server console when accessing nearly any component. 

{code}
14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
{code}

The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).


    
> Showcase for 4.5.x - richfaces-event.js problem
> -----------------------------------------------
>
>                 Key: RF-13384
>                 URL: https://issues.jboss.org/browse/RF-13384
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>
> The showcase application shows following warning in server console when accessing nearly any component. 
> {code}
> 14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
> {code}
> The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).
> May be related to [this issue|https://issues.jboss.org/browse/RF-13186].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:01:10 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 09:01:10 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224000.32908.1385474470015@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny updated RF-13384:
-------------------------------

    Description: 
The showcase application shows following warning in server console when accessing nearly any component. 

{code}
14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
{code}

The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).

May be related to [this issue|https://issues.jboss.org/browse/RF-13186], but that one is signed as resolved.

  was:
The showcase application shows following warning in server console when accessing nearly any component. 

{code}
14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
{code}

The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).

May be related to [this issue|https://issues.jboss.org/browse/RF-13186].


    
> Showcase for 4.5.x - richfaces-event.js problem
> -----------------------------------------------
>
>                 Key: RF-13384
>                 URL: https://issues.jboss.org/browse/RF-13384
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>
> The showcase application shows following warning in server console when accessing nearly any component. 
> {code}
> 14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
> {code}
> The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).
> May be related to [this issue|https://issues.jboss.org/browse/RF-13186], but that one is signed as resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:03:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 09:03:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224000.32912.1385474586064@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny updated RF-13384:
-------------------------------

    Steps to Reproduce: 
* Build (with 'mvn clean package -Pjbas71' command) showcase repo. Make sure to build branch 4.5.x.
* Start JBoss AS 7.1 server
* Deploy to server
* Go to [main page|http://localhost:8080/showcase] and try accessing some component (for instance 'Menus->dropdownMenu)
* See console for warning, try to interact with component (nothing happens)

  was:
* Build (with 'mvn clean package -Pjbas71' command) showcase repo
* Start JBoss AS 7.1 server
* Deploy to server
* Go to [main page|http://localhost:8080/showcase] and try accessing some component (for instance 'Menus->dropdownMenu)
* See console for warning, try to interact with component (nothing happens)


    
> Showcase for 4.5.x - richfaces-event.js problem
> -----------------------------------------------
>
>                 Key: RF-13384
>                 URL: https://issues.jboss.org/browse/RF-13384
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>
> The showcase application shows following warning in server console when accessing nearly any component. 
> {code}
> 14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
> {code}
> The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).
> May be related to [this issue|https://issues.jboss.org/browse/RF-13186], but that one is signed as resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:05:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 09:05:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13210) Move RichFaces resources
 from META-INF/resources/ to org.richfaces library
In-Reply-To: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501334.1379967310000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501334.1379967310000.32923.1385474706469@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13210.
------------------------------



Verified, closing
                
> Move RichFaces resources from META-INF/resources/ to org.richfaces library
> --------------------------------------------------------------------------
>
>                 Key: RF-13210
>                 URL: https://issues.jboss.org/browse/RF-13210
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.3.4, 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:19:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13383) Select and CSV doesn't
 work: UndeclaredThrowableException in ResourceFactoryImpl
In-Reply-To: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526143.1385471286000.32981.1385475546233@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13383:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Select and CSV doesn't work: UndeclaredThrowableException in ResourceFactoryImpl
> --------------------------------------------------------------------------------
>
>                 Key: RF-13383
>                 URL: https://issues.jboss.org/browse/RF-13383
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, component-validators, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml
> result:
> * UndeclaredThrowableException is thrown
> * works fine when you replace r:select with r:inplaceSelect
> {quote}
> java.lang.reflect.UndeclaredThrowableException
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.reflect.InvocationTargetException
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.NullPointerException
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
> 	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:19:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13382) rich:select realign
 options list on window resize
In-Reply-To: <JIRA.12526119.1385457002000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526119.1385457002000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526119.1385457002000.32991.1385475546788@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13382:
-------------------------------

    Fix Version/s: 5-Tracking

    
> rich:select realign options list on window resize
> -------------------------------------------------
>
>                 Key: RF-13382
>                 URL: https://issues.jboss.org/browse/RF-13382
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 4.3.4
>            Reporter: Gabriele Gervasi
>            Priority: Optional
>             Fix For: 5-Tracking
>
>         Attachments: Schermata 2013-11-25 alle 18.51.03.png, Schermata 2013-11-25 alle 18.51.30.png
>
>
> I'm currently developing a web application and i notice that rich:select options   doesn't follow rich:select input on window resize. If it's possible to change this  behaviour it will be really appreciated. I temporarily simply solved hiding on window resize.
> {code}
> <script>
>             window.onresize = function(event) {
>                 document.activeElement.blur();
>             }
> </script>
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:19:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13382) rich:select realign
 options list on window resize
In-Reply-To: <JIRA.12526119.1385457002000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526119.1385457002000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526119.1385457002000.32989.1385475546637@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13382:
-------------------------------

    Description: 
I'm currently developing a web application and i notice that rich:select options   doesn't follow rich:select input on window resize. If it's possible to change this  behaviour it will be really appreciated. I temporarily simply solved hiding on window resize.
{code}
<script>
            window.onresize = function(event) {
                document.activeElement.blur();
            }
</script>
{code}

  was:
I'm currently developing a web application and i notice that rich:select options   doesn't follow rich:select input on window resize. If it's possible to change this  behaviour it will be really apprentice. I temporarily simply solved hiding on window resize.
<script>
            window.onresize = function(event) {
                document.activeElement.blur();
            }
</script>


    
> rich:select realign options list on window resize
> -------------------------------------------------
>
>                 Key: RF-13382
>                 URL: https://issues.jboss.org/browse/RF-13382
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 4.3.4
>            Reporter: Gabriele Gervasi
>            Priority: Optional
>         Attachments: Schermata 2013-11-25 alle 18.51.03.png, Schermata 2013-11-25 alle 18.51.30.png
>
>
> I'm currently developing a web application and i notice that rich:select options   doesn't follow rich:select input on window resize. If it's possible to change this  behaviour it will be really appreciated. I temporarily simply solved hiding on window resize.
> {code}
> <script>
>             window.onresize = function(event) {
>                 document.activeElement.blur();
>             }
> </script>
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:21:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side
In-Reply-To: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525807.1385035920000.32993.1385475665852@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13370:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Charts - server-side
> --------------------
>
>                 Key: RF-13370
>                 URL: https://issues.jboss.org/browse/RF-13370
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>
> * rename attribute *clickListener* in chart and series tag to *plotClickListner*
> * send request to server only if a server-side listener is attached 
> * particular series server-side listeners (called only for particular series events)
> * server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:21:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side
In-Reply-To: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525807.1385035920000.32995.1385475665953@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926780#comment-12926780 ] 

Brian Leathem commented on RF-13370:
------------------------------------

[~lukindo] could you file a separate issue to track the part you want to schedule for 5.0.0.Alpha3?
                
> Charts - server-side
> --------------------
>
>                 Key: RF-13370
>                 URL: https://issues.jboss.org/browse/RF-13370
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>
> * rename attribute *clickListener* in chart and series tag to *plotClickListner*
> * send request to server only if a server-side listener is attached 
> * particular series server-side listeners (called only for particular series events)
> * server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:23:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:23:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11455) Full-featured Push CDI
 integration based on CDI 1.1
In-Reply-To: <JIRA.12448627.1317817468000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12448627.1317817468000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12448627.1317817468000.32998.1385475786404@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926781#comment-12926781 ] 

Brian Leathem commented on RF-11455:
------------------------------------

[~lfryc] can we do this in a way that is compatible with CDI 1.0 implementations?
                
> Full-featured Push CDI integration based on CDI 1.1
> ---------------------------------------------------
>
>                 Key: RF-11455
>                 URL: https://issues.jboss.org/browse/RF-11455
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 4.1.0.Milestone3
>            Reporter: Luk?? Fry?
>             Fix For: 5-Future
>
>
> When designing Push CDI integration in 4.1.0.M3, it wasn't possible to use classic CDI event observers.
> As result, CDI extension was designed instead with limitations bellow.
> Once CDI-36 will be solved, it will be possible to read InjectionPoint and its @Push annotation with classic event observer.
> * @Push annotation's parameters will be switched to @Nonbinding (there will be no reason to have them bound and user will be able to observe all @Push events).
> * It will also make possible to use runtime selection of topics/subtopics (not currently possible, observers are specifically resolved in deploy time)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:25:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:25:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-11455) Full-featured Push CDI
 integration based on CDI 1.1
In-Reply-To: <JIRA.12448627.1317817468000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12448627.1317817468000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12448627.1317817468000.33002.1385475906071@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-11455:
-------------------------------

    Fix Version/s: 5-Tracking
                       (was: 5-Future)

    
> Full-featured Push CDI integration based on CDI 1.1
> ---------------------------------------------------
>
>                 Key: RF-11455
>                 URL: https://issues.jboss.org/browse/RF-11455
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: component-push/poll
>    Affects Versions: 4.1.0.Milestone3
>            Reporter: Luk?? Fry?
>             Fix For: 5-Tracking
>
>
> When designing Push CDI integration in 4.1.0.M3, it wasn't possible to use classic CDI event observers.
> As result, CDI extension was designed instead with limitations bellow.
> Once CDI-36 will be solved, it will be possible to read InjectionPoint and its @Push annotation with classic event observer.
> * @Push annotation's parameters will be switched to @Nonbinding (there will be no reason to have them bound and user will be able to observe all @Push events).
> * It will also make possible to use runtime selection of topics/subtopics (not currently possible, observers are specifically resolved in deploy time)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:25:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 09:25:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638000.33013.1385475906787@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926783#comment-12926783 ] 

Matej Novotny commented on RF-13312:
------------------------------------

Verified for rich:editor in Metamer with RF 4.5 - renders correctly and with no errors/warnings in server console.
Closing this issue.
                
> rich:editor doesn't work in RF 4.5
> ----------------------------------
>
>                 Key: RF-13312
>                 URL: https://issues.jboss.org/browse/RF-13312
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> The editor's UI doesn't get rendered. The rendering fails with:
> {panel}
> 10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> {panel}
> It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:25:07 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 09:25:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13312) rich:editor doesn't work
	in RF 4.5
In-Reply-To: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511014.1383559638000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511014.1383559638000.33017.1385475907155@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13312.
------------------------------


    
> rich:editor doesn't work in RF 4.5
> ----------------------------------
>
>                 Key: RF-13312
>                 URL: https://issues.jboss.org/browse/RF-13312
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> The editor's UI doesn't get rendered. The rendering fails with:
> {panel}
> 10:59:36,709 SEVERE \[javax.enterprise.resource.webcontainer.jsf.application\] (http--127.0.0.1-8080-1) Error Rendering View\[/richfaces/component-sample.xhtml\]: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> {panel}
> It is caused by [this line|https://github.com/richfaces4/components/blob/master/input/ui/src/main/java/org/richfaces/renderkit/EditorRendererBase.java#L61]. The actual request path does not contain any parameters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:27:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:27:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13383) Select and CSV doesn't
 work: UndeclaredThrowableException in ResourceFactoryImpl
In-Reply-To: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526143.1385471286000.33024.1385476026005@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13383:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 7

    
> Select and CSV doesn't work: UndeclaredThrowableException in ResourceFactoryImpl
> --------------------------------------------------------------------------------
>
>                 Key: RF-13383
>                 URL: https://issues.jboss.org/browse/RF-13383
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, component-validators, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml
> result:
> * UndeclaredThrowableException is thrown
> * works fine when you replace r:select with r:inplaceSelect
> {quote}
> java.lang.reflect.UndeclaredThrowableException
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.reflect.InvocationTargetException
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.NullPointerException
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
> 	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:27:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:27:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side
In-Reply-To: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525807.1385035920000.33026.1385476026103@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13370:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 7

    
> Charts - server-side
> --------------------
>
>                 Key: RF-13370
>                 URL: https://issues.jboss.org/browse/RF-13370
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>
> * rename attribute *clickListener* in chart and series tag to *plotClickListner*
> * send request to server only if a server-side listener is attached 
> * particular series server-side listeners (called only for particular series events)
> * server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:27:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:27:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224000.33029.1385476026224@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13384:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 7

    
> Showcase for 4.5.x - richfaces-event.js problem
> -----------------------------------------------
>
>                 Key: RF-13384
>                 URL: https://issues.jboss.org/browse/RF-13384
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>
> The showcase application shows following warning in server console when accessing nearly any component. 
> {code}
> 14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
> {code}
> The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).
> May be related to [this issue|https://issues.jboss.org/browse/RF-13186], but that one is signed as resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:27:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:27:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13383) Select and CSV doesn't
 work: UndeclaredThrowableException in ResourceFactoryImpl
In-Reply-To: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526143.1385471286000.33033.1385476026420@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13383:
-------------------------------

     Original Estimate: 1 hour
    Remaining Estimate: 1 hour

    
> Select and CSV doesn't work: UndeclaredThrowableException in ResourceFactoryImpl
> --------------------------------------------------------------------------------
>
>                 Key: RF-13383
>                 URL: https://issues.jboss.org/browse/RF-13383
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, component-validators, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml
> result:
> * UndeclaredThrowableException is thrown
> * works fine when you replace r:select with r:inplaceSelect
> {quote}
> java.lang.reflect.UndeclaredThrowableException
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.reflect.InvocationTargetException
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.NullPointerException
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
> 	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:27:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:27:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side
In-Reply-To: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525807.1385035920000.33031.1385476026327@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13370:
-------------------------------

     Original Estimate: 2 hours
    Remaining Estimate: 2 hours

    
> Charts - server-side
> --------------------
>
>                 Key: RF-13370
>                 URL: https://issues.jboss.org/browse/RF-13370
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> * rename attribute *clickListener* in chart and series tag to *plotClickListner*
> * send request to server only if a server-side listener is attached 
> * particular series server-side listeners (called only for particular series events)
> * server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:27:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 09:27:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13385) Chart listener doesn't
	work with @Named
In-Reply-To: <JIRA.12526168.1385476013142@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526168.1385476013142@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526168.1385476013142.33035.1385476026507@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Macko created RF-13385:
--------------------------------

             Summary: Chart listener doesn't work with @Named
                 Key: RF-13385
                 URL: https://issues.jboss.org/browse/RF-13385
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-output
            Reporter: Luk?? Macko


server-side plotclick listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:27:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:27:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224000.33038.1385476026605@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13384:
-------------------------------

     Original Estimate: 1 hour
    Remaining Estimate: 1 hour

    
> Showcase for 4.5.x - richfaces-event.js problem
> -----------------------------------------------
>
>                 Key: RF-13384
>                 URL: https://issues.jboss.org/browse/RF-13384
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> The showcase application shows following warning in server console when accessing nearly any component. 
> {code}
> 14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
> {code}
> The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).
> May be related to [this issue|https://issues.jboss.org/browse/RF-13186], but that one is signed as resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 09:31:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 09:31:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side
In-Reply-To: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525807.1385035920000.33046.1385476265817@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926785#comment-12926785 ] 

Luk?? Macko commented on RF-13370:
----------------------------------

New issue for the 5.0.0.Alpha3 part https://issues.jboss.org/browse/RF-13385
                
> Charts - server-side
> --------------------
>
>                 Key: RF-13370
>                 URL: https://issues.jboss.org/browse/RF-13370
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> * rename attribute *clickListener* in chart and series tag to *plotClickListner*
> * send request to server only if a server-side listener is attached 
> * particular series server-side listeners (called only for particular series events)
> * server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:33:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 09:33:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224000.33050.1385476385992@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13384:
-------------------------------

    Assignee: Luk?? Fry?

    
> Showcase for 4.5.x - richfaces-event.js problem
> -----------------------------------------------
>
>                 Key: RF-13384
>                 URL: https://issues.jboss.org/browse/RF-13384
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Matej Novotny
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> The showcase application shows following warning in server console when accessing nearly any component. 
> {code}
> 14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
> {code}
> The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).
> May be related to [this issue|https://issues.jboss.org/browse/RF-13186], but that one is signed as resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:39:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 09:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224000.33091.1385476746009@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926790#comment-12926790 ] 

Luk?? Fry? commented on RF-13384:
---------------------------------

Matej, I have tried to reproduce, but with fresh build of RF5 and RF4 Components (branch 4.5.x), everything works as expected, no messages in a console as you indicated.

Could you please try to build the demo including dependencies ([RF4 Components|https://github.com/richfaces4/components/tree/4.5.x]) and try again?
                
> Showcase for 4.5.x - richfaces-event.js problem
> -----------------------------------------------
>
>                 Key: RF-13384
>                 URL: https://issues.jboss.org/browse/RF-13384
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Matej Novotny
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> The showcase application shows following warning in server console when accessing nearly any component. 
> {code}
> 14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
> {code}
> The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).
> May be related to [this issue|https://issues.jboss.org/browse/RF-13186], but that one is signed as resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:39:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 09:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224000.33096.1385476746319@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13384:
----------------------------

    Assignee: Matej Novotny  (was: Luk?? Fry?)

    
> Showcase for 4.5.x - richfaces-event.js problem
> -----------------------------------------------
>
>                 Key: RF-13384
>                 URL: https://issues.jboss.org/browse/RF-13384
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Matej Novotny
>            Assignee: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> The showcase application shows following warning in server console when accessing nearly any component. 
> {code}
> 14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
> {code}
> The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).
> May be related to [this issue|https://issues.jboss.org/browse/RF-13186], but that one is signed as resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:41:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 09:41:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13383) Select and CSV doesn't
 work: UndeclaredThrowableException in ResourceFactoryImpl
In-Reply-To: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526143.1385471286000.33100.1385476866299@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13383:
-------------------------------

    Assignee: Luk?? Fry?

    
> Select and CSV doesn't work: UndeclaredThrowableException in ResourceFactoryImpl
> --------------------------------------------------------------------------------
>
>                 Key: RF-13383
>                 URL: https://issues.jboss.org/browse/RF-13383
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, component-validators, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml
> result:
> * UndeclaredThrowableException is thrown
> * works fine when you replace r:select with r:inplaceSelect
> {quote}
> java.lang.reflect.UndeclaredThrowableException
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.reflect.InvocationTargetException
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.NullPointerException
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
> 	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:48:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:48:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13385) Chart listener doesn't
	work with @Named
In-Reply-To: <JIRA.12526168.1385476013000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526168.1385476013000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526168.1385476013000.33113.1385477285907@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926791#comment-12926791 ] 

Brian Leathem commented on RF-13385:
------------------------------------

[~lukindo] are you sure you have a beans.xml in the sample you used to test the @Named annotation?
                
> Chart listener doesn't work with @Named
> ---------------------------------------
>
>                 Key: RF-13385
>                 URL: https://issues.jboss.org/browse/RF-13385
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>
> server-side plotclick listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:53:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 09:53:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13386) Resource Mapping feature
 throws NPE for non-existing Resource, but it should log message
In-Reply-To: <JIRA.12526173.1385477544842@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526173.1385477544842@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526173.1385477544842.33127.1385477586446@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13386:
-------------------------------

             Summary: Resource Mapping feature throws NPE for non-existing Resource, but it should log message
                 Key: RF-13386
                 URL: https://issues.jboss.org/browse/RF-13386
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: resource handling
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?


In RF-13383, we have discovered that Resource Mapping does not handle situation when a resource is mapped to another ResourcePath, but the ResourcePath is not correct (e.g. the resource does not exist on that path).

In this situation, a message should be logged and RES_NOT_FOUND resource should be returned.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:55:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 09:55:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13383) Select and CSV doesn't
 work: UndeclaredThrowableException in ResourceFactoryImpl
In-Reply-To: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526143.1385471286000.33139.1385477706272@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13383:
----------------------------

    Description: 
# deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml

result:
* UndeclaredThrowableException is thrown
* works fine when you replace r:select with r:inplaceSelect

{code}
java.lang.reflect.UndeclaredThrowableException
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
JBWEB000071: root cause

java.lang.reflect.InvocationTargetException
	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
JBWEB000071: root cause

java.lang.NullPointerException
	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
{code}

  was:
# deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml

result:
* UndeclaredThrowableException is thrown
* works fine when you replace r:select with r:inplaceSelect

{quote}
java.lang.reflect.UndeclaredThrowableException
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
JBWEB000071: root cause

java.lang.reflect.InvocationTargetException
	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
JBWEB000071: root cause

java.lang.NullPointerException
	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
	$Proxy75.createResource(Unknown Source)
	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
{quote}


    
> Select and CSV doesn't work: UndeclaredThrowableException in ResourceFactoryImpl
> --------------------------------------------------------------------------------
>
>                 Key: RF-13383
>                 URL: https://issues.jboss.org/browse/RF-13383
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, component-validators, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml
> result:
> * UndeclaredThrowableException is thrown
> * works fine when you replace r:select with r:inplaceSelect
> {code}
> java.lang.reflect.UndeclaredThrowableException
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.reflect.InvocationTargetException
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.NullPointerException
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
> 	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:57:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 09:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13383) Select and CSV doesn't
 work: UndeclaredThrowableException in ResourceFactoryImpl
In-Reply-To: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526143.1385471286000.33164.1385477826232@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13383.
-----------------------------

    Resolution: Done

    
> Select and CSV doesn't work: UndeclaredThrowableException in ResourceFactoryImpl
> --------------------------------------------------------------------------------
>
>                 Key: RF-13383
>                 URL: https://issues.jboss.org/browse/RF-13383
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, component-validators, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml
> result:
> * UndeclaredThrowableException is thrown
> * works fine when you replace r:select with r:inplaceSelect
> {code}
> java.lang.reflect.UndeclaredThrowableException
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.reflect.InvocationTargetException
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.NullPointerException
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
> 	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:57:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:57:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13386) Resource Mapping feature
 throws NPE for non-existing Resource, but it should log message
In-Reply-To: <JIRA.12526173.1385477544000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526173.1385477544000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526173.1385477544000.33166.1385477826317@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13386:
-------------------------------

    Fix Version/s: 5.0.0.Alpha3

    
> Resource Mapping feature throws NPE for non-existing Resource, but it should log message
> ----------------------------------------------------------------------------------------
>
>                 Key: RF-13386
>                 URL: https://issues.jboss.org/browse/RF-13386
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: resource handling
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha3
>
>
> In RF-13383, we have discovered that Resource Mapping does not handle situation when a resource is mapped to another ResourcePath, but the ResourcePath is not correct (e.g. the resource does not exist on that path).
> In this situation, a message should be logged and RES_NOT_FOUND resource should be returned.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 09:59:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Tue, 26 Nov 2013 09:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13385) Chart listener doesn't
	work with @Named
In-Reply-To: <JIRA.12526168.1385476013000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526168.1385476013000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526168.1385476013000.33170.1385477946321@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13385:
-------------------------------

    Fix Version/s: 5.0.0.Alpha3

    
> Chart listener doesn't work with @Named
> ---------------------------------------
>
>                 Key: RF-13385
>                 URL: https://issues.jboss.org/browse/RF-13385
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>             Fix For: 5.0.0.Alpha3
>
>
> server-side plotclick listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 10:01:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 10:01:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224000.33179.1385478066634@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926799#comment-12926799 ] 

Matej Novotny commented on RF-13384:
------------------------------------

Hmm now that I rebuild everything from scratch it works for me too. I must have had outdated build of RF 4 Components, it's my bad. Sorry for bothering then, I will close this issue.
                
> Showcase for 4.5.x - richfaces-event.js problem
> -----------------------------------------------
>
>                 Key: RF-13384
>                 URL: https://issues.jboss.org/browse/RF-13384
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Matej Novotny
>            Assignee: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> The showcase application shows following warning in server console when accessing nearly any component. 
> {code}
> 14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
> {code}
> The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).
> May be related to [this issue|https://issues.jboss.org/browse/RF-13186], but that one is signed as resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 10:03:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 10:03:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13384) Showcase for 4.5.x -
 richfaces-event.js problem
In-Reply-To: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526161.1385474224000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526161.1385474224000.33200.1385478186049@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13384.
------------------------------

    Resolution: Cannot Reproduce Bug


Had an outdated build causing me to see this error. Works correctly after rebuilding dependencies.
                
> Showcase for 4.5.x - richfaces-event.js problem
> -----------------------------------------------
>
>                 Key: RF-13384
>                 URL: https://issues.jboss.org/browse/RF-13384
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Matej Novotny
>            Assignee: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> The showcase application shows following warning in server console when accessing nearly any component. 
> {code}
> 14:39:01,300 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) JSF1064: Unable to find or serve resource, richfaces-event.js.
> {code}
> The consequences are that the component does not respond on any form of interaction. This is probably a missing resource problem (or maybe a conflicting resource since we are talking RF 4.5?).
> May be related to [this issue|https://issues.jboss.org/browse/RF-13186], but that one is signed as resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Tue Nov 26 10:09:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 10:09:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload -
 progress bar doesn't show up
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.33238.1385478546049@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926808#comment-12926808 ] 

Matej Novotny commented on RF-13313:
------------------------------------

Verified using locally deployed showcase app for 4.5 and for 5.0. Progress bar shows up and images are uploaded correctly.
                
> rich:fileupload - progress bar doesn't show up
> ----------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 10:09:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 10:09:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13313) rich:fileupload -
 progress bar doesn't show up
In-Reply-To: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511966.1383560542000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511966.1383560542000.33242.1385478546232@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13313.
------------------------------



Issue was verified, closing.
                
> rich:fileupload - progress bar doesn't show up
> ----------------------------------------------
>
>                 Key: RF-13313
>                 URL: https://issues.jboss.org/browse/RF-13313
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> After uploading an image error appears in console:
> {panel}
> GET http://localhost:8080/showcase/org.richfaces.resources/javax.faces.resource/org.richfaces/fileUploadProgress?rf_fu_uid_alt=0.008011564146727324 404 (Not Found) jquery.js:8434
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 10:37:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 10:37:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13214) TreeModelAdaptor and
 TreeModelRecursive Adaptor doesn't work
In-Reply-To: <JIRA.12501341.1379968438000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501341.1379968438000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501341.1379968438000.33316.1385480225979@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13214.
------------------------------



Verified, closing
                
> TreeModelAdaptor and TreeModelRecursive Adaptor doesn't work
> ------------------------------------------------------------
>
>                 Key: RF-13214
>                 URL: https://issues.jboss.org/browse/RF-13214
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tree
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 10:37:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Tue, 26 Nov 2013 10:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10756) collapsibleSubtable: id
 set to tbody differs from component id and break rendering.
In-Reply-To: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12432840.1300178676000.33327.1385480226525@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak reassigned RF-10756:
----------------------------------

    Assignee: Juraj H?ska  (was: Pavol Pitonak)

    
> collapsibleSubtable: id set to tbody differs from component id and break rendering.
> -----------------------------------------------------------------------------------
>
>                 Key: RF-10756
>                 URL: https://issues.jboss.org/browse/RF-10756
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.0.0.Final
>            Reporter: Ilya Shaikovsky
>            Assignee: Juraj H?ska
>
> added to richfaces-showcase code:
> {code}
> 			<rich:column colspan="6">
> 				<rich:collapsibleSubTableToggler for="sbtbl" />
> 				<h:outputText value="#{list.vendor}" />
> 				<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
> 				</a4j:commandButton>
> 			</rich:column>
> 			<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
> 				expandMode="client">
> 				<rich:column>
> 					<h:outputText value="#{item.daysLive}" />
> 				</rich:column>
> {code}
> and 
> {code}
>     public void incDaysLive(){
>         for (InventoryVendorList vendor : inventoryVendorLists) {
>             for (InventoryVendorItem item : vendor.getVendorItems()) {
>                 item.setDaysLive(item.getDaysLive()+1);
>             }
>             
>         }
>     }
> {code}
> do not see values updated before refreshing the browser.
> According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 10:51:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Tue, 26 Nov 2013 10:51:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13196) Rename all
 component/renderers types org.richfaces.ui (so it won't conflict with RF4.5
 org.richfaces namespace)
In-Reply-To: <JIRA.12500864.1379438388000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500864.1379438388000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500864.1379438388000.33358.1385481066236@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13196.
------------------------------



Verified, closing issue.
                
> Rename all component/renderers types org.richfaces.ui (so it won't conflict with RF4.5 org.richfaces namespace)
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13196
>                 URL: https://issues.jboss.org/browse/RF-13196
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 5.0.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 13:33:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 13:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13387) pickList: when nested in
 r:outputPanel with ajaxRendered=true, then submitting breaks pickList
In-Reply-To: <JIRA.12526211.1385490770665@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526211.1385490770665@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526211.1385490770665.33680.1385490786117@jira02.app.mwc.hst.phx2.redhat.com>

Juraj H?ska created RF-13387:
--------------------------------

             Summary: pickList: when nested in r:outputPanel with ajaxRendered=true, then submitting breaks pickList
                 Key: RF-13387
                 URL: https://issues.jboss.org/browse/RF-13387
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Juraj H?ska


When {{pickList}} is nested in {{<r:outputPanel ajaxRendered="true"> }} then ajax submitting breaks the pickList.

It seems like the ajax response is being stuck and it is not completed correctly. (Firebug shows request completed correctly with 200, but there is no response, also the metamer ajax activity indicator stills displays WORKING like there is still an ajax request).

Regular {{h:commandButton}} submitting works correctly.

JS error being logged in browser console:
{code}
TypeError: component.detach is not a function
component.detach(source);
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Tue Nov 26 13:37:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 26 Nov 2013 13:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13370) Charts - server-side
	improvements
In-Reply-To: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525807.1385035920000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525807.1385035920000.33694.1385491026114@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13370:
----------------------------

    Summary: Charts - server-side improvements  (was: Charts - server-side)

    
> Charts - server-side improvements
> ---------------------------------
>
>                 Key: RF-13370
>                 URL: https://issues.jboss.org/browse/RF-13370
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> * rename attribute *clickListener* in chart and series tag to *plotClickListner*
> * send request to server only if a server-side listener is attached 
> * particular series server-side listeners (called only for particular series events)
> * server-side listener method is not called when Bean is annotated with @Named (listener is called properly for @MangedBean)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 03:14:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:14:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12913) Use Grunt/Karma to run
 tests for RichFaces bridge and core JavaScripts
In-Reply-To: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12489457.1366021799000.34278.1385540045912@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-12913:
-------------------------------

    Component/s:     (was: qe)

    
> Use Grunt/Karma to run tests for RichFaces bridge and core JavaScripts
> ----------------------------------------------------------------------
>
>                 Key: RF-12913
>                 URL: https://issues.jboss.org/browse/RF-12913
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> There is Arquillian QUnit extension [1] for running QUnit tests.
> Use this extension to replace currenct HtmlUnit based runner.
> Communicate with the author to make it work and report any requests for enhancements.
> [1] https://github.com/qa/arquillian-qunit/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 03:14:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:14:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.34282.1385540046224@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13343:
-------------------------------

    Component/s:     (was: qe)

    
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 03:16:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:16:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12913) Use Grunt/Karma to run
 tests for RichFaces bridge and core JavaScripts
In-Reply-To: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12489457.1366021799000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12489457.1366021799000.34284.1385540167767@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-12913:
-------------------------------

    Fix Version/s: 5.0.0.Alpha3
                       (was: 5.0.0.Alpha2)

    
> Use Grunt/Karma to run tests for RichFaces bridge and core JavaScripts
> ----------------------------------------------------------------------
>
>                 Key: RF-12913
>                 URL: https://issues.jboss.org/browse/RF-12913
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Fry?
>             Fix For: 5.0.0.Alpha3
>
>
> There is Arquillian QUnit extension [1] for running QUnit tests.
> Use this extension to replace currenct HtmlUnit based runner.
> Communicate with the author to make it work and report any requests for enhancements.
> [1] https://github.com/qa/arquillian-qunit/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 03:18:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:18:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) DataTable: row height
 strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.34287.1385540285993@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926971#comment-12926971 ] 

Brian Leathem commented on RF-13356:
------------------------------------

[~ppitonak] please clarify what was re-produced (this jira conflates several issues).
                
> DataTable: row height strechted to 100% of the table height
> -----------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3, 5.0.0.Alpha1
>            Reporter: Anton Bogoslavskyi
>            Assignee: Brian Leathem
>         Attachments: edt.png, extended-screen1.png, extended-screen2.png, screen1.png, screen2.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 03:18:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:18:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) DataTable: row height
 strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.34292.1385540286411@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13356:
-------------------------------

    Assignee: Pavol Pitonak  (was: Brian Leathem)

    
> DataTable: row height strechted to 100% of the table height
> -----------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3, 5.0.0.Alpha1
>            Reporter: Anton Bogoslavskyi
>            Assignee: Pavol Pitonak
>         Attachments: edt.png, extended-screen1.png, extended-screen2.png, screen1.png, screen2.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 03:31:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:31:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13387) pickList: when nested in
 r:outputPanel with ajaxRendered=true, then submitting breaks pickList
In-Reply-To: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526211.1385490770000.34303.1385541066076@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13387:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> pickList: when nested in r:outputPanel with ajaxRendered=true, then submitting breaks pickList
> ----------------------------------------------------------------------------------------------
>
>                 Key: RF-13387
>                 URL: https://issues.jboss.org/browse/RF-13387
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> When {{pickList}} is nested in {{<r:outputPanel ajaxRendered="true"> }} then ajax submitting breaks the pickList.
> It seems like the ajax response is being stuck and it is not completed correctly. (Firebug shows request completed correctly with 200, but there is no response, also the metamer ajax activity indicator stills displays WORKING like there is still an ajax request).
> Regular {{h:commandButton}} submitting works correctly.
> JS error being logged in browser console:
> {code}
> TypeError: component.detach is not a function
> component.detach(source);
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 03:33:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:33:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13387) pickList: when nested in
 r:outputPanel with ajaxRendered=true, then submitting breaks pickList
In-Reply-To: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526211.1385490770000.34305.1385541185898@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926976#comment-12926976 ] 

Brian Leathem commented on RF-13387:
------------------------------------

This error was introduced with the resolution of RF-13381
                
> pickList: when nested in r:outputPanel with ajaxRendered=true, then submitting breaks pickList
> ----------------------------------------------------------------------------------------------
>
>                 Key: RF-13387
>                 URL: https://issues.jboss.org/browse/RF-13387
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> When {{pickList}} is nested in {{<r:outputPanel ajaxRendered="true"> }} then ajax submitting breaks the pickList.
> It seems like the ajax response is being stuck and it is not completed correctly. (Firebug shows request completed correctly with 200, but there is no response, also the metamer ajax activity indicator stills displays WORKING like there is still an ajax request).
> Regular {{h:commandButton}} submitting works correctly.
> JS error being logged in browser console:
> {code}
> TypeError: component.detach is not a function
> component.detach(source);
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 03:35:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:35:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13387) rf.cleanComponent method
 is incorrectly operating on jQuery UI Widget factory widgets
In-Reply-To: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526211.1385490770000.34307.1385541305850@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13387:
-------------------------------

    Summary: rf.cleanComponent method is incorrectly operating on jQuery UI Widget factory widgets  (was: pickList: when nested in r:outputPanel with ajaxRendered=true, then submitting breaks pickList)

    
> rf.cleanComponent method is incorrectly operating on jQuery UI Widget factory widgets
> -------------------------------------------------------------------------------------
>
>                 Key: RF-13387
>                 URL: https://issues.jboss.org/browse/RF-13387
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> When {{pickList}} is nested in {{<r:outputPanel ajaxRendered="true"> }} then ajax submitting breaks the pickList.
> It seems like the ajax response is being stuck and it is not completed correctly. (Firebug shows request completed correctly with 200, but there is no response, also the metamer ajax activity indicator stills displays WORKING like there is still an ajax request).
> Regular {{h:commandButton}} submitting works correctly.
> JS error being logged in browser console:
> {code}
> TypeError: component.detach is not a function
> component.detach(source);
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 03:35:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:35:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13387) rf.cleanComponent method
 is incorrectly operating on jQuery UI Widget factory widgets
In-Reply-To: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526211.1385490770000.34309.1385541305988@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13387:
-------------------------------

    Priority: Blocker  (was: Major)

    
> rf.cleanComponent method is incorrectly operating on jQuery UI Widget factory widgets
> -------------------------------------------------------------------------------------
>
>                 Key: RF-13387
>                 URL: https://issues.jboss.org/browse/RF-13387
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>
> When {{pickList}} is nested in {{<r:outputPanel ajaxRendered="true"> }} then ajax submitting breaks the pickList.
> It seems like the ajax response is being stuck and it is not completed correctly. (Firebug shows request completed correctly with 200, but there is no response, also the metamer ajax activity indicator stills displays WORKING like there is still an ajax request).
> Regular {{h:commandButton}} submitting works correctly.
> JS error being logged in browser console:
> {code}
> TypeError: component.detach is not a function
> component.detach(source);
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 03:35:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:35:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13387) rf.cleanComponent method
 is incorrectly operating on jQuery UI Widget factory widgets
In-Reply-To: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526211.1385490770000.34311.1385541306129@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13387:
-------------------------------

     Original Estimate: 30 minutes
    Remaining Estimate: 30 minutes

    
> rf.cleanComponent method is incorrectly operating on jQuery UI Widget factory widgets
> -------------------------------------------------------------------------------------
>
>                 Key: RF-13387
>                 URL: https://issues.jboss.org/browse/RF-13387
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> When {{pickList}} is nested in {{<r:outputPanel ajaxRendered="true"> }} then ajax submitting breaks the pickList.
> It seems like the ajax response is being stuck and it is not completed correctly. (Firebug shows request completed correctly with 200, but there is no response, also the metamer ajax activity indicator stills displays WORKING like there is still an ajax request).
> Regular {{h:commandButton}} submitting works correctly.
> JS error being logged in browser console:
> {code}
> TypeError: component.detach is not a function
> component.detach(source);
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 03:58:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 03:58:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13387) rf.cleanComponent method
 is incorrectly operating on jQuery UI Widget factory widgets
In-Reply-To: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526211.1385490770000.34332.1385542686223@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13387.
--------------------------------

      Assignee: Brian Leathem
    Resolution: Done

    
> rf.cleanComponent method is incorrectly operating on jQuery UI Widget factory widgets
> -------------------------------------------------------------------------------------
>
>                 Key: RF-13387
>                 URL: https://issues.jboss.org/browse/RF-13387
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> When {{pickList}} is nested in {{<r:outputPanel ajaxRendered="true"> }} then ajax submitting breaks the pickList.
> It seems like the ajax response is being stuck and it is not completed correctly. (Firebug shows request completed correctly with 200, but there is no response, also the metamer ajax activity indicator stills displays WORKING like there is still an ajax request).
> Regular {{h:commandButton}} submitting works correctly.
> JS error being logged in browser console:
> {code}
> TypeError: component.detach is not a function
> component.detach(source);
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 04:21:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Wed, 27 Nov 2013 04:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13311) Make Push independent of
	BaseComponent
In-Reply-To: <JIRA.12511012.1383558111000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12511012.1383558111000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12511012.1383558111000.34364.1385544066006@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13311.
------------------------------



Verified
                
> Make Push independent of BaseComponent
> --------------------------------------
>
>                 Key: RF-13311
>                 URL: https://issues.jboss.org/browse/RF-13311
>             Project: RichFaces
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5-Tracking
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> Currently Push extends BaseComponent but since BaseComponent is not a part of core the extending fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 04:28:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 04:28:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13387) rf.cleanComponent method
 is incorrectly operating on jQuery UI Widget factory widgets
In-Reply-To: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526211.1385490770000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526211.1385490770000.34372.1385544486219@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska closed RF-13387.
----------------------------



Verified. Closing.
                
> rf.cleanComponent method is incorrectly operating on jQuery UI Widget factory widgets
> -------------------------------------------------------------------------------------
>
>                 Key: RF-13387
>                 URL: https://issues.jboss.org/browse/RF-13387
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Juraj H?ska
>            Assignee: Brian Leathem
>            Priority: Blocker
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> When {{pickList}} is nested in {{<r:outputPanel ajaxRendered="true"> }} then ajax submitting breaks the pickList.
> It seems like the ajax response is being stuck and it is not completed correctly. (Firebug shows request completed correctly with 200, but there is no response, also the metamer ajax activity indicator stills displays WORKING like there is still an ajax request).
> Regular {{h:commandButton}} submitting works correctly.
> JS error being logged in browser console:
> {code}
> TypeError: component.detach is not a function
> component.detach(source);
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 04:47:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 04:47:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13388) autocomplete,
 orderingList, picklist: js error on submit
In-Reply-To: <JIRA.12526250.1385545552801@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526250.1385545552801@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526250.1385545552801.34421.1385545625860@jira02.app.mwc.hst.phx2.redhat.com>

Ji?? ?tefek created RF-13388:
--------------------------------

             Summary: autocomplete, orderingList, picklist: js error on submit
                 Key: RF-13388
                 URL: https://issues.jboss.org/browse/RF-13388
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 5.0.0.Alpha2
            Reporter: Ji?? ?tefek
            Priority: Critical




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 04:58:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Wed, 27 Nov 2013 04:58:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13389) Showcase for RF 5,
 pick list rendering in firefox
In-Reply-To: <JIRA.12526251.1385546192424@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526251.1385546192424@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526251.1385546192424.34450.1385546286336@jira02.app.mwc.hst.phx2.redhat.com>

Matej Novotny created RF-13389:
----------------------------------

             Summary: Showcase for RF 5, pick list rendering in firefox
                 Key: RF-13389
                 URL: https://issues.jboss.org/browse/RF-13389
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
         Environment: JBoss AS 7.1
Firefox version 25.0
Chrome version 31
            Reporter: Matej Novotny
             Fix For: 5.0.0.Alpha2


When using Firefox (in my case version 25) and accessing a pick list page in showcase(selects->r:pickList), the simple pick list does not render correctly (see attached screenshot). However pick list with columns cause no problems.

I tested it with Chrome where everything works correctly.

Also to make sure I rebuilded whole repository with dependencies not to have any outdated artifacts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 05:00:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Wed, 27 Nov 2013 05:00:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13389) Showcase for RF 5,
 pick list rendering in firefox
In-Reply-To: <JIRA.12526251.1385546192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526251.1385546192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526251.1385546192000.34452.1385546405818@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny updated RF-13389:
-------------------------------

    Attachment: Chrome_screenshot.png
                Firefox_screenshot.png


Screenshots of pick list in showcase, one from FF and the other from Chrome.
                
> Showcase for RF 5, pick list rendering in firefox
> -------------------------------------------------
>
>                 Key: RF-13389
>                 URL: https://issues.jboss.org/browse/RF-13389
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: JBoss AS 7.1
> Firefox version 25.0
> Chrome version 31
>            Reporter: Matej Novotny
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: Chrome_screenshot.png, Firefox_screenshot.png
>
>
> When using Firefox (in my case version 25) and accessing a pick list page in showcase(selects->r:pickList), the simple pick list does not render correctly (see attached screenshot). However pick list with columns cause no problems.
> I tested it with Chrome where everything works correctly.
> Also to make sure I rebuilded whole repository with dependencies not to have any outdated artifacts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 05:07:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Wed, 27 Nov 2013 05:07:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13332) Showcase: update what
 components are new in 5.0 Alpha2
In-Reply-To: <JIRA.12524763.1384173502000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524763.1384173502000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524763.1384173502000.34454.1385546825850@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13332.
------------------------------



Verified, new components are correctly labeled as "new" in showcase and working.
Closing issue.
                
> Showcase: update what components are new in 5.0 Alpha2
> ------------------------------------------------------
>
>                 Key: RF-13332
>                 URL: https://issues.jboss.org/browse/RF-13332
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 05:18:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Wed, 27 Nov 2013 05:18:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13352) Introduce
 @Category(FailingOnFirefox.class) to pom.xml
In-Reply-To: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525405.1384766969000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525405.1384766969000.34468.1385547485979@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13352.
------------------------------



Verified, tests are correctly excluded on Firefox.
Closing issue.
                
> Introduce @Category(FailingOnFirefox.class) to pom.xml
> ------------------------------------------------------
>
>                 Key: RF-13352
>                 URL: https://issues.jboss.org/browse/RF-13352
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: tests - functional 
>            Reporter: Luk?? Macko
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> Creating test for the chart component, I came across an issues that one test is running in Chrome and PhantomJS and it is failing on Firefox. As [~lfryc] suggested in the [comment | https://issues.jboss.org/browse/RF-13331?focusedCommentId=12923949&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12923949], I've annotated it with FailingOnFirefox. ATM it has no effect concerning tests.
> It might be useful to add this category to rf/pom.xml configuration to exclude FailingOnFirefox test when tests run on firefox. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 05:18:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Wed, 27 Nov 2013 05:18:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13331) Move tests for Chart
 component from Sandbox to Framework Tests
In-Reply-To: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12524761.1384171743000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524761.1384171743000.34474.1385547486220@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13331.
------------------------------



Verified, tests are present inside framework tests and running.
Closing issue.
                
> Move tests for Chart component from Sandbox to Framework Tests
> --------------------------------------------------------------
>
>                 Key: RF-13331
>                 URL: https://issues.jboss.org/browse/RF-13331
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 05:24:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Wed, 27 Nov 2013 05:24:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13284) Create showcase samples
 for the chart components
In-Reply-To: <JIRA.12508522.1382476109000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508522.1382476109000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508522.1382476109000.34479.1385547845858@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13284.
------------------------------



Verified, showcase sample for charts is present and working.
Closing issue.
                
> Create showcase samples for the chart components
> ------------------------------------------------
>
>                 Key: RF-13284
>                 URL: https://issues.jboss.org/browse/RF-13284
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component-output
>            Reporter: Brian Leathem
>            Assignee: Luk?? Macko
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 05:28:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 05:28:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13388) autocomplete,
 orderingList, picklist: js error on submit
In-Reply-To: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526250.1385545552000.34484.1385548086228@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13388:
-----------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> autocomplete, orderingList, picklist: js error on submit
> --------------------------------------------------------
>
>                 Key: RF-13388
>                 URL: https://issues.jboss.org/browse/RF-13388
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 05:43:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Wed, 27 Nov 2013 05:43:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13383) Select and CSV doesn't
 work: UndeclaredThrowableException in ResourceFactoryImpl
In-Reply-To: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526143.1385471286000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526143.1385471286000.34508.1385548985938@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13383.
------------------------------



Verified, page now loads without errors.
Closing issue.
                
> Select and CSV doesn't work: UndeclaredThrowableException in ResourceFactoryImpl
> --------------------------------------------------------------------------------
>
>                 Key: RF-13383
>                 URL: https://issues.jboss.org/browse/RF-13383
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, component-validators, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Metame and open http://localhost:8080/metamer/faces/components/richSelect/RF-13383.xhtml
> result:
> * UndeclaredThrowableException is thrown
> * works fine when you replace r:select with r:inplaceSelect
> {code}
> java.lang.reflect.UndeclaredThrowableException
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.reflect.InvocationTargetException
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> JBWEB000071: root cause
> java.lang.NullPointerException
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:90)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getMappedPath(ResourceServletMapping.java:83)
> 	org.richfaces.resource.mapping.ResourceServletMapping.getResourcePath(ResourceServletMapping.java:72)
> 	org.richfaces.resource.external.MappedResourceFactoryImpl.createResource(MappedResourceFactoryImpl.java:106)
> 	sun.reflect.GeneratedMethodAccessor930.invoke(Unknown Source)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:601)
> 	org.richfaces.services.ServiceTracker$1.invoke(ServiceTracker.java:153)
> 	$Proxy75.createResource(Unknown Source)
> 	org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393)
> 	org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360)
> 	org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
> 	org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
> 	com.sun.faces.renderkit.html_basic.ScriptRenderer.encodeEnd(ScriptRenderer.java:102)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	org.richfaces.ui.core.ResourceRenderer.encodeResource(ResourceRenderer.java:53)
> 	org.richfaces.ui.core.ResourceRenderer.encodeDependentResources(ResourceRenderer.java:45)
> 	org.richfaces.ui.core.ScriptsRenderer.encodeEnd(ScriptsRenderer.java:56)
> 	org.richfaces.ui.core.UITransient.encodeEnd(UITransient.java:263)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	com.sun.faces.renderkit.html_basic.BodyRenderer.encodeEnd(BodyRenderer.java:105)
> 	javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
> 	javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
> 	com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439)
> 	com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
> 	com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
> 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> 	com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
> 	javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
> 	org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 06:33:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 06:33:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13388) autocomplete,
 orderingList, picklist: js error on submit
In-Reply-To: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526250.1385545552000.34604.1385551985923@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927034#comment-12927034 ] 

Luk?? Fry? commented on RF-13388:
---------------------------------

I believe this is duplicate of RF-13387
                
> autocomplete, orderingList, picklist: js error on submit
> --------------------------------------------------------
>
>                 Key: RF-13388
>                 URL: https://issues.jboss.org/browse/RF-13388
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 06:33:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 06:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13388) autocomplete,
 orderingList, picklist: js error on submit
In-Reply-To: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526250.1385545552000.34607.1385551986028@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13388.
-----------------------------

    Resolution: Duplicate Issue


[~jstefek], could you please verify?
                
> autocomplete, orderingList, picklist: js error on submit
> --------------------------------------------------------
>
>                 Key: RF-13388
>                 URL: https://issues.jboss.org/browse/RF-13388
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 06:33:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 06:33:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13388) autocomplete,
 orderingList, picklist: js error on submit
In-Reply-To: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526250.1385545552000.34609.1385551986140@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13388:
-------------------------------

    Assignee: Luk?? Fry?

    
> autocomplete, orderingList, picklist: js error on submit
> --------------------------------------------------------
>
>                 Key: RF-13388
>                 URL: https://issues.jboss.org/browse/RF-13388
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 06:45:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 06:45:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13389) Showcase for RF 5,
 pick list rendering in firefox
In-Reply-To: <JIRA.12526251.1385546192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526251.1385546192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526251.1385546192000.34619.1385552706130@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13389:
----------------------------

    Assignee: Brian Leathem

    
> Showcase for RF 5, pick list rendering in firefox
> -------------------------------------------------
>
>                 Key: RF-13389
>                 URL: https://issues.jboss.org/browse/RF-13389
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: JBoss AS 7.1
> Firefox version 25.0
> Chrome version 31
>            Reporter: Matej Novotny
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: Chrome_screenshot.png, Firefox_screenshot.png
>
>
> When using Firefox (in my case version 25) and accessing a pick list page in showcase(selects->r:pickList), the simple pick list does not render correctly (see attached screenshot). However pick list with columns cause no problems.
> I tested it with Chrome where everything works correctly.
> Also to make sure I rebuilded whole repository with dependencies not to have any outdated artifacts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 06:47:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 06:47:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.34624.1385552826061@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13343:
-------------------------------

    Assignee: Luk?? Fry?

    
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 06:47:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 06:47:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.34628.1385552826211@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13343:
----------------------------

    Assignee: Juraj H?ska  (was: Luk?? Fry?)

    
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 07:08:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 07:08:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13388) autocomplete,
 orderingList, picklist: js error on submit
In-Reply-To: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526250.1385545552000.34687.1385554086120@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927048#comment-12927048 ] 

Ji?? ?tefek commented on RF-13388:
----------------------------------

[~lfryc], yes it is a duplicate. 
And fixed already, my fault.
                
> autocomplete, orderingList, picklist: js error on submit
> --------------------------------------------------------
>
>                 Key: RF-13388
>                 URL: https://issues.jboss.org/browse/RF-13388
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 07:08:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 07:08:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13388) autocomplete,
 orderingList, picklist: js error on submit
In-Reply-To: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526250.1385545552000.34689.1385554086194@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek closed RF-13388.
----------------------------



Verified. closing.
                
> autocomplete, orderingList, picklist: js error on submit
> --------------------------------------------------------
>
>                 Key: RF-13388
>                 URL: https://issues.jboss.org/browse/RF-13388
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 08:18:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Wed, 27 Nov 2013 08:18:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.34878.1385558285864@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927075#comment-12927075 ] 

Matej Novotny commented on RF-13186:
------------------------------------

I am trying to verify this issue since it is marked as resolved.
So far the components render correctly and interact. However there is one problem present in showcase which is mentioned and crossed out (don't know why though) in this issue's description: 
_"The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"_

Amongst the comments I didn't manage to find any other issue which would describe this problem separately. Is there a reason why it was crossed out?
Please let me know if this should be tracked elsewhere or has nothing to do with this issue and I will resume the verification.

You may come across the above mentioned warning with following components:
* a4j:queue (just click Apply button)
* a4j:outputPanel (switch to second tab - 'Auto update for h:messages component', fill out the fields and submit)
* rich:graphValidator (fill out some passwords and store them)
* rich:messages (since it uses a4j:outputPanel I believe)
* rich:notify (first tab, just press Ajax Validate button)

Steps to reproduce:
* Build a components and showcase repos in respective branches
* Deploy to JBoss AS 7.1
* See the components I mentioned earlier
                
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 08:44:05 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Wed, 27 Nov 2013 08:44:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.34919.1385559845857@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927082#comment-12927082 ] 

Michal Petrov commented on RF-13186:
------------------------------------

[~manovotn], it's a bug in JSF, it only appears in Development stage.
                
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 10:15:06 2013
From: jira-events at lists.jboss.org (Cody Lerum (JIRA))
Date: Wed, 27 Nov 2013 10:15:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13390) Region fails to render
	after ajax request
In-Reply-To: <JIRA.12526322.1385565192721@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526322.1385565192721@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526322.1385565192721.35219.1385565306877@jira02.app.mwc.hst.phx2.redhat.com>

Cody Lerum created RF-13390:
-------------------------------

             Summary: Region fails to render after ajax request
                 Key: RF-13390
                 URL: https://issues.jboss.org/browse/RF-13390
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
         Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0
Wildfly 8.0.0.Beta2-SNAPSHOT
Mojarra 2.2.4-jbossorg-1 20131017-1524
            Reporter: Cody Lerum
             Fix For: 5.0.0.Alpha2


When

{code}
<r:region>
  <h:inputText>
    <r:ajax execute="@this" render="@region" />
  </h:inputText>
</r:region>
{code}

A partial response seems to be generated with the correct content but the dom is not updated

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 10:17:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 27 Nov 2013 10:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13354) Autocomplete:
 suggestions stay visible after input is cleared
In-Reply-To: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525458.1384783692000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525458.1384783692000.35231.1385565426045@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13354.
------------------------------


    
> Autocomplete: suggestions stay visible after input is cleared
> -------------------------------------------------------------
>
>                 Key: RF-13354
>                 URL: https://issues.jboss.org/browse/RF-13354
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input, regression
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # type "ala" into input (several suggestions will appear)
> # clear input, e.g. by using backspace key
> result:
> * the list with all available suggestions is displayed
> * in 4.3.4.Final, the suggestions are *not* displayed when input is empty

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 10:19:05 2013
From: jira-events at lists.jboss.org (Cody Lerum (JIRA))
Date: Wed, 27 Nov 2013 10:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13391) jsf.ajax.addOnEvent not
 fired after r:ajax completes
In-Reply-To: <JIRA.12526323.1385565450277@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526323.1385565450277@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526323.1385565450277.35233.1385565545971@jira02.app.mwc.hst.phx2.redhat.com>

Cody Lerum created RF-13391:
-------------------------------

             Summary: jsf.ajax.addOnEvent not fired after r:ajax completes
                 Key: RF-13391
                 URL: https://issues.jboss.org/browse/RF-13391
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 5.0.0.Alpha2
         Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 
Wildfly 8.0.0.Beta2-SNAPSHOT 
Mojarra 2.2.4-jbossorg-1 20131017-1524
            Reporter: Cody Lerum


Unsure if this is a bug or a limiation of using the r:ajax but with f:ajax I am able to listen for jsf.ajax events and for example

{code}
jsf.ajax.addOnEvent(function(data) {
  if (data.status == 'success')
    addFormGroupClasses();
  });
{code}

This code is called after completion of an f:ajax but not for an r:ajax

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 10:19:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 27 Nov 2013 10:19:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13365) push: cannot be disabled
	with ajax request
In-Reply-To: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525697.1384953090000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525697.1384953090000.35239.1385565546268@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13365.
------------------------------


    
> push: cannot be disabled with ajax request
> ------------------------------------------
>
>                 Key: RF-13365
>                 URL: https://issues.jboss.org/browse/RF-13365
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: EAP 6.1, Glassfish 3.1.2.2
> FF 25, Chrome 31
>            Reporter: Ji?? ?tefek
>            Assignee: Luk?? Fry?
>              Labels: regression
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Worked in 4.3.4.Final.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 10:21:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Wed, 27 Nov 2013 10:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13371) Clarify and fix Push
	destroy logic
In-Reply-To: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525811.1385042093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525811.1385042093000.35253.1385565666122@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13371.
------------------------------



Verified as part of RF-13365.
                
> Clarify and fix Push destroy logic
> ----------------------------------
>
>                 Key: RF-13371
>                 URL: https://issues.jboss.org/browse/RF-13371
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>
> I need to comment on the approach I took for destroying the Push component which follows approximately what Widget Factory does.
> I have also found that the widget _destroy method isn't called at all, because there is no such event as {{cleanDom}}.
> richfaces.js throws {{beforeDomClean}} and {{afterDomClean}}. The foremost is the right event to listen for for component cleanup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 11:26:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 11:26:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.35667.1385569565991@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927154#comment-12927154 ] 

Brian Leathem commented on RF-13186:
------------------------------------

Upstream issue:
https://java.net/jira/browse/JAVASERVERFACES-2147
                
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 12:10:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 12:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13389) Showcase for RF 5,
 pick list rendering in firefox
In-Reply-To: <JIRA.12526251.1385546192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526251.1385546192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526251.1385546192000.35817.1385572206409@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927177#comment-12927177 ] 

Brian Leathem commented on RF-13389:
------------------------------------

I am unable to reproduce this with a fresh build on firefox 25 (linux).  [~manovotn] would you please check this issue again?  Try clearing your browser cache to make sure you are not using any old CSS files.
                
> Showcase for RF 5, pick list rendering in firefox
> -------------------------------------------------
>
>                 Key: RF-13389
>                 URL: https://issues.jboss.org/browse/RF-13389
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: JBoss AS 7.1
> Firefox version 25.0
> Chrome version 31
>            Reporter: Matej Novotny
>            Assignee: Brian Leathem
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: Chrome_screenshot.png, Firefox_screenshot.png
>
>
> When using Firefox (in my case version 25) and accessing a pick list page in showcase(selects->r:pickList), the simple pick list does not render correctly (see attached screenshot). However pick list with columns cause no problems.
> I tested it with Chrome where everything works correctly.
> Also to make sure I rebuilded whole repository with dependencies not to have any outdated artifacts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 12:10:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 12:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13389) Showcase for RF 5,
 pick list rendering in firefox
In-Reply-To: <JIRA.12526251.1385546192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526251.1385546192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526251.1385546192000.35819.1385572206504@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13389:
-------------------------------

    Assignee: Matej Novotny  (was: Brian Leathem)

    
> Showcase for RF 5, pick list rendering in firefox
> -------------------------------------------------
>
>                 Key: RF-13389
>                 URL: https://issues.jboss.org/browse/RF-13389
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: JBoss AS 7.1
> Firefox version 25.0
> Chrome version 31
>            Reporter: Matej Novotny
>            Assignee: Matej Novotny
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: Chrome_screenshot.png, Firefox_screenshot.png
>
>
> When using Firefox (in my case version 25) and accessing a pick list page in showcase(selects->r:pickList), the simple pick list does not render correctly (see attached screenshot). However pick list with columns cause no problems.
> I tested it with Chrome where everything works correctly.
> Also to make sure I rebuilded whole repository with dependencies not to have any outdated artifacts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 12:10:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 12:10:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13390) Region fails to render
	after ajax request
In-Reply-To: <JIRA.12526322.1385565192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526322.1385565192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526322.1385565192000.35831.1385572207120@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13390:
-------------------------------

    Fix Version/s: 4.3.5
                   5.0.0.Alpha3
                       (was: 5.0.0.Alpha2)

    
> Region fails to render after ajax request
> -----------------------------------------
>
>                 Key: RF-13390
>                 URL: https://issues.jboss.org/browse/RF-13390
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0
> Wildfly 8.0.0.Beta2-SNAPSHOT
> Mojarra 2.2.4-jbossorg-1 20131017-1524
>            Reporter: Cody Lerum
>             Fix For: 4.3.5, 5.0.0.Alpha3
>
>
> When
> {code}
> <r:region>
>   <h:inputText>
>     <r:ajax execute="@this" render="@region" />
>   </h:inputText>
> </r:region>
> {code}
> A partial response seems to be generated with the correct content but the dom is not updated

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 12:10:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 12:10:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13390) Region fails to render
	after ajax request
In-Reply-To: <JIRA.12526322.1385565192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526322.1385565192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526322.1385565192000.35833.1385572207235@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13390:
-------------------------------

    Labels: jsf22  (was: )

    
> Region fails to render after ajax request
> -----------------------------------------
>
>                 Key: RF-13390
>                 URL: https://issues.jboss.org/browse/RF-13390
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0
> Wildfly 8.0.0.Beta2-SNAPSHOT
> Mojarra 2.2.4-jbossorg-1 20131017-1524
>            Reporter: Cody Lerum
>              Labels: jsf22
>             Fix For: 4.3.5, 5.0.0.Alpha3
>
>
> When
> {code}
> <r:region>
>   <h:inputText>
>     <r:ajax execute="@this" render="@region" />
>   </h:inputText>
> </r:region>
> {code}
> A partial response seems to be generated with the correct content but the dom is not updated

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 12:12:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 12:12:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13390) Region fails to render
	after ajax request
In-Reply-To: <JIRA.12526322.1385565192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526322.1385565192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526322.1385565192000.35835.1385572325878@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13390:
-------------------------------

    Component/s: component-a4j-core

    
> Region fails to render after ajax request
> -----------------------------------------
>
>                 Key: RF-13390
>                 URL: https://issues.jboss.org/browse/RF-13390
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>         Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0
> Wildfly 8.0.0.Beta2-SNAPSHOT
> Mojarra 2.2.4-jbossorg-1 20131017-1524
>            Reporter: Cody Lerum
>              Labels: jsf22
>             Fix For: 4.3.5, 5.0.0.Alpha3
>
>
> When
> {code}
> <r:region>
>   <h:inputText>
>     <r:ajax execute="@this" render="@region" />
>   </h:inputText>
> </r:region>
> {code}
> A partial response seems to be generated with the correct content but the dom is not updated

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 12:12:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 12:12:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13391) jsf.ajax.addOnEvent not
 fired after r:ajax completes
In-Reply-To: <JIRA.12526323.1385565450000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526323.1385565450000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526323.1385565450000.35837.1385572325950@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13391:
-------------------------------

    Fix Version/s: 4.3.5
                   5.0.0.Alpha3

    
> jsf.ajax.addOnEvent not fired after r:ajax completes
> ----------------------------------------------------
>
>                 Key: RF-13391
>                 URL: https://issues.jboss.org/browse/RF-13391
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 
> Wildfly 8.0.0.Beta2-SNAPSHOT 
> Mojarra 2.2.4-jbossorg-1 20131017-1524
>            Reporter: Cody Lerum
>             Fix For: 4.3.5, 5.0.0.Alpha3
>
>
> Unsure if this is a bug or a limiation of using the r:ajax but with f:ajax I am able to listen for jsf.ajax events and for example
> {code}
> jsf.ajax.addOnEvent(function(data) {
>   if (data.status == 'success')
>     addFormGroupClasses();
>   });
> {code}
> This code is called after completion of an f:ajax but not for an r:ajax

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 12:12:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 12:12:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13391) jsf.ajax.addOnEvent not
 fired after r:ajax completes
In-Reply-To: <JIRA.12526323.1385565450000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526323.1385565450000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526323.1385565450000.35839.1385572326056@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13391:
-------------------------------

    Component/s: component-a4j-core

    
> jsf.ajax.addOnEvent not fired after r:ajax completes
> ----------------------------------------------------
>
>                 Key: RF-13391
>                 URL: https://issues.jboss.org/browse/RF-13391
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 
> Wildfly 8.0.0.Beta2-SNAPSHOT 
> Mojarra 2.2.4-jbossorg-1 20131017-1524
>            Reporter: Cody Lerum
>             Fix For: 4.3.5, 5.0.0.Alpha3
>
>
> Unsure if this is a bug or a limiation of using the r:ajax but with f:ajax I am able to listen for jsf.ajax events and for example
> {code}
> jsf.ajax.addOnEvent(function(data) {
>   if (data.status == 'success')
>     addFormGroupClasses();
>   });
> {code}
> This code is called after completion of an f:ajax but not for an r:ajax

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 12:12:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 12:12:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13391) jsf.ajax.addOnEvent not
 fired after r:ajax completes
In-Reply-To: <JIRA.12526323.1385565450000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526323.1385565450000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526323.1385565450000.35841.1385572326120@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13391:
-------------------------------

    Fix Version/s:     (was: 5.0.0.Alpha3)
                       (was: 4.3.5)

    
> jsf.ajax.addOnEvent not fired after r:ajax completes
> ----------------------------------------------------
>
>                 Key: RF-13391
>                 URL: https://issues.jboss.org/browse/RF-13391
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 
> Wildfly 8.0.0.Beta2-SNAPSHOT 
> Mojarra 2.2.4-jbossorg-1 20131017-1524
>            Reporter: Cody Lerum
>
> Unsure if this is a bug or a limiation of using the r:ajax but with f:ajax I am able to listen for jsf.ajax events and for example
> {code}
> jsf.ajax.addOnEvent(function(data) {
>   if (data.status == 'success')
>     addFormGroupClasses();
>   });
> {code}
> This code is called after completion of an f:ajax but not for an r:ajax

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 12:14:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 12:14:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13391) jsf.ajax.addOnEvent not
 fired after r:ajax completes
In-Reply-To: <JIRA.12526323.1385565450000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526323.1385565450000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526323.1385565450000.35847.1385572445813@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927179#comment-12927179 ] 

Brian Leathem commented on RF-13391:
------------------------------------

[~clerum] this should work.  Does it work for you on a JSF 2.1 platform?
                
> jsf.ajax.addOnEvent not fired after r:ajax completes
> ----------------------------------------------------
>
>                 Key: RF-13391
>                 URL: https://issues.jboss.org/browse/RF-13391
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 
> Wildfly 8.0.0.Beta2-SNAPSHOT 
> Mojarra 2.2.4-jbossorg-1 20131017-1524
>            Reporter: Cody Lerum
>
> Unsure if this is a bug or a limiation of using the r:ajax but with f:ajax I am able to listen for jsf.ajax events and for example
> {code}
> jsf.ajax.addOnEvent(function(data) {
>   if (data.status == 'success')
>     addFormGroupClasses();
>   });
> {code}
> This code is called after completion of an f:ajax but not for an r:ajax

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 12:14:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 12:14:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13391) jsf.ajax.addOnEvent not
 fired after r:ajax completes
In-Reply-To: <JIRA.12526323.1385565450000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526323.1385565450000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526323.1385565450000.35849.1385572445873@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13391:
-------------------------------

    Labels: waiting_on_user  (was: )

    
> jsf.ajax.addOnEvent not fired after r:ajax completes
> ----------------------------------------------------
>
>                 Key: RF-13391
>                 URL: https://issues.jboss.org/browse/RF-13391
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 
> Wildfly 8.0.0.Beta2-SNAPSHOT 
> Mojarra 2.2.4-jbossorg-1 20131017-1524
>            Reporter: Cody Lerum
>              Labels: waiting_on_user
>
> Unsure if this is a bug or a limiation of using the r:ajax but with f:ajax I am able to listen for jsf.ajax events and for example
> {code}
> jsf.ajax.addOnEvent(function(data) {
>   if (data.status == 'success')
>     addFormGroupClasses();
>   });
> {code}
> This code is called after completion of an f:ajax but not for an r:ajax

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Wed Nov 27 13:21:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 13:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13388) autocomplete,
 orderingList, picklist: js error on submit
In-Reply-To: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526250.1385545552000.35942.1385576466588@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reopened RF-13388:
--------------------------------

      Assignee:     (was: Luk?? Fry?)


Tr-opening to correct fixVerison
                
> autocomplete, orderingList, picklist: js error on submit
> --------------------------------------------------------
>
>                 Key: RF-13388
>                 URL: https://issues.jboss.org/browse/RF-13388
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 13:21:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 13:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13388) autocomplete,
 orderingList, picklist: js error on submit
In-Reply-To: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526250.1385545552000.35945.1385576466685@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13388:
-------------------------------

    Fix Version/s:     (was: 5.0.0.Alpha2)

    
> autocomplete, orderingList, picklist: js error on submit
> --------------------------------------------------------
>
>                 Key: RF-13388
>                 URL: https://issues.jboss.org/browse/RF-13388
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Priority: Critical
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 13:21:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Wed, 27 Nov 2013 13:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13388) autocomplete,
 orderingList, picklist: js error on submit
In-Reply-To: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526250.1385545552000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526250.1385545552000.35948.1385576466815@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem closed RF-13388.
------------------------------

    Resolution: Done

    
> autocomplete, orderingList, picklist: js error on submit
> --------------------------------------------------------
>
>                 Key: RF-13388
>                 URL: https://issues.jboss.org/browse/RF-13388
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Priority: Critical
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 15:15:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 15:15:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support
 complex components like rich:autocomplete
In-Reply-To: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502430.1381226839000.36034.1385583306788@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927212#comment-12927212 ] 

Luk?? Fry? commented on RF-13251:
---------------------------------

Focus (and FocusManager) works with any [tabbable|http://api.jqueryui.com/tabbable-selector/] input including autocomplete.

I have checked on a modified sample in richfaces-showcase using focus-preserving approach:

{code}
<h:form>
        <rich:focus preserve="true" />
        
        <rich:autocomplete id="autocomplete" mode="cachedAjax" minChars="2" autocompleteMethod="#{autocompleteBean.autocomplete}" />
        
        <a4j:commandButton render="autocomplete" />
    </h:form>
{code}

When you hit commandButton, the autocomplete is re-rendered and rich:focus then brings focus back to the component thas was focused before the request (autocomplete).
                
> FocusManager to support complex components like rich:autocomplete
> -----------------------------------------------------------------
>
>                 Key: RF-13251
>                 URL: https://issues.jboss.org/browse/RF-13251
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.3.4
>            Reporter: Immo Benjes
>            Assignee: Luk?? Fry?
>            Priority: Minor
>
> Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete.
> It would be good if FocusManager could support complex components or 'real' Ids as generated for that page.
> The use case for the support on autocomplete is like this:
> User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 15:17:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 15:17:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support
 complex components like rich:autocomplete
In-Reply-To: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502430.1381226839000.36037.1385583425858@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927213#comment-12927213 ] 

Luk?? Fry? commented on RF-13251:
---------------------------------

Immo, could you please clarify in what aspects is your usage different or provide some sample of usage?

I know you use FocusManager and you would probably do something like {{focusManager.focus("autocomplete")}} but that should at the end work very similar to my sample above.
                
> FocusManager to support complex components like rich:autocomplete
> -----------------------------------------------------------------
>
>                 Key: RF-13251
>                 URL: https://issues.jboss.org/browse/RF-13251
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.3.4
>            Reporter: Immo Benjes
>            Assignee: Luk?? Fry?
>            Priority: Minor
>
> Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete.
> It would be good if FocusManager could support complex components or 'real' Ids as generated for that page.
> The use case for the support on autocomplete is like this:
> User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Wed Nov 27 15:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Wed, 27 Nov 2013 15:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support
 complex components like rich:autocomplete
In-Reply-To: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502430.1381226839000.36040.1385583426043@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13251:
----------------------------

    Labels: waiting_on_user  (was: )

    
> FocusManager to support complex components like rich:autocomplete
> -----------------------------------------------------------------
>
>                 Key: RF-13251
>                 URL: https://issues.jboss.org/browse/RF-13251
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.3.4
>            Reporter: Immo Benjes
>            Assignee: Luk?? Fry?
>            Priority: Minor
>              Labels: waiting_on_user
>
> Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete.
> It would be good if FocusManager could support complex components or 'real' Ids as generated for that page.
> The use case for the support on autocomplete is like this:
> User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 02:08:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 02:08:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13389) Showcase for RF 5,
 pick list rendering in firefox
In-Reply-To: <JIRA.12526251.1385546192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526251.1385546192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526251.1385546192000.36241.1385622485864@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13389.
------------------------------

    Resolution: Cannot Reproduce Bug


Ok, I double checked everything before I reported this but I forgot to clear the cache. It did the trick.
Closing as unreproducible and sorry for the bother..
                
> Showcase for RF 5, pick list rendering in firefox
> -------------------------------------------------
>
>                 Key: RF-13389
>                 URL: https://issues.jboss.org/browse/RF-13389
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>         Environment: JBoss AS 7.1
> Firefox version 25.0
> Chrome version 31
>            Reporter: Matej Novotny
>            Assignee: Matej Novotny
>             Fix For: 5.0.0.Alpha2
>
>         Attachments: Chrome_screenshot.png, Firefox_screenshot.png
>
>
> When using Firefox (in my case version 25) and accessing a pick list page in showcase(selects->r:pickList), the simple pick list does not render correctly (see attached screenshot). However pick list with columns cause no problems.
> I tested it with Chrome where everything works correctly.
> Also to make sure I rebuilded whole repository with dependencies not to have any outdated artifacts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 03:50:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 03:50:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.36322.1385628605971@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927273#comment-12927273 ] 

Matej Novotny commented on RF-13186:
------------------------------------

Thanks for quick response and link.
I resumed verifying and came across one more thing.

It only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid the above mentioned JSF bug.
{code}
<context-param>
        <param-name>javax.faces.PROJECT_STAGE</param-name>
        <param-value>Production</param-value>
</context-param>
{code}

Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code).
{code}
Uncaught TypeError: Object [object Object] has no method 'setPosition'      inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145
{code}
The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub.

Otherwise I found no problems/errors/warnings.
                
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 04:03:05 2013
From: jira-events at lists.jboss.org (Andreas Hahne (JIRA))
Date: Thu, 28 Nov 2013 04:03:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13392) TreeSelectionChangeEvent
 always triggered during Apply Request Phase
In-Reply-To: <JIRA.12526404.1385629372972@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526404.1385629372972@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526404.1385629372972.36338.1385629385953@jira02.app.mwc.hst.phx2.redhat.com>

Andreas Hahne created RF-13392:
----------------------------------

             Summary: TreeSelectionChangeEvent always triggered during Apply Request Phase
                 Key: RF-13392
                 URL: https://issues.jboss.org/browse/RF-13392
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-tree
    Affects Versions: 4.3.3
            Reporter: Andreas Hahne


When selecting a {{rich:treeNode}}, the corresponding {{selectionChangeListener}} is triggered during Apply Request Phase, no matter if the immediate attribute is set to true or false.

This leads to a weird behaviour in our application where an output panel is filled with the data selected in the tree. Both components are located in the same {{h:form}} element (in contrast to the showcase on the RF homepage). While the value of the {{h:outputText}} component is updated correctly, the one in the {{h:inputText}} is not because it is overwritten by the old value during Update Model Phase. If the change was processed during Invoke Application Phase this would not occur most likely.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 04:19:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 04:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13225) RF5 build fails to
 render optimized resources
In-Reply-To: <JIRA.12501617.1380205928000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501617.1380205928000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501617.1380205928000.36384.1385630345824@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13225.
------------------------------



Verified
                
> RF5 build fails to render optimized resources
> ---------------------------------------------
>
>                 Key: RF-13225
>                 URL: https://issues.jboss.org/browse/RF-13225
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: resource handling
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Michal Petrov
>            Assignee: Michal Petrov
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> The improvements for 4.5.x along with resource handling improvements introduced several issues:
> * framework/pom.xml resource optimization
> {code}
> <execution>
>     <id>static-resources</id>
>          <phase>process-classes</phase>
>          <goals>
>              <goal>java</goal>
>          </goals>
>          <configuration>
>              <arguments>
>                  <argument>--classpathDir</argument>
>                  <argument>${project.build.outputDirectory}</argument>
>                  <argument>--output</argument>
>                  <argument>${optimized.resources.directory}/Static/</argument>
>                  <argument>--prefix</argument>
>                  <argument>${optimized.resources.prefix}/Static/</argument>
>                  <argument>--mapping</argument
>                  <argument>${optimized.resources.mapping}/Static.properties</argument>
>                  <argument>--skins</argument>
>                  <argument>${optimized.resources.skins}</argument>
>                  <argument>--excludeFile</argument>
>                  <argument>^javax.faces</argument>
>                  <argument>excludeFile</argument>
>                  <argument>^org.richfaces.ui.images.*</argument>
> {code}
> {panel}
> the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail
> {panel}
> * CSS rendering from *.ecss
> {code}
> #{richSkin.imageUrl('inputBackgroundImage.png')}
> {code}
> {panel}
> the imageUrl method doesn't return the proper path, e.g. 
> {{../org.richfaces.ui.images/gradientA.png}} (proper) 
> instead of 
> {{%skin%/org.richfaces.ui.images/gradientA.png}} (current)
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 04:21:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 04:21:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13224) RF 4.5 build fails to
 render optimized resources
In-Reply-To: <JIRA.12501539.1380130905000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501539.1380130905000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501539.1380130905000.36390.1385630466039@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13224.
------------------------------



Verified
                
> RF 4.5 build fails to render optimized resources
> ------------------------------------------------
>
>                 Key: RF-13224
>                 URL: https://issues.jboss.org/browse/RF-13224
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: resource handling
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Michal Petrov
>             Fix For: 4.5.0.Alpha1
>
>
> -I believe it's caused by:-
> https://github.com/richfaces/richfaces/commit/46b03d226ae420bcbc8abd7f79ed5790f2bb6dc4
> This is no longer an issue.
> Current issues:
> * packed.js is not generated, .js files do not seem to be handled by the plugin at all
> * some images are not rendered, e.g. gradientA.png (used in several components for background), it is not defined in resource-mappings.properties

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 04:29:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 04:29:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13229) Inspect RF 4.5 Java
 classes for occurences of 'import org.richfaces.ui'
In-Reply-To: <JIRA.12501889.1380609002000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12501889.1380609002000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12501889.1380609002000.36408.1385630945839@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13229.
------------------------------



Verified
                
> Inspect RF 4.5 Java classes for occurences of 'import org.richfaces.ui'
> -----------------------------------------------------------------------
>
>                 Key: RF-13229
>                 URL: https://issues.jboss.org/browse/RF-13229
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 04:45:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 04:45:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13280) RF 5 packed resources
 cause conflict in RF 4.5
In-Reply-To: <JIRA.12508458.1382446287000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12508458.1382446287000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12508458.1382446287000.36458.1385631906394@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13280.
------------------------------



Verified
                
> RF 5 packed resources cause conflict in RF 4.5
> ----------------------------------------------
>
>                 Key: RF-13280
>                 URL: https://issues.jboss.org/browse/RF-13280
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Michal Petrov
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>
> Showcase uses resource from RF 5 core instead of using the proper ones from RF 4.5 components. (e.g. packed.js)
> The solution is to split core and ui resources in RF 5. RF 4.5 will only generate ui resources and use core resources from RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 04:49:05 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 04:49:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13362) ajax.reslib and
 base-component.reslib conflicts with RF 5.0 versions
In-Reply-To: <JIRA.12525577.1384871238000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525577.1384871238000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525577.1384871238000.36464.1385632145942@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13362.
------------------------------



Verified
                
> ajax.reslib and base-component.reslib conflicts with RF 5.0 versions
> --------------------------------------------------------------------
>
>                 Key: RF-13362
>                 URL: https://issues.jboss.org/browse/RF-13362
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 04:57:05 2013
From: jira-events at lists.jboss.org (Immo Benjes (JIRA))
Date: Thu, 28 Nov 2013 04:57:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support
 complex components like rich:autocomplete
In-Reply-To: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502430.1381226839000.36484.1385632625867@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927298#comment-12927298 ] 

Immo Benjes commented on RF-13251:
----------------------------------

Hi Luk??,

If you have a autocomplete component with the id="autocomplete" the actual generated code does not have an input field with the id="autocomplete". It has some subIds. The preserve focus might work but if you want to assign the focus with the focusManager it does not work. I have tried using focusManager.focus("autocomplete") (does not work) and focusManager.focus("autocomplete_input") (or similar can't remember the subID the actual input field has) but this doesn't work either. 
                
> FocusManager to support complex components like rich:autocomplete
> -----------------------------------------------------------------
>
>                 Key: RF-13251
>                 URL: https://issues.jboss.org/browse/RF-13251
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.3.4
>            Reporter: Immo Benjes
>            Assignee: Luk?? Fry?
>            Priority: Minor
>              Labels: waiting_on_user
>
> Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete.
> It would be good if FocusManager could support complex components or 'real' Ids as generated for that page.
> The use case for the support on autocomplete is like this:
> User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 05:03:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 05:03:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13265) Add RichFaces UI 4.5
 dist module for generating ZIP distribution
In-Reply-To: <JIRA.12503108.1381857890000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12503108.1381857890000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12503108.1381857890000.36508.1385632986026@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-13265.
------------------------------



Verified, ZIP distribution is created correctly.
                
> Add RichFaces UI 4.5 dist module for generating ZIP distribution
> ----------------------------------------------------------------
>
>                 Key: RF-13265
>                 URL: https://issues.jboss.org/browse/RF-13265
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: build/distribution
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 45 minutes
>  Remaining Estimate: 45 minutes
>
> It should distribute at least following artifacts:
> - richfaces-components-a4j
> - richfaces-components-rich

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 05:18:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 05:18:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support
 complex components like rich:autocomplete
In-Reply-To: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502430.1381226839000.36528.1385633885897@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927304#comment-12927304 ] 

Luk?? Fry? commented on RF-13251:
---------------------------------

Hey Immo,

you shouldn't try to put focus on input itself, but rather use the component. Focus component itself will determine what to focus inside the component.

Here is the alghoritm:

1. determine {{focusCandidates}} (that's what FocusManager, focus preserve or others do)
2. look for {{:tabbable}} elements under candidates
3. select first {{:tabbable}} candidate element

If we have similar DOM:

{code}
<div id="autocomplete">
  <input id="autocompleteInput" />
</div>
{code}

you have focus candidate {{autocomplete}} (known on server as a client ID) (step 1),
and you build list of actual candidate elements as {{[ 'autocompleteInput' ]}} (step 2),
and use the first of them: {{autocompleteInput}} (step 3).

See the implementation here:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/misc/focus/focus.js#L77

----

In other words, use 'autocomplete' as a focus ID.

You can access RichFaces client-side log to see what's happening.
                
> FocusManager to support complex components like rich:autocomplete
> -----------------------------------------------------------------
>
>                 Key: RF-13251
>                 URL: https://issues.jboss.org/browse/RF-13251
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.3.4
>            Reporter: Immo Benjes
>            Assignee: Luk?? Fry?
>            Priority: Minor
>              Labels: waiting_on_user
>
> Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete.
> It would be good if FocusManager could support complex components or 'real' Ids as generated for that page.
> The use case for the support on autocomplete is like this:
> User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 05:18:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 05:18:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support
 complex components like rich:autocomplete
In-Reply-To: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502430.1381226839000.36531.1385633886075@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927305#comment-12927305 ] 

Luk?? Fry? commented on RF-13251:
---------------------------------

Immo, could you please give it one more try and see whether {{focusManager.focus("autocomplete")}} works or not?
                
> FocusManager to support complex components like rich:autocomplete
> -----------------------------------------------------------------
>
>                 Key: RF-13251
>                 URL: https://issues.jboss.org/browse/RF-13251
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.3.4
>            Reporter: Immo Benjes
>            Assignee: Luk?? Fry?
>            Priority: Minor
>              Labels: waiting_on_user
>
> Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete.
> It would be good if FocusManager could support complex components or 'real' Ids as generated for that page.
> The use case for the support on autocomplete is like this:
> User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 05:18:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 05:18:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support
 complex components like rich:autocomplete
In-Reply-To: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12502430.1381226839000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12502430.1381226839000.36533.1385633886177@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927304#comment-12927304 ] 

Luk?? Fry? edited comment on RF-13251 at 11/28/13 5:18 AM:
-----------------------------------------------------------

Hey Immo,

you shouldn't try to put focus on input itself, but rather use the component. Focus component itself will determine what to focus inside the target component.

Here is the alghoritm:

1. determine {{focusCandidates}} (that's what FocusManager, focus preserve or others do)
2. look for {{:tabbable}} elements under candidates
3. select first {{:tabbable}} candidate element

If we have similar DOM:

{code}
<div id="autocomplete">
  <input id="autocompleteInput" />
</div>
{code}

you have focus candidate {{autocomplete}} (known on server as a client ID) (step 1),
and you build list of actual candidate elements as {{[ 'autocompleteInput' ]}} (step 2),
and use the first of them: {{autocompleteInput}} (step 3).

See the implementation here:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/misc/focus/focus.js#L77

----

In other words, use 'autocomplete' as a focus ID.

You can access RichFaces client-side log to see what's happening.
                
      was (Author: lfryc):
    Hey Immo,

you shouldn't try to put focus on input itself, but rather use the component. Focus component itself will determine what to focus inside the component.

Here is the alghoritm:

1. determine {{focusCandidates}} (that's what FocusManager, focus preserve or others do)
2. look for {{:tabbable}} elements under candidates
3. select first {{:tabbable}} candidate element

If we have similar DOM:

{code}
<div id="autocomplete">
  <input id="autocompleteInput" />
</div>
{code}

you have focus candidate {{autocomplete}} (known on server as a client ID) (step 1),
and you build list of actual candidate elements as {{[ 'autocompleteInput' ]}} (step 2),
and use the first of them: {{autocompleteInput}} (step 3).

See the implementation here:
https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/misc/focus/focus.js#L77

----

In other words, use 'autocomplete' as a focus ID.

You can access RichFaces client-side log to see what's happening.
                  
> FocusManager to support complex components like rich:autocomplete
> -----------------------------------------------------------------
>
>                 Key: RF-13251
>                 URL: https://issues.jboss.org/browse/RF-13251
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.3.4
>            Reporter: Immo Benjes
>            Assignee: Luk?? Fry?
>            Priority: Minor
>              Labels: waiting_on_user
>
> Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete.
> It would be good if FocusManager could support complex components or 'real' Ids as generated for that page.
> The use case for the support on autocomplete is like this:
> User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 05:31:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 05:31:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12930) Rename RichFaces.$ to
 less ambiguous RichFaces.component
In-Reply-To: <JIRA.12489763.1366251374000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12489763.1366251374000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12489763.1366251374000.36547.1385634666236@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny closed RF-12930.
------------------------------



Verified
                
> Rename RichFaces.$ to less ambiguous RichFaces.component
> --------------------------------------------------------
>
>                 Key: RF-12930
>                 URL: https://issues.jboss.org/browse/RF-12930
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: core
>            Reporter: Brian Leathem
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> Possibly rename it to RichFaces.findComponent

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 06:32:05 2013
From: jira-events at lists.jboss.org (Andreas Hahne (JIRA))
Date: Thu, 28 Nov 2013 06:32:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13392) TreeSelectionChangeEvent
 always triggered during Apply Request Phase
In-Reply-To: <JIRA.12526404.1385629372000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526404.1385629372000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526404.1385629372000.36641.1385638325836@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Hahne updated RF-13392:
-------------------------------

    Attachment: tree.zip


Attached a simple Maven project demonstrating the effect.
                
> TreeSelectionChangeEvent always triggered during Apply Request Phase
> --------------------------------------------------------------------
>
>                 Key: RF-13392
>                 URL: https://issues.jboss.org/browse/RF-13392
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tree
>    Affects Versions: 4.3.3
>            Reporter: Andreas Hahne
>              Labels: richfaces, selectionChangeListener, tree
>         Attachments: tree.zip
>
>
> When selecting a {{rich:treeNode}}, the corresponding {{selectionChangeListener}} is triggered during Apply Request Phase, no matter if the immediate attribute is set to true or false.
> This leads to a weird behaviour in our application where an output panel is filled with the data selected in the tree. Both components are located in the same {{h:form}} element (in contrast to the showcase on the RF homepage). While the value of the {{h:outputText}} component is updated correctly, the one in the {{h:inputText}} is not because it is overwritten by the old value during Update Model Phase. If the change was processed during Invoke Application Phase this would not occur most likely.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 08:06:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 08:06:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898379@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898379@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898379.36791.1385643965958@jira02.app.mwc.hst.phx2.redhat.com>

Ji?? ?tefek created RF-13393:
--------------------------------

             Summary: orderingList: JavaScript api is bound to wrong element
                 Key: RF-13393
                 URL: https://issues.jboss.org/browse/RF-13393
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-selects
    Affects Versions: 5.0.0.Alpha2
            Reporter: Ji?? ?tefek
            Priority: Critical




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 08:10:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 08:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898000.36796.1385644206249@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek updated RF-13393:
-----------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> orderingList: JavaScript api is bound to wrong element
> ------------------------------------------------------
>
>                 Key: RF-13393
>                 URL: https://issues.jboss.org/browse/RF-13393
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 08:26:06 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Thu, 28 Nov 2013 08:26:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898000.36825.1385645166094@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Petrov reassigned RF-13393:
----------------------------------

    Assignee: Michal Petrov

    
> orderingList: JavaScript api is bound to wrong element
> ------------------------------------------------------
>
>                 Key: RF-13393
>                 URL: https://issues.jboss.org/browse/RF-13393
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 08:32:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 08:32:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.36855.1385645526070@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny reopened RF-12224:
--------------------------------

      Assignee: Luk?? Fry?  (was: Simone Cinti)


I am trying to verify this issue, however this feature doesn't seem to work.

I only tested it manually yet (started working on some automated tests atm, that will take me some time I guess) but the result is following:
* You are able to SELECT (in a file manager) as many files as you like (OK)
* All these files will be displayed correctly (OK)
* As you try to upload them progress bars pop up and then you see "Done" (OK)
* Filters works (detects which files to accept and which to decline) (OK)
* *However then you check the uploaded files (second column, loading all uploaded files from bean) and only the first of the files is actually uploaded (ERROR)*
 
Steps to reproduce:
* Use Metamer or Showcase for RF 4.5 (both work the same)
* Deploy it to JBoss AS 7.1
* See [Metamer|http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml] or [Showcase|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky] page for upload
* Get some (preferably small) files you can upload
* Add them all in one addition and press Upload
* See the "Uploaded files" section - only one file gets uploaded

_NOTE: In Showcase there is limitation to GIF, JPG, BMP, PNG and the maximum size of each file must not exceed 100kB, so I suggest reproducing with Metamer_

*Addition:* If we are implementing this feature in 4.x is there a reason why this is not present in RF 5.x (tested with 5.x showcase)?
                
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 08:38:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 08:38:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.36870.1385645886098@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Novotny reopened RF-13186:
--------------------------------


    
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 09:02:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Thu, 28 Nov 2013 09:02:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control:
 attributes targetItem and targetPanel don't work
In-Reply-To: <JIRA.12526442.1385647291836@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526442.1385647291836@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526442.1385647291836.36899.1385647325928@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13394:
----------------------------------

             Summary: Toggle control: attributes targetItem and targetPanel don't work
                 Key: RF-13394
                 URL: https://issues.jboss.org/browse/RF-13394
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-panels-layout-themes, regression
    Affects Versions: 4.5.0.Alpha1
         Environment: RichFaces 4.5.0-SNAPSHOT
Metamer 4.5.0-SNAPSHOT
EAP 6.1.1
Mojarra 2.1.19
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Chrome 31.0.1650.57 @ Linux x86_64
            Reporter: Pavol Pitonak


# deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml
# set targetPanel=panel2
# set targetItem=item3
# click on "universal toggle control" button

result:
* nothing happens
* third item on second panel should be active
* when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 09:02:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Thu, 28 Nov 2013 09:02:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.36904.1385647326405@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13186:
-------------------------------

    Affects Version/s: 4.5.0.Alpha1

    
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 09:02:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Thu, 28 Nov 2013 09:02:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.36909.1385647326631@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13186:
-------------------------------

    Fix Version/s:     (was: 4.5.0.Alpha1)

    
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 09:06:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Thu, 28 Nov 2013 09:06:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.36937.1385647565930@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13186:
-------------------------------

    Fix Version/s: 4.5.0.Alpha1

    
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 09:18:05 2013
From: jira-events at lists.jboss.org (Michal Petrov (JIRA))
Date: Thu, 28 Nov 2013 09:18:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898000.36978.1385648285985@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927372#comment-12927372 ] 

Michal Petrov commented on RF-13393:
------------------------------------

The widget expects to be called directly on a list, but the CDK renders a list wrapped in a div. Now, do we need that wrapper? I seems to work fine without it (tried it in showcase).
                
> orderingList: JavaScript api is bound to wrong element
> ------------------------------------------------------
>
>                 Key: RF-13393
>                 URL: https://issues.jboss.org/browse/RF-13393
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 09:34:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 09:34:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.37013.1385649246334@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927377#comment-12927377 ] 

Luk?? Fry? commented on RF-13186:
---------------------------------

[~manovotn], could you please create a nw issue? This one's history is little bit polluted yet.
                
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 09:38:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 09:38:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.37029.1385649486159@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927379#comment-12927379 ] 

Luk?? Fry? commented on RF-12224:
---------------------------------

{quote}
 If we are implementing this feature in 4.x is there a reason why this is not present in RF 5.x (tested with 5.x showcase)?
{quote}

[~manovotn] that's because we haven't yet established a process where we port patches for 4.5 to 5.0 (even though we did so for 4.3). Please create an issue to identify patches that needs to be ported from 4.5 to 5.0.
                
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 09:48:07 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 09:48:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13395) Showcase 4.5.x,
	input number slider
In-Reply-To: <JIRA.12526458.1385650061591@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526458.1385650061591@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526458.1385650061591.37082.1385650087402@jira02.app.mwc.hst.phx2.redhat.com>

Matej Novotny created RF-13395:
----------------------------------

             Summary: Showcase 4.5.x, input number slider
                 Key: RF-13395
                 URL: https://issues.jboss.org/browse/RF-13395
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: showcase
    Affects Versions: 4.5.0.Alpha1
         Environment: JBoss AS 7.1
Firefox 25
            Reporter: Matej Novotny
             Fix For: 4.5.0.Alpha1


This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186].

It is about a RF 4.5.x Showcase.

The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186.
{code}
<context-param>
        <param-name>javax.faces.PROJECT_STAGE</param-name>
        <param-value>Production</param-value>
</context-param>
{code}

Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code).
{code}
Uncaught TypeError: Object [object Object] has no method 'setPosition'      inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145
{code}
The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub.

Otherwise I found no problems/errors/warnings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 09:50:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 09:50:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.37101.1385650206904@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927386#comment-12927386 ] 

Matej Novotny commented on RF-13186:
------------------------------------

[~lfryc], the issue can be found [here|https://issues.jboss.org/browse/RF-13395].
                
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 09:52:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 09:52:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13395) Showcase 4.5.x,
	input number slider
In-Reply-To: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526458.1385650061000.37113.1385650326772@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927389#comment-12927389 ] 

Matej Novotny commented on RF-13395:
------------------------------------

Linked as "Cloned from".
                
> Showcase 4.5.x, input number slider
> -----------------------------------
>
>                 Key: RF-13395
>                 URL: https://issues.jboss.org/browse/RF-13395
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.5.0.Alpha1
>         Environment: JBoss AS 7.1
> Firefox 25
>            Reporter: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>
> This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186].
> It is about a RF 4.5.x Showcase.
> The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186.
> {code}
> <context-param>
>         <param-name>javax.faces.PROJECT_STAGE</param-name>
>         <param-value>Production</param-value>
> </context-param>
> {code}
> Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code).
> {code}
> Uncaught TypeError: Object [object Object] has no method 'setPosition'      inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145
> {code}
> The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub.
> Otherwise I found no problems/errors/warnings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 10:00:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 10:00:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13396) Identify patches that
 needs to be ported from 4.5 to 5.0.
In-Reply-To: <JIRA.12526465.1385650688125@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526465.1385650688125@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526465.1385650688125.37139.1385650806622@jira02.app.mwc.hst.phx2.redhat.com>

Matej Novotny created RF-13396:
----------------------------------

             Summary: Identify patches that needs to be ported from 4.5 to 5.0.
                 Key: RF-13396
                 URL: https://issues.jboss.org/browse/RF-13396
             Project: RichFaces
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.5-Tracking, 5-Tracking
            Reporter: Matej Novotny


Identify what changes/features need to be ported from RF 4.5 TO RF 5.

Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224])

If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 10:02:06 2013
From: jira-events at lists.jboss.org (Matej Novotny (JIRA))
Date: Thu, 28 Nov 2013 10:02:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.37152.1385650926312@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927394#comment-12927394 ] 

Matej Novotny commented on RF-12224:
------------------------------------

Alright I created an issue [here|https://issues.jboss.org/browse/RF-13396].

Back to this bug, when I manage to write some tests I will link them here so we know what exactly is failing.
                
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 10:10:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 10:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13186) Showcase 4.5.x fails
In-Reply-To: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12500422.1378823872000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12500422.1378823872000.37193.1385651406608@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13186.
-----------------------------

    Resolution: Done


Thanks Matej, I will resolve this one then.
                
> Showcase 4.5.x fails
> --------------------
>
>                 Key: RF-13186
>                 URL: https://issues.jboss.org/browse/RF-13186
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5.0.Alpha1
>            Reporter: Michal Petrov
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/showcase] - showcase 4.5
> [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components
> [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples
> Builds and deploys fine.
> Examples that do not work:
> * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"-
> * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization
> * trees/rich:tree - missing ?/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces
> * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource)
> * inputs/rich:inplaceInput - ditto
> * selects/rich:inplaceSelect - ditto
> * output/rich:tooltip - ditto
> When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}}
> h5. resource optimization turned off
> h6. Issue with Validator
>   - org.richfaces.validator.FacesObjectDescriptor.getMessage()
>   - collision between RF4.5 and RF5
>     the interface is the same in both versions but the Message class is in different packages in the two
> h6. Issue with menus
>   - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils()
>   - probably the same problem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 10:10:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 10:10:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.37198.1385651406855@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927399#comment-12927399 ] 

Luk?? Fry? commented on RF-12224:
---------------------------------

Thanks Matej, we will look into the fileupload issues you mentioned shortly.
                
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 10:18:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 10:18:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control:
 attributes targetItem and targetPanel don't work
In-Reply-To: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526442.1385647291000.37210.1385651885799@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13394:
-------------------------------

    Fix Version/s: 4.5.0.Alpha1

    
> Toggle control: attributes targetItem and targetPanel don't work
> ----------------------------------------------------------------
>
>                 Key: RF-13394
>                 URL: https://issues.jboss.org/browse/RF-13394
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-panels-layout-themes, regression
>    Affects Versions: 4.5.0.Alpha1
>         Environment: RichFaces 4.5.0-SNAPSHOT
> Metamer 4.5.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>             Fix For: 4.5.0.Alpha1
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml
> # set targetPanel=panel2
> # set targetItem=item3
> # click on "universal toggle control" button
> result:
> * nothing happens
> * third item on second panel should be active
> * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 10:24:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 10:24:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13396) Identify patches that
 needs to be ported from 4.5 to 5.0.
In-Reply-To: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526465.1385650688000.37224.1385652245874@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927402#comment-12927402 ] 

Luk?? Fry? commented on RF-13396:
---------------------------------

There are visible here:
https://github.com/richfaces4/components/commits/4.5.x?page=4
                
> Identify patches that needs to be ported from 4.5 to 5.0.
> ---------------------------------------------------------
>
>                 Key: RF-13396
>                 URL: https://issues.jboss.org/browse/RF-13396
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5-Tracking, 5-Tracking
>            Reporter: Matej Novotny
>
> Identify what changes/features need to be ported from RF 4.5 TO RF 5.
> Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224])
> If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 12:00:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:00:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13395) Showcase 4.5.x,
	input number slider
In-Reply-To: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526458.1385650061000.37453.1385658007183@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13395:
-------------------------------

     Original Estimate: 30 minutes
    Remaining Estimate: 30 minutes

    
> Showcase 4.5.x, input number slider
> -----------------------------------
>
>                 Key: RF-13395
>                 URL: https://issues.jboss.org/browse/RF-13395
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.5.0.Alpha1
>         Environment: JBoss AS 7.1
> Firefox 25
>            Reporter: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186].
> It is about a RF 4.5.x Showcase.
> The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186.
> {code}
> <context-param>
>         <param-name>javax.faces.PROJECT_STAGE</param-name>
>         <param-value>Production</param-value>
> </context-param>
> {code}
> Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code).
> {code}
> Uncaught TypeError: Object [object Object] has no method 'setPosition'      inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145
> {code}
> The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub.
> Otherwise I found no problems/errors/warnings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 12:00:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:00:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898000.37456.1385658007357@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13393:
-------------------------------

     Original Estimate: 15 minutes
    Remaining Estimate: 15 minutes

    
> orderingList: JavaScript api is bound to wrong element
> ------------------------------------------------------
>
>                 Key: RF-13393
>                 URL: https://issues.jboss.org/browse/RF-13393
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 12:00:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:00:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.37460.1385658007499@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13343:
-------------------------------

     Original Estimate: 2 hours
    Remaining Estimate: 2 hours

    
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 12:00:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:00:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control:
 attributes targetItem and targetPanel don't work
In-Reply-To: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526442.1385647291000.37469.1385658007851@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13394:
-------------------------------

     Original Estimate: 1 hour
    Remaining Estimate: 1 hour

    
> Toggle control: attributes targetItem and targetPanel don't work
> ----------------------------------------------------------------
>
>                 Key: RF-13394
>                 URL: https://issues.jboss.org/browse/RF-13394
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-panels-layout-themes, regression
>    Affects Versions: 4.5.0.Alpha1
>         Environment: RichFaces 4.5.0-SNAPSHOT
> Metamer 4.5.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml
> # set targetPanel=panel2
> # set targetItem=item3
> # click on "universal toggle control" button
> result:
> * nothing happens
> * third item on second panel should be active
> * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 12:00:08 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:00:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13343) Page Fragments:
 Re-implement setupFragmentFromWidget() methods using component options
 access
In-Reply-To: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525011.1384357195000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525011.1384357195000.37473.1385658007999@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13343:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 8

    
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
>                 Key: RF-13343
>                 URL: https://issues.jboss.org/browse/RF-13343
>             Project: RichFaces
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: page-fragments
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Juraj H?ska
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 12:00:08 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:00:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13395) Showcase 4.5.x,
	input number slider
In-Reply-To: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526458.1385650061000.37476.1385658008119@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13395:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 8

    
> Showcase 4.5.x, input number slider
> -----------------------------------
>
>                 Key: RF-13395
>                 URL: https://issues.jboss.org/browse/RF-13395
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.5.0.Alpha1
>         Environment: JBoss AS 7.1
> Firefox 25
>            Reporter: Matej Novotny
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186].
> It is about a RF 4.5.x Showcase.
> The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186.
> {code}
> <context-param>
>         <param-name>javax.faces.PROJECT_STAGE</param-name>
>         <param-value>Production</param-value>
> </context-param>
> {code}
> Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code).
> {code}
> Uncaught TypeError: Object [object Object] has no method 'setPosition'      inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145
> {code}
> The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub.
> Otherwise I found no problems/errors/warnings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 12:00:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:00:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.37467.1385658007795@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-12224:
-------------------------------

     Original Estimate: 2 hours
    Remaining Estimate: 2 hours

    
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 12:00:08 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:00:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898000.37481.1385658008334@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13393:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 8

    
> orderingList: JavaScript api is bound to wrong element
> ------------------------------------------------------
>
>                 Key: RF-13393
>                 URL: https://issues.jboss.org/browse/RF-13393
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 12:00:08 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:00:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.37488.1385658008612@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-12224:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 8

    
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 12:00:08 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:00:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control:
 attributes targetItem and targetPanel don't work
In-Reply-To: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526442.1385647291000.37478.1385658008185@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13394:
-------------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 8

    
> Toggle control: attributes targetItem and targetPanel don't work
> ----------------------------------------------------------------
>
>                 Key: RF-13394
>                 URL: https://issues.jboss.org/browse/RF-13394
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-panels-layout-themes, regression
>    Affects Versions: 4.5.0.Alpha1
>         Environment: RichFaces 4.5.0-SNAPSHOT
> Metamer 4.5.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml
> # set targetPanel=panel2
> # set targetItem=item3
> # click on "universal toggle control" button
> result:
> * nothing happens
> * third item on second panel should be active
> * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 12:02:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:02:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898000.37491.1385658125815@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927436#comment-12927436 ] 

Brian Leathem commented on RF-13393:
------------------------------------

We need the wrapper div to hold the clientId, as the list gets wrapped by DOM elements in the widget initialisation.  I have some ideas of how to improve this, but they are out of scope for RichWidgets 0.1.
                
> orderingList: JavaScript api is bound to wrong element
> ------------------------------------------------------
>
>                 Key: RF-13393
>                 URL: https://issues.jboss.org/browse/RF-13393
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 12:06:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:06:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898000.37494.1385658365887@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927437#comment-12927437 ] 

Brian Leathem commented on RF-13393:
------------------------------------

The fix here is to look up the top-level CDK div via the clientId, and change [this line|https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/org.richfaces/bridge/select/ordering-list-bridge.js#L25] to store the widget in that element, rather than the list element.

                
> orderingList: JavaScript api is bound to wrong element
> ------------------------------------------------------
>
>                 Key: RF-13393
>                 URL: https://issues.jboss.org/browse/RF-13393
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Michal Petrov
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 12:17:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:17:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13396) Identify patches that
 needs to be ported from 4.5 to 5.0.
In-Reply-To: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526465.1385650688000.37497.1385659025877@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13396:
-------------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Identify patches that needs to be ported from 4.5 to 5.0.
> ---------------------------------------------------------
>
>                 Key: RF-13396
>                 URL: https://issues.jboss.org/browse/RF-13396
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5-Tracking, 5-Tracking
>            Reporter: Matej Novotny
>             Fix For: 5.0.0.Alpha2
>
>
> Identify what changes/features need to be ported from RF 4.5 TO RF 5.
> Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224])
> If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 12:24:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 12:24:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13392) TreeSelectionChangeEvent
 always triggered during Apply Request Phase
In-Reply-To: <JIRA.12526404.1385629372000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526404.1385629372000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526404.1385629372000.37499.1385659445823@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13392:
-------------------------------

    Fix Version/s: 5-Tracking

    
> TreeSelectionChangeEvent always triggered during Apply Request Phase
> --------------------------------------------------------------------
>
>                 Key: RF-13392
>                 URL: https://issues.jboss.org/browse/RF-13392
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tree
>    Affects Versions: 4.3.3
>            Reporter: Andreas Hahne
>              Labels: richfaces, selectionChangeListener, tree
>             Fix For: 5-Tracking
>
>         Attachments: tree.zip
>
>
> When selecting a {{rich:treeNode}}, the corresponding {{selectionChangeListener}} is triggered during Apply Request Phase, no matter if the immediate attribute is set to true or false.
> This leads to a weird behaviour in our application where an output panel is filled with the data selected in the tree. Both components are located in the same {{h:form}} element (in contrast to the showcase on the RF homepage). While the value of the {{h:outputText}} component is updated correctly, the one in the {{h:inputText}} is not because it is overwritten by the old value during Update Model Phase. If the change was processed during Invoke Application Phase this would not occur most likely.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 12:50:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 12:50:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13396) Identify patches that
 needs to be ported from 4.5 to 5.0.
In-Reply-To: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526465.1385650688000.37521.1385661005978@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927441#comment-12927441 ] 

Luk?? Fry? commented on RF-13396:
---------------------------------

RF-12224 fileUpload: Multiple file selection
- https://github.com/richfaces4/components/commit/72417a985e2aa9ef9ee316344312c34032a1bfec

RF-13090 Fixed <rich:jQuery> default argument.
- https://github.com/richfaces4/components/commit/4bb0d43e4ea48fabfa64b6293d95407f26da2722

                
> Identify patches that needs to be ported from 4.5 to 5.0.
> ---------------------------------------------------------
>
>                 Key: RF-13396
>                 URL: https://issues.jboss.org/browse/RF-13396
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5-Tracking, 5-Tracking
>            Reporter: Matej Novotny
>             Fix For: 5.0.0.Alpha2
>
>
> Identify what changes/features need to be ported from RF 4.5 TO RF 5.
> Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224])
> If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 13:37:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 13:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.37602.1385663826084@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-12224:
----------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 13:37:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 13:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.37609.1385663826349@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-12224:
----------------------------

    Assignee: Simone Cinti  (was: Luk?? Fry?)

    
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Simone Cinti
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 13:39:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 13:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.37617.1385663946123@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927453#comment-12927453 ] 

Luk?? Fry? commented on RF-12224:
---------------------------------

I have introduced support to RF 5 Core + FileUpload component.

Additionally, I have fixed support in RF 4.5.
It was caused by wrong refactoring here:
https://github.com/richfaces4/components/commit/f936e60797c037643937f1eedbd2a60c0db242b9
                
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Simone Cinti
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 13:39:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 13:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.37623.1385663946368@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-12224.
-----------------------------

    Resolution: Done

    
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Simone Cinti
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 13:45:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 13:45:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13090) <rich:jQuery> named
 functions not working as documented
In-Reply-To: <JIRA.12496244.1373610269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12496244.1373610269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12496244.1373610269000.37633.1385664306090@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13090:
----------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> <rich:jQuery> named functions not working as documented
> -------------------------------------------------------
>
>                 Key: RF-13090
>                 URL: https://issues.jboss.org/browse/RF-13090
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.3.2
>            Reporter: Vincent W?lcknitz
>            Assignee: Vincent W?lcknitz
>            Priority: Minor
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> I have found some strange behaviour with the <rich:jQuery> component when you implement named functions like described in the component reference:
> http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/html/chap-Component_Reference-Layout_and_appearance.html#sect-Component_Reference-richjQuery-Named_queries
> If I implement the given code from the reference:
> {code}
> <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this)"  />
>  <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this)"  />
>  ...
>  <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" />
>  <rich:jQuery name="releasePic" query="animate({width:'50px'})"/>
> {code}
> only the onmouseover calls will work. The prictures will get bigger but not smaller onmouseout.
> I found out that if I do some small changes to the onmouseout call it works fine:
> {code}
> <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this,{})"  />
>  <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this,{})"  />
>  ...
>  <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" />
>  <rich:jQuery name="releasePic" query="animate({width:'50px'})"/>
> {code}
> It only works when adding a second parameter to the call even if its empty.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 13:48:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 13:48:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13396) Port patches from 4.5 to
	5.0.
In-Reply-To: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526465.1385650688000.37636.1385664485910@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13396:
----------------------------

    Summary: Port patches from 4.5 to 5.0.  (was: Identify patches that needs to be ported from 4.5 to 5.0.)

    
> Port patches from 4.5 to 5.0.
> -----------------------------
>
>                 Key: RF-13396
>                 URL: https://issues.jboss.org/browse/RF-13396
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5-Tracking, 5-Tracking
>            Reporter: Matej Novotny
>             Fix For: 5.0.0.Alpha2
>
>
> Identify what changes/features need to be ported from RF 4.5 TO RF 5.
> Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224])
> If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 13:48:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 13:48:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13396) Port patches from
 4.5.0.Alpha1 to 5.0.0.Alpha2.
In-Reply-To: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526465.1385650688000.37639.1385664486127@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13396:
----------------------------

    Summary: Port patches from 4.5.0.Alpha1 to 5.0.0.Alpha2.  (was: Port patches from 4.5 to 5.0.)

    
> Port patches from 4.5.0.Alpha1 to 5.0.0.Alpha2.
> -----------------------------------------------
>
>                 Key: RF-13396
>                 URL: https://issues.jboss.org/browse/RF-13396
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5-Tracking, 5-Tracking
>            Reporter: Matej Novotny
>             Fix For: 5.0.0.Alpha2
>
>
> Identify what changes/features need to be ported from RF 4.5 TO RF 5.
> Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224])
> If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 13:48:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 13:48:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13396) Port patches from
 4.5.0.Alpha1 to 5.0.0.Alpha2
In-Reply-To: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526465.1385650688000.37641.1385664486207@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13396:
----------------------------

    Summary: Port patches from 4.5.0.Alpha1 to 5.0.0.Alpha2  (was: Port patches from 4.5.0.Alpha1 to 5.0.0.Alpha2.)

    
> Port patches from 4.5.0.Alpha1 to 5.0.0.Alpha2
> ----------------------------------------------
>
>                 Key: RF-13396
>                 URL: https://issues.jboss.org/browse/RF-13396
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5-Tracking, 5-Tracking
>            Reporter: Matej Novotny
>             Fix For: 5.0.0.Alpha2
>
>
> Identify what changes/features need to be ported from RF 4.5 TO RF 5.
> Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224])
> If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 13:50:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Thu, 28 Nov 2013 13:50:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13396) Port patches from
 4.5.0.Alpha1 to 5.0.0.Alpha2
In-Reply-To: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526465.1385650688000.37645.1385664605946@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13396.
-----------------------------

      Assignee: Luk?? Fry?
    Resolution: Done


Done. Issues committed with respective IDs of their issues.
                
> Port patches from 4.5.0.Alpha1 to 5.0.0.Alpha2
> ----------------------------------------------
>
>                 Key: RF-13396
>                 URL: https://issues.jboss.org/browse/RF-13396
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5-Tracking, 5-Tracking
>            Reporter: Matej Novotny
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> Identify what changes/features need to be ported from RF 4.5 TO RF 5.
> Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224])
> If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 15:20:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 15:20:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13396) Port patches from
 4.5.0.Alpha1 to 5.0.0.Alpha2
In-Reply-To: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526465.1385650688000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526465.1385650688000.37722.1385670005969@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927472#comment-12927472 ] 

Brian Leathem commented on RF-13396:
------------------------------------

Thanks [~lfryc]

Issues: RF-12224 and RF-13090
                
> Port patches from 4.5.0.Alpha1 to 5.0.0.Alpha2
> ----------------------------------------------
>
>                 Key: RF-13396
>                 URL: https://issues.jboss.org/browse/RF-13396
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.5-Tracking, 5-Tracking
>            Reporter: Matej Novotny
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> Identify what changes/features need to be ported from RF 4.5 TO RF 5.
> Example of such feature would be uploading multiple files using rich:fileUpload ([request|https://issues.jboss.org/browse/RF-12224])
> If all feature requests are listed in JIRA it would be sufficient to go though the implemented ones and see if they are included in RF 5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Thu Nov 28 15:22:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 15:22:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.37729.1385670126563@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-12224:
-------------------------------

    Labels: needs-qe  (was: )

    
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Simone Cinti
>              Labels: needs-qe
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Thu Nov 28 15:22:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Thu, 28 Nov 2013 15:22:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13090) <rich:jQuery> named
 functions not working as documented
In-Reply-To: <JIRA.12496244.1373610269000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12496244.1373610269000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12496244.1373610269000.37732.1385670126678@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13090:
-------------------------------

    Labels: needs-qe  (was: )

    
> <rich:jQuery> named functions not working as documented
> -------------------------------------------------------
>
>                 Key: RF-13090
>                 URL: https://issues.jboss.org/browse/RF-13090
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-misc
>    Affects Versions: 4.3.2
>            Reporter: Vincent W?lcknitz
>            Assignee: Vincent W?lcknitz
>            Priority: Minor
>              Labels: needs-qe
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> I have found some strange behaviour with the <rich:jQuery> component when you implement named functions like described in the component reference:
> http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/html/chap-Component_Reference-Layout_and_appearance.html#sect-Component_Reference-richjQuery-Named_queries
> If I implement the given code from the reference:
> {code}
> <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this)"  />
>  <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this)"  />
>  ...
>  <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" />
>  <rich:jQuery name="releasePic" query="animate({width:'50px'})"/>
> {code}
> only the onmouseover calls will work. The prictures will get bigger but not smaller onmouseout.
> I found out that if I do some small changes to the onmouseout call it works fine:
> {code}
> <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this,{})"  />
>  <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this,{})"  />
>  ...
>  <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" />
>  <rich:jQuery name="releasePic" query="animate({width:'50px'})"/>
> {code}
> It only works when adding a second parameter to the call even if its empty.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 02:19:05 2013
From: jira-events at lists.jboss.org (Tobias Seppenhauser (JIRA))
Date: Fri, 29 Nov 2013 02:19:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working
 with Internet Exporer >= 10
In-Reply-To: <JIRA.12526502.1385709468331@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526502.1385709468331@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526502.1385709468331.37890.1385709545858@jira02.app.mwc.hst.phx2.redhat.com>

Tobias Seppenhauser created RF-13397:
----------------------------------------

             Summary: a4j:push not working with Internet Exporer >= 10
                 Key: RF-13397
                 URL: https://issues.jboss.org/browse/RF-13397
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: showcase
    Affects Versions: 4.3.4
         Environment: Any where Internet Explorer 10 or above is available
            Reporter: Tobias Seppenhauser


The <a4j:push> mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. 

Unfortunately I can't see any error in the Javascript console.

[1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 02:21:05 2013
From: jira-events at lists.jboss.org (Tobias Seppenhauser (JIRA))
Date: Fri, 29 Nov 2013 02:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working
 with Internet Explorer >= 10
In-Reply-To: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526502.1385709468000.37892.1385709665848@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Seppenhauser updated RF-13397:
-------------------------------------

    Summary: a4j:push not working with Internet Explorer >= 10  (was: a4j:push not working with Internet Exporer >= 10)

    
> a4j:push not working with Internet Explorer >= 10
> -------------------------------------------------
>
>                 Key: RF-13397
>                 URL: https://issues.jboss.org/browse/RF-13397
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.3.4
>         Environment: Any where Internet Explorer 10 or above is available
>            Reporter: Tobias Seppenhauser
>              Labels: richfaces
>
> The <a4j:push> mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. 
> Unfortunately I can't see any error in the Javascript console.
> [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 03:24:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 29 Nov 2013 03:24:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working
 with Internet Explorer >= 10
In-Reply-To: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526502.1385709468000.37972.1385713447215@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13397:
----------------------------------

    Assignee: Pavol Pitonak


QE, please verify
                
> a4j:push not working with Internet Explorer >= 10
> -------------------------------------------------
>
>                 Key: RF-13397
>                 URL: https://issues.jboss.org/browse/RF-13397
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.3.4
>         Environment: Any where Internet Explorer 10 or above is available
>            Reporter: Tobias Seppenhauser
>            Assignee: Pavol Pitonak
>              Labels: richfaces
>
> The <a4j:push> mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. 
> Unfortunately I can't see any error in the Javascript console.
> [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 03:26:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 29 Nov 2013 03:26:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898000.37976.1385713565947@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem reassigned RF-13393:
----------------------------------

    Assignee: Brian Leathem  (was: Michal Petrov)

    
> orderingList: JavaScript api is bound to wrong element
> ------------------------------------------------------
>
>                 Key: RF-13393
>                 URL: https://issues.jboss.org/browse/RF-13393
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 03:54:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 29 Nov 2013 03:54:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working
 with Internet Explorer >= 10
In-Reply-To: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526502.1385709468000.38041.1385715246072@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak reassigned RF-13397:
----------------------------------

    Assignee: Juraj H?ska  (was: Pavol Pitonak)

    
> a4j:push not working with Internet Explorer >= 10
> -------------------------------------------------
>
>                 Key: RF-13397
>                 URL: https://issues.jboss.org/browse/RF-13397
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.3.4
>         Environment: Any where Internet Explorer 10 or above is available
>            Reporter: Tobias Seppenhauser
>            Assignee: Juraj H?ska
>              Labels: richfaces
>
> The <a4j:push> mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. 
> Unfortunately I can't see any error in the Javascript console.
> [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 04:02:07 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 29 Nov 2013 04:02:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13395) Showcase 4.5.x,
	input number slider
In-Reply-To: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526458.1385650061000.38045.1385715727016@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak updated RF-13395:
-------------------------------

    Priority: Blocker  (was: Major)

    
> Showcase 4.5.x, input number slider
> -----------------------------------
>
>                 Key: RF-13395
>                 URL: https://issues.jboss.org/browse/RF-13395
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.5.0.Alpha1
>         Environment: JBoss AS 7.1
> Firefox 25
>            Reporter: Matej Novotny
>            Priority: Blocker
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186].
> It is about a RF 4.5.x Showcase.
> The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186.
> {code}
> <context-param>
>         <param-name>javax.faces.PROJECT_STAGE</param-name>
>         <param-value>Production</param-value>
> </context-param>
> {code}
> Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code).
> {code}
> Uncaught TypeError: Object [object Object] has no method 'setPosition'      inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145
> {code}
> The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub.
> Otherwise I found no problems/errors/warnings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 04:02:08 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 29 Nov 2013 04:02:08 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13395) Showcase 4.5.x,
	input number slider
In-Reply-To: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526458.1385650061000.38049.1385715728238@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927519#comment-12927519 ] 

Pavol Pitonak commented on RF-13395:
------------------------------------

It can be reproduced in Metamer, too.
                
> Showcase 4.5.x, input number slider
> -----------------------------------
>
>                 Key: RF-13395
>                 URL: https://issues.jboss.org/browse/RF-13395
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.5.0.Alpha1
>         Environment: JBoss AS 7.1
> Firefox 25
>            Reporter: Matej Novotny
>            Priority: Blocker
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186].
> It is about a RF 4.5.x Showcase.
> The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186.
> {code}
> <context-param>
>         <param-name>javax.faces.PROJECT_STAGE</param-name>
>         <param-value>Production</param-value>
> </context-param>
> {code}
> Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code).
> {code}
> Uncaught TypeError: Object [object Object] has no method 'setPosition'      inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145
> {code}
> The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub.
> Otherwise I found no problems/errors/warnings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 04:40:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 04:40:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13395) Showcase 4.5.x,
	input number slider
In-Reply-To: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526458.1385650061000.38147.1385718006480@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13395:
-------------------------------

    Assignee: Luk?? Fry?

    
> Showcase 4.5.x, input number slider
> -----------------------------------
>
>                 Key: RF-13395
>                 URL: https://issues.jboss.org/browse/RF-13395
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.5.0.Alpha1
>         Environment: JBoss AS 7.1
> Firefox 25
>            Reporter: Matej Novotny
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186].
> It is about a RF 4.5.x Showcase.
> The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186.
> {code}
> <context-param>
>         <param-name>javax.faces.PROJECT_STAGE</param-name>
>         <param-value>Production</param-value>
> </context-param>
> {code}
> Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code).
> {code}
> Uncaught TypeError: Object [object Object] has no method 'setPosition'      inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145
> {code}
> The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub.
> Otherwise I found no problems/errors/warnings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 04:40:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 04:40:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control:
 attributes targetItem and targetPanel don't work
In-Reply-To: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526442.1385647291000.38149.1385718006552@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927538#comment-12927538 ] 

Luk?? Fry? commented on RF-13394:
---------------------------------

[~ppitonak] is this a regression?
                
> Toggle control: attributes targetItem and targetPanel don't work
> ----------------------------------------------------------------
>
>                 Key: RF-13394
>                 URL: https://issues.jboss.org/browse/RF-13394
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-panels-layout-themes, regression
>    Affects Versions: 4.5.0.Alpha1
>         Environment: RichFaces 4.5.0-SNAPSHOT
> Metamer 4.5.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml
> # set targetPanel=panel2
> # set targetItem=item3
> # click on "universal toggle control" button
> result:
> * nothing happens
> * third item on second panel should be active
> * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 04:46:07 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 29 Nov 2013 04:46:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898000.38162.1385718367149@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem resolved RF-13393.
--------------------------------

    Resolution: Done

    
> orderingList: JavaScript api is bound to wrong element
> ------------------------------------------------------
>
>                 Key: RF-13393
>                 URL: https://issues.jboss.org/browse/RF-13393
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 05:14:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 29 Nov 2013 05:14:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control:
 attributes targetItem and targetPanel don't work
In-Reply-To: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526442.1385647291000.38207.1385720045872@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927545#comment-12927545 ] 

Pavol Pitonak commented on RF-13394:
------------------------------------

Yes, it is a regression...you can see it in "Component/s" field :)
                
> Toggle control: attributes targetItem and targetPanel don't work
> ----------------------------------------------------------------
>
>                 Key: RF-13394
>                 URL: https://issues.jboss.org/browse/RF-13394
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-panels-layout-themes, regression
>    Affects Versions: 4.5.0.Alpha1
>         Environment: RichFaces 4.5.0-SNAPSHOT
> Metamer 4.5.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml
> # set targetPanel=panel2
> # set targetItem=item3
> # click on "universal toggle control" button
> result:
> * nothing happens
> * third item on second panel should be active
> * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 05:22:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 05:22:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.38223.1385720526532@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ji?? ?tefek reopened RF-12224:
------------------------------

      Assignee:     (was: Simone Cinti)


I have tried to verify this, but:

In both RF 4.5 and 5 Metamer:
* You are able to SELECT (in a file manager) as many files as you like (OK)
* All these files will be displayed correctly (OK)
* As you try to upload them progress bars pop up and then you see "Done" (OK)
* Filters works (detects which files to accept and which to decline) (OK)

BUT
* FileUploadListener is not invoked with multiple (in single step or in multiple steps) or even a single file upload (ERROR, base component functionality is broken)

I have used RF framework version 5.0.0-20131129.090901-137 and in 4.5 also components 4.5.0-20131129.100450-6.
Used FF 25, on EAP 6.1 and Glassfish 3.1.2.2.

So, I am reopening this issue.
                
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>              Labels: needs-qe
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 06:17:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 29 Nov 2013 06:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13393) orderingList: JavaScript
 api is bound to wrong element
In-Reply-To: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526436.1385643898000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526436.1385643898000.38277.1385723826038@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak closed RF-13393.
------------------------------



Verified
                
> orderingList: JavaScript api is bound to wrong element
> ------------------------------------------------------
>
>                 Key: RF-13393
>                 URL: https://issues.jboss.org/browse/RF-13393
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Ji?? ?tefek
>            Assignee: Brian Leathem
>            Priority: Critical
>             Fix For: 5.0.0.Alpha2
>
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 06:21:05 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 29 Nov 2013 06:21:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13356) DataTable: row height
 strechted to 100% of the table height
In-Reply-To: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12525467.1384785454000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12525467.1384785454000.38281.1385724065915@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927558#comment-12927558 ] 

Pavol Pitonak commented on RF-13356:
------------------------------------

# in EDT, rows are *not* stretched to 100% of the table height (see attached screenshot edt.png)
# in data table, rows *are* stretched to 100% so I changed the summary text of this issue
# in EDT, footer is not sticked to the bottom of table (see attached screenshot edt.png) - I asked Anton to file a new Jira for this issue
                
> DataTable: row height strechted to 100% of the table height
> -----------------------------------------------------------
>
>                 Key: RF-13356
>                 URL: https://issues.jboss.org/browse/RF-13356
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.3.3, 5.0.0.Alpha1
>            Reporter: Anton Bogoslavskyi
>            Assignee: Pavol Pitonak
>         Attachments: edt.png, extended-screen1.png, extended-screen2.png, screen1.png, screen2.png
>
>
> The same as in the parent issue:
> Instead of having fixed row height and blank space if not enough rows to fill the entire table height, the rows are stretched to fill the entire table height. For instance with an extended data table of 500px height and 2 rows, each row is approximately 250px height (minus the height of the header, borders and cell spacing).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 07:41:07 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 29 Nov 2013 07:41:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-6678) RichFaces Select
 components: implement disabled state support for selectItem
In-Reply-To: <JIRA.12383309.1238663780000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12383309.1238663780000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12383309.1238663780000.38473.1385728867533@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Pitonak reassigned RF-6678:
---------------------------------

    Assignee: Brian Leathem  (was: Pavol Pitonak)


Brian,

in RichFaces 5.0.0-SNAPSHOT, attribute disabled has no effect on rendered select/inplaceSelect.

{code:xml}
<r:select ...>
  <f:selectItem itemValue="something" itemLabel="Something" itemDisabled="true"/>
</r:select>
{code}
                
> RichFaces Select components: implement disabled state support for selectItem
> ----------------------------------------------------------------------------
>
>                 Key: RF-6678
>                 URL: https://issues.jboss.org/browse/RF-6678
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 4.0.0.Milestone5
>            Reporter: Ilya Shaikovsky
>            Assignee: Brian Leathem
>             Fix For: 5-Tracking
>
>
> components:
> inplaceSelect
> select
> In future we should support the same in:
> listShuttle
> orderingList
> note: s:selectItems disabled attribute should also works fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 09:11:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 09:11:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10756) collapsibleSubtable: id
 set to tbody differs from component id and break rendering.
In-Reply-To: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12432840.1300178676000.38590.1385734266036@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927594#comment-12927594 ] 

Juraj H?ska commented on RF-10756:
----------------------------------

I have reproduced the issue on Showcase at [this|https://github.com/jhuska/richfaces/tree/RF-10756] branch.

It is so as it is reported. Workaround works as well. Please see Steps to reproduce.

Please, tell me if you wanna something more. E.g. reproducing it with other iteration elements as well.
                
> collapsibleSubtable: id set to tbody differs from component id and break rendering.
> -----------------------------------------------------------------------------------
>
>                 Key: RF-10756
>                 URL: https://issues.jboss.org/browse/RF-10756
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.0.0.Final
>            Reporter: Ilya Shaikovsky
>            Assignee: Juraj H?ska
>
> added to richfaces-showcase code:
> {code}
> 			<rich:column colspan="6">
> 				<rich:collapsibleSubTableToggler for="sbtbl" />
> 				<h:outputText value="#{list.vendor}" />
> 				<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
> 				</a4j:commandButton>
> 			</rich:column>
> 			<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
> 				expandMode="client">
> 				<rich:column>
> 					<h:outputText value="#{item.daysLive}" />
> 				</rich:column>
> {code}
> and 
> {code}
>     public void incDaysLive(){
>         for (InventoryVendorList vendor : inventoryVendorLists) {
>             for (InventoryVendorItem item : vendor.getVendorItems()) {
>                 item.setDaysLive(item.getDaysLive()+1);
>             }
>             
>         }
>     }
> {code}
> do not see values updated before refreshing the browser.
> According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 09:13:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 09:13:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10756) collapsibleSubtable: id
 set to tbody differs from component id and break rendering.
In-Reply-To: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12432840.1300178676000.38603.1385734386450@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-10756:
-----------------------------

    Steps to Reproduce: 
# checkout showcase from [this|https://github.com/jhuska/richfaces/tree/RF-10756] branch.
# build it and deploy on any server
# load: http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=subTableToggleControl&skin=blueSky
# click on the render button
# see that the numbers are not increased
# see also the {{r:log}} output that the the client id of the table differs from the one which is being updated

    
> collapsibleSubtable: id set to tbody differs from component id and break rendering.
> -----------------------------------------------------------------------------------
>
>                 Key: RF-10756
>                 URL: https://issues.jboss.org/browse/RF-10756
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.0.0.Final
>            Reporter: Ilya Shaikovsky
>            Assignee: Juraj H?ska
>
> added to richfaces-showcase code:
> {code}
> 			<rich:column colspan="6">
> 				<rich:collapsibleSubTableToggler for="sbtbl" />
> 				<h:outputText value="#{list.vendor}" />
> 				<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
> 				</a4j:commandButton>
> 			</rich:column>
> 			<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
> 				expandMode="client">
> 				<rich:column>
> 					<h:outputText value="#{item.daysLive}" />
> 				</rich:column>
> {code}
> and 
> {code}
>     public void incDaysLive(){
>         for (InventoryVendorList vendor : inventoryVendorLists) {
>             for (InventoryVendorItem item : vendor.getVendorItems()) {
>                 item.setDaysLive(item.getDaysLive()+1);
>             }
>             
>         }
>     }
> {code}
> do not see values updated before refreshing the browser.
> According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 09:13:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 09:13:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-10756) collapsibleSubtable: id
 set to tbody differs from component id and break rendering.
In-Reply-To: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12432840.1300178676000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12432840.1300178676000.38610.1385734386706@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-10756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-10756:
-----------------------------

    Assignee:     (was: Juraj H?ska)

    
> collapsibleSubtable: id set to tbody differs from component id and break rendering.
> -----------------------------------------------------------------------------------
>
>                 Key: RF-10756
>                 URL: https://issues.jboss.org/browse/RF-10756
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 4.0.0.Final
>            Reporter: Ilya Shaikovsky
>
> added to richfaces-showcase code:
> {code}
> 			<rich:column colspan="6">
> 				<rich:collapsibleSubTableToggler for="sbtbl" />
> 				<h:outputText value="#{list.vendor}" />
> 				<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
> 				</a4j:commandButton>
> 			</rich:column>
> 			<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
> 				expandMode="client">
> 				<rich:column>
> 					<h:outputText value="#{item.daysLive}" />
> 				</rich:column>
> {code}
> and 
> {code}
>     public void incDaysLive(){
>         for (InventoryVendorList vendor : inventoryVendorLists) {
>             for (InventoryVendorItem item : vendor.getVendorItems()) {
>                 item.setDaysLive(item.getDaysLive()+1);
>             }
>             
>         }
>     }
> {code}
> do not see values updated before refreshing the browser.
> According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 09:32:06 2013
From: jira-events at lists.jboss.org (Pavol Pitonak (JIRA))
Date: Fri, 29 Nov 2013 09:32:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13398) Autocomplete: JavaScript
	API doesn't work
In-Reply-To: <JIRA.12526554.1385735522016@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526554.1385735522016@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526554.1385735522016.38638.1385735526024@jira02.app.mwc.hst.phx2.redhat.com>

Pavol Pitonak created RF-13398:
----------------------------------

             Summary: Autocomplete: JavaScript API doesn't work
                 Key: RF-13398
                 URL: https://issues.jboss.org/browse/RF-13398
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-input
    Affects Versions: 5.0.0.Alpha2
         Environment: RichFaces 5.0.0-SNAPSHOT
            Reporter: Pavol Pitonak


# deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
# open browser console
# run in console RichFaces.component("form:autocomplete").disable()

result:
* the method fails with this error:
{code}
TypeError: Cannot call method 'attr' of undefined
{code}
* the method enable() doesn't work as well

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 11:04:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 11:04:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working
 with Internet Explorer >= 10
In-Reply-To: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526502.1385709468000.38782.1385741046663@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927626#comment-12927626 ] 

Juraj H?ska commented on RF-13397:
----------------------------------

I can reproduce the error.

I have reproduced it with both online referenced showcase (after restart of the application server) and also with locally running JBoss AS 7.1.1.Final.

The issue is occurring only in IE. Other browsers works.

I git this JS error into the console:
{code}
HTML1524: Invalid DOCTYPE. The shortest valid doctype is "<!DOCTYPE html>". 
component-sample.jsf, line 1 character 1
{code}

I have tried to change the doctype, as is advised [here|http://stackoverflow.com/a/16127782]. However the error disappeared, the {{r:push}} is still not working. I can not see any network activity in the browser, so I guess it is server/atmosphere problem ?

Let me know if I can test sth more.
                
> a4j:push not working with Internet Explorer >= 10
> -------------------------------------------------
>
>                 Key: RF-13397
>                 URL: https://issues.jboss.org/browse/RF-13397
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.3.4
>         Environment: Any where Internet Explorer 10 or above is available
>            Reporter: Tobias Seppenhauser
>            Assignee: Juraj H?ska
>              Labels: richfaces
>
> The <a4j:push> mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. 
> Unfortunately I can't see any error in the Javascript console.
> [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 11:04:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 11:04:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working
 with Internet Explorer >= 10
In-Reply-To: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526502.1385709468000.38789.1385741047020@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927626#comment-12927626 ] 

Juraj H?ska edited comment on RF-13397 at 11/29/13 11:03 AM:
-------------------------------------------------------------

I can reproduce the error.

I have reproduced it with both online referenced showcase (after restart of the application server) and also with locally running JBoss AS 7.1.1.Final.

The issue is occurring only in IE. Other browsers works.

I got this JS error into the console:
{code}
HTML1524: Invalid DOCTYPE. The shortest valid doctype is "<!DOCTYPE html>". 
component-sample.jsf, line 1 character 1
{code}

I have tried to change the doctype, as is advised [here|http://stackoverflow.com/a/16127782]. However the error disappeared, the {{r:push}} is still not working. I can not see any network activity in the browser, so I guess it is server/atmosphere problem ?

Let me know if I can test sth more.
                
      was (Author: jhuska):
    I can reproduce the error.

I have reproduced it with both online referenced showcase (after restart of the application server) and also with locally running JBoss AS 7.1.1.Final.

The issue is occurring only in IE. Other browsers works.

I git this JS error into the console:
{code}
HTML1524: Invalid DOCTYPE. The shortest valid doctype is "<!DOCTYPE html>". 
component-sample.jsf, line 1 character 1
{code}

I have tried to change the doctype, as is advised [here|http://stackoverflow.com/a/16127782]. However the error disappeared, the {{r:push}} is still not working. I can not see any network activity in the browser, so I guess it is server/atmosphere problem ?

Let me know if I can test sth more.
                  
> a4j:push not working with Internet Explorer >= 10
> -------------------------------------------------
>
>                 Key: RF-13397
>                 URL: https://issues.jboss.org/browse/RF-13397
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.3.4
>         Environment: Any where Internet Explorer 10 or above is available
>            Reporter: Tobias Seppenhauser
>            Assignee: Juraj H?ska
>              Labels: richfaces
>
> The <a4j:push> mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. 
> Unfortunately I can't see any error in the Javascript console.
> [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 11:04:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 11:04:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working
 with Internet Explorer >= 10
In-Reply-To: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526502.1385709468000.38799.1385741047481@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juraj H?ska updated RF-13397:
-----------------------------

    Assignee:     (was: Juraj H?ska)

    
> a4j:push not working with Internet Explorer >= 10
> -------------------------------------------------
>
>                 Key: RF-13397
>                 URL: https://issues.jboss.org/browse/RF-13397
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.3.4
>         Environment: Any where Internet Explorer 10 or above is available
>            Reporter: Tobias Seppenhauser
>              Labels: richfaces
>
> The <a4j:push> mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. 
> Unfortunately I can't see any error in the Javascript console.
> [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 11:15:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 11:15:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13398) Autocomplete: JavaScript
	API doesn't work
In-Reply-To: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526554.1385735522000.38809.1385741707157@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-13398:
-------------------------------

    Assignee: Luk?? Fry?

    
> Autocomplete: JavaScript API doesn't work
> -----------------------------------------
>
>                 Key: RF-13398
>                 URL: https://issues.jboss.org/browse/RF-13398
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # open browser console
> # run in console RichFaces.component("form:autocomplete").disable()
> result:
> * the method fails with this error:
> {code}
> TypeError: Cannot call method 'attr' of undefined
> {code}
> * the method enable() doesn't work as well

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 11:17:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 11:17:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13398) Autocomplete: JavaScript
	API doesn't work
In-Reply-To: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526554.1385735522000.38813.1385741825977@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13398:
----------------------------

    Fix Version/s: 5.0.0.Alpha2

    
> Autocomplete: JavaScript API doesn't work
> -----------------------------------------
>
>                 Key: RF-13398
>                 URL: https://issues.jboss.org/browse/RF-13398
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # open browser console
> # run in console RichFaces.component("form:autocomplete").disable()
> result:
> * the method fails with this error:
> {code}
> TypeError: Cannot call method 'attr' of undefined
> {code}
> * the method enable() doesn't work as well

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 11:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 11:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.38822.1385741826375@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? reassigned RF-12224:
-------------------------------

    Assignee: Luk?? Fry?

    
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>              Labels: needs-qe
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 11:17:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 11:17:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13398) Autocomplete: JavaScript
	API doesn't work
In-Reply-To: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526554.1385735522000.38825.1385741826531@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? updated RF-13398:
----------------------------

    Sprint: 5.0.0.Alpha2 - Sprint 8

    
> Autocomplete: JavaScript API doesn't work
> -----------------------------------------
>
>                 Key: RF-13398
>                 URL: https://issues.jboss.org/browse/RF-13398
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # open browser console
> # run in console RichFaces.component("form:autocomplete").disable()
> result:
> * the method fails with this error:
> {code}
> TypeError: Cannot call method 'attr' of undefined
> {code}
> * the method enable() doesn't work as well

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 12:40:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 12:40:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13398) Autocomplete: JavaScript
	API doesn't work
In-Reply-To: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526554.1385735522000.38914.1385746806223@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927645#comment-12927645 ] 

Luk?? Fry? commented on RF-13398:
---------------------------------

Upstream issue: https://github.com/richwidgets/richwidgets/issues/151
                
> Autocomplete: JavaScript API doesn't work
> -----------------------------------------
>
>                 Key: RF-13398
>                 URL: https://issues.jboss.org/browse/RF-13398
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # open browser console
> # run in console RichFaces.component("form:autocomplete").disable()
> result:
> * the method fails with this error:
> {code}
> TypeError: Cannot call method 'attr' of undefined
> {code}
> * the method enable() doesn't work as well

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 12:59:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 12:59:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13398) Autocomplete: JavaScript
	API doesn't work
In-Reply-To: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526554.1385735522000.38919.1385747945983@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927646#comment-12927646 ] 

Luk?? Fry? commented on RF-13398:
---------------------------------

Other API methods should work as expected.
                
> Autocomplete: JavaScript API doesn't work
> -----------------------------------------
>
>                 Key: RF-13398
>                 URL: https://issues.jboss.org/browse/RF-13398
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # open browser console
> # run in console RichFaces.component("form:autocomplete").disable()
> result:
> * the method fails with this error:
> {code}
> TypeError: Cannot call method 'attr' of undefined
> {code}
> * the method enable() doesn't work as well

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 12:59:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 12:59:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13398) Autocomplete: JavaScript
	API doesn't work
In-Reply-To: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526554.1385735522000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526554.1385735522000.38929.1385747946397@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13398.
-----------------------------

    Resolution: Done

    
> Autocomplete: JavaScript API doesn't work
> -----------------------------------------
>
>                 Key: RF-13398
>                 URL: https://issues.jboss.org/browse/RF-13398
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 5.0.0.Alpha2
>         Environment: RichFaces 5.0.0-SNAPSHOT
>            Reporter: Pavol Pitonak
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocomplete.xhtml
> # open browser console
> # run in console RichFaces.component("form:autocomplete").disable()
> result:
> * the method fails with this error:
> {code}
> TypeError: Cannot call method 'attr' of undefined
> {code}
> * the method enable() doesn't work as well

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 13:12:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 13:12:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13395) Showcase 4.5.x,
	input number slider
In-Reply-To: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526458.1385650061000.38947.1385748725834@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927651#comment-12927651 ] 

Luk?? Fry? commented on RF-13395:
---------------------------------

In the console, I can se:;
{code}
19:04:53,404 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "richfaces-showcase.war" (runtime-name : "richfaces-showcase.war")
19:05:01,245 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost/127.0.0.1:8080-3) JSF1064: Unable to find or serve resource, jquery.position.js.
19:08:19,785 WARNING [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost/127.0.0.1:8080-6) JSF1064: Unable to find or serve resource, jquery.position.js.
{code}
                
> Showcase 4.5.x, input number slider
> -----------------------------------
>
>                 Key: RF-13395
>                 URL: https://issues.jboss.org/browse/RF-13395
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.5.0.Alpha1
>         Environment: JBoss AS 7.1
> Firefox 25
>            Reporter: Matej Novotny
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186].
> It is about a RF 4.5.x Showcase.
> The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186.
> {code}
> <context-param>
>         <param-name>javax.faces.PROJECT_STAGE</param-name>
>         <param-value>Production</param-value>
> </context-param>
> {code}
> Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code).
> {code}
> Uncaught TypeError: Object [object Object] has no method 'setPosition'      inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145
> {code}
> The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub.
> Otherwise I found no problems/errors/warnings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 13:18:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 13:18:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13395) Showcase 4.5.x,
	input number slider
In-Reply-To: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526458.1385650061000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526458.1385650061000.38951.1385749085842@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13395.
-----------------------------

    Resolution: Done


Resource library corrected.
                
> Showcase 4.5.x, input number slider
> -----------------------------------
>
>                 Key: RF-13395
>                 URL: https://issues.jboss.org/browse/RF-13395
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.5.0.Alpha1
>         Environment: JBoss AS 7.1
> Firefox 25
>            Reporter: Matej Novotny
>            Assignee: Luk?? Fry?
>            Priority: Blocker
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> This is a follow-up issue to [https://issues.jboss.org/browse/RF-13186].
> It is about a RF 4.5.x Showcase.
> The bug only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid JSF bug mentioned in RF-13186.
> {code}
> <context-param>
>         <param-name>javax.faces.PROJECT_STAGE</param-name>
>         <param-value>Production</param-value>
> </context-param>
> {code}
> Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code).
> {code}
> Uncaught TypeError: Object [object Object] has no method 'setPosition'      inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145
> {code}
> The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/resources/META-INF/resources/org.richfaces/inputNumberSlider.js#L145] line on GitHub.
> Otherwise I found no problems/errors/warnings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 13:37:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 13:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.38965.1385750226300@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927656#comment-12927656 ] 

Luk?? Fry? commented on RF-12224:
---------------------------------

Hey Jiri, I have re-verified and file upload works for me in latest Showcase 4.5 and 5.0 built from sources on EAP 6.1.1.

It also works on latest Showcase uploaded online:
http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky
                
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>              Labels: needs-qe
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 13:37:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 13:37:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.38974.1385750226626@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927656#comment-12927656 ] 

Luk?? Fry? edited comment on RF-12224 at 11/29/13 1:35 PM:
-----------------------------------------------------------

Hey Jiri, I have re-verified and file upload works for me in latest Showcase 4.5 and 5.0 built from sources on EAP 6.1.1 with Firefox 25 and Chrome 31.

It also works on latest Showcase uploaded online:
http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky
                
      was (Author: lfryc):
    Hey Jiri, I have re-verified and file upload works for me in latest Showcase 4.5 and 5.0 built from sources on EAP 6.1.1.

It also works on latest Showcase uploaded online:
http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky
                  
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>              Labels: needs-qe
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 13:37:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 13:37:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.38986.1385750227029@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927656#comment-12927656 ] 

Luk?? Fry? edited comment on RF-12224 at 11/29/13 1:36 PM:
-----------------------------------------------------------

Hey Jiri, I have re-verified and file upload works for me in latest Showcase 4.5 and 5.0 built from sources on EAP 6.1.1 with Firefox 25 and Chrome 31.

It also works on latest Showcase uploaded online:
http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky

I have verified by putting breakpoint into listener method:
https://github.com/richfaces/richfaces/blob/master/examples/showcase/src/main/java/org/richfaces/demo/fileupload/FileUploadBean.java#L50
                
      was (Author: lfryc):
    Hey Jiri, I have re-verified and file upload works for me in latest Showcase 4.5 and 5.0 built from sources on EAP 6.1.1 with Firefox 25 and Chrome 31.

It also works on latest Showcase uploaded online:
http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=fileUpload&skin=blueSky
                  
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>              Labels: needs-qe
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 13:37:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 13:37:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.38995.1385750227361@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-12224.
-----------------------------

    Resolution: Done

    
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>              Labels: needs-qe
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 13:37:07 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 13:37:07 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.39004.1385750227659@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927658#comment-12927658 ] 

Luk?? Fry? commented on RF-12224:
---------------------------------

Resolving issues as I cannot reproduce the failure.
                
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>              Labels: needs-qe
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 13:39:06 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 13:39:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-12224) fileUpload: Multiple
	file selection
In-Reply-To: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12465468.1335949093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12465468.1335949093000.39012.1385750346212@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927658#comment-12927658 ] 

Luk?? Fry? edited comment on RF-12224 at 11/29/13 1:37 PM:
-----------------------------------------------------------

Resolving this issue as I cannot reproduce the failure.
                
      was (Author: lfryc):
    Resolving issues as I cannot reproduce the failure.
                  
> fileUpload: Multiple file selection
> -----------------------------------
>
>                 Key: RF-12224
>                 URL: https://issues.jboss.org/browse/RF-12224
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-input
>    Affects Versions: 4.2.1.Final
>            Reporter: Anthony O.
>            Assignee: Luk?? Fry?
>              Labels: needs-qe
>             Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> Is it possible to support multiple file selection in the selection box as it was possible with RF 3 ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 13:48:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 29 Nov 2013 13:48:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-6678) RichFaces Select
 components: implement disabled state support for selectItem
In-Reply-To: <JIRA.12383309.1238663780000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12383309.1238663780000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12383309.1238663780000.39020.1385750886000@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-6678:
------------------------------

    Assignee:     (was: Brian Leathem)

    
> RichFaces Select components: implement disabled state support for selectItem
> ----------------------------------------------------------------------------
>
>                 Key: RF-6678
>                 URL: https://issues.jboss.org/browse/RF-6678
>             Project: RichFaces
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: component-selects
>    Affects Versions: 4.0.0.Milestone5
>            Reporter: Ilya Shaikovsky
>             Fix For: 5-Tracking
>
>
> components:
> inplaceSelect
> select
> In future we should support the same in:
> listShuttle
> orderingList
> note: s:selectItems disabled attribute should also works fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 13:50:05 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 29 Nov 2013 13:50:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13397) a4j:push not working
 with Internet Explorer >= 10
In-Reply-To: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526502.1385709468000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526502.1385709468000.39024.1385751005953@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13397:
-------------------------------

    Fix Version/s: 4.3.5

    
> a4j:push not working with Internet Explorer >= 10
> -------------------------------------------------
>
>                 Key: RF-13397
>                 URL: https://issues.jboss.org/browse/RF-13397
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: showcase
>    Affects Versions: 4.3.4
>         Environment: Any where Internet Explorer 10 or above is available
>            Reporter: Tobias Seppenhauser
>              Labels: richfaces
>             Fix For: 4.3.5
>
>
> The <a4j:push> mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. 
> Unfortunately I can't see any error in the Javascript console.
> [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&skin=blueSky

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 13:50:06 2013
From: jira-events at lists.jboss.org (Brian Leathem (JIRA))
Date: Fri, 29 Nov 2013 13:50:06 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13394) Toggle control:
 attributes targetItem and targetPanel don't work
In-Reply-To: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526442.1385647291000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526442.1385647291000.39033.1385751006382@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Leathem updated RF-13394:
-------------------------------

    Labels: regression  (was: )

    
> Toggle control: attributes targetItem and targetPanel don't work
> ----------------------------------------------------------------
>
>                 Key: RF-13394
>                 URL: https://issues.jboss.org/browse/RF-13394
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-panels-layout-themes, regression
>    Affects Versions: 4.5.0.Alpha1
>         Environment: RichFaces 4.5.0-SNAPSHOT
> Metamer 4.5.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 31.0.1650.57 @ Linux x86_64
>            Reporter: Pavol Pitonak
>              Labels: regression
>             Fix For: 4.5.0.Alpha1
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richToggleControl/accordion.xhtml
> # set targetPanel=panel2
> # set targetItem=item3
> # click on "universal toggle control" button
> result:
> * nothing happens
> * third item on second panel should be active
> * when you change targetPanel and/or targetItem and press the button again, it is switched to panel2/item3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From jira-events at lists.jboss.org  Fri Nov 29 14:47:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 14:47:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13399) RichFaces can't be built
	with Maven 3.1.1
In-Reply-To: <JIRA.12526566.1385754370749@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526566.1385754370749@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526566.1385754370749.39043.1385754425870@jira02.app.mwc.hst.phx2.redhat.com>

Luk?? Fry? created RF-13399:
-------------------------------

             Summary: RichFaces can't be built with Maven 3.1.1
                 Key: RF-13399
                 URL: https://issues.jboss.org/browse/RF-13399
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: build/distribution
    Affects Versions: 5.0.0.Alpha2
            Reporter: Luk?? Fry?
            Assignee: Luk?? Fry?
             Fix For: 5.0.0.Alpha2




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 14:47:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 14:47:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13399) RichFaces can't be built
	with Maven 3.1.1
In-Reply-To: <JIRA.12526566.1385754370000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526566.1385754370000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526566.1385754370000.39045.1385754425989@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927661#comment-12927661 ] 

Luk?? Fry? commented on RF-13399:
---------------------------------

Can be fixed by tweaking plugin configuration:

{code}

                            <classpathScope>compile</classpathScope>
                            <includeProjectDependencies>true</includeProjectDependencies>
{code}
                
> RichFaces can't be built with Maven 3.1.1
> -----------------------------------------
>
>                 Key: RF-13399
>                 URL: https://issues.jboss.org/browse/RF-13399
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: build/distribution
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 15:51:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 15:51:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13399) RichFaces can't be built
	with Maven 3.1.1
In-Reply-To: <JIRA.12526566.1385754370000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526566.1385754370000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526566.1385754370000.39079.1385758265818@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/RF-13399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927661#comment-12927661 ] 

Luk?? Fry? edited comment on RF-13399 at 11/29/13 3:49 PM:
-----------------------------------------------------------

Can be fixed by tweaking plugin configuration:

{code}

                            <classpathScope>compile</classpathScope>
{code}
                
      was (Author: lfryc):
    Can be fixed by tweaking plugin configuration:

{code}

                            <classpathScope>compile</classpathScope>
                            <includeProjectDependencies>true</includeProjectDependencies>
{code}
                  
> RichFaces can't be built with Maven 3.1.1
> -----------------------------------------
>
>                 Key: RF-13399
>                 URL: https://issues.jboss.org/browse/RF-13399
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: build/distribution
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


From jira-events at lists.jboss.org  Fri Nov 29 15:51:05 2013
From: jira-events at lists.jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Fri, 29 Nov 2013 15:51:05 -0500 (EST)
Subject: [richfaces-issues] [JBoss JIRA] (RF-13399) RichFaces can't be built
	with Maven 3.1.1
In-Reply-To: <JIRA.12526566.1385754370000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12526566.1385754370000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12526566.1385754370000.39080.1385758265852@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/RF-13399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luk?? Fry? resolved RF-13399.
-----------------------------

    Resolution: Done

    
> RichFaces can't be built with Maven 3.1.1
> -----------------------------------------
>
>                 Key: RF-13399
>                 URL: https://issues.jboss.org/browse/RF-13399
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: build/distribution
>    Affects Versions: 5.0.0.Alpha2
>            Reporter: Luk?? Fry?
>            Assignee: Luk?? Fry?
>             Fix For: 5.0.0.Alpha2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira