Foren

Error in Liferay - works (sort of) but wondering why I'm seeing it.

thumbnail
Robert Smith, geändert vor 6 Jahren.

Error in Liferay - works (sort of) but wondering why I'm seeing it.

Junior Member Beiträge: 63 Beitrittsdatum: 15.10.09 Neueste Beiträge
Hi folks,

I am working on a Maven Primefaces 5.3 JSF portlet 'tabbed' project using Liferay faces running in Liferay 7.0 ce ga5 on wildfly 10.
I tried using Primefaces 6.0 and 6.1 but ran into some html top tag issues so switched to 5.3 which works better.
I've seen some anomalies with it that are interesting.
1. At startup I see the following exception:
15:41:28,494 ERROR [Framework Event Dispatcher: Equinox Container: e0874552-e60c-0018-128b-d7f222901f18][IUP-up-portlet:97] FrameworkEvent ERROR
org.osgi.framework.BundleException: Could not resolve module: IUP-up-portlet [554]_ Unresolved requirement: Import-Package: com.liferay.faces.portal.context_ [Sanitized]
at org.eclipse.osgi.container.Module.start(Module.java:429)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)


Also when the portlet is deployed we see the following error (i think this is a known issue but I figured I would add it here):
[BridgeDependencyVerifier:56] Liferay Faces Bridge Implementation 4.0.0 (Aug 30, 2016 AD) is designed to be used with Portlet 2.0 but detected 1.0

When the application is deployed, a javascript error occurs :
Uncaught ReferenceError: PrimeFaces is not defined

After a refresh, primefaces is loaded, but the tab bodies do not display:

Clicking on a tab allows it the body to display.

Anyway, my pom contains the following:

<properties>
<faces.api.version>2.2</faces.api.version>
<liferay.faces.bridge.ext.version>5.0.0</liferay.faces.bridge.ext.version>
<liferay.faces.bridge.version>4.0.0</liferay.faces.bridge.version>
<mojarra.version>2.2.13</mojarra.version>
<project.stage>Development</project.stage>
</properties>
<build>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.3</version>
<configuration>
<encoding>UTF-8</encoding>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.3</version>
<configuration>
<filteringDeploymentDescriptors>true</filteringDeploymentDescriptors>
</configuration>
</plugin>
</plugins>
</build>

<dependencies>
<!-- liferay -->
<dependency>
<groupId>com.liferay.portal</groupId>
<artifactId>com.liferay.portal.kernel</artifactId>
<version>2.3.0</version>
<scope>provided</scope>
</dependency>


<!-- OSGI -->
<dependency>
<groupId>org.osgi</groupId>
<artifactId>org.osgi.core</artifactId>
<version>6.0.0</version>
<scope>provided</scope>
</dependency>
<!-- Common -->
<dependency>
<groupId>commons-fileupload</groupId>
<artifactId>commons-fileupload</artifactId>
<version>1.3.1</version>
<optional>true</optional>
</dependency>
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.4</version>
<optional>true</optional>
</dependency>

<!-- JSF -->
<dependency>
<groupId>javax.faces</groupId>
<artifactId>javax.faces-api</artifactId>
<version>${faces.api.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.glassfish</groupId>
<artifactId>javax.faces</artifactId>
<version>${mojarra.version}</version>
<scope>runtime</scope>
</dependency>
<!-- liferay faces -->
<dependency>
<groupId>com.liferay.faces</groupId>
<artifactId>com.liferay.faces.portal</artifactId>
<version>3.0.0</version>
</dependency>
<dependency>
<groupId>com.liferay.faces</groupId>
<artifactId>com.liferay.faces.bridge.ext</artifactId>
<version>${liferay.faces.bridge.ext.version}</version>
</dependency>
<dependency>
<groupId>com.liferay.faces</groupId>
<artifactId>com.liferay.faces.bridge.impl</artifactId>
<version>${liferay.faces.bridge.version}</version>
</dependency>
<!-- primefaces -->
<dependency>
<groupId>org.primefaces</groupId>
<artifactId>primefaces</artifactId>
<version>5.3</version>
</dependency>

<dependency>
<groupId>org.primefaces.themes</groupId>
<artifactId>afterwork</artifactId>
<version>1.0.10</version>
</dependency>

<!-- logging -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.7.2</version>
</dependency>
<dependency>
<groupId>com.liferay.portal</groupId>
<artifactId>util-slf4j</artifactId>
<version>6.2.5</version>
</dependency>

<!-- EL -->
<dependency>
<groupId>org.glassfish.web</groupId>
<artifactId>el-impl</artifactId>
<version>2.2</version>
<scope>provided</scope>
</dependency>

<!-- IUP dependencies -->
<dependency>
<groupId>com.sfs.iup</groupId>
<artifactId>IUP-admin-api</artifactId>
<version>1.0.0.1</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.sfs.iup</groupId>
<artifactId>IUP-admin-api</artifactId>
<version>1.0.0.1</version>
<scope>provided</scope>
</dependency>

<dependency>
<groupId>javax.portlet</groupId>
<artifactId>portlet-api</artifactId>
<version>2.0</version>
<scope>provided</scope>
</dependency>

<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
<version>3.0.1</version>
<scope>provided</scope>
</dependency>
</dependencies>
Web.xml
<?xml version="1.0"?>

<web-app xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
version="3.0">
<display-name>IUP-up-portlet</display-name>

<context-param>
<param-name>com.sun.faces.expressionFactory</param-name>
<param-value>com.sun.el.ExpressionFactoryImpl</param-value>
</context-param>

<context-param>
<param-name>javax.faces.PROJECT_STAGE</param-name>
<param-value>Development</param-value>
</context-param>

<context-param>
<param-name>com.sun.faces.namespaceParameters</param-name>
<param-value>true</param-value>
</context-param>

<context-param>
<param-name>primefaces.THEME</param-name>
<param-value>afterwork</param-value>
</context-param>

<context-param>
<param-name>primefaces.FONT_AWESOME</param-name>
<param-value>true</param-value>
</context-param>

<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>

<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>server</param-value>
</context-param>

<context-param>
<param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
<param-value>true</param-value>
</context-param>

<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>

<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.xhtml</url-pattern>
</servlet-mapping>

<security-constraint>
<display-name>Prevent direct access to Facelet XHTML</display-name>
<web-resource-collection>
<web-resource-name>Facelet XHTML</web-resource-name>
<url-pattern>*.xhtml</url-pattern>
</web-resource-collection>
<auth-constraint />
</security-constraint>
</web-app>
thumbnail
Neil Griffin, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it.

Liferay Legend Beiträge: 2655 Beitrittsdatum: 27.07.05 Neueste Beiträge
Hi Robert,

Regarding the "Portlet 2.0 but detected 1.0" warning, it is a benign problem caused by FACES-3238.

Regarding dependencies, please upgrade to our latest Liferay Faces dependencies which you can determine from the www.liferayfaces.org home page.

Regarding PrimeFaces, we did all of our testing with 6.1, so it would be easiest for us to help you with PrimeFaces problems if you were to upgrade to 6.1.

Finally I would recommend that you shutdown your WildFly server and delete the $LIFERAY_HOME/osgi/state folder before starting up again. Then redeploy your portlet war with the upgraded dependencies.

Kind Regards,

Neil
thumbnail
Robert Smith, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it.

Junior Member Beiträge: 63 Beitrittsdatum: 15.10.09 Neueste Beiträge
Hi Neil,

I will try using the updated faces jars. Pertaining to Primefaces, I reverted to 5.3 because of
https://forum.primefaces.org/viewtopic.php?t=50770
I get different errors including the split issue on a paginator.

Thanks,
Bob
thumbnail
Robert Smith, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it.

Junior Member Beiträge: 63 Beitrittsdatum: 15.10.09 Neueste Beiträge
I updated the jars to:
<properties>
<faces.api.version>2.2</faces.api.version>
<liferay.faces.bridge.ext.version>5.0.1</liferay.faces.bridge.ext.version>
<liferay.faces.bridge.version>4.1.0</liferay.faces.bridge.version>
<mojarra.version>2.2.14</mojarra.version>
<project.stage>Development</project.stage>
</properties>

and now when I try to access i get the following error:

18:38:26,833 ERROR [default task-56][status_jsp:880] javax.servlet.ServletException: com.liferay.portal.kernel.portlet.PortletContainerException: com.liferay.portal.kernel.portlet.PortletContainerException: org.apache.jasper.JasperException: javax.servlet.ServletException: java.lang.NoSuchMethodError: com.liferay.faces.util.factory.FactoryExtensionFinder.getFactory(Ljavax/faces/context/ExternalContext;Ljava/lang/Class;)Ljava/lang/Object;
18:38:26,868 ERROR [liferay/monitoring-1][ParallelDestination:55] Unable to process message {destinationName=liferay/monitoring, response=null, responseDestinationName=null, responseId=null, payload=[{displayName=IUP-up-portlet, portletId=IUPupportlet_WAR_UPportlet, requestType=RENDER, {attributes=null, companyId=20116, groupId=73599, description=null, duration=0, name=IUP-up-portlet, namespace=com.liferay.monitoring.Portlet, requestStatus=null, stopWatch=0:00:00.345, timeout=0, user=20156}}, {displayName=Product Menu, portletId=com_liferay_product_navigation_product_menu_web_portlet_ProductMenuPortlet, requestType=RENDER, {attributes=null, companyId=20116, groupId=73599, description=null, duration=57, name=com_liferay_product_navigation_product_menu_web_portlet_ProductMenuPortlet, namespace=com.liferay.monitoring.Portlet, requestStatus=SUCCESS, stopWatch=0:00:00.057, timeout=0, user=20156}}, {displayName=User Personal Bar, portletId=com_liferay_product_navigation_user_personal_bar_web_portlet_ProductNavigationUserPersonalBarPortlet, requestType=RENDER, {attributes=null, companyId=20116, groupId=73599, description=null, duration=1, name=com_liferay_product_navigation_user_personal_bar_web_portlet_ProductNavigationUserPersonalBarPortlet, namespace=com.liferay.monitoring.Portlet, requestStatus=SUCCESS, stopWatch=0:00:00.001, timeout=0, user=20156}}, {displayName=Search, portletId=com_liferay_portal_search_web_portlet_SearchPortlet, requestType=RENDER, {attributes=null, companyId=20116, groupId=73599, description=null, duration=40, name=com_liferay_portal_search_web_portlet_SearchPortlet, namespace=com.liferay.monitoring.Portlet, requestStatus=SUCCESS, stopWatch=0:00:00.040, timeout=0, user=20156}}, {displayName=Navigation, portletId=com_liferay_site_navigation_menu_web_portlet_SiteNavigationMenuPortlet, requestType=RENDER, {attributes=null, companyId=20116, groupId=73599, description=null, duration=6, name=com_liferay_site_navigation_menu_web_portlet_SiteNavigationMenuPortlet, namespace=com.liferay.monitoring.Portlet, requestStatus=SUCCESS, stopWatch=0:00:00.006, timeout=0, user=20156}}, {referer=http://localhost:8080/group/application, remoteAddr=127.0.0.1, requestURL=http://localhost:8080/html/common/themes/portal.jsp.jsp_display, statusCode=400, userAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36, {attributes=null, companyId=20116, groupId=73599, description=Portal Request, duration=296, name=/html/common/themes/portal.jsp, namespace=com.liferay.monitoring.Portal, requestStatus=SUCCESS, stopWatch=0:00:00.296, timeout=-1, user=20156}}, {referer=http://localhost:8080/group/application, remoteAddr=127.0.0.1, requestURL=, statusCode=400, userAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36, {attributes=null, companyId=20116, groupId=73599, description=null, duration=333, name=/c/portal/status, namespace=com.liferay.monitoring.Portal, requestStatus=SUCCESS, stopWatch=0:00:00.333, timeout=-1, user=20156}}, {referer=http://localhost:8080/group/application, remoteAddr=127.0.0.1, requestURL=, statusCode=400, userAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36, {attributes=null, companyId=20116, groupId=73599, description=null, duration=388, name=/c/portal/layout, namespace=com.liferay.monitoring.Portal, requestStatus=SUCCESS, stopWatch=0:00:00.388, timeout=-1, user=20156}}, {referer=http://localhost:8080/group/application, remoteAddr=127.0.0.1, requestURL=, statusCode=400, userAgent=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36, {attributes=null, companyId=20116, groupId=73599, description=null, duration=397, name=/group/application/user-personalization, namespace=com.liferay.monitoring.Portal, requestStatus=SUCCESS, stopWatch=0:00:00.397, timeout=-1, user=null}}], values={defaultLocale=en_US, companyId=20116, groupId=0, principalName=20156, permissionChecker=com.liferay.portal.kernel.util.TransientValue@41e63d8f, siteDefaultLocale=en_US, themeDisplayLocale=en_US}}
com.liferay.portal.kernel.messaging.MessageListenerException: java.lang.NullPointerException
at com.liferay.portal.kernel.messaging.BaseMessageListener.receive(BaseMessageListener.java:32)
at com.liferay.portal.kernel.messaging.InvokerMessageListener.receive(InvokerMessageListener.java:74)
at com.liferay.portal.kernel.messaging.ParallelDestination$1.run(ParallelDestination.java:52)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask._runTask(ThreadPoolExecutor.java:756)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask.run(ThreadPoolExecutor.java:667)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at com.liferay.portal.monitoring.internal.statistics.portlet.PortletStatistics.processDataSample(PortletStatistics.java:106)
at com.liferay.portal.monitoring.internal.statistics.portlet.CompanyStatistics.processDataSample(CompanyStatistics.java:209)
at com.liferay.portal.monitoring.internal.statistics.portlet.ServerStatistics.processDataSample(ServerStatistics.java:117)
at com.liferay.portal.monitoring.internal.statistics.portlet.ServerStatistics.processDataSample(ServerStatistics.java:35)
at com.liferay.portal.monitoring.internal.messaging.MonitoringMessageListener.processDataSample(MonitoringMessageListener.java:93)
at com.liferay.portal.monitoring.internal.messaging.MonitoringMessageListener.doReceive(MonitoringMessageListener.java:120)
at com.liferay.portal.kernel.messaging.BaseMessageListener.receive(BaseMessageListener.java:26)
... 5 more
thumbnail
Neil Griffin, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it.

Liferay Legend Beiträge: 2655 Beitrittsdatum: 27.07.05 Neueste Beiträge
Hi Robert,

If you don't mind, let's take a different approach. Please generate a new PrimeFaces project from our latest archetype:

mvn archetype:generate \
  -DarchetypeGroupId=com.liferay.faces.archetype \
  -DarchetypeArtifactId=com.liferay.faces.archetype.primefaces.portlet \
  -DarchetypeVersion=5.0.2 \
  -DgroupId=com.mycompany \
  -DartifactId=com.mycompany.my.primefaces.portlet


Then build it with "mvn clean package" and copy target/*.war to $LIFERAY_HOME/deploy

Hopefully that will give us something that works to start with.

Kind Regards,

Neil
thumbnail
Robert Smith, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it.

Junior Member Beiträge: 63 Beitrittsdatum: 15.10.09 Neueste Beiträge
Hi Neill,

Thanks for the suggestion; however, due to time constraints I really dont have the time to create a new project and inject the code from this project in. My initial concern, that of the error stack trace for unresolved requirement: com.liferay.faces.portal.context_ from org.eclipse.osgi.framework.eventmgr is the reason for this post. I searched all the jars listed in my dependencies and none contain it, nor does any of our code reference it. Our code does reference 'context' but not 'context_'.

We are using the LiferayPortletHelperUtil quite a bit and also use ServiceTrackers to get to custom services which may explain why we get the errors when going to ext 5.0.1 and bridge 4.1.0.

Unfortunately the stack trace does not provide much information about the source of the issues. Anyway, I've reverted back to using ext 5.0.0 and bridge 4.1.0 because of the MessageListenerException
com.liferay.portal.kernel.messaging.MessageListenerException: java.lang.NullPointerException
at com.liferay.portal.kernel.messaging.BaseMessageListener.receive(BaseMessageListener.java:32)
at com.liferay.portal.kernel.messaging.InvokerMessageListener.receive(InvokerMessageListener.java:74)
at com.liferay.portal.kernel.messaging.ParallelDestination$1.run(ParallelDestination.java:52)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask._runTask(ThreadPoolExecutor.java:756)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask.run(ThreadPoolExecutor.java:667)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at com.liferay.portal.monitoring.internal.statistics.portlet.PortletStatistics.processDataSample(PortletStatistics.java:106)
at com.liferay.portal.monitoring.internal.statistics.portlet.CompanyStatistics.processDataSample(CompanyStatistics.java:209)
at com.liferay.portal.monitoring.internal.statistics.portlet.ServerStatistics.processDataSample(ServerStatistics.java:117)
at com.liferay.portal.monitoring.internal.statistics.portlet.ServerStatistics.processDataSample(ServerStatistics.java:35)
at com.liferay.portal.monitoring.internal.messaging.MonitoringMessageListener.processDataSample(MonitoringMessageListener.java:93)
at com.liferay.portal.monitoring.internal.messaging.MonitoringMessageListener.doReceive(MonitoringMessageListener.java:120)

followed by:
18:51:02,967 ERROR [Framework Event Dispatcher: Equinox Container: a0ea2f14-7d15-0018-1abc-8fbeb28c9bb4][org_eclipse_equinox_http_servlet:97] FrameworkEvent ERROR
java.lang.NoSuchMethodError: com.liferay.faces.util.factory.FactoryExtensionFinder.getFactory(Ljavax/faces/context/ExternalContext;Ljava/lang/Class;)Ljava/lang/Object;
at com.liferay.faces.bridge.internal.BridgeFactoryFinderImpl.getFactoryInstance(BridgeFactoryFinderImpl.java:54)
at com.liferay.faces.bridge.BridgeFactoryFinder.getFactory(BridgeFactoryFinder.java:64)
at com.liferay.faces.bridge.servlet.BridgeSessionListener.sessionDestroyed(BridgeSessionListener.java:145)
at org.eclipse.equinox.http.servlet.internal.servlet.HttpSessionAdaptor.invokeSessionListeners(HttpSessionAdaptor.java:132)
at org.eclipse.equinox.http.servlet.internal.registration.ListenerRegistration.destroy(ListenerRegistration.java:77)
at org.eclipse.equinox.http.servlet.internal.customizer.ContextListenerTrackerCustomizer.removedService(ContextListenerTrackerCustomizer.java:100)
at org.eclipse.equinox.http.servlet.internal.customizer.ContextListenerTrackerCustomizer.removedService(ContextListenerTrackerCustomizer.java:1)
at org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:967)
at org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:1)
at org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:909)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:917)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:222)
at com.liferay.portal.osgi.web.wab.extender.internal.WabBundleProcessor.destroyListeners(WabBundleProcessor.java:373)
at com.liferay.portal.osgi.web.wab.extender.internal.WabBundleProcessor.destroy(WabBundleProcessor.java:113)
at com.liferay.portal.osgi.web.wab.extender.internal.WebBundleDeployer.doStop(WebBundleDeployer.java:129)
at com.liferay.portal.osgi.web.wab.extender.internal.WabFactory$WABExtension.destroy(WabFactory.java:152)
at org.apache.felix.utils.extender.AbstractExtender$2.run(AbstractExtender.java:290)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.apache.felix.utils.extender.AbstractExtender.destroyExtension(AbstractExtender.java:312)
at org.apache.felix.utils.extender.AbstractExtender.bundleChanged(AbstractExtender.java:186)
at com.liferay.osgi.felix.util.AbstractExtender.bundleChanged(AbstractExtender.java:50)
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:905)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:165)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:75)
at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:67)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:102)
at org.eclipse.osgi.container.Module.publishEvent(Module.java:461)
at org.eclipse.osgi.container.Module.doStop(Module.java:619)
at org.eclipse.osgi.container.Module.stop(Module.java:483)
at org.eclipse.osgi.internal.framework.EquinoxBundle.stop(EquinoxBundle.java:429)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.stopTransient(DirectoryWatcher.java:1191)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.update(DirectoryWatcher.java:1132)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.update(DirectoryWatcher.java:906)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:484)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:361)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:312)
thumbnail
Neil Griffin, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it. (Antwort)

Liferay Legend Beiträge: 2655 Beitrittsdatum: 27.07.05 Neueste Beiträge
Hi Robert,

Whenever you have time to try reproducing by starting with a new project from the archetype, we'd be happy to help.

Kind Regards,

Neil
thumbnail
Robert Smith, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it.

Junior Member Beiträge: 63 Beitrittsdatum: 15.10.09 Neueste Beiträge
Hi Neil,

Thanks for the quick response. If i get a chance I will use the archetype. So is it true, the only supported projects are projects created via the archetype?

Regards,
Bob
thumbnail
Neil Griffin, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it.

Liferay Legend Beiträge: 2655 Beitrittsdatum: 27.07.05 Neueste Beiträge
Hi Robert,

We are happy to support projects created with or without the archetype. But if we get to the point at which we need to reproduce a problem that was reported in the forums, then we need an SSCCE that we can build locally. The archetype is usually the easiest way to start down the path of building an SSCCE.

Kind Regards,

Neil
thumbnail
Kyle Joseph Stiemann, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it.

Liferay Master Beiträge: 760 Beitrittsdatum: 14.01.13 Neueste Beiträge
Hi Robert,
I just wanted to mention that StackOverflow has a similar requirement for questions called a Minimal, Complete, and Verifiable Example or (MCVE). Without a MCVE or a Short, Self Contained, Correct (Compilable), Example we cannot be sure that we are reproducing your exact issue, and if the example is not minimal, other bugs or code may obfuscate the problem. On the Liferay Faces Team, we try to answer every forum post, so we need straightforward reproducers in order to answer questions as quickly and accurately as possible. Hopefully that helps explain our side of things emoticon

- Kyle

Related links:
thumbnail
Robert Smith, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it.

Junior Member Beiträge: 63 Beitrittsdatum: 15.10.09 Neueste Beiträge
Hi Neil,

Thanks for your suggestions and help - really do appreciate it. I finally got a chance to do what you suggested. I created a new project using the archetype and that fixed both problems - both the missing dependency and the misreporting of the bridge version.


Thanks again

Bob
thumbnail
Neil Griffin, geändert vor 6 Jahren.

RE: Error in Liferay - works (sort of) but wondering why I'm seeing it.

Liferay Legend Beiträge: 2655 Beitrittsdatum: 27.07.05 Neueste Beiträge
Hi Robert,

Thanks for reporting back -- I'm glad to know that things are working for you now. Thanks for using Liferay Faces. emoticon

Neil