Claire Tech Blog

Scriptlet vs JSTL http://www.informit.com/articles/article.aspx?p=30334

SessionMessages.add(actionRequest, SessionMessages.KEY_SUFFIX_HIDE_DEFAULT_SUCCESS_MESSAGE); "javax.portlet.init-param.add-process-action-success-action=false" Component properties on portlet Is this to disable the default liferay frontend success popover thing? By convention we've been doing that in the component properties on the portlet.

You need to add the module-log4j.xml config under /META-INF for the appender configuration. You can look at most of the other modules for syntax.

Microsoft lds

https://mailtrap.io/ http://nilhcem.com/FakeSMTP/

You should  not  have scriptlet code in JSPs. I'd recommend 100% JSTL and zero scriplet code. JSPs should be purely presentation. That's the hidden benefit of writing JSPs using only JSTL, because they get all their dynamic data elsewhere. Let the service layer have the business logic and determine what data the JSP needs. This answers your unit testing question, too. You should not have to unit test JSPs; those would be Selenium-like UI tests. If the logic is in the service tier, it's obvious how you test it. JSPs should not be inherited. You can certainly compose them together using something like SiteMesh, but inheritance has no part in your JSPs. Once they inherit from Servlet, the chain should be ended. Besides, it's a false alternative. Neither one should require reuse, inheritance, or unit testing. But that doesn't mean there isn't a clear winner: it's JSTL. No one should be using scriptlets in JSPs, except for very rare one-liners. Scriptlet