I've spend on this more hours that I can with no result. I've been trying to put this working on my EAR app. They've written their own dialog component, so I have to use p:dialog to get things to work, or else add modules to the PF jquery.js.īTW, if RichFaces ever updates its components to be fully jQuery-UI-compatible (as is proposed), i probably wouldn't be looking at combining the two libraries. I can't, for example, use plain jquery ui dialogs (instantiated from my script files) with only PF's version of jquery.js. But in my project, for now, I also have to edit that PF version of jquery.js to include some vanilla jquery ui components. My solution, so far, is to have RichFaces point to PrimeFaces' jquery.js, for both jquery.js and jquery-ui-core.js. And the fact that they concatenate those two libraries (or parts of them) by default means that you can't just use RichFaces resource mapping to solve the problem. To be a little more concrete about it, I can't just replace PrimeFaces jquery with a combination of CDN-served jquery core and jquery ui - things break. #PRIMEFACES CONTENT APPEARS OUTSIDEOF TABVIEW MANUAL#I've seen that's a future goal for RichFaces, which is great, but unless both projects adopt that same strategy, the combination will remain tricky or a heavily manual process. That wish may be difficult to achieve, if, as in PrimeFaces' case, the custom components are really just leveraging the UI, but not simply wrapping native jQuery UI components. My vote for both libraries would be to either use vanilla jquery core (already the case) and jquery ui (not currently the case), and if something needs to be added for particular functionality/theming of components, that's done in separate files as overrides or additions. One issue is that PrimeFaces concatenates jquery core and (parts of the) jquery ui, so a reference to jquery.js is different for RichFaces and PrimeFaces.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |