[JBoss JIRA] (RF-13256) Push does not work in Firefox 17
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13256?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13256:
----------------------------
Summary: Push does not work in Firefox 17 (was: CDI Push does not work in Firefox 17)
> Push does not work in Firefox 17
> --------------------------------
>
> Key: RF-13256
> URL: https://issues.jboss.org/browse/RF-13256
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.4
> Reporter: Oliver Kišš
> Fix For: 4.3.5
>
>
> CDI Push does not work in Firefox 17.
> To reproduce, see [CDI Push sample |http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&sample=pushCdi&skin=blueSky] in Richfaces Showcase. Added messages are not visible in the Messages Consumer window.
> I could not see any errors in the developer console
--
This message is automatically generated by JIRA.
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-11309) form authentication broken
by John Manko (JIRA)
[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ]
John Manko commented on RF-11309:
---------------------------------
This is still a problem in Richfaces 4.3.4.Final
> form authentication broken
> --------------------------
>
> Key: RF-11309
> URL: https://issues.jboss.org/browse/RF-11309
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 4.0.0.Final
> Environment: jboss-6.0.0.Final, richfaces-4.0.0.Final, Firefox 4 & 5
> Reporter: Radim Hanus
> Fix For: 5-Tracking
>
> Attachments: jsf2demo-original.zip, jsf2demo-updated-mapping.zip
>
>
> described in forum thread in a great detail, simple war to reproduce enclosed as well
> *steps to deploy the test application to JBoss AS 7.0.2* (from forum)
> # download and extract jsf2demo.zip (see attachments)
> # package contained maven project
> # add a security domain into standalone.xml:
> {code}
> <security-domain name="jmx-console">
> <authentication>
> <login-module code="UsersRoles" flag="required">
> <module-option name="usersProperties" value="${jboss.server.config.dir}/jmx-console-users.properties"/>
> <module-option name="rolesProperties" value="${jboss.server.config.dir}/jmx-console-roles.properties"/>
> </login-module>
> </authentication>
> </security-domain>
> {code}
> # copy both *jmx-console-users.properties* and *jmx-console-roles.properties* from jboss-6.0.0.Final/server/default/conf/props to jboss7/standalone/configuration
> # deplot packaged WAR file
--
This message is automatically generated by JIRA.
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-13276) Optimized resources should be generated into generated-resources
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13276?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13276:
-------------------------------
Sprint: 5.0.0.Alpha2 - Sprint 3
> Optimized resources should be generated into generated-resources
> ----------------------------------------------------------------
>
> Key: RF-13276
> URL: https://issues.jboss.org/browse/RF-13276
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 5.0.0.Alpha1
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> The execution of org.richfaces.resource.optimizer.GenerateResourcesMain places the generated resources directly into the _target/classes_ folder. Rather, the generated resources should be placed into _target/generated-resources_.
--
This message is automatically generated by JIRA.
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-13276) Optimized resources should be generated into generated-resources
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13276?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13276:
------------------------------------
Ideally we would generate the resources in the _generate-resources_ phase. And copy them in the _process-resources_. However we cannot generate the optimized resources until after the _GenerateResourcesMain_ class has been compiled.
To resolve this chicken/egg problem, I have split the _build-helper-maven-plugin_ execution into 2 parts. The first continues to copy all non-resources sources in the _process-resources_ phase, and the second copies the resource sources in the _process-classes_ phase. Not ideal, but it works.
Note: this solution requires the maven plugin execution order to be deterministic, as we have 2 plugins executing in the same phase. This is expected to be true for maven >= 3.0.3 (MNG-2258). If however the plugin execution does turn out to be none-deterministic (due to some outstanding bug) we can move the resource optimisation execution to a later maven phase.
> Optimized resources should be generated into generated-resources
> ----------------------------------------------------------------
>
> Key: RF-13276
> URL: https://issues.jboss.org/browse/RF-13276
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 5.0.0.Alpha1
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> The execution of org.richfaces.resource.optimizer.GenerateResourcesMain places the generated resources directly into the _target/classes_ folder. Rather, the generated resources should be placed into _target/generated-resources_.
--
This message is automatically generated by JIRA.
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-13276) Optimized resources should be generated into generated-resources
by Brian Leathem (JIRA)
Brian Leathem created RF-13276:
----------------------------------
Summary: Optimized resources should be generated into generated-resources
Key: RF-13276
URL: https://issues.jboss.org/browse/RF-13276
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: resource handling
Affects Versions: 5.0.0.Alpha1
Reporter: Brian Leathem
Assignee: Brian Leathem
Fix For: 5.0.0.Alpha2
The execution of org.richfaces.resource.optimizer.GenerateResourcesMain places the generated resources directly into the _target/classes_ folder. Rather, the generated resources should be placed into _target/generated-resources_.
--
This message is automatically generated by JIRA.
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-13272) Manage the RichFaces jquery.js dependency with RichWidgets
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13272?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13272:
-------------------------------
Fix Version/s: 5.0.0.Alpha3
(was: 5.0.0.Alpha2)
> Manage the RichFaces jquery.js dependency with RichWidgets
> ----------------------------------------------------------
>
> Key: RF-13272
> URL: https://issues.jboss.org/browse/RF-13272
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: third-party
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The jQuery UI dependencies are currently set within RichWidgets and copied into RichFaces via a grunt task.
> The jQuery.js dpendency should be similarly managed. While making this change, the jQuery.js library should be changed to _com.jquery_.
--
This message is automatically generated by JIRA.
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-13272) Manage the RichFaces jquery.js dependency with RichWidgets
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13272?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13272:
-------------------------------
Sprint: (was: 5.0.0.Alpha2 - Sprint 3)
> Manage the RichFaces jquery.js dependency with RichWidgets
> ----------------------------------------------------------
>
> Key: RF-13272
> URL: https://issues.jboss.org/browse/RF-13272
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: third-party
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The jQuery UI dependencies are currently set within RichWidgets and copied into RichFaces via a grunt task.
> The jQuery.js dpendency should be similarly managed. While making this change, the jQuery.js library should be changed to _com.jquery_.
--
This message is automatically generated by JIRA.
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-13272) Manage the RichFaces jquery.js dependency with RichWidgets
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13272?page=com.atlassian.jira.plugin.s... ]
Brian Leathem edited comment on RF-13272 at 10/21/13 9:42 AM:
--------------------------------------------------------------
RichFaces 4.5 uses jQuery from RichFaces core (now part of RichFaces 5 framework). With this update we will need to be sure we don't break the 4.5 UI components.
RichFaces 4.5 use of _jQuery.browser_ will be the most difficult to remove. We may want to just keep RichFaces 4.5 components using the jQuery Migrate plugin indefinitely.
was (Author: bleathem):
RichFaces 4.5 uses jQuery from RichFaces core (now part of RichFaces 5 framework). With this update we will need to be sure we don't break the 4.5 UI components.
> Manage the RichFaces jquery.js dependency with RichWidgets
> ----------------------------------------------------------
>
> Key: RF-13272
> URL: https://issues.jboss.org/browse/RF-13272
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: third-party
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The jQuery UI dependencies are currently set within RichWidgets and copied into RichFaces via a grunt task.
> The jQuery.js dpendency should be similarly managed. While making this change, the jQuery.js library should be changed to _com.jquery_.
--
This message is automatically generated by JIRA.
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