JSP Changes are not reflected in Liferay 7.?

[Mahendra Panchal, modificado 7 Anos atrás.]

Hello

I am working with liferay 7 g.a.3.

I have to customize Login user Account Settings -> User Information. I have created fragment module as

blade create -t fragment -h com.liferay.users.admin.web -H 2.0.7 "project-name"

after that I am putting jsp file which want to customize at path. src/main/resources/META-INF/resources/*.jsp.

Module deployed successfully.

server log are :

11:17:29,419 INFO [Refresh Thread: Equinox Container: 00b7f182-40ec-0016-1543-9e87f4614605][BundleStartStopLogger:38] STOPPED com.liferay.users.admin.web_2.0.7 [341]
11:17:29,550 INFO [Refresh Thread: Equinox Container: 00b7f182-40ec-0016-1543-9e87f4614605][BundleStartStopLogger:38] STOPPED com.liferay.my.account.web_1.0.3 [229]
11:17:30,138 INFO [Refresh Thread: Equinox Container: 00b7f182-40ec-0016-1543-9e87f4614605][BundleStartStopLogger:35] STARTED com.liferay.my.account.web_1.0.3 [229]
11:17:31,263 INFO [Refresh Thread: Equinox Container: 00b7f182-40ec-0016-1543-9e87f4614605][BundleStartStopLogger:35] STARTED com.liferay.users.admin.web_2.0.7 [341]

I am customizing com.liferay.users.admin.web. but while I am deploying this module why com.liferay.my.account.web stopped and started.?



But changes are not reflected on jsp(ui).

[David H Nebinger, modificado 7 Anos atrás.]

Mahendra Panchal:

I am customizing com.liferay.users.admin.web. but while I am deploying this module why com.liferay.my.account.web stopped and started.?

OSGi understands the dependencies between modules. Login and my account share some JSP and therefore they have dependencies. When your fragment bundle deploys, anything that might be dependent on the change must be stopped so the update can start and then all dependencies will be restarted.

But changes are not reflected on jsp(ui).

Sometimes the internal JSP compiler may not notice the changed timestamp of the jsp file especially since it is contained within a jar file.

When you see something like this I recommend stopping your app server, then delete the osgi/state directory (to drop all OSGi metadata) and also the contents of the $LIFERAY_HOME/work folder (not the app server work folder) as this will force a recompile of the JSP and should make everything work.

[Peter Stelmachovic, modificado 7 Anos atrás.]

Hi

my observations with JSP not refreshed

1) disable caching and similar stuff via including the following line in the portal-ext.properties

include-and-override=portal-developer.properties

2) set server (tomcat) timezone to GMT

for more details see
https://web.liferay.com/community/forums/-/message_boards/message/73393084

After (1) and (2) the jsps are refreshed. No need to restart the server.

[David H Nebinger, modificado 7 Anos atrás.]

Peter Stelmachovic:

1) disable caching and similar stuff via including the following line in the portal-ext.properties

include-and-override=portal-developer.properties

This is not a production optimization that you want to take. This is akin to killing a fly by burning your house down.






Come meet me at the 2017 LSNA!

[Gaurav Joshi, modificado 7 Anos atrás.]

In tomcat\conf\web.xml set following:-

<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<init-param>
<param-name>development</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>modificationTestInterval</param-name>
<param-value>0</param-value>
</init-param>
<init-param>
<param-name>xpoweredBy</param-name>
<param-value>false</param-value>
</init-param>
<load-on-startup>3</load-on-startup>
</servlet>

Click on the clean gradle task to remove the module from osgi/modules folder.
in work folder which is located at same level as tomcat delete the module's folder.

Now deploy the module to see the JSP changes reflecting.

Hope this helps .

[David H Nebinger, modificado 7 Anos atrás.]

Gaurav Joshi:

In tomcat\conf\web.xml set following:-

<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<init-param>
<param-name>development</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>modificationTestInterval</param-name>
<param-value>0</param-value>
</init-param>
<init-param>
<param-name>xpoweredBy</param-name>
<param-value>false</param-value>
</init-param>
<load-on-startup>3</load-on-startup>
</servlet>

Click on the clean gradle task to remove the module from osgi/modules folder.
in work folder which is located at same level as tomcat delete the module's folder.

Now deploy the module to see the JSP changes reflecting.

Hope this helps .

Actually, no, this won't have an impact. Liferay uses it's own catalina JSP compiler, not the tomcat's compiler. It is not going to look at the tomcat/conf/server.xml file at all for controlling the Liferay JSP recompilation.

Besides, again enabling debug mode like this is also akin to killing a fly in your home by burning the house down.









Come meet me at the 2017 LSNA!