jsr168 - Developer IT

How to change portlet mode outside processAction (jsr168)?

- by skydreamerr

I'm writing mail client portlet. I would like to show portlet in edit mode for new user and don't allow change this mode while user filling html form.

why jsf is better than struts ?

someone said to me that jsf is better to share information within context, but struts 1.1 can't. In JSR168, if we need to develop a portlet, share information in context is critical. so jsf is better option. so what is share information within context ? Does that mean that different application deployed in the same container can share date ? Or what other means ?

Read the article

What Java portal server do you use?

- by bpapa

I've been tasked with learning Vignette and setting it up is a nightmare. There are many different components in the wizard. If something fails, you get a cryptic error message and then have to start again. This is the worst "Wizard" since Kwame Brown. Are there other Portal servers out there that are easy to configure, or at least seem to have kept a developer's sanity in mind during configuration? To those that have used several different portal servers, which is your favorite?

Read the article

How can I get the client IP in a JSR168 Portlet?

- by danimajo

How can I get the IP of the Client (request) in a JSR168 Portlet? I'm on Liferay 5.2.3 I can get the IP with Liferay internal functionality: String ip = com.liferay.portal.util.PortalUtil.getHttpServletRequest(renderRequest).getRemoteAddr(); Is there any portal neutral way to do this?

Read the article

Portlet container like pluto or jetspeed on google app engine?

- by Patrick Cornelissen

I am trying to build something "portlet server"-ish on the google app engine. (as open source) I'd like to use the JSR168/286 standards, but I think that the restrictions of the app engine will make it somewhere between tricky and impossible. Has anyone tried to run jetspeed or an application that uses pluto internally on the google app engine? Based on my current knowledge of portlets and the google app engine I'm anticipating these problems: A war file with portlets is from the deployment standpoint more or less a complete webapp (yes, I know that it doesn't really work without a portal server). The war file may contain it's own web.xml etc. This makes deployment on the app engine rather difficult, because the apps are not visible to each other, so all portlet containing archives need to be included in the war file of the deployed "app engine based portal server". The "portlets" are (at least in liferay) started as permanent servlet processes, based on their portlet.xmls and web.xmls which is located in the same spot for every portlet archive that is loaded. I think this may be problematic in the app engine, because everything is in one big "web app", so it may be tricky to access the portlet.xmls from each archive. This prevents a 100% compatibility in my opinion. Is here anyone who has any experience with the combination of portlets and the app engine? Do you think it's feasible to modify jetspeed, pluto or any other portlet container to be able to run it on the app engine?

Read the article

pluto or jetspeed on google app engine?

- by Patrick Cornelissen

I am trying to build something "portlet server"-ish on the google app engine. (as open source) I'd like to use the JSR168/286 standards, but I think that the restrictions of the app engine will make it somewhere between tricky and impossible. Has anyone tried to run jetspeed or an application that uses pluto internally on the google app engine? Based on my current knowledge of portlets and the google app engine I'm anticipating these problems: A war file with portlets is from the deployment standpoint more or less a complete webapp (yes, I know that it doesn't really work without a portal server). The war file may contain it's own web.xml etc. This makes deployment on the app engine rather difficult, because the apps are not visible to each other, so all portlet containing archives need to be included in the war file of the deployed "app engine based portal server". The "portlets" are (at least in liferay) started as permanent servlet processes, based on their portlet.xmls and web.xmls which is located in the same spot for every portlet archive that is loaded. I think this may be problematic in the app engine, because everything is in one big "web app", so it may be tricky to access the portlet.xmls from each archive. This prevents a 100% compatibility in my opinion. Is here anyone who has any experience with the combination of portlets and the app engine? Do you think it's feasible to modify jetspeed, pluto or any other portlet container to be able to run it on the app engine?

Developer IT