[JBoss JIRA] (RF-12628) richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12628?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12628.
--------------------------------
Resolution: Done
Thanks for the feedback Fred,
# resolved: Moved the jboss.bom.version definition into the enterprise=true check
# 4.2.3.Final-redhat-1 will be in the enterprise repo when WFK 2.1 is released. I'll see if I can get a date on that.
> richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
> -----------------------------------------------------------------------
>
> Key: RF-12628
> URL: https://issues.jboss.org/browse/RF-12628
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.2.3.Final
> Reporter: Fred Bricon
> Assignee: Brian Leathem
> Priority: Critical
> Fix For: 4.3.0.M3, 4.2.3.Final
>
>
> When you create a project from richfaces-archetype-kitchensink 4.2.3.Final-1, using the -Denterprise=true flag, there are 2 problems :
> 1 - <jboss.bom.version> points at the community version, it should be <jboss.bom.version>1.0.0.M12-redhat-1</jboss.bom.version>, so that dependencies from the EAP6 repo are added to the classpath
> 2 - <org.richfaces.bom.version>4.2.3.Final-redhat-1</org.richfaces.bom.version> is not found in the Red Hat maven repo : http://maven.repository.redhat.com/techpreview/all/org/richfaces/richface...
> #1 must be fixed before releasing the archetype
> #2 Brian told me 4.2.3.Final-redhat-1 *will* be available in RH's Maven repo eventually, so, in JBoss Tools/JBDS, we can override the value to use the community bits, until 4.2.3.Final-redhat-1 is available (having an ETA on that would be nice).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (RF-12628) richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12628?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12628:
-------------------------------
Fix Version/s: 4.2.3.Final
> richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
> -----------------------------------------------------------------------
>
> Key: RF-12628
> URL: https://issues.jboss.org/browse/RF-12628
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.2.3.Final
> Reporter: Fred Bricon
> Assignee: Brian Leathem
> Priority: Critical
> Fix For: 4.2.3.Final, 4.3.0.M3
>
>
> When you create a project from richfaces-archetype-kitchensink 4.2.3.Final-1, using the -Denterprise=true flag, there are 2 problems :
> 1 - <jboss.bom.version> points at the community version, it should be <jboss.bom.version>1.0.0.M12-redhat-1</jboss.bom.version>, so that dependencies from the EAP6 repo are added to the classpath
> 2 - <org.richfaces.bom.version>4.2.3.Final-redhat-1</org.richfaces.bom.version> is not found in the Red Hat maven repo : http://maven.repository.redhat.com/techpreview/all/org/richfaces/richface...
> #1 must be fixed before releasing the archetype
> #2 Brian told me 4.2.3.Final-redhat-1 *will* be available in RH's Maven repo eventually, so, in JBoss Tools/JBDS, we can override the value to use the community bits, until 4.2.3.Final-redhat-1 is available (having an ETA on that would be nice).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (RF-12604) "Uncaught TypeError: Cannot read property 'name' of null" when double clicking on a a4j:commandButton
by Anthony O. (JIRA)
Anthony O. created RF-12604:
-------------------------------
Summary: "Uncaught TypeError: Cannot read property 'name' of null" when double clicking on a a4j:commandButton
Key: RF-12604
URL: https://issues.jboss.org/browse/RF-12604
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core, component-input
Affects Versions: 4.2.3.Final
Environment: JBoss 7.1.1.Final
Reporter: Anthony O.
Priority: Blocker
I've got a {{a4j:commandButton}} which {{render}} itself and is {{rendered}} if the number of time I've clicked on it is less than 1.
The problem is that when I click twice on it very quickly, then I've got a "Uncaught TypeError: Cannot read property 'name' of null" from {{jsf.js.xhtml}} and then no more AJAX query can be sent from the UI (all the {{a4j:commandButton}} for example do nothing more), and the status is frozen to the {{start}} facet (my progress.gif is never hidden because neither {{onstop}} nor {{onerror}} methods are called).
Here is the JS stack :
{noformat}
Uncaught TypeError: Cannot read property 'name' of null jsf.js.xhtml:1
request jsf.js.xhtml:1
richfaces.queue.submitFirstEntry richfaces-queue.js.xhtml:270
richfaces.queue.onComplete richfaces-queue.js.xhtml:248
sendEvent jsf.js.xhtml:1
response jsf.js.xhtml:1
richfaces.queue.response richfaces-queue.js.xhtml:413
jsf.ajax.response richfaces-queue.js.xhtml:50
onComplete jsf.js.xhtml:1
req.xmlReq.onreadystatechange jsf.js.xhtml:1
{noformat}
I will attach test.xhtml & TestAction.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
11 years, 8 months
[JBoss JIRA] (RF-11992) cache bug in portlet
by Ivan Ravin (JIRA)
Ivan Ravin created RF-11992:
-------------------------------
Summary: cache bug in portlet
Key: RF-11992
URL: https://issues.jboss.org/browse/RF-11992
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.0.CR1, 3.3.3.Final
Environment: jboss portal 2.7.2; Gatein portal
Reporter: Ivan Ravin
On Jboss and Gatein portal richfaces cant be cached when user is logged in.
Bug is found for richfaces 3.3.3 but i think can be reproduced for 4.x because org.richfaces.resource.AbstractCacheableResource has similar code.
The steps for reproduce bug are:
download portlet bridge 2.2 archive
deploy richFacesPortlet.war from portlet bridge archive (i used jboss portal 2.7.2 bundle and GateIn-3.1.0-FINAL-jbossas)
look at network activity (i did with firefox + firebug, the same result on any other browser). Just open page with richfaces portlet.
When user is not logged in, all richfaces resources are caching well, and this is headers returned by server:
|Cache-Control |max-age=86400|
|Content-Type |text/javascript|
|Date |Thu, 26 Jan 2012 17:57:39 GMT|
|Expires |27 Jan 2012 17:57:39 GMT|
|Last-Modified |26 Jan 2012 17:42:17 GMT|
|Server |Apache-Coyote/1.1|
|X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0|
But when user is logged in all richfaces stuff come from network every time (more than 1.3 mb).
This is headers returned by portal 2.7.2 when user logged in:
|Cache-Control |{color:red}no-cache,{color} max-age=86400|
|Content-Type |text/javascript|
|Date |Thu, 26 Jan 2012 18:26:49 GMT|
|Expires |{color:red}Thu, 01 Jan 1970 03:00:00 MSK,{color} 27 Jan 2012 18:26:49 GMT|
|Last-Modified |26 Jan 2012 18:05:56 GMT|
|{color:red}Pragma{color} |{color:red}No-cache{color}|
|Server |Apache-Coyote/1.1|
|Transfer-Encoding |chunked|
|X-Powered-By |Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0|
The same problem with GateIn-3.1.0-FINAL-jbossas bundle, but now only one wrong header:
|Cache-Control |max-age=86400|
|Content-Type |text/javascript;charset=UTF-8|
|Date |Sat, 28 Jan 2012 08:54:14 GMT|
|Expires |29 Jan 2012 08:54:14 GMT|
|Last-Modified |28 Jan 2012 08:51:11 GMT|
|{color:red}Pragma{color} |{color:red}No-cache{color}|
|Server |Apache-Coyote/1.1|
|Transfer-Encoding |chunked|
|X-Powered-By |Servlet 2.5; JBoss-5.0/JBossWeb-2.1|
This header (Pragma) appears only when user is logged in, and again, all richfaces resources come through network.
I did some debug and found that bridge create good headers, but there is some code in portal which put wrong values into real response before richfaces. I cant find this code in portal sources, so maybe it is JBoss AS problem, or third party component.
Gatein portal overwrite 2 wrong headers with values provided by richfaces, but "pragma" header is absent in richfaces response, and this way in secured portlets richfaces generate too much unnesessary traffic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (RF-12628) richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12628?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12628:
-------------------------------
Sprint: 4.3.0.M3 - Quick Issue Sprint
> richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
> -----------------------------------------------------------------------
>
> Key: RF-12628
> URL: https://issues.jboss.org/browse/RF-12628
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.2.3.Final
> Reporter: Fred Bricon
> Assignee: Brian Leathem
> Priority: Critical
> Fix For: 4.3.0.M3
>
>
> When you create a project from richfaces-archetype-kitchensink 4.2.3.Final-1, using the -Denterprise=true flag, there are 2 problems :
> 1 - <jboss.bom.version> points at the community version, it should be <jboss.bom.version>1.0.0.M12-redhat-1</jboss.bom.version>, so that dependencies from the EAP6 repo are added to the classpath
> 2 - <org.richfaces.bom.version>4.2.3.Final-redhat-1</org.richfaces.bom.version> is not found in the Red Hat maven repo : http://maven.repository.redhat.com/techpreview/all/org/richfaces/richface...
> #1 must be fixed before releasing the archetype
> #2 Brian told me 4.2.3.Final-redhat-1 *will* be available in RH's Maven repo eventually, so, in JBoss Tools/JBDS, we can override the value to use the community bits, until 4.2.3.Final-redhat-1 is available (having an ETA on that would be nice).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (RF-12628) richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12628?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12628:
-------------------------------
Fix Version/s: 4.3.0.M3
> richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
> -----------------------------------------------------------------------
>
> Key: RF-12628
> URL: https://issues.jboss.org/browse/RF-12628
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.2.3.Final
> Reporter: Fred Bricon
> Fix For: 4.3.0.M3
>
>
> When you create a project from richfaces-archetype-kitchensink 4.2.3.Final-1, using the -Denterprise=true flag, there are 2 problems :
> 1 - <jboss.bom.version> points at the community version, it should be <jboss.bom.version>1.0.0.M12-redhat-1</jboss.bom.version>, so that dependencies from the EAP6 repo are added to the classpath
> 2 - <org.richfaces.bom.version>4.2.3.Final-redhat-1</org.richfaces.bom.version> is not found in the Red Hat maven repo : http://maven.repository.redhat.com/techpreview/all/org/richfaces/richface...
> #1 must be fixed before releasing the archetype
> #2 Brian told me 4.2.3.Final-redhat-1 *will* be available in RH's Maven repo eventually, so, in JBoss Tools/JBDS, we can override the value to use the community bits, until 4.2.3.Final-redhat-1 is available (having an ETA on that would be nice).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (RF-12628) richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12628?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12628:
-------------------------------
Priority: Critical (was: Major)
> richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
> -----------------------------------------------------------------------
>
> Key: RF-12628
> URL: https://issues.jboss.org/browse/RF-12628
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.2.3.Final
> Reporter: Fred Bricon
> Priority: Critical
> Fix For: 4.3.0.M3
>
>
> When you create a project from richfaces-archetype-kitchensink 4.2.3.Final-1, using the -Denterprise=true flag, there are 2 problems :
> 1 - <jboss.bom.version> points at the community version, it should be <jboss.bom.version>1.0.0.M12-redhat-1</jboss.bom.version>, so that dependencies from the EAP6 repo are added to the classpath
> 2 - <org.richfaces.bom.version>4.2.3.Final-redhat-1</org.richfaces.bom.version> is not found in the Red Hat maven repo : http://maven.repository.redhat.com/techpreview/all/org/richfaces/richface...
> #1 must be fixed before releasing the archetype
> #2 Brian told me 4.2.3.Final-redhat-1 *will* be available in RH's Maven repo eventually, so, in JBoss Tools/JBDS, we can override the value to use the community bits, until 4.2.3.Final-redhat-1 is available (having an ETA on that would be nice).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (RF-12628) richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12628?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12628:
----------------------------------
Assignee: Brian Leathem
> richfaces-archetype-kitchensink 4.2.3.Final-1 is not "enterprise" ready
> -----------------------------------------------------------------------
>
> Key: RF-12628
> URL: https://issues.jboss.org/browse/RF-12628
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: examples
> Affects Versions: 4.2.3.Final
> Reporter: Fred Bricon
> Assignee: Brian Leathem
> Priority: Critical
> Fix For: 4.3.0.M3
>
>
> When you create a project from richfaces-archetype-kitchensink 4.2.3.Final-1, using the -Denterprise=true flag, there are 2 problems :
> 1 - <jboss.bom.version> points at the community version, it should be <jboss.bom.version>1.0.0.M12-redhat-1</jboss.bom.version>, so that dependencies from the EAP6 repo are added to the classpath
> 2 - <org.richfaces.bom.version>4.2.3.Final-redhat-1</org.richfaces.bom.version> is not found in the Red Hat maven repo : http://maven.repository.redhat.com/techpreview/all/org/richfaces/richface...
> #1 must be fixed before releasing the archetype
> #2 Brian told me 4.2.3.Final-redhat-1 *will* be available in RH's Maven repo eventually, so, in JBoss Tools/JBDS, we can override the value to use the community bits, until 4.2.3.Final-redhat-1 is available (having an ETA on that would be nice).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months