tags:

views:

197

answers:

2

I'm a complete noob when it comes to portlet development. I have a task which is to take a fairly small static html site and incorporate it into a portal/portlet environment.

My first thought is to develop one portlet that contains the entire html site within it.

Is this just a terrible idea?

If not, then I know I could make a simple portlet with an iframe to pull in the html for the site, but is there some other way to make a portlet that is a full functional little website?

Any help is greatly appreciated.

A: 

That's a pretty vague question, but I don't see why ou can't do what you're trying to do.

The Portlet API is pretty unpleasant, though, and makes the servlet API look fluffy and joyous. I suggest using Spring's Portlet MVC support to make it a bit less painful.

skaffman
Yeah, I guess that is pretty vague. I get that typical portlets are more like widgets for small little apps for simple things like pulling in your local weather or pulling in stock quotes (things of that nature) and that a portal would house these little apps. But what I am tasked with is taking a fully functional website (let's even say something like stackoverflow) and pull the whole thing into a single portlet that can be run inside pretty much any portal server. Is that any more clear?
Mike M
A: 

I dont think that you can and want "put" a whole website into a portlet because of the limitations of the api. Even if the website is servlet based that seems not to be a good idea.

From a user perspective you should perhaps focus on your widget idea. Think about a smaller subset that encapsules the functionality of the website that should be embedded or write an aggregator for the information of the site.

Think about why the website should be integrated and which information of the site are the most important ones. Perhaps there are any other information exchange interfaces like rss or atom feeds that you can use.

Another solution would be to use an existing cms-like portlet that can be "filled" with content. Here are some examples: http://www.jboss.org/portletswap/portlets%5Fcollab.html

MrWhite
Yeah, in all the research I am doing I am starting to find that trying to put an entire website into a portlet really is not what it is designed for. But the idea still intrigues me. Lets say that I am required to build a pretty robust website/webapp that could be deployed on pretty much any portal server out there. For instance my entire webapp could simply be dropped into a company's intranet portal server.
Mike M