Message Boards

ParamUtil causes failure

thumbnail
Dan Griffiths, modified 3 Years ago.

ParamUtil causes failure

New Member Posts: 8 Join Date: 6/25/20 Recent Posts
I have just started creating a new module in the Liferay IDE by following the example here and I have run across a problem.
Normally, when I make a change to the module and save it in the IDE, the module deploys to my running Liferay server and a  message about the app STARTED appears in the log. However, as soon as I reference ParamUtil in any way (by using ANY of its methods) within the action event function in my main MVC class (in my case this is src/main/java/guestbook/portlet/GuestbookPortlet.java)  and save it, the STARTED message does not appear and the web page just shows 'Temporarily unavailable' where the web application should be.There does not appear to be any error messages in the log or from Gradle (although I am new to that too, so I might have missed something).I would have thought that as this example came from the Liferay docs themselves, it would work! Can anybody help me?
thumbnail
Olaf Kock, modified 3 Years ago.

RE: ParamUtil causes failure

Liferay Legend Posts: 6396 Join Date: 9/23/08 Recent Posts
Dan Griffiths:

I have just started creating a new module in the Liferay IDE by following the example here and I have run across a problem.
You're linking to the 7.0 Developer Tutorials - while 7.3 is current. Which version are you using? There's a good chance that dependencies (and their versions) from 4 years back won't be exact any more.

In general, I'd consider ParamUtil to be quite an unsuspective class to use. There's little that can go wrong.
thumbnail
Dan Griffiths, modified 3 Years ago.

RE: ParamUtil causes failure

New Member Posts: 8 Join Date: 6/25/20 Recent Posts
Thanks for replying, Olaf. You are correct and the problem did indeed boil down to version incompatability. 
I discovered that if I manually copied the JAR file created by Gradle in the deploy/libs directory to the deploy directory  of my server (rather than letting the IDE deploy it for me); the log actually displayed an error message to this end.