Article: Developing Portlets using JSF, Ajax, and Seam (Part 2 of 3)

Posted by Ryan Slobojan on Aug 25, 2008

Community

Java

Topics

Portal/CMS

Tags

JSR 301 ,

AJAX ,

JSF ,

RichFaces ,

JBoss Portlet Container ,

JBoss Portlet Bridge ,

JBoss Portal

This article, the second in a three-part series by Wesley Hales, expands upon the previous article by introducing RichFaces. It covers integrating RichFaces into the previous sample application, deploying a RichFaces portlet, and several features and capabilities of RichFaces.

From the article:

One thing I will explain before we get started is the difference in JBoss Portal installations between this article and the previous one. In the last article we deployed to a JBoss App Server running the lightweight Portlet Container 2.0 demo. Since that article was published, we have released JBoss Portal 2.7 as a beta. This combines the old JSR-168 implementation of JBoss Portal with the new Portlet 2.0 implementation, giving us the ability to run 1.0 and 2.0 portlets in the standard JBoss Portal project. So if keeping track of what version you should be using seems confusing, it's not. Just keep in mind that JBoss Portal 2.7 is the ultimate combination of everything we have to offer and versions 2.6.x are the supported stable releases that only support JSR-168 (portlet 1.0).

Read the full article here.

1. Back to top

   Excellent series so far!

   Aug 25, 2008 5:35 AM by John Haselden

   Thanks Wesley, this has proven to be a great series of articles so far and has arrived just at the right time for the project I'm working on! I can't wait for the third installment.
   
   
   
   John
   
   Thinking in Seam

   Reply

2. Back to top

   Please provide an example to use JBoss Portal services with a4J

   Dec 22, 2008 9:03 AM by vineet tripathi

   The sample application is wonderful to start with implementation of ajax on JSF portlet with JBoss portal. But when i send an ajax request using a4j to a bean action that uses Jboss -portal services , such as instanceContainer, PortalObjectContainer or userModule, i get an exception that says:
   org.hibernate.HibernateException: Unable to locate current JTA transactio
   
   Please provide an example that uses these services with ajax.

   Reply

3. Back to top

   avoid "unable to locate current JTA transaction" for a4j & portal services

   Dec 23, 2008 9:04 AM by vineet tripathi

   I got the solution for using JBoss portal services with a4j. The following is the solution
   1)You need to demarcate your action with a JTA transaction:
   /*
   *
   * Start transaction
   */
   boolean isNewTransaction = true;
   InitialContext ctx=null;
   UserTransaction tx=null;
   try{
   ctx = new InitialContext();
   tx = (UserTransaction)ctx.lookup("UserTransaction");
   System.out.println("transaction tx is>>>>>>>>>>>>>"+tx);
   tx.begin();
   }catch(Exception e){
   System.out.println("Exception occured>>>>>>"+e.getMessage());
   isNewTransaction = false;
   // e.printStackTrace();
   }
   /*
   *
   * Start transaction end
   */
   
   /***Perform your actions by calling the JBoss portal services ****/
   
   /**commit the transaction
   *
   */
   if(isNewTransaction){
   
   try{
   tx.commit();
   System.out.println("Transaction commited *********************");
   }catch(Exception e){
   // log.info("Exception occured");
   System.out.println("Exception>>>>>>"+e.getMessage());
   }
   }
   /**
   * commit the transaction
   */
   If you are creating or destroying a portal object you need to load the object using following method to sync up your VO with Db:
   
   portalObjectContainer.getObject(objectId);

   Reply

• Older >