2 Replies Latest reply on Apr 24, 2006 6:05 PM by rjcarr

    Deploy Portlet ... Am I Missing Something?

      I currently have a JSR-168 portlet that I've been mostly using in WebLogic but at various times has also lived in pluto and jetspeed.

      I'm evaluating JBoss Portal and I cannot figure out how to deploy my portlet to the portal. I've got the JBoss Portal 2.2 and AS bundled edition, and without any config it started right up and seems to work.

      However, I have no idea how to deploy a custom portlet. The best info I've found is the documentation here:

      http://docs.jboss.com/jbportal/v2.2/reference-guide/en/html/xmldescriptors.html

      But there has to be more information available somewhere.

      I see the PortletSwap site has portlets you can grab, but no info about how to install them. I see people talking about "hot deploying" but no mention of how it was done. Am I totally missing something? Or is this information hard to find?

      Thanks in advance.

        • 1. Re: Deploy Portlet ... Am I Missing Something?

          starting from your last question first:
          hot deployment means when the server and portal are already up and runnning, you 'drop' a file into the deploy directory and it is picked up by the server and deployed.
          Each portlet from the PortletSwap has a README file specifying how to be deployed - usually you execute an ant target that will create a war or ear file you need to place in the deploy directory of the server. Now, depending which extension you are using - ear or war, the XML descriptors are different.

          • 2. Re: Deploy Portlet ... Am I Missing Something?

             

            "rali.genova@jboss.com" wrote:
            starting from your last question first:
            hot deployment means when the server and portal are already up and runnning


            Ha ... that wasn't a question! I know what hot deployment means, but I think you've answered me indirectly. It appears that deploying a portlet is done by just dropping it into a directory ... this is the step I had missed.

            As I said, I was missing something obvious, as I predicted ... I'll give it a shot now. Thanks for the quick reply. I'll report back here with any problems.

            Much appreciated.