[JBoss JIRA] (RF-10618) autocomplete: unnesessary request on item selection
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-10618?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-10618:
-------------------------------
Description:
{code}
<h:form>
<rich:autocomplete mode="cachedAjax" tokens=", " minChars="0"
autoFill="false" selectFirst="false" id="ac2"
value="#{autocompleteBean.svalue}" var="a"
autocompleteList="#{autocompleteBean.autocompleteList}">
</rich:autocomplete>
<h:outputText value="#{autocompleteBean.svalue}" id="out2" />
</h:form>
{code}
# focus input
# type a - Ajax request sent and list populated - OK
# select first item. - item selected and one more Ajax request sent. - FAIL. no need in one more request.
This one is minor and I believe future. minor because in that case list returned not according to "a" letter but all the states starting on different letters.
was:
{code}
<h:form>
<rich:autocomplete mode="cachedAjax" tokens=", " minChars="0"
autoFill="false" selectFirst="false" id="ac2"
value="#{autocompleteBean.svalue}" var="a"
autocompleteList="#{autocompleteBean.autocompleteList}">
</rich:autocomplete>
<h:outputText value="#{autocompleteBean.svalue}" id="out2" />
</h:form>
{code}
focus input
type a - Ajax request sent and list populated - OK
select first item. - item selected and one more Ajax request sent. - FAIL. no need in one more request.
This one is minor and I believe future. minor because in that case list returned not according to "a" letter but all the states starting on different letters.
> autocomplete: unnesessary request on item selection
> ---------------------------------------------------
>
> Key: RF-10618
> URL: https://issues.jboss.org/browse/RF-10618
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Milestone6
> Reporter: Ilya Shaikovsky
> Assignee: Nick Belaevski
> Priority: Minor
> Fix For: 5-Future
>
>
> {code}
> <h:form>
> <rich:autocomplete mode="cachedAjax" tokens=", " minChars="0"
> autoFill="false" selectFirst="false" id="ac2"
> value="#{autocompleteBean.svalue}" var="a"
> autocompleteList="#{autocompleteBean.autocompleteList}">
> </rich:autocomplete>
> <h:outputText value="#{autocompleteBean.svalue}" id="out2" />
> </h:form>
> {code}
> # focus input
> # type a - Ajax request sent and list populated - OK
> # select first item. - item selected and one more Ajax request sent. - FAIL. no need in one more request.
> This one is minor and I believe future. minor because in that case list returned not according to "a" letter but all the states starting on different letters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-9340) autocomplete, select, and inplaceSelect not sharing any js for popup functionality.
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-9340?page=com.atlassian.jira.plugin.sy... ]
Brian Leathem resolved RF-9340.
-------------------------------
Fix Version/s: (was: 5-Future)
Resolution: Won't Fix
The client-side implementation of these components is being replaced with RichWidgets in RichFaces 5.
> autocomplete, select, and inplaceSelect not sharing any js for popup functionality.
> -----------------------------------------------------------------------------------
>
> Key: RF-9340
> URL: https://issues.jboss.org/browse/RF-9340
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: component-input, optimization
> Affects Versions: 4.0.0.Milestone3
> Reporter: Ilya Shaikovsky
>
> there should be some object which fully responsible for popup list representation construction and show/hide/select item inside functionality.
> for now Anton do not get the autocomplete script as he reviewed it and it has additional functionality which relies on the fact that it based on input. (intering inside causes filtering in list and so on)
> So both components for now has it's own impl for popup functionlity.
> I believe critical as such impls breaks "clean-up" and "improve design" ideas for 4.x
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-10618) autocomplete: unnesessary request on item selection
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-10618?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-10618:
------------------------------------
[~lfryc] is this issue now obsolete with the new RF 5 widget implementation?
> autocomplete: unnesessary request on item selection
> ---------------------------------------------------
>
> Key: RF-10618
> URL: https://issues.jboss.org/browse/RF-10618
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Milestone6
> Reporter: Ilya Shaikovsky
> Assignee: Nick Belaevski
> Priority: Minor
> Fix For: 5-Future
>
>
> <h:form>
> <rich:autocomplete mode="cachedAjax" tokens=", " minChars="0"
> autoFill="false" selectFirst="false" id="ac2"
> value="#{autocompleteBean.svalue}" var="a"
> autocompleteList="#{autocompleteBean.autocompleteList}">
> </rich:autocomplete>
> <h:outputText value="#{autocompleteBean.svalue}" id="out2" />
> </h:form>
> focus input
> type a - Ajax request sent and list populated - OK
> select first item. - item selected and one more Ajax request sent. - FAIL. no need in one more request.
> This one is minor and I believe future. minor because in that case list returned not according to "a" letter but all the states starting on different letters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-10618) autocomplete: unnesessary request on item selection
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-10618?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-10618:
-------------------------------
Description:
{code}
<h:form>
<rich:autocomplete mode="cachedAjax" tokens=", " minChars="0"
autoFill="false" selectFirst="false" id="ac2"
value="#{autocompleteBean.svalue}" var="a"
autocompleteList="#{autocompleteBean.autocompleteList}">
</rich:autocomplete>
<h:outputText value="#{autocompleteBean.svalue}" id="out2" />
</h:form>
{code}
focus input
type a - Ajax request sent and list populated - OK
select first item. - item selected and one more Ajax request sent. - FAIL. no need in one more request.
This one is minor and I believe future. minor because in that case list returned not according to "a" letter but all the states starting on different letters.
was:
<h:form>
<rich:autocomplete mode="cachedAjax" tokens=", " minChars="0"
autoFill="false" selectFirst="false" id="ac2"
value="#{autocompleteBean.svalue}" var="a"
autocompleteList="#{autocompleteBean.autocompleteList}">
</rich:autocomplete>
<h:outputText value="#{autocompleteBean.svalue}" id="out2" />
</h:form>
focus input
type a - Ajax request sent and list populated - OK
select first item. - item selected and one more Ajax request sent. - FAIL. no need in one more request.
This one is minor and I believe future. minor because in that case list returned not according to "a" letter but all the states starting on different letters.
> autocomplete: unnesessary request on item selection
> ---------------------------------------------------
>
> Key: RF-10618
> URL: https://issues.jboss.org/browse/RF-10618
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.0.0.Milestone6
> Reporter: Ilya Shaikovsky
> Assignee: Nick Belaevski
> Priority: Minor
> Fix For: 5-Future
>
>
> {code}
> <h:form>
> <rich:autocomplete mode="cachedAjax" tokens=", " minChars="0"
> autoFill="false" selectFirst="false" id="ac2"
> value="#{autocompleteBean.svalue}" var="a"
> autocompleteList="#{autocompleteBean.autocompleteList}">
> </rich:autocomplete>
> <h:outputText value="#{autocompleteBean.svalue}" id="out2" />
> </h:form>
> {code}
> focus input
> type a - Ajax request sent and list populated - OK
> select first item. - item selected and one more Ajax request sent. - FAIL. no need in one more request.
> This one is minor and I believe future. minor because in that case list returned not according to "a" letter but all the states starting on different letters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ]
Brian Leathem edited comment on RF-13250 at 10/9/13 1:03 PM:
-------------------------------------------------------------
[~ppitonak] do we have any load tests in place that can be used to reproduce this issue? If not, we should ask [~MilovdZee] for a sample we can use as the basis for such a test.
was (Author: bleathem):
[~ppitonak] do we have any load tests in place that can be used to reproduce this issue? If not, we should ask [~MilovdZee] for a sample we can use to build such a test.
> Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
> --------------------------------------------------------------
>
> Key: RF-13250
> URL: https://issues.jboss.org/browse/RF-13250
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
> Reporter: Milo van der Zee
> Assignee: Pavol Pitonak
> Labels: memoryleak
>
> Hello,
> I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
> I also started seeing this message lot's of times:
> {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
> I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
> In the crashed system heap dump I see a lot of:
> - AtomicBoolean (751.000, 15.0MB)
> - ConcurrentLinkedQueue
> - AtmospereRequest$Builder (60.042, 13.8MB)
> To me it looks like it has something to do with Atmosphere. Any ideas?
> Thanks,
> Milo van der Zee
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13250:
----------------------------------
Assignee: Pavol Pitonak
[~ppitonak] do we have any load tests in place that can be used to reproduce this issue? If not, we should ask [~MilovdZee] for a sample we can use to build such a test.
> Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
> --------------------------------------------------------------
>
> Key: RF-13250
> URL: https://issues.jboss.org/browse/RF-13250
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
> Reporter: Milo van der Zee
> Assignee: Pavol Pitonak
> Labels: memoryleak
>
> Hello,
> I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
> I also started seeing this message lot's of times:
> {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
> I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
> In the crashed system heap dump I see a lot of:
> - AtomicBoolean (751.000, 15.0MB)
> - ConcurrentLinkedQueue
> - AtmospereRequest$Builder (60.042, 13.8MB)
> To me it looks like it has something to do with Atmosphere. Any ideas?
> Thanks,
> Milo van der Zee
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13250:
------------------------------------
[~MilovdZee] can you check of you do you see this issue when you use Mojarra as well?
> Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
> --------------------------------------------------------------
>
> Key: RF-13250
> URL: https://issues.jboss.org/browse/RF-13250
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5
> Reporter: Milo van der Zee
> Labels: memoryleak
>
> Hello,
> I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone.
> I also started seeing this message lot's of times:
> {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
> I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory.
> In the crashed system heap dump I see a lot of:
> - AtomicBoolean (751.000, 15.0MB)
> - ConcurrentLinkedQueue
> - AtmospereRequest$Builder (60.042, 13.8MB)
> To me it looks like it has something to do with Atmosphere. Any ideas?
> Thanks,
> Milo van der Zee
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13249) PushServlet initialized twice
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13249?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13249:
-------------------------------
Fix Version/s: 5-Tracking
> PushServlet initialized twice
> -----------------------------
>
> Key: RF-13249
> URL: https://issues.jboss.org/browse/RF-13249
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.4
> Reporter: Milo van der Zee
> Priority: Minor
> Labels: push
> Fix For: 5-Tracking
>
>
> In PushServlet of Richfaces 4.3.4 I see there is a flag 'private boolean initialized = false;'. This is done to NOT initialize the servlet multiple times. But the servlet is also initialized to attach the Atmosphere handler. Idea of Lukáš Fryč is to break the init code appart. One to init the servlet and one to connect the Atmosphere handler.
> Also see the forum thread
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (RF-13247) Upgrade the RichFaces guava dependency to version 15.0
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13247?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13247:
-------------------------------
Component/s: third-party
> Upgrade the RichFaces guava dependency to version 15.0
> ------------------------------------------------------
>
> Key: RF-13247
> URL: https://issues.jboss.org/browse/RF-13247
> Project: RichFaces
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Components: third-party
> Reporter: Jeremy Landis
> Priority: Minor
>
> Upgrading to guava 15 from 14.0.1 causes this richfaces error. I have not looked into this further but wanted to put it out there as an issue.
> Caused by: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.richfaces.resource.ResourceLibraryFactoryImpl
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months