[richfaces-issues] [JBoss JIRA] (RF-12833) richfaces.js conflicts with prototype.js

[Lukáš Fryč (JIRA)]

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

Lukáš Fryč edited comment on RF-12833 at 4/15/13 6:47 AM:
----------------------------------------------------------

For workaround, you can use the patched version of {{richfaces.js}} from the linked pull request.
(Note that the patch isn't completely correct as of now, but it will work for you).

Use RichFaces Resource Mapping [1] to rewrite original {{richfaces.js}} with the file stored in your own application.

[1] http://lukas.fryc.eu/blog/2012/02/re-routing-jsf-resource-requests-with.html
                
      was (Author: lfryc):
    For workaround, you can use the patched version of {{richfaces.js}} from the linked pull request.
(Note that the patch isn't completely correct as of now).

Use RichFaces Resource Mapping [1] to rewrite original {{richfaces.js}} with the file stored in your own application.

[1] http://lukas.fryc.eu/blog/2012/02/re-routing-jsf-resource-requests-with.html
                  
> richfaces.js conflicts with prototype.js
> ----------------------------------------
>
>                 Key: RF-12833
>                 URL: https://issues.jboss.org/browse/RF-12833
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-a4j-core
>    Affects Versions: 4.3.1
>            Reporter: Mark Torres
>             Fix For: 5-Tracking
>
>
> Getting some javascript errors on richfaces.js.
> Upon inspection, it is using
> (function(jQuery, richfaces) {
> ...
> instead of 
> (function($, richfaces) {
> ...

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