Fóruns

Início » Liferay Portal » English » 3. Development

Visualização combinada Visão plana Exibição em árvore
Tópicos [ Anterior | Próximo ]
Mostrando 1 - 20 de 45 resultados.
de 3
Balazs Zsoldos
Working Richfaces portlet available
11 de Agosto de 2010 14:58
Resposta

Balazs Zsoldos

Ranking: Junior Member

Mensagens: 41

Data de entrada: 11 de Abril de 2006

Mensagens recentes

Hi,

I uploaded a Richfaces portlet that works for me to the Liferay community plugin page.
It works with Glassfish and Tomcat as well.

I hope others will like the solution and in the future we will always have working Richfaces portlets for each version of Liferay.

You can find the plugin here.

Regards,
Balazs
Laurens van der Blom
RE: Working Richfaces portlet available
12 de Agosto de 2010 03:05
Resposta

Laurens van der Blom

Ranking: New Member

Mensagens: 11

Data de entrada: 6 de Agosto de 2010

Mensagens recentes

Thanks, this might be what I need for deploying JSF portlets containig RichFaces. I'm having a lot of difficulties in getting it to work, especially when ADF comes into play.

However, upon clicking the download link, I'm prompted for a username and password in order to log into the Maven repository. Instead, this link (last line of the page has the correct download link) might be better until the repository is clear of access restrictions.

I'll let you know how it goes with the portlet on my Tomcat server.
Balazs Zsoldos
RE: Working Richfaces portlet available
12 de Agosto de 2010 08:51
Resposta

Balazs Zsoldos

Ranking: Junior Member

Mensagens: 41

Data de entrada: 11 de Abril de 2006

Mensagens recentes

Hi,

due to some reason the security settings on the web site were changed. The download link should work now well.

Also it is possible now to install the plugin at "control panel/Plugin Installation" page in an own Liferay instance.

Please let me know if something does not work as it would be nice to find it out before going live with any project. Thanks!

Regards,
Balazs
Henrique Simoes de Andrade
RE: Working Richfaces portlet available
12 de Agosto de 2010 10:48
Resposta

Henrique Simoes de Andrade

Ranking: Regular Member

Mensagens: 165

Data de entrada: 30 de Abril de 2010

Mensagens recentes

Hi!
It's a great example and works fine in LR 5.2.3, I was looking for something like this a long time ago.
Thanks!

sorry my English... ehe
Balazs Zsoldos
RE: Working Richfaces portlet available
12 de Agosto de 2010 11:21
Resposta

Balazs Zsoldos

Ranking: Junior Member

Mensagens: 41

Data de entrada: 11 de Abril de 2006

Mensagens recentes

Hi,

I am happy to hear that it works also in 5.2.3. In that version I must mention the followings:

You might have realized that the menu of Liferay does not work well. This is because the version of jquery in Liferay 5.2.3 is not compatible fully with the version of Richfaces jquery.

To fix it:
- Go into richfaces-impl.jar
- Find the file jquery.js
- Delete the content of jquery.js

With this Richfaces only downloads an empty jquery.js file so the on comes with Liferay will be the stronger. There are some components in Richfaces that have problems with the Liferay jquery version. For exampl the rich:calendar component works but you cannot set the hour and minutes in it.

Regards,
Balazs
Balazs Zsoldos
RE: Working Richfaces portlet available
12 de Agosto de 2010 18:43
Resposta

Balazs Zsoldos

Ranking: Junior Member

Mensagens: 41

Data de entrada: 11 de Abril de 2006

Mensagens recentes

Hi,

I have just uploaded a new version of the war that contains a new richfaces-impl.jar
The difference is that I copied to the end of prototype.js the patch available at the issue tracker of prototype . This fixes the issue that poller servlet is throwing exceptions when prototype.js is loaded (richfaces portlet is on the page)
The issue is also noted in this post.
Laurens van der Blom
RE: Working Richfaces portlet available
13 de Agosto de 2010 00:26
Resposta

Laurens van der Blom

Ranking: New Member

Mensagens: 11

Data de entrada: 6 de Agosto de 2010

Mensagens recentes

I can confirm it works on Liferay 6.0.4 CE on Tomcat 6.0.29. However, due to my Tomcat configuration, I had trouble loading your portlet. I have different kinds of libraries installed in the tomcat/lib folder, which apparently conflicted with yours in the portlet. Removing the conflicting libraries solved it.

Moreover, deployment goes without problems, but when adding the portlet to the portal in the same session, I get the following exception and the portlet fails to load:

  1
  2ERROR [SerializableSessionAttributeListener:39] com.liferay.samplesffacelets.bean.UserBean is not serializable and will prevent this session frombeing replicated
  3ERROR [InsertTag:922] ServletException in '/html/common/themes/porlet.jsp': File "/pages/view.jsf" not found
  4javax.servlet.ServletException: File "/pages/view.jsf" not found
  5        at org.apache.jasper.servlet.JspServlet.handleMissingResource(JspServle.java:335)
  6        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:01)
  7        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
  8        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
  9        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(AppicationFilterChain.java:290)
 10        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationilterChain.java:206)
 11        at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisatcher.java:646)
 12        at org.apache.catalina.core.ApplicationDispatcher.doInclude(Applicationispatcher.java:551)
 13        at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDipatcher.java:488)
 14        at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrar.java:968)
 15        at org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.jaa:621)
 16        at com.liferay.portal.kernel.servlet.PageContextWrapper.include(PageConextWrapper.java:147)
 17        at org.apache.struts.tiles.TilesUtilImpl.doInclude(TilesUtilImpl.java:9)
 18        at org.apache.struts.tiles.TilesUtil.doInclude(TilesUtil.java:135)
 19        at org.apache.struts.taglib.tiles.InsertTag.doInclude(InsertTag.java:76)
 20        at org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsetTag.java:892)
 21        at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:462)
 22        at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(render005fportlet_jsp.java:1848)
 23        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
 24        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 25        at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrappe.java:377)
 26        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:13)
 27        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
 28        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 29        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(AppicationFilterChain.java:290)
 30        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationilterChain.java:206)
 31        at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisatcher.java:646)
 32        at org.apache.catalina.core.ApplicationDispatcher.doInclude(Applicationispatcher.java:551)
 33        at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDipatcher.java:488)
 34        at com.liferay.portal.util.PortalImpl.renderPortlet(PortalImpl.java:364)
 35        at com.liferay.portal.util.PortalImpl.renderPortlet(PortalImpl.java:360)
 36        at com.liferay.portal.util.PortalUtil.renderPortlet(PortalUtil.java:115)
 37        at com.liferay.portal.action.RenderPortletAction.execute(RenderPortletAtion.java:85)
 38        at com.liferay.portal.action.UpdateLayoutAction.addPortlet(UpdateLayoutAction.java:260)
 39        at com.liferay.portal.action.UpdateLayoutAction.execute(UpdateLayoutAction.java:211)
 40        at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
 41        at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
 42        at com.liferay.portal.struts.PortalRequestProcessor.process(PortalRequestProcessor.java:152)
 43        at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
 44        at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
 45        at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 46        at com.liferay.portal.servlet.MainServlet.callParentService(MainServlet.java:502)
 47        at com.liferay.portal.servlet.MainServlet.service(MainServlet.java:479)
 48        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 49        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 50        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 51        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 52        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:107)
 53        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 54        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 55        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 56        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:107)
 57        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 58        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 59        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 60        at com.liferay.portal.servlet.filters.strip.StripFilter.processFilter(StripFilter.java:259)
 61        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:104)
 62        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 63        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 64        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 65        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:107)
 66        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 67        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 68        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 69        at com.liferay.portal.servlet.filters.gzip.GZipFilter.processFilter(GZipFilter.java:126)
 70        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:104)
 71        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 72        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 73        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 74        at com.liferay.portal.servlet.filters.secure.SecureFilter.processFilter(SecureFilter.java:204)
 75        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:104)
 76        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 77        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 78        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 79        at com.liferay.portal.servlet.filters.sso.ntlm.NtlmPostFilter.processFilter(NtlmPostFilter.java:81)
 80        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:104)
 81        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 82        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 83        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 84        at com.liferay.portal.sharepoint.SharepointFilter.processFilter(SharepointFilter.java:179)
 85        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:104)
 86        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 87        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 88        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 89        at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.processFilter(VirtualHostFilter.java:241)
 90        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:104)
 91        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 92        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 93        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 94        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:107)
 95        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 96        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 97        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
 98        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:107)
 99        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
100        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
101        at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:738)
102        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
103        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
104        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:177)
105        at com.liferay.portal.servlet.filters.threadlocal.ThreadLocalFilter.processFilter(ThreadLocalFilter.java:35)
106        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:104)
107        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
108        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
109        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
110        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
111        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470)
112        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
113        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
114        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
115        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
116        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
117        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
118        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
119        at java.lang.Thread.run(Unknown Source)


Restarting the Tomcat server fixes it and the portlet loads fine. I'll use your work to find out whether ADF can be used as well, as that's what I'm having lots of trouble with (see my thread, if you want).
Balazs Zsoldos
RE: Working Richfaces portlet available
13 de Agosto de 2010 02:51
Resposta

Balazs Zsoldos

Ranking: Junior Member

Mensagens: 41

Data de entrada: 11 de Abril de 2006

Mensagens recentes

Hi,

I do not know about library conflicts as for tests I use clean Liferay. A played a lot around having Richfaces and it's dependencies in the classpath of the Application server. It worked but as my main target is Glassfish V3 the classloading mechanism is much more complicated there due to the possibility of modularization.

the first error about Serialization can be solved if the UserBean implements Serializable. It is only necessary if the managed bean is in session scope. However the portlet works with this error as well. I will upload a modified version that will have a Serializable UserBean.

The second error only happens when somebody places out the portlet onto the screen. There is no need to restart the server only to refresh the page. It seems that the AJAX based portlet insert of Liferay does not like this portlet. An <ajaxable>false</ajaxable> in liferay-portlet.xml can help on this however for me it was more confortable to press an F5 in the browser after placing the portlet out emoticon. In the future if I have some time I might check why this happens.

Regards,
Balazs
Laurens van der Blom
RE: Working Richfaces portlet available
13 de Agosto de 2010 04:35
Resposta

Laurens van der Blom

Ranking: New Member

Mensagens: 11

Data de entrada: 6 de Agosto de 2010

Mensagens recentes

Thanks for your reply.

I figured you'd use a clean version of Tomcat and Liferay for testing purposes. Upon discovering that conflict, I simply deleted the libraries temporarily, effectively reverting the server back to default and it worked. You'll probably know how cumbersome it can be to find out which libraries are supposed to be used for an application and which are not. I had it too when working with ADF 11g on Tomcat. emoticon

It's good to know that a server restart is not necessary to fix that last error. Thanks for the tip. emoticon

You did a nice job with this sample application.
Sergej Logis
RE: Working Richfaces portlet available
1 de Setembro de 2010 07:35
Resposta

Sergej Logis

Ranking: New Member

Mensagens: 4

Data de entrada: 9 de Junho de 2010

Mensagens recentes

I totally agree! Huge THANKS for your work, Balazs! emoticon

Look, maybe you can check my post and see if you can help me on this one? Right now I'm doing research for a new long-term project, and I must choose which technology to incorporate for our portlets - Wicket or JSF (RichFaces or ICEFaces). Also, maybe you have a word on the choice between RichFaces and ICEFaces?
I would be very grateful for any of your help! Thanks in advance.
Balazs Zsoldos
RE: Working Richfaces portlet available
8 de Setembro de 2010 17:17
Resposta

Balazs Zsoldos

Ranking: Junior Member

Mensagens: 41

Data de entrada: 11 de Abril de 2006

Mensagens recentes

Hi,

sorry, I forgot about the question about RichFaces and ICEFaces.

I did not use ICEFaces much. My colleagues used it for a project because there were an ICEFaces portlet available at that time. However just before the end of the project they switched everything to RichFaces due to a bug they could not solve faster than converting to the other technology. The bug was that if multiple users visited the same page the ajax requests seemed to be randomly use the other user's session. It was pretty strange emoticon The conclusion was that it is not impossible to do the switch on the end of a project as the components are almost the same. And luckily we used the MVC patter that is described at http://blog.icefaces.org/blojsom/blog/default/2009/04/23/Making-distinctions-between-different-kinds-of-JSF-managed-beans/ so biggest part of the code remained jsf implementation independent.

I guess that bug has been solved since. We discussed it at that time and we got the impression that ICEFaces hides the AJAX calls a bit more from the developer. There were many AJAX calls and without looking into the javascript of the component we did not know why and when. This is not a bad behavior but we felt that we could not have control over the happenings.

For me at least RichFaces components seem to be a bit more logical, they do what I expect and they send AJAX calls when I expect. Also the a4j:support tag that came with Ajax4Jsf seems to become now a basic tag in JSF2. It is called differently however it is the same.

As I do not have much experience with ICEFaces I think it is important to ask somebody who has. What I can say is that both of them are buggy but if somebody does not afraid to look into the source code it is not such a big problem. The most important question is which one will have better support in the future. I do not know about ICEFaces but RichFaces seems to have a pretty big community or at least the source in SVN changes rapidly.


Regards,
Balazs
Angelo Immediata
RE: Working Richfaces portlet available
8 de Outubro de 2010 03:51
Resposta

Angelo Immediata

Ranking: Junior Member

Mensagens: 34

Data de entrada: 8 de Fevereiro de 2010

Mensagens recentes

Hi Balazs

I'm using this environment:

  • Richfaces 3.3.3 final
  • Spring 3.0.4 for bean definition
  • Liferay 5.2.3


Well when i deploy a portlet built by richfaces and portlet bridge 1.0 i saw that Liferay javascripts no more work (the menu is not working, the drag and drop is no more working and so on) when i change page and i go in a page where no richfaces portlet is present all works pretty good
I think it's a JQuery conflicts problem but how may i solve it? In liferay 6 all works pretty good (both richfaces portlet and the liferay javascripts) i tried your sample too but in liferay 5.2.3 i have the described error....Do you have any ideas?

Regards,
Angelo
Balazs Zsoldos
RE: Working Richfaces portlet available
8 de Outubro de 2010 04:20
Resposta

Balazs Zsoldos

Ranking: Junior Member

Mensagens: 41

Data de entrada: 11 de Abril de 2006

Mensagens recentes

Hi Angelo,

in Liferay 5.2.3 a different version of JQuery is used as in Richfaces. The only solution is if you use only the one that Liferay uses.

To do that you must go into Richfaces-impl.jar, find the jquery.js file and delete the content of it.

With this solution only the Liferay Jquery is downloaded and most of the Richfaces components will work with that version. Some of them will have problems as they need newer JQuery. For example the rich:calendar component works but you cannot set the hour and minutes in the popup window.

In Liferay 6.x this is not a problem anymore as Liferay does not use JQuery in this version.

Regards,
Balazs
jGofio code code
RE: Working Richfaces portlet available
14 de Outubro de 2010 02:23
Resposta

jGofio code code

Ranking: New Member

Mensagens: 22

Data de entrada: 3 de Novembro de 2009

Mensagens recentes

Hi Balazs,

first congratulation for your contribution to Liferay + RichFaces Community.

I have created an application based on your example portlet and all is ok BUT I have problem with tab panel component and modal dialogs...

I'm using Liferay 6.0.4, GlassFish 2.1.1 and these libraries:
portletbridge-api-2.0.1-SNAPSHOT.jar
portletbridge-impl-2.0.1.everit-SNAPSHOT.jar
richfaces-api-3.3.3.Final.jar
richfaces-impl-3.3.3.patched.jar
richfaces-ui-3.3.3.Final.jar
jsf-facelets-1.1.15.jar
jsf-api-1.2_14.jar
jsf-impl-1.2_14.jar

The problems are:
  • Tab component works with switchType="server", but doesn't work using client or ajax switch type, if you click nothings happens...
  • Modal Dialogs give you a blank screen when they are shown.

I can avoid using modal dialog... but tabs are important for me...

Did you have find a solution for these issues??

If you don't have a solution but have tips about solving theses problems I can try and share with the community...

Thanks in advance!!

jGofio
Balazs Zsoldos
RE: Working Richfaces portlet available
14 de Outubro de 2010 02:36
Resposta

Balazs Zsoldos

Ranking: Junior Member

Mensagens: 41

Data de entrada: 11 de Abril de 2006

Mensagens recentes

Hi,

for me it is really funny that we were suffering due to a very similar problem yesterday and today I got a message that others met the same issue.

We tried to open a modalpanel from within tabs. We found out the followings:

- The modalpanel appears but on the modalpanel nothing works.
- If we use ajax tab navigation after we change the tab at least ones everything works fine.
- If we use componentControl to hide the modalpanel we get a blank screen. This is because due to some reason compoenentcontrol sets a "display:none" on the body tag of the full html page.
- Similar problems when we use server side tab navigation with the difference that a tab change does not solve the problem (as the full page is re-rendered)

We have not tried it but if this problem does not occur when using a simple JSF application (without Liferay) then I guess the problem is related to incompatibility with one of javascript libraries that is brought by Liferay.

As we have a really close due date in the project we could not spend much time investigating the issue so we simply avoiding the use of modal panels and have simple page navigation and hope that this will not occur in the next release of richfaces.

However if you find a solution in the future I would be really happy if you could share emoticon.

Withing the next weeks we will not have time to investigate this problem.

Regards,
Balazs
jGofio code code
RE: Working Richfaces portlet available
14 de Outubro de 2010 05:46
Resposta

jGofio code code

Ranking: New Member

Mensagens: 22

Data de entrada: 3 de Novembro de 2009

Mensagens recentes

Hi Balazs,

I have found a way to show the modal dialogs... It's a workaround, I hope it will help you and the rest of the community...

The modal dialog fails (at least for me) if it was shown from h:outputLink. Using h:commandLink is working, here is an example:

1
2  <h:commandLink id="lnkEdit" value="edit" immediate="true" onclick="return false;">
3      <rich:componentControl for="mpEditH" event="onmouseup" operation="show" />                        
4  </h:commandLink> 



HOWEVER, I still have problems with Tabs. My tabs are not in a modal dialog. The tabs work until you make an ajax call in the page, in example a4j:support, then when you click on the tab the panel doesn't change.

Any ideas?

Regards!
Balazs Zsoldos
RE: Working Richfaces portlet available
14 de Outubro de 2010 05:54
Resposta

Balazs Zsoldos

Ranking: Junior Member

Mensagens: 41

Data de entrada: 11 de Abril de 2006

Mensagens recentes

Hi,

showing the modalpanel was not such a big problem for us but hiding it was not really possible emoticon
No ajax calls or any other call worked after a modalpanel was shown.

What took some time to find out before was that there cannot be h:form tag around modalpanel, and it might be true for the tabs as well. (For modalpanel it is in the manual but who reads the full manual always emoticon)

Regards,
Balazs
jGofio code code
RE: Working Richfaces portlet available
15 de Outubro de 2010 04:39
Resposta

jGofio code code

Ranking: New Member

Mensagens: 22

Data de entrada: 3 de Novembro de 2009

Mensagens recentes

Hi,

after some tests, the real problem is that all works ok until a reRender is done after an ajax request. Then certain components (tabs panel, a4j:queue) start
to fail (looks like the javascript related to the components doesn't work).

You can see this behaviour even in your example portlet (Sample Richfaces JSF 1.2 Sun Facelets 6.0.4.2). If you put a tabpanel at the end of the view.xhtml all goes fine until you write a name, then the reRender is executed and the tabs will fail (reload the page solve the problem till the next rerender).

Make a application without ajax and rerenders limit too much...

Have you avoid this problem or have any tips?

Thanks in advance for listen to me! ;)

regards.
jGofio
Ayorinde Afolayan
RE: Working Richfaces portlet available
18 de Novembro de 2010 02:48
Resposta

Ayorinde Afolayan

Ranking: New Member

Mensagens: 5

Data de entrada: 16 de Junho de 2010

Mensagens recentes

Hello Balazs Zsoldos ,

If there is anything making me switch over to using richfaces in liferay, then it's you! I had gave up until i tried your example(it worked fine---i even used it with spring 3,JPA). Now after investing time and trust into it, i suddenly came to this showstopper! The problem is that whenever i add two or more portlets having menu on a page, only the first one is enabled, the rest just feel disabled kind of.

Please kindly help on this.

Once again am using this medium to say a very big thank you for making it possible to use richfaces in liferay 6.05
Balazs Zsoldos
RE: Working Richfaces portlet available
18 de Novembro de 2010 03:57
Resposta

Balazs Zsoldos

Ranking: Junior Member

Mensagens: 41

Data de entrada: 11 de Abril de 2006

Mensagens recentes

Hi,

I am happy that others are using the same solution as we do. That means for me that it will live a long time (I mean Richfaces and Liferay combo).

For this problem I would have only a couple of idea at the moment as I am very busy (working on weekends as well...):
  • Maybe adding rich:page to wrap the portlet helps. Some of the components does not work if the portlet response does not contain html, head and body elements. Not a nice solution but browsers can handle it.
  • Using f:subview with unique id. Everything that is under a subview will get an id like subviewId:xxx. With that you can be sure that the ids in the page are unique and they do not hit the other portlet.
  • Reconstructing the menu and portlets: Having two different liferay subpage for each portlet. I know this is not the nices solution for you. However we designed our pages always to have only one function portlet on it with Richfaces technology. This was because portlets cannot access each others session attributes anyway.
  • Using a page and put two iframe portlets within it, that point to your richfaces portlets (that are placed on hidden pages). Also not the nicest but in this case I am pretty sure both portlets will work on the same page.


I am sorry if non of this fits to your needs. I can try something not before the end of next week as we have a project deadline at that time.

Regards,
Balazs
Mostrando 1 - 20 de 45 resultados.
de 3