掲示板

Primefaces lazyloading datatable ajax calling issue

9年前 に fstn ITESOFT によって更新されました。

Primefaces lazyloading datatable ajax calling issue

Junior Member 投稿: 63 参加年月日: 14/10/03 最新の投稿
HI,

I try to put an existing primefaces application inside a portlet. This application user primefaces 4.0 datatable in lazy mode. In this mode, the client browser is doing ajax call when user enter a filter. I can see request in webdeveloper but my bean function is never call. I have no errors (client side or server side but nothing works)


I use Liferay 6.2 GA2 with the following dependencies:
<dependency>
			<groupid>org.mybatis</groupid>
			<artifactid>mybatis</artifactid>
			<version>3.2.3</version>
		</dependency>
		<dependency>
			<groupid>org.springframework</groupid>
			<artifactid>spring-context</artifactid>
			<version>3.2.3.RELEASE</version>
		</dependency>
		<dependency>
			<groupid>org.springframework</groupid>
			<artifactid>spring-core</artifactid>
			<version>3.2.3.RELEASE</version>
		</dependency>
		<dependency>
			<groupid>org.springframework</groupid>
			<artifactid>spring-jdbc</artifactid>
			<version>3.2.3.RELEASE</version>
		</dependency>
		<dependency>
			<groupid>org.springframework</groupid>
			<artifactid>spring-tx</artifactid>
			<version>3.2.3.RELEASE</version>
		</dependency>
		<dependency>
			<groupid>org.mybatis</groupid>
			<artifactid>mybatis-spring</artifactid>
			<version>1.2.0</version>
		</dependency>
		<dependency>
			<groupid>ch.qos.logback</groupid>
			<artifactid>logback-classic</artifactid>
			<version>1.0.13</version>
		</dependency>
		<dependency>
			<groupid>org.slf4j</groupid>
			<artifactid>slf4j-api</artifactid>
			<version>${slf4j.version}</version>
		</dependency>
		<dependency>
			<groupid>net.ju-n.commons-dbcp-jmx</groupid>
			<artifactid>commons-dbcp-jmx-jdbc3</artifactid>
			<version>0.2</version>
		</dependency>
		<dependency>
			<groupid>javax.mail</groupid>
			<artifactid>mail</artifactid>
			<version>1.4</version>
			<scope>provided</scope>
		</dependency>
		<dependency>
			<groupid>org.mockito</groupid>
			<artifactid>mockito-all</artifactid>
			<version>1.9.5</version>
			<scope>test</scope>
		</dependency>
		<dependency>
	      <groupid>junit</groupid>
	      <artifactid>junit</artifactid>
	      <version>4.8.2</version>
	      <scope>test</scope>
	    </dependency>


This is my web.xml
<!--?xml version="1.0" encoding="UTF-8"?-->

<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_2_5.xsd" version="2.5">

	<!-- Set the JSF 2 PROJECT_STAGE to Development so that the JSF implementation will do the following at runtime: -->
	<!-- 1. Log more verbose messages. -->
	<!-- 2. Render tips and/or warnings in the view markup. -->
	<!-- 3. Cause the default ExceptionHandler to display a developer-friendly error page. -->
	<context-param>
		<param-name>javax.faces.PROJECT_STAGE</param-name>
		<param-value>Development</param-value>
	</context-param>
	
	<!-- Instruct Mojarra to utilize JBoss-EL instead of the EL implementation provided by the servlet container. -->
	<context-param>
		<param-name>com.sun.faces.expressionFactory</param-name>
		<param-value>org.jboss.el.ExpressionFactoryImpl</param-value>
	</context-param>
	<!-- Workaround for http://issues.liferay.com/browse/FACES-1194 -->
	<context-param>
		<param-name>com.liferay.faces.bridge.primeFileUploadForceResourceURL</param-name>
		<param-value>true</param-value>
	</context-param>
	<!-- Although the FacesServlet will not be invoked by any portlet requests, it is required to initialize JSF. -->
	<servlet>
		<servlet-name>Faces Servlet</servlet-name>
		<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
		<load-on-startup>1</load-on-startup>
	</servlet>
	<!-- MyFaces will not initialize unless a servlet-mapping to the Faces Servlet is present. -->
	<servlet-mapping>
		<servlet-name>Faces Servlet</servlet-name>
		<url-pattern>*.xhtml</url-pattern>
	</servlet-mapping>
	<!-- Prevent direct access to Facelet view XHTML by the userAgent (browser). --> 
	<security-constraint>
		<web-resource-collection>
			<web-resource-name>Facelet View XHTML</web-resource-name>
			<url-pattern>*.xhtml</url-pattern>
		</web-resource-collection>
		<auth-constraint>
			<role-name>nobody</role-name>
		</auth-constraint>
	</security-constraint>
	<security-role>
		<role-name>nobody</role-name>
	</security-role>
</web-app>


My faces config:
<!--?xml version="1.0"?-->

<faces-config version="2.1" 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-facesconfig_2_1.xsd">
	<lifecycle>
		<phase-listener>com.liferay.faces.util.lifecycle.DebugPhaseListener</phase-listener>
		<phase-listener>com.liferay.faces.util.lifecycle.ViewScopePhaseListener</phase-listener>
	</lifecycle>
</faces-config>


Thank you


Thank you
thumbnail
9年前 に Vernon Singleton によって更新されました。

RE: Primefaces lazyloading datatable ajax calling issue

Expert 投稿: 315 参加年月日: 13/01/14 最新の投稿
Hi fstn,

fstn ITESOFT:
I try to put an existing primefaces application inside a portlet. This application user primefaces 4.0 datatable in lazy mode. In this mode, the client browser is doing ajax call when user enter a filter. I can see request in webdeveloper but my bean function is never call. I have no errors (client side or server side but nothing works)


Could you deploy the primefaces4-portlet in your environment, and make sure that works?

Then, we can start to modify that demo's p:dataTable to use code that we can both see. From the looks of your dependencies, it seems like we would be taking a big bite to chew, if we looked at the entire application your are trying to convert to use primefaces. let's see if we can reproduce the same issue with the small primefaces4 demo portlet.

- Vernon
9年前 に fstn fs によって更新されました。

RE: Primefaces lazyloading datatable ajax calling issue

Junior Member 投稿: 63 参加年月日: 14/10/03 最新の投稿
Ok I tried the primefaces4-portlet in my environment, it's ok, it works very well.

But with PF datatable, I already have the issue,
chrome developers tools, request when I enter a filter :

Remote Address:127.0.0.1:8090
Request URL:http://127.0.0.1:8090/group/client/invoice-list?p_p_id=newjsf_WAR_listinvoicesportlet&amp;p_p_lifecycle=2&amp;p_p_state=normal&amp;p_p_mode=view&amp;p_p_cacheability=cacheLevelPage&amp;p_p_col_id=column-1&amp;p_p_col_count=4&amp;p_p_col_pos=3&amp;_newjsf_WAR_listinvoicesportlet__jsfBridgeAjax=true&amp;_newjsf_WAR_listinvoicesportlet__facesViewIdResource=%2Fviews%2Fnew-jsf%2Fview.xhtml
Request Method:POST
Status Code:200 OK
Request Headersview source
Accept:application/xml, text/xml, */*; q=0.01
Accept-Encoding:gzip, deflate
Accept-Language:fr-FR,fr;q=0.8,en-US;q=0.6,en;q=0.4
Connection:keep-alive
Content-Length:1354
Content-Type:application/x-www-form-urlencoded; charset=UTF-8
Cookie:COOKIE_SUPPORT=true; SCREEN_NAME=41584752485130376a75363662704848524671716c413d3d; LFR_SESSION_STATE_10671=1418206799296; __utma=96992031.2111036265.1418319091.1418319091.1418319091.1; __utmc=96992031; __utmz=96992031.1418319091.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); JSESSIONID=D7046C37E615D1B565A94A626C685DF6; COMPANY_ID=10154; ID=31767844534772694c67306c6b445a43594a48744e513d3d; USER_UUID="w28LxfE8Y81KC3kBPv+Pz2YNhM6P/q/ctsB3iiqNQSA="; GUEST_LANGUAGE_ID=fr_FR; LFR_SESSION_STATE_10198=1418381701777
Faces-Request:partial/ajax
Host:127.0.0.1:8090
Origin:http://127.0.0.1:8090
Referer:http://127.0.0.1:8090/group/client//invoice-list
User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36
X-Requested-With:XMLHttpRequest
Query String Parametersview sourceview URL encoded
p_p_id:newjsf_WAR_listinvoicesportlet
p_p_lifecycle:2
p_p_state:normal
p_p_mode:view
p_p_cacheability:cacheLevelPage
p_p_col_id:column-1
p_p_col_count:4
p_p_col_pos:3
_newjsf_WAR_listinvoicesportlet__jsfBridgeAjax:true
_newjsf_WAR_listinvoicesportlet__facesViewIdResource:/views/new-jsf/view.xhtml
Form Dataview sourceview URL encoded
javax.faces.partial.ajax:true
javax.faces.source:_newjsf_WAR_listinvoicesportlet_:form:carTable
javax.faces.partial.execute:_newjsf_WAR_listinvoicesportlet_:form:carTable
javax.faces.partial.render:_newjsf_WAR_listinvoicesportlet_:form:carTable
_newjsf_WAR_listinvoicesportlet_:form:carTable:_newjsf_WAR_listinvoicesportlet_:form:carTable
_newjsf_WAR_listinvoicesportlet_:form:carTable_filtering:true
_newjsf_WAR_listinvoicesportlet_:form:carTable_encodeFeature:true
_newjsf_WAR_listinvoicesportlet_:form:_newjsf_WAR_listinvoicesportlet_:form
javax.faces.encodedURL:http://127.0.0.1:8090/group/client/invoice-list?p_p_id=newjsf_WAR_listinvoicesportlet&amp;p_p_lifecycle=2&amp;p_p_state=normal&amp;p_p_mode=view&amp;p_p_cacheability=cacheLevelPage&amp;p_p_col_id=column-1&amp;p_p_col_count=4&amp;p_p_col_pos=3&amp;_newjsf_WAR_listinvoicesportlet__jsfBridgeAjax=true&amp;_newjsf_WAR_listinvoicesportlet__facesViewIdResource=%2Fviews%2Fnew-jsf%2Fview.xhtml
_newjsf_WAR_listinvoicesportlet_:form:carTable:j_idt4:filter:
_newjsf_WAR_listinvoicesportlet_:form:carTable:j_idt6:filter:1212
_newjsf_WAR_listinvoicesportlet_:form:carTable:j_idt8:filter:
_newjsf_WAR_listinvoicesportlet_:form:carTable_selection:
javax.faces.ViewState:923733404288275412:843505119303369977
Response Headersview source
Cache-Control:no-cache
Cache-Control:private, no-cache, no-store, must-revalidate
Content-Encoding:gzip
Content-Type:text/xml;charset=UTF-8
Date:Fri, 12 Dec 2014 10:58:25 GMT
Expires:Thu, 01 Jan 1970 00:00:00 GMT
Liferay-Portal:Liferay Portal Community Edition 6.2 CE GA2 (Newton / Build 6201 / March 20, 2014)
Pragma:no-cache
Server:Apache-Coyote/1.1
Transfer-Encoding:chunked
X-Content-Type-Options:nosniff
X-Frame-Options:SAMEORIGIN
X-JAVAX-PORTLET-FACES-NAMESPACED-RESPONSE:true
X-XSS-Protection:1


log server side;
11:00:09,921 DEBUG [DebugPhaseListener:64] BEFORE phaseId=[RESTORE_VIEW 1] viewId=[null]
11:00:09,923 DEBUG [DebugPhaseListener:48] AFTER phaseId=[RESTORE_VIEW 1] viewId=[/views/new-jsf/view.xhtml]
11:00:09,923 DEBUG [DebugPhaseListener:64] BEFORE phaseId=[RENDER_RESPONSE 6] viewId=[/views/new-jsf/view.xhtml]
11:00:09,928 DEBUG [DebugPhaseListener:48] AFTER phaseId=[RENDER_RESPONSE 6] viewId=[/views/new-jsf/view.xhtml]


It would be very nice if ou can compile a small primefaces 4.0 demo with lazy datatable, you can find the code i used in this page
http://www.primefaces.org/showcase/ui/data/datatable/lazy.xhtml

Thank you for your help
thumbnail
9年前 に Neil Griffin によって更新されました。

RE: Primefaces lazyloading datatable ajax calling issue

Liferay Legend 投稿: 2655 参加年月日: 05/07/27 最新の投稿
We have an example of PrimeFaces 4 lazy loading for p:dataTable in the primefaces4-users-portlet demo. We have a downloadable version of it that uses PrimeFaces 3 here. The PrimeFaces 4 version is only available in source form (at the time of this writing) but will be made available in binary form when we have our next production release.

For more information, see UsersModelBean.java and UserLazyDataModel.java
9年前 に fstn fs によって更新されました。

RE: Primefaces lazyloading datatable ajax calling issue

Junior Member 投稿: 63 参加年月日: 14/10/03 最新の投稿
Thank you Neil, I built primefaces4-users-portlet and it's work well, there is no problem with this version.

I compared with my own project, I have the same config, the same code. There are only differences in my pom.xml.
this is mine:

<!--?xml version="1.0"?-->

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemalocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
	<modelversion>4.0.0</modelversion>
	<artifactid>list-invoices-portlet</artifactid>
	<packaging>war</packaging>
	<name>Supplier Portal Liferay Portlet</name>
	<properties>
		<project.build.sourceencoding>UTF-8</project.build.sourceencoding>
		<slf4j.version>1.7.5</slf4j.version>
	</properties>
	<parent>
		<groupid>com.p2p</groupid>
		<artifactid>SupplierPortal</artifactid>
		<version>2.6.0-SNAPSHOT</version>
		<relativepath>../../</relativepath>
	</parent>
	<profiles>
		<profile>
			<id>SPDev</id>
			<build>
				<plugins>
					<plugin>
						<groupid>com.liferay.maven.plugins</groupid>
						<artifactid>liferay-maven-plugin</artifactid>
						<version>${liferay.version}</version>
						<configuration>
							<plugintype>portlet</plugintype>
							<liferayversion>${liferay.version}</liferayversion>
							<autodeploydir>${liferay.auto.deploy.dir}</autodeploydir>
						</configuration>
						<executions>
							<execution>
								<id>deploy-package</id>
								<phase>install</phase>
								<goals>
									<goal>deploy</goal>
								</goals>
							</execution>
						</executions>
					</plugin>
				</plugins>
			</build>
		</profile>
	</profiles>
	<build>
		<plugins>
			<plugin>
				<groupid>com.liferay.maven.plugins</groupid>
				<artifactid>liferay-maven-plugin</artifactid>
				<version>${liferay.version}</version>
				<configuration>
					<autodeploydir>${liferay.auto.deploy.dir}</autodeploydir>
					<liferayversion>${liferay.version}</liferayversion>
					<plugintype>portlet</plugintype>
				</configuration>
			</plugin>

			<plugin>
				<artifactid>maven-compiler-plugin</artifactid>
				<version>3.1</version>
				<configuration>
					<encoding>UTF-8</encoding>
					<source>1.6
					<target>1.6</target>
				</configuration>
			</plugin>
			<plugin>
				<artifactid>maven-resources-plugin</artifactid>
				<version>2.4.2</version>
				<configuration>
					<encoding>UTF-8</encoding>
				</configuration>
			</plugin>
		</plugins>
		<resources>
			<resource>
				<directory>src/main/resources</directory>
				<excludes>
					<exclude>sp-database.properties</exclude>
				</excludes>
			</resource>
		</resources>
	</build>
	<dependencies>
		<dependency>
			<groupid>commons-fileupload</groupid>
			<artifactid>commons-fileupload</artifactid>
			<version>1.2.2</version>
		</dependency>
		<dependency>
			<groupid>commons-io</groupid>
			<artifactid>commons-io</artifactid>
			<version>1.3.2</version>
		</dependency>
		<dependency>
			<groupid>org.slf4j</groupid>
			<artifactid>slf4j-api</artifactid>
			<version>${slf4j.version}</version>
		</dependency>
		<dependency>
			<groupid>com.liferay.faces</groupid>
			<artifactid>liferay-faces-bridge-impl</artifactid>
			<version>3.2.4-ga5</version>
		</dependency>
		<dependency>
			<groupid>com.liferay.faces</groupid>
			<artifactid>liferay-faces-bridge-api</artifactid>
			<version>3.2.4-ga5</version>
		</dependency>
		<dependency>
			<groupid>com.liferay.portal</groupid>
			<artifactid>portal-service</artifactid>
			<version>6.2.1</version>
			<scope>provided</scope>
		</dependency>
		
		<dependency>
			<groupid>com.liferay.faces</groupid>
			<artifactid>liferay-faces-portal</artifactid>
			<version>3.2.4-ga5</version>
		</dependency>
		<dependency>
			<groupid>com.liferay.portal</groupid>
			<artifactid>util-java</artifactid>
			<version>6.2.1</version>
			<scope>provided</scope>
		</dependency>
		<dependency>
			<groupid>com.sun.faces</groupid>
			<artifactid>jsf-api</artifactid>
			<version>2.1.21</version>
		</dependency>
		<dependency>
			<groupid>javax.servlet</groupid>
			<artifactid>javax.servlet-api</artifactid>
			<version>3.1.0</version>
		</dependency>
		<dependency>
			<groupid>org.jboss.seam</groupid>
			<artifactid>jboss-el</artifactid>
			<version>2.0.0.GA</version>
		</dependency>
		
		<dependency>
			<groupid>com.sun.faces</groupid>
			<artifactid>jsf-impl</artifactid>
			<version>2.1.21</version>
		</dependency>
		<dependency>
			<groupid>org.mybatis</groupid>
			<artifactid>mybatis</artifactid>
			<version>3.2.3</version>
		</dependency>
		<dependency>
			<groupid>org.springframework</groupid>
			<artifactid>spring-context</artifactid>
			<version>3.2.3.RELEASE</version>
		</dependency>
		<dependency>
			<groupid>org.springframework</groupid>
			<artifactid>spring-core</artifactid>
			<version>3.2.3.RELEASE</version>
		</dependency>
		<dependency>
			<groupid>org.springframework</groupid>
			<artifactid>spring-jdbc</artifactid>
			<version>3.2.3.RELEASE</version>
		</dependency>
		<dependency>
			<groupid>org.springframework</groupid>
			<artifactid>spring-tx</artifactid>
			<version>3.2.3.RELEASE</version>
		</dependency>
		<dependency>
			<groupid>org.mybatis</groupid>
			<artifactid>mybatis-spring</artifactid>
			<version>1.2.0</version>
		</dependency>
		<dependency>
			<groupid>ch.qos.logback</groupid>
			<artifactid>logback-classic</artifactid>
			<version>1.0.13</version>
		</dependency>
		<dependency>
			<groupid>org.slf4j</groupid>
			<artifactid>slf4j-api</artifactid>
			<version>${slf4j.version}</version>
		</dependency>
		<dependency>
			<groupid>net.ju-n.commons-dbcp-jmx</groupid>
			<artifactid>commons-dbcp-jmx-jdbc3</artifactid>
			<version>0.2</version>
		</dependency>
		<dependency>
			<groupid>javax.mail</groupid>
			<artifactid>mail</artifactid>
			<version>1.4</version>
			<scope>provided</scope>
		</dependency>
		<dependency>
			<groupid>org.mockito</groupid>
			<artifactid>mockito-all</artifactid>
			<version>1.9.5</version>
			<scope>test</scope>
		</dependency>
		<dependency>
			<groupid>org.primefaces</groupid>
			<artifactid>primefaces</artifactid>
			<version>4.0</version>
		</dependency>
		<dependency>
	      <groupid>junit</groupid>
	      <artifactid>junit</artifactid>
	      <version>4.8.2</version>
	      <scope>test</scope>
	    </dependency>
	</dependencies>
</project>



this is yours:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemalocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">

	<modelversion>4.0.0</modelversion>
	<parent>
		<groupid>com.liferay.faces.demos</groupid>
		<artifactid>liferay-faces-portal-demos</artifactid>
		<version>4.2.0-m2</version>
		<relativepath>../pom.xml</relativepath>
	</parent>
	<artifactid>primefaces4-users-portlet</artifactid>
	<packaging>war</packaging>
	<name>PrimeFaces4 Users Portlet</name>
	<description>This plugin is an alternate portlet for the Liferay Control Panel "Users" portlet.</description>

	<dependencies>
	<dependency>
			<groupid>commons-fileupload</groupid>
			<artifactid>commons-fileupload</artifactid>
		</dependency>
		<dependency>
			<groupid>commons-io</groupid>
			<artifactid>commons-io</artifactid>
		</dependency>
		<dependency>
			<groupid>com.liferay.portal</groupid>
			<artifactid>portal-service</artifactid>
		</dependency>
		<dependency>
			<groupid>javax.annotation</groupid>
			<artifactid>jsr250-api</artifactid>
		</dependency>
		<dependency>
			<groupid>javax.portlet</groupid>
			<artifactid>portlet-api</artifactid>
		</dependency>
		<dependency>
			<groupid>javax.servlet</groupid>
			<artifactid>javax.servlet-api</artifactid>
		</dependency>
		<dependency>
			<groupid>org.primefaces</groupid>
			<artifactid>primefaces</artifactid>
			<version>${primefaces4.version}</version>
		</dependency>
		<dependency>
			<groupid>org.jboss.seam</groupid>
			<artifactid>jboss-el</artifactid>
		</dependency>
		<dependency>
			<groupid>com.liferay.faces</groupid>
			<artifactid>liferay-faces-alloy</artifactid>
			<version>${project.version}</version>
		</dependency>
		<dependency>
			<groupid>com.liferay.faces</groupid>
			<artifactid>liferay-faces-bridge-impl</artifactid>
			<version>${project.version}</version>
		</dependency>
		<dependency>
			<groupid>com.liferay.faces</groupid>
			<artifactid>liferay-faces-portal</artifactid>
			<version>${project.version}</version>
		</dependency>
	</dependencies>

</project>


Your are using version 4.2.0-m2 in your portlet, did you make any changes that can solved my problem inside these jars?
can I use 4.2.0-m2 in production?

regards
9年前 に fstn fs によって更新されました。

RE: Primefaces lazyloading datatable ajax calling issue

Junior Member 投稿: 63 参加年月日: 14/10/03 最新の投稿
I find a solution, by comparing pom files with primefaces3 portlet.

The good pom was:
		<dependency>
			<groupid>commons-fileupload</groupid>
			<artifactid>commons-fileupload</artifactid>
			<version>1.2.2</version>
		</dependency>
		<dependency>
			<groupid>commons-io</groupid>
			<artifactid>commons-io</artifactid>
			<version>1.3.2</version>
		</dependency>
		<dependency>
			<groupid>org.slf4j</groupid>
			<artifactid>slf4j-api</artifactid>
			<version>${slf4j.version}</version>
		</dependency>
		<dependency>
			<groupid>com.liferay.faces</groupid>
			<artifactid>liferay-faces-bridge-impl</artifactid>
			<version>3.2.4-ga5</version>
		</dependency>
		<dependency>
			<groupid>com.liferay.faces</groupid>
			<artifactid>liferay-faces-bridge-api</artifactid>
			<version>3.2.4-ga5</version>
		</dependency>		
		<dependency>
			<groupid>com.liferay.faces</groupid>
			<artifactid>liferay-faces-portal</artifactid>
			<version>3.2.4-ga5</version>
		</dependency>
		<dependency>
			<groupid>com.sun.faces</groupid>
			<artifactid>jsf-api</artifactid>
			<version>2.1.21</version>
		</dependency>
		<dependency>
			<groupid>org.jboss.seam</groupid>
			<artifactid>jboss-el</artifactid>
			<version>2.0.0.GA</version>
		</dependency>
		
		<dependency>
			<groupid>com.sun.faces</groupid>
			<artifactid>jsf-impl</artifactid>
			<version>2.1.21</version>
		</dependency>
		<dependency>
			<groupid>org.primefaces</groupid>
			<artifactid>primefaces</artifactid>
			<version>4.0</version>
		</dependency>
		<dependency>
	      <groupid>junit</groupid>
	      <artifactid>junit</artifactid>
	      <version>4.8.2</version>
	      <scope>test</scope>
	    </dependency>
	
thumbnail
9年前 に Vernon Singleton によって更新されました。

RE: Primefaces lazyloading datatable ajax calling issue

Expert 投稿: 315 参加年月日: 13/01/14 最新の投稿
Hi fstn,

fstn fs:
I find a solution


Glad to hear you got it working.