portlet

JSR 286 compliant namespace parameter

元气小坏坏 提交于 2019-12-06 12:33:49
In portlet What is the best way to read namespace parameter in action method. My form contains <input id="<portlet:namespace/>param1" name="<portlet:namespace/>param1" value='hello'/> option1: request.getParameter(response.getNamespace() + "param1"); option2: request.getParameter("param1"); option1 does not work in liferay, but does seem will work in websphere. option2 works fine in liferay 6.2. option1 seems to work in before 6.1. Can anyone please tell me what is the jsr 286 compliant way? As I mentioned in a comment of an answer to this question, the problem is with Liferay 6.2 because IBM

Kaleo workflow in custom portlet

南楼画角 提交于 2019-12-06 12:23:13
问题 Steps to create kaleo workflow in custom portlet Liferay 6.1.1 GA2. Hi, I am new to liferay. I am using Liferay 6.1.1 GA2 version. Can somebody please provide me the steps to create workflow in custom portlets with some workable samples. Thanks in advance. 回答1: Add entity in service.xml regarding your workflow portlet. i.e <entity name="XXWorkflow" local-service="true" remote-service="false"> <!-- PK fields --> <column name="workflowId" type="long" primary="true" /> <!-- Foreign key columns -

ERROR: 'ContentNegotiatingViewResolver'of Spring 3.0.3 MVC Portlet+JSON

倖福魔咒の 提交于 2019-12-06 08:12:18
I want to make spring MVC 3.0.3 portlet using DispatcherPortlet class With JSON support. So, i added following configuration in the spring context file. <bean class="org.springframework.web.servlet.view.ContentNegotiatingViewResolver"> text/html Without this, if i use the 'InternalResourceViewResolver' only then it runs fine and i am able to use the portlet. But with this bean defined, i got the following error on tomcat startup. I googled around and find a link stating that this bean with JSON only works with servlets in the latest spring vesion. please check the link as well. http://jira

Item value in JSTL foreach loop not working in Portlet

寵の児 提交于 2019-12-06 07:41:24
Given the following Portlet Code: ArrayList nameList = new ArrayList(); nameList.add("Willi Willisch"); nameList.add("Seppi Seppisch"); renderRequest.setAttribute("names", nameList); And the following JSP Code: <c:forEach var="aName" items="${names}"> <tr> <td>${aName} </td> </tr> </c:forEach> Prints out: ${aName} ${aName} I don't have any clue why a $(aName) isn't evaluated. The forEach loops works, because ${aName} is printed out twice .... <c:out value="${aName}"/> works!! But shouldn't ${aName} work aswell? Thus, "EL in template text" doesn't work? That can have one or more of the

AD sync with Liferay

最后都变了- 提交于 2019-12-06 07:34:26
We have a portal hosted at our side on Liferay and a Active Directory is in sync through LDAP with Liferay. The problem which we are facing is that when the user gets deleted from the AD it neither gets deactivated nor deleted from Liferay. I want the user to be deactivated not deleted from Liferay when deleted from the AD. Although Liferay strongly discourages to deactivate/delete the user when the user is deleted from the AD as there may be dependencies on other user, sites or organisations or unexpected behavior which may be caused. I checked all the required fields which are necessary for

Using jsp:param / c:param in a Portlet Environment

半城伤御伤魂 提交于 2019-12-06 06:35:01
问题 I'm trying to include JSP pages with jsp:param in a Portlet environment (using the Pluto portlet container). for example, <jsp:include page="test.jsp"> <jsp:param name="foo" value="bar"/> </jsp:include> and in test.jsp, <c:out value="${foo}"/> or <%= request.getParameter("foo") %> The output is always null and i've also tried using c tags, but got the same result. <c:import url="test.jsp"> <c:param name="foo" value="bar"/> </c:import> I've searched through the net and many people have faced

File upload in specific folder of web application in liferay..?

牧云@^-^@ 提交于 2019-12-06 03:45:26
I am using liferay 6.0.5. I am uploading file using following code. UploadPortletRequest uploadRequest = PortalUtil.getUploadPortletRequest(actionRequest); String submissionFileName = uploadRequest.getFileName("file");//uploaded filename File submissionFile = uploadRequest.getFile("file"); this works fine and upload file in tomcat's temp directory with some different name. What I want is.."There is one folder docs in my project directory. I want uploaded file in this directory". How to do this in liferay..? If you want to change the temp directory for the file upload then you can change the

Eventing in Liferay Portlets

感情迁移 提交于 2019-12-06 03:39:53
问题 In any portlet application, if the same page containing a portlet is opened in two browser tabs, how is the event in the first page distinguished from the second page? I want to assign a unique Id for each event, store it and append it to the URL so that the link can be shared. Can someone provide their thoughts on this ? Also, if the page URL is opened on other computer the data shown on the page is the same as the data seen on the first computer. This is being set globally. How can I

Passing object list from the action to the render phase

一曲冷凌霜 提交于 2019-12-05 21:03:47
I'm working with spring MVC for portlets, and I found a problem. I need to pass an Object List from the action phase to the render phase. I've tried to use the setRenderParameter, something like this: actionresponse.setRenderParameter(String string, String[] strings); actionresponse.setRenderParameter("myList",myList.toString()); Here we have the two methods: @RequestMapping(params = ACTION_MYACTION) public final void doAction(MyBean search, Errors errors, ActionRequest actionrequest, ActionResponse actionresponse) { String processName = UtilLog.getProcessName(CLASS_NAME, "doAction");

Unable to view deployed Liferay portlet in the add >> more option

一笑奈何 提交于 2019-12-05 20:58:05
问题 I have created a sample Liferay portlet and it has successfully deployed. But, the eclipse console didn't say "1 portlet is ready for use". And, I couldn't find this portlet in the Add >> More.. option on a Liferay page. 回答1: As Mark mentioned, it is undeterministic and it sometimes happen. I usually follow the following steps and after this it works normally. Steps: remove all the references of the portlet from webapps. stop the server deploy the portlet's WAR restart the server check the