January 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13469) RF 5 pickList NPE ResourceServletMapping - resource.getLibraryName()

by H G (JIRA)

H G created RF-13469: ------------------------ Summary: RF 5 pickList NPE ResourceServletMapping - resource.getLibraryName() Key: RF-13469 URL: https://issues.jboss.org/browse/RF-13469 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 5.0.0.Alpha2 Environment: WildFly CR1, RF 5 Alpha2, jboss-jsf-api_2.2_spec-2.2.4 WildFly B1, RF 5 Alpha2, jboss-jsf-api_2.2_spec-2.2.3 Firefox 26.0 Reporter: H G Fix For: 5.0.0.Alpha3 An exception is handled. The exception is related to the source code "resource.getLibraryName()" from ResourceServletMapping Link to exception - https://community.jboss.org/message/852156 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13274) Use QSTools:archetypeSync to keep the kitchensink archetype synchronized with the kithensink-rf quickstart

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13274?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13274: ------------------------------------ An initial trial of the qstools archetypeSync plugin with the following configuration looks promising: {code} <plugins> <plugin> <groupId>org.jboss.maven.plugins</groupId> <artifactId>maven-qstools-plugin</artifactId> <version>1.3.2.Final</version> <configuration> <projectGitRepo>git://github.com/richfaces/jdf-quickstarts.git</projectGitRepo> <projectPath>kitchensink-rf</projectPath> <rootPackage>org.jboss.as.quickstarts.kitchensinkrf</rootPackage> <branch>master</branch> <archetypeExpressionReplaceValues> <archetypeExpressionReplaceValue>jboss-kitchensink-rf</archetypeExpressionReplaceValue> <archetypeExpressionReplaceValue>kitchensink quickstart</archetypeExpressionReplaceValue> <archetypeExpressionReplaceValue>JBoss WFK Quickstart: kitchensink-richfaces</archetypeExpressionReplaceValue> </archetypeExpressionReplaceValues> </configuration> <executions> <execution> <phase>generate-sources</phase> <goals> <goal>archetypeSync</goal> </goals> </execution> </executions> </plugin> </plugins> </build> {code} I filed JDF-592 to address the issue of having more control over generating conditionals in the pom. > Use QSTools:archetypeSync to keep the kitchensink archetype synchronized with the kithensink-rf quickstart > ----------------------------------------------------------------------------------------------------------- > > Key: RF-13274 > URL: https://issues.jboss.org/browse/RF-13274 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Fix For: 4.3.5 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > As per [~rafabene]'s description in IRC: > {quote} > use QSTools:archetypeSync to keep your Archetype Synchornized with the kithensink-rf Quickstart as we did for our Archetypes > look at an example here: https://github.com/jboss-developer/jboss-eap-archetypes/blob/master/jboss... > you tell where the quickstart is projectGitRepo projectPath > tell what's your branch or commit or tag > them what's your rootPackage > you can configure expression that will be replaced by $\{artifactId} with archetypeExpressionReplaceValues > so every fix that you make on Quickstarts will be available on your next Archetype build > call me if you have any issues with QSTools:archetypeSync > {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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13203) a4j:queue should have status attribute

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13203?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13203: ------------------------------- Fix Version/s: 5-Tracking (was: 4.3.5) Re-scheduling for implementation in RF 5. We will consider back-porting this to our stable branch once the feature itself has stabilized. > a4j:queue should have status attribute > -------------------------------------- > > Key: RF-13203 > URL: https://issues.jboss.org/browse/RF-13203 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.2 > Reporter: Jonáš Trantina > Labels: gss, queue > Fix For: 5-Tracking > > Original Estimate: 2 days > Remaining Estimate: 2 days > > a4j:queue should have status attribute, so it can connect to a4j:status. Consider the following example: > {noformat} > <a4j:queue name="quick" requestDelay="200" /> > <a4j:queue name="slow" requestDelay="1000" /> > <a4j:status name="quickStatus" startText="Started!" stopText="Stopped"/> > <br/> > <a4j:statusname="slowStatus" startText="Started!" stopText="Stopped" /> > > <h:form> > <a4j:commandButton action="#{test.dummy}" value="Quick"> > <a4j:attachQueue name="quick"/> > </a4j:commandButton> > </h:form> > <br/> > <h:form> > <a4j:commandButton action="#{test.dummy}" value="Slow"> > <a4j:attachQueue name="slow"/> > </a4j:commandButton> > </h:form> > {noformat} > By using the status attr. of a4j:queue, it would be possible to connect "slow" queue to "slowStatus" and thus every component that would be connected to the queue, would also be connected to the status. > Note in this example it would be simpler to set status attr. on the components themselves, but imagine there are more components connected to the queue. > I was also informed, that this functionality was present in RF 3.3. > Workarounds: > - set status attr on every component instead of on the queue- in larger applications this is not doable. > - use a4j:status JS API and a4j:queues' onsubmit and oncomplete methods- onsubmit and oncomplete a4j:queue are not implemented, so not working now -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13208) Push: error "not well-formed" appears in browser console in Firefox

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13208?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13208 at 1/8/14 10:21 AM: ---------------------------------------------------------- Since the response headers don't specify any particular type, we should be okay with transporting basically anything, but it seems that Firefox expects XML (that's probably because the response is padded with HTML comments () by Atmosphere. I'm okay with expanding {{"<message>"}} format to e.g {{"<msg>message</msg>"}}. e.g. {quote} <msg topic="jmsSampleAddress2" number="0">day: 23, month: 9, time: 11:01:12.829</msg> {quote} was (Author: lfryc): Since the response headers don't specify any particular type, we should be okay with transporting basically anything, but it seems that Firefox expects XML (that's probably because the response is padded with HTML comments () by Atmosphere. I'm okay with expanding {{"<message>"}} format to e.g {{"<update>message</update>"}}. e.g. {quote} <msg>"topic":"jmsSampleAddress2","data":"day: 23, month: 9, time: 11:01:12.829","number":0</msg> {quote} Later, we could switch to e.g.: {quote} <msg topic="jmsSampleAddress2" number="0">day: 23, month: 9, time: 11:01:12.829</msg> {quote} > Push: error "not well-formed" appears in browser console in Firefox > ------------------------------------------------------------------- > > Key: RF-13208 > URL: https://issues.jboss.org/browse/RF-13208 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.4 > Environment: RichFaces 4.3.4.Final > Metamer 4.3.4.20130919-Final > Mojarra 2.1.19 > EAP 6.1.1 > OpenJDK Runtime Environment 1.7.0_40-mockbuild_2013_09_19_20_10-b00 @ Linux > Firefox 24.0 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Fix For: 4.3.5, 5.0.0.Alpha3 > > Attachments: firefox_console.png > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://127.0.0.1:8080/metamer/faces/components/a4jPush/twoPush.xhtml > # open browser console > # click "Push 2!" button > result: > * browser console contains "not well-formed" JavaScript error (see screenshot) > * when you click on the error, you can see something like this: > {quote} > <"topic":"jmsSampleAddress2","data":"day: 23, month: 9, time: 11:01:12.829","number":0> > {quote} > * component seems to work fine despite this error > * I couldn't see this error in Chrome 29 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13208) Push: error "not well-formed" appears in browser console in Firefox

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13208?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13208 at 1/8/14 9:52 AM: --------------------------------------------------------- Since the response headers don't specify any particular type, we should be okay with transporting basically anything, but it seems that Firefox expects XML (that's probably because the response is padded with HTML comments () by Atmosphere. I'm okay with expanding {{"<message>"}} format to e.g {{"<update>message</update>"}}. e.g. {quote} <msg>"topic":"jmsSampleAddress2","data":"day: 23, month: 9, time: 11:01:12.829","number":0</msg> {quote} Later, we could switch to e.g.: {quote} <msg topic="jmsSampleAddress2" number="0">day: 23, month: 9, time: 11:01:12.829</msg> {quote} was (Author: lfryc): Since the response headers don't specify any particular type, we should be okay with transporting basically anything, but it seems that Firefox expects XML (that's probably because the response is padded with HTML comments () by Atmosphere. I'm okay with expanding {{"<message>"}} format to e.g {{"<update>message</update>"}}. > Push: error "not well-formed" appears in browser console in Firefox > ------------------------------------------------------------------- > > Key: RF-13208 > URL: https://issues.jboss.org/browse/RF-13208 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.4 > Environment: RichFaces 4.3.4.Final > Metamer 4.3.4.20130919-Final > Mojarra 2.1.19 > EAP 6.1.1 > OpenJDK Runtime Environment 1.7.0_40-mockbuild_2013_09_19_20_10-b00 @ Linux > Firefox 24.0 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Fix For: 4.3.5, 5.0.0.Alpha3 > > Attachments: firefox_console.png > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > # deploy Metamer and open http://127.0.0.1:8080/metamer/faces/components/a4jPush/twoPush.xhtml > # open browser console > # click "Push 2!" button > result: > * browser console contains "not well-formed" JavaScript error (see screenshot) > * when you click on the error, you can see something like this: > {quote} > <"topic":"jmsSampleAddress2","data":"day: 23, month: 9, time: 11:01:12.829","number":0> > {quote} > * component seems to work fine despite this error > * I couldn't see this error in Chrome 29 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13397) a4j:push not working with Internet Explorer >= 10

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-13397. ----------------------------- Resolution: Duplicate Issue > 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: Lukáš Fryč > Labels: needs-qe > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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&sk... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13397) a4j:push not working with Internet Explorer >= 10

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13397 at 1/8/14 9:47 AM: --------------------------------------------------------- The issue seems to be fixed in 4.3.5-SNAPSHOT. I guess that's because of Atmosphere upgrade in RF-13277. QE ([~jhuska]): could you please verify that? was (Author: lfryc): The issue seems to be fixed in 4.3.5-SNAPSHOT. I guess that's because of Atmosphere upgrade in RF-13277. QE ([~ppitonak]): could you please verify that? > 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: Lukáš Fryč > Labels: needs-qe > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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&sk... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13397) a4j:push not working with Internet Explorer >= 10

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13397: ---------------------------- Labels: needs-qe (was: ) > 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: Lukáš Fryč > Labels: needs-qe > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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&sk... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13397) a4j:push not working with Internet Explorer >= 10

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13397: ---------------------------- Labels: (was: richfaces) > 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: Lukáš Fryč > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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&sk... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13397) a4j:push not working with Internet Explorer >= 10

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reopened RF-13397: ----------------------------- > 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: Lukáš Fryč > Labels: richfaces > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > 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&sk... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2014