Fórum
Problem create JSF Portlet
Anderson Mendes dos Santos, modificado 9 Anos atrás.
Problem create JSF Portlet
New Member Postagens: 9 Data de Entrada: 21/08/14 Postagens Recentes
Hello everyone, I'm having trouble creating a project to run JSF Portlet Primefaces, my situation is as follows:
I'm using Liferay Developer Studio 2.0.0, the installation comes SDK 6.2.
I need to create the project for LP EE 6.1, which is running in our production environment.
When I create the project, I select the 6.2 SDK that comes in Developer, and Tomcat 6.1 EE. The error happens when i go to deploy the portlet generates several exceptions. After researching in internet, I realized that you need to modify the configuration files to make reference to the LP EE 6.1, so modified:
liferay-plugin-package.properties
liferay-display.xml
liferay-hook.xml
If I do a project Portlet MVC works normal, but when JSF is generating this exception:
And when I try to change the liferay-portlet.xml file to 6.1 with previous files, the IDE shows this error:
And when I try to change the liferay-portlet.xml file to 6.1 with previous files, IDE shows this error:
If I delete the line:
Makes the deploy, I can add in the portal, but generates various errors JSF
Could anyone help me?
I'm using Liferay Developer Studio 2.0.0, the installation comes SDK 6.2.
I need to create the project for LP EE 6.1, which is running in our production environment.
When I create the project, I select the 6.2 SDK that comes in Developer, and Tomcat 6.1 EE. The error happens when i go to deploy the portlet generates several exceptions. After researching in internet, I realized that you need to modify the configuration files to make reference to the LP EE 6.1, so modified:
liferay-plugin-package.properties
name=Telecom
module-group-id=liferay
module-incremental-version=1
tags=
short-description=
long-description=
change-log=
page-url=http://www.liferay.com
author=Liferay, Inc.
licenses=EE
liferay-versions=6.2.20+
portal-dependency-jars=commons-beanutils.jar,commons-collections.jar,commons-digester.jar,commons-fileupload.jar,commons-io.jar,commons-lang.jar
speed-filters-enabled=falsename=Telecom
module-group-id=liferay
module-incremental-version=1
tags=
short-description=
long-description=
change-log=
page-url=http://www.liferay.com
author=Liferay, Inc.
licenses=EE
liferay-versions=6.1.20
portal-dependency-jars=commons-beanutils.jar,commons-collections.jar,commons-digester.jar,commons-fileupload.jar,commons-io.jar,commons-lang.jar
speed-filters-enabled=falseliferay-display.xml
<!--?xml version="1.0"?-->
<display>
<category name="category.sample">
<portlet id="telecom" />
</category>
</display><!--?xml version="1.0"?-->
<display>
<category name="category.sample">
<portlet id="telecom" />
</category>
</display>liferay-hook.xml
<!--?xml version="1.0"?-->
<hook>
<language-properties>Language_en_US.properties</language-properties>
</hook><!--?xml version="1.0"?-->
<hook>
<language-properties>Language_en_US.properties</language-properties>
</hook>If I do a project Portlet MVC works normal, but when JSF is generating this exception:
Set 24, 2014 4:12:00 PM org.apache.catalina.core.AprLifecycleListener init
INFORMAÇÕES: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre7\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program Files/Java/jre7/bin/client;C:/Program Files/Java/jre7/bin;C:/Program Files/Java/jre7/lib/i386;C:\sybase\DataAccess\ADONET\dll;C:\sybase\DataAccess\OLEDB\dll;C:\sybase\DataAccess\ODBC\dll;C:\sybase\OCS-12_5\lib3p;C:\sybase\OCS-12_5\dll;C:\sybase\OCS-12_5\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\APLICA~1\JUDWIN\DEPLOY;C:\APLICA~1\JUDWIN\DLLS;C:\JUDWIN\DEPLOY;C:\SYBASE\DLL;C:\SYBASE\OCS-12_0;%JAVA_HOME\bin%;D:\Usuários\amesantos\Desktop\liferay-developer-studio\DeveloperStudio;;.
Set 24, 2014 4:12:01 PM org.apache.coyote.AbstractProtocol init
INFORMAÇÕES: Initializing ProtocolHandler ["http-bio-8080"]
Set 24, 2014 4:12:01 PM org.apache.coyote.AbstractProtocol init
INFORMAÇÕES: Initializing ProtocolHandler ["ajp-bio-8009"]
Set 24, 2014 4:12:01 PM org.apache.catalina.startup.Catalina load
INFORMAÇÕES: Initialization processed in 489 ms
Set 24, 2014 4:12:01 PM org.apache.catalina.core.StandardService startInternal
INFORMAÇÕES: Starting service Catalina
Set 24, 2014 4:12:01 PM org.apache.catalina.core.StandardEngine startInternal
INFORMAÇÕES: Starting Servlet Engine: Apache Tomcat/7.0.27
Set 24, 2014 4:12:01 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFORMAÇÕES: Deploying configuration descriptor C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\conf\Catalina\localhost\ROOT.xml
Loading jar:file:/C:/liferay-portal-6.1.20-ee-ga2/tomcat-7.0.27/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/system.properties
Loading jar:file:/C:/liferay-portal-6.1.20-ee-ga2/tomcat-7.0.27/webapps/ROOT/WEB-INF/lib/portal-impl.jar!/portal.properties
Loading file:/C:/liferay-portal-6.1.20-ee-ga2/portal-ide.properties
Loading file:/C:/liferay-portal-6.1.20-ee-ga2/tomcat-7.0.27/webapps/ROOT/WEB-INF/classes/portal-developer.properties
Loading file:/C:/liferay-portal-6.1.20-ee-ga2/portal-setup-wizard.properties
Set 24, 2014 4:12:03 PM org.apache.catalina.core.ApplicationContext log
INFORMAÇÕES: Initializing Spring root WebApplicationContext
16:12:09,284 INFO [pool-2-thread-1][DialectDetector:71] Determine dialect for HSQL Database Engine 2
16:12:09,288 WARN [pool-2-thread-1][DialectDetector:86] Liferay is configured to use Hypersonic as its database. Do NOT use Hypersonic in production. Hypersonic is an embedded database useful for development and demo'ing purposes. The database settings can be changed in portal-ext.properties.
16:12:09,333 INFO [pool-2-thread-1][DialectDetector:136] Found dialect org.hibernate.dialect.HSQLDialect
Starting Liferay Portal Enterprise Edition 6.1.20 EE (Paton / Build 6120 / July 31, 2012)
16:12:34,867 INFO [pool-2-thread-1][BaseDB:452] Database supports case sensitive queries
16:12:35,253 INFO [pool-2-thread-1][LicenseManager:?] Portal Development license validation passed
16:12:35,258 INFO [pool-2-thread-1][ServerDetector:154] Server supports hot deploy
16:12:35,266 INFO [pool-2-thread-1][PluginPackageUtil:1030] Reading plugin package for the root context
16:12:44,162 INFO [pool-2-thread-1][AutoDeployDir:106] Auto deploy scanner started for C:\liferay-portal-6.1.20-ee-ga2\deploy
Set 24, 2014 4:12:47 PM org.apache.catalina.core.ApplicationContext log
INFORMAÇÕES: Initializing Spring FrameworkServlet 'Remoting Servlet'
Set 24, 2014 4:12:49 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFORMAÇÕES: Deploying configuration descriptor C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\conf\Catalina\localhost\telecom-portlet.xml
Set 24, 2014 4:12:49 PM org.apache.catalina.startup.HostConfig deployDescriptor
ADVERTÊNCIA: A docBase C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\webapps\telecom-portlet inside the host appBase has been specified, and will be ignored
Set 24, 2014 4:12:49 PM org.apache.catalina.startup.SetContextPropertiesRule begin
ADVERTÊNCIA: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:telecom-portlet' did not find a matching property.
Set 24, 2014 4:12:49 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFORMAÇÕES: validateJarFile(C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\webapps\telecom-portlet\WEB-INF\lib\el-api-1.0.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
Set 24, 2014 4:12:49 PM com.liferay.faces.portal.listener.StartupListener contextInitialized
INFORMAÇÕES: Context initialized for contextPath=[/telecom-portlet]
Set 24, 2014 4:12:49 PM com.liferay.faces.portal.listener.StartupListener contextInitialized
INFORMAÇÕES: Copied input-editor.jsp from LiferayFaces JAR to context path file=[C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\webapps\telecom-portlet\resources\liferay-ui\jsp\input-editor.jsp]
Set 24, 2014 4:12:49 PM com.liferay.faces.bridge.servlet.BridgeSessionListener contextInitialized
INFORMAÇÕES: Context initialized for contextPath=[/telecom-portlet]
Set 24, 2014 4:12:49 PM com.sun.faces.config.ConfigureListener contextInitialized
INFORMAÇÕES: Inicializando Mojarra 2.1.21 ( 20130409-1421 https://svn.java.net/svn/mojarra~svn/tags/2.1.21@11854) para o contexto '/telecom-portlet'
Set 24, 2014 4:12:49 PM com.sun.faces.spi.InjectionProviderFactory createInstance
INFORMAÇÕES: JSF1048: Anotações PostConstruct/PreDestroy presentes. Os métodos ManagedBeans marcados com essas anotações informarão as anotações processadas.
Set 24, 2014 4:12:51 PM org.primefaces.webapp.PostConstructApplicationEventListener processEvent
INFORMAÇÕES: Running on PrimeFaces 3.5
Set 24, 2014 4:12:51 PM com.sun.faces.config.ConfigureListener$WebConfigResourceMonitor$Monitor <init>
INFORMAÇÕES: Monitoring jndi:/localhost/telecom-portlet/WEB-INF/faces-config.xml for modifications
Set 24, 2014 4:12:51 PM com.sun.faces.lifecycle.ELResolverInitPhaseListener populateFacesELResolverForJsp
INFORMAÇÕES: JSF1027: [null] Os ELResolvers para JSF não foram registrados com o contêiner JSP.
Set 24, 2014 4:12:51 PM org.apache.coyote.AbstractProtocol start
INFORMAÇÕES: Starting ProtocolHandler ["http-bio-8080"]
Set 24, 2014 4:12:51 PM org.apache.coyote.AbstractProtocol start
INFORMAÇÕES: Starting ProtocolHandler ["ajp-bio-8009"]
Set 24, 2014 4:12:51 PM org.apache.catalina.startup.Catalina start
INFORMAÇÕES: Server startup in 50529 ms
16:12:55,162 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:177] Processing telecom-portlet.xml
16:12:55,171 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletExplodedTomcatListener:60] Modifying portlets for C:\liferay-portal-6.1.20-ee-ga2\deploy\telecom-portlet.xml
Copying 1 file to C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\webapps\telecom-portlet\WEB-INF\classes
Copying 1 file to C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\webapps\telecom-portlet\WEB-INF\jsp
Set 24, 2014 4:12:55 PM com.sun.faces.config.ConfigureListener$WebConfigResourceMonitor$Monitor hasBeenModified
INFORMAÇÕES: jndi:/localhost/telecom-portlet/WEB-INF/faces-config.xml changed!
Set 24, 2014 4:12:55 PM com.sun.faces.config.ConfigureListener reload
INFORMAÇÕES: Reloading JSF configuration for context /telecom-portlet
java.lang.NullPointerException
at java.util.ArrayList.<init>(Unknown Source)
at com.sun.faces.application.WebappLifecycleListener.getActiveSessions(WebappLifecycleListener.java:350)
at com.sun.faces.config.ConfigureListener.reload(ConfigureListener.java:510)
at com.sun.faces.config.ConfigureListener.access$600(ConfigureListener.java:122)
at com.sun.faces.config.ConfigureListener$WebConfigResourceMonitor.run(ConfigureListener.java:1039)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Set 24, 2014 4:12:55 PM com.sun.faces.spi.InjectionProviderFactory createInstance
INFORMAÇÕES: JSF1048: Anotações PostConstruct/PreDestroy presentes. Os métodos ManagedBeans marcados com essas anotações informarão as anotações processadas.
Set 24, 2014 4:12:55 PM org.primefaces.webapp.PostConstructApplicationEventListener processEvent
INFORMAÇÕES: Running on PrimeFaces 3.5
Set 24, 2014 4:12:55 PM com.sun.faces.config.ConfigureListener reload
INFORMAÇÕES: Reload complete.
16:12:55,962 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseDeployer:2083] Modifying Servlet 2.5 C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\webapps\telecom-portlet\WEB-INF\web.xml
16:12:55,962 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][PortletExplodedTomcatListener:66] Portlets for C:\liferay-portal-6.1.20-ee-ga2\deploy\telecom-portlet.xml modified successfully
16:12:55,963 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][BaseExplodedTomcatListener:49] Copying file C:\liferay-portal-6.1.20-ee-ga2\deploy\telecom-portlet.xml to C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\conf\Catalina\localhost
Set 24, 2014 4:13:01 PM com.sun.faces.config.ConfigureListener$WebConfigResourceMonitor$Monitor hasBeenModified
INFORMAÇÕES: jndi:/localhost/telecom-portlet/WEB-INF/faces-config.xml changed!
Set 24, 2014 4:13:01 PM com.sun.faces.config.ConfigureListener reload
INFORMAÇÕES: Reloading JSF configuration for context /telecom-portlet
Set 24, 2014 4:13:01 PM org.apache.catalina.startup.HostConfig checkResources
INFORMAÇÕES: Undeploying context [/telecom-portlet]
Set 24, 2014 4:13:01 PM com.sun.faces.lifecycle.ELResolverInitPhaseListener populateFacesELResolverForJsp
INFORMAÇÕES: JSF1027: [/telecom-portlet] Os ELResolvers para JSF não foram registrados com o contêiner JSP.
Set 24, 2014 4:13:02 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFORMAÇÕES: Deploying configuration descriptor C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\conf\Catalina\localhost\telecom-portlet.xml
Set 24, 2014 4:13:02 PM org.apache.catalina.startup.HostConfig deployDescriptor
ADVERTÊNCIA: A docBase C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\webapps\telecom-portlet inside the host appBase has been specified, and will be ignored
Set 24, 2014 4:13:02 PM org.apache.catalina.startup.SetContextPropertiesRule begin
ADVERTÊNCIA: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:telecom-portlet' did not find a matching property.
Set 24, 2014 4:13:02 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFORMAÇÕES: validateJarFile(C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\webapps\telecom-portlet\WEB-INF\lib\el-api-1.0.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
16:13:03,023 INFO [pool-2-thread-2][HotDeployImpl:178] Deploying telecom-portlet from queue
16:13:03,025 INFO [pool-2-thread-2][PluginPackageUtil:1033] Reading plugin package for telecom-portlet
Set 24, 2014 4:13:03 PM org.apache.catalina.core.ApplicationContext log
INFORMAÇÕES: Initializing Spring root WebApplicationContext
16:13:03,489 INFO [pool-2-thread-2][HookHotDeployListener:550] Registering hook for telecom-portlet
16:13:03,501 INFO [pool-2-thread-2][HookHotDeployListener:690] Hook for telecom-portlet is available for use
16:13:24,542 ERROR [pool-2-thread-2][PortletLocalServiceImpl:758] com.liferay.portal.kernel.xml.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
com.liferay.portal.kernel.xml.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:399)
at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:415)
at com.liferay.portal.kernel.xml.SAXReaderUtil.read(SAXReaderUtil.java:161)
at com.liferay.portal.service.impl.PortletLocalServiceImpl._readLiferayPortletXML(PortletLocalServiceImpl.java:1602)
at com.liferay.portal.service.impl.PortletLocalServiceImpl.initWAR(PortletLocalServiceImpl.java:711)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:122)
at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:71)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:57)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
at com.liferay.portal.security.pacl.PACLAdvice.invoke(PACLAdvice.java:51)
at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:118)
at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:211)
at com.sun.proxy.$Proxy67.initWAR(Unknown Source)
at com.liferay.portal.service.PortletLocalServiceUtil.initWAR(PortletLocalServiceUtil.java:409)
at com.liferay.portal.deploy.hot.PortletHotDeployListener.doInvokeDeploy(PortletHotDeployListener.java:297)
at com.liferay.portal.deploy.hot.PortletHotDeployListener.invokeDeploy(PortletHotDeployListener.java:120)
at com.liferay.portal.deploy.hot.HotDeployImpl.doFireDeployEvent(HotDeployImpl.java:188)
at com.liferay.portal.deploy.hot.HotDeployImpl.fireDeployEvent(HotDeployImpl.java:96)
at com.liferay.portal.kernel.deploy.hot.HotDeployUtil.fireDeployEvent(HotDeployUtil.java:27)
at com.liferay.portal.kernel.servlet.PluginContextListener.fireDeployEvent(PluginContextListener.java:151)
at com.liferay.portal.kernel.servlet.PluginContextListener.doPortalInit(PluginContextListener.java:141)
at com.liferay.portal.kernel.util.BasePortalLifecycle.portalInit(BasePortalLifecycle.java:42)
at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:64)
at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:56)
at com.liferay.portal.kernel.util.BasePortalLifecycle.registerPortalLifecycle(BasePortalLifecycle.java:52)
at com.liferay.portal.kernel.servlet.PluginContextListener.contextInitialized(PluginContextListener.java:103)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4779)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5273)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:895)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:871)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:649)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1585)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.dom4j.io.SAXReader.read(SAXReader.java:365)
at com.liferay.portal.xml.SAXReaderImpl.read(SAXReaderImpl.java:396)
... 49 more
16:13:24,553 INFO [StartupListener:50] Context initialized for contextPath=[/telecom-portlet]
16:13:24,561 INFO [StartupListener:77] Copied input-editor.jsp from LiferayFaces JAR to context path file=[C:\liferay-portal-6.1.20-ee-ga2\tomcat-7.0.27\webapps\telecom-portlet\resources\liferay-ui\jsp\input-editor.jsp]
16:13:24,561 INFO [BridgeSessionListener:96] Context initialized for contextPath=[/telecom-portlet]</init></init>And when I try to change the liferay-portlet.xml file to 6.1 with previous files, the IDE shows this error:
<!--?xml version="1.0"?-->
<liferay-portlet-app>
<portlet>
<portlet-name>telecom</portlet-name>
<icon>/icon.png</icon>
<instanceable>true</instanceable>
<requires-namespaced-parameters>false</requires-namespaced-parameters>
<ajaxable>false</ajaxable>
<header-portlet-css>/css/main.css</header-portlet-css>
<css-class-wrapper>telecom-portlet</css-class-wrapper>
</portlet>
<role-mapper>
<role-name>administrator</role-name>
<role-link>Administrator</role-link>
</role-mapper>
<role-mapper>
<role-name>guest</role-name>
<role-link>Guest</role-link>
</role-mapper>
<role-mapper>
<role-name>power-user</role-name>
<role-link>Power User</role-link>
</role-mapper>
<role-mapper>
<role-name>user</role-name>
<role-link>User</role-link>
</role-mapper>
</liferay-portlet-app><!--?xml version="1.0"?-->
<liferay-portlet-app>
<portlet>
<portlet-name>telecom</portlet-name>
<icon>/icon.png</icon>
<instanceable>true</instanceable>
<requires-namespaced-parameters>false</requires-namespaced-parameters>
<ajaxable>false</ajaxable>
<header-portlet-css>/css/main.css</header-portlet-css>
<css-class-wrapper>telecom-portlet</css-class-wrapper>
</portlet>
<role-mapper>
<role-name>administrator</role-name>
<role-link>Administrator</role-link>
</role-mapper>
<role-mapper>
<role-name>guest</role-name>
<role-link>Guest</role-link>
</role-mapper>
<role-mapper>
<role-name>power-user</role-name>
<role-link>Power User</role-link>
</role-mapper>
<role-mapper>
<role-name>user</role-name>
<role-link>User</role-link>
</role-mapper>
</liferay-portlet-app>And when I try to change the liferay-portlet.xml file to 6.1 with previous files, IDE shows this error:
The content of element type "portlet" must match "(portlet-name,icon?,virtual-path?,struts-path?,parent-struts-path?,configuration-path?,configuration-action-
class?,indexer-class*,open-search-class?,scheduler-entry*,portlet-url-class?,friendly-url-mapper-class?,friendly-url-mapping?,friendly-url-routes?,url-encoder-
class?,portlet-data-handler-class?,portlet-layout-listener-class?,poller-processor-class?,pop-message-listener-class?,social-activity-interpreter-class?,social-
request-interpreter-class?,webdav-storage-token?,webdav-storage-class?,xml-rpc-method-class?,control-panel-entry-category?,control-panel-entry-
weight?,control-panel-entry-class?,asset-renderer-factory*,atom-collection-adapter*,custom-attributes-display*,permission-propagator?,workflow-
handler*,preferences-company-wide?,preferences-unique-per-layout?,preferences-owned-by-group?,use-default-template?,show-portlet-access-denied?,show-
portlet-inactive?,action-url-redirect?,restore-current-view?,maximize-edit?,maximize-help?,pop-up-print?,layout-
cacheable?,instanceable?,remoteable?,scopeable?,user-principal-strategy?,private-request-attributes?,private-session-attributes?,autopropagated-
parameters?,action-timeout?,render-timeout?,render-weight?,ajaxable?,header-portal-css*,header-portlet-css*,header-portal-javascript*,header-portlet-
javascript*,footer-portal-css*,footer-portlet-css*,footer-portal-javascript*,footer-portlet-javascript*,css-class-wrapper?,facebook-integration?,add-default-
resource?,system?,active?,include?)".If I delete the line:
<-requires-namespaced parameters> false <!-- requires-namespaced-parameters--> Makes the deploy, I can add in the portal, but generates various errors JSF
Could anyone help me?
Juan Gonzalez, modificado 9 Anos atrás.
RE: Problem create JSF Portlet
Liferay Legend Postagens: 3089 Data de Entrada: 28/10/08 Postagens RecentesAnderson Mendes dos Santos:
I need to create the project for LP EE 6.1, which is running in our production environment.
When I create the project, I select the 6.2 SDK that comes in Developer, and Tomcat 6.1 EE.
Why don't you use a 6.1 EE SDK?
Anderson Mendes dos Santos, modificado 9 Anos atrás.
RE: Problem create JSF Portlet
New Member Postagens: 9 Data de Entrada: 21/08/14 Postagens Recentes
I just found the SDK 6.1.1 CE, even so i could not make it work.
Do you have the link?
Thanks
Do you have the link?
Thanks
Juan Gonzalez, modificado 9 Anos atrás.
RE: Problem create JSF Portlet
Liferay Legend Postagens: 3089 Data de Entrada: 28/10/08 Postagens Recentes
You can download it from Customer Portal.