starting liferay -
i work on liferay.we use 1 module in our project liferay theme creation. use command ant -ddeploy.war=true
deploys in server. war file gets created in liferay deploy folder. when start server not options login. not liferay specific options. following server logs
an error occurred @ line: 117 in jsp file: /html/portlet/login/login.jsp com.alepo.hooks.concurrentloginexception cannot resolved type 114: <liferay-ui:error exception="<%= userlockoutexception.class %>" message="this-account-has-been-locked" /> 115: <liferay-ui:error exception="<%= userpasswordexception.class %>" message="please-enter-a-valid-password" /> 116: <liferay-ui:error exception="<%= userscreennameexception.class %>" message="please-enter-a-valid-screen-name" /> 117: <liferay-ui:error exception="<%= com.alepo.hooks.concurrentloginexception.class %>" message="max-sessions-exceeded" /> 118: 119: <fieldset class="block-labels"> 120: <div class="ctrl-holder"> stacktrace: @ org.apache.jasper.compiler.defaulterrorhandler.javacerror(defaulterrorhandler.java:93) @ org.apache.jasper.compiler.errordispatcher.javacerror(errordispatcher.java:330) @ org.apache.jasper.compiler.jdtcompiler.generateclass(jdtcompiler.java:451) @ org.apache.jasper.compiler.compiler.compile(compiler.java:328) @ org.apache.jasper.compiler.compiler.compile(compiler.java:307) @ org.apache.jasper.compiler.compiler.compile(compiler.java:295) @ org.apache.jasper.jspcompilationcontext.compile(jspcompilationcontext.java:565) @ org.apache.jasper.servlet.jspservletwrapper.service(jspservletwrapper.java:311) @ org.apache.jasper.servlet.jspservlet.servicejspfile(jspservlet.java:308) @ org.apache.jasper.servlet.jspservlet.service(jspservlet.java:259) @ javax.servlet.http.httpservlet.service(httpservlet.java:729) @ org.apache.catalina.core.applicationfilterchain.internaldofilter(applicationfilterchain.java:269) @ org.apache.catalina.core.applicationfilterchain.dofilter(applicationfilterchain.java:188) @ org.apache.catalina.core.applicationdispatcher.invoke(applicationdispatcher.java:679) @ org.apache.catalina.core.applicationdispatcher.doinclude(applicationdispatcher.java:584) @ org.apache.catalina.core.applicationdispatcher.include(applicationdispatcher.java:497) @ com.liferay.taglib.util.includetag.doendtag(includetag.java:67) @ org.apache.jsp.html.common.themes.portlet_jsp._jspservice(portlet_jsp.java:2669) @ org.apache.jasper.runtime.httpjspbase.service(httpjspbase.java:98)
any idea it?
it seems custom login-hook messed-up , not problem theme.
if read error carefully:
an error occurred @ line: 117 in jsp file: /html/portlet/login/login.jsp com.alepo.hooks.concurrentloginexception cannot resolved type
so happening /html/portlet/login/login.jsp
not able find class concurrentloginexception
resides in hook, why happening because way liferay handles class-loading.
in short, there 3 classloaders:
- global (the classes in servers lib
tomcat/ext/lib
database drivers ,portal-service.jar
): these classes can used , available plugins context , liferay's context. - portal classloader (classes in
root/web-inf/lib
famousportal-impl.jar
): these classes or implementation available liferay's context. - portlet / plugin classloader (loads classes of our plugins): these available our plugins (portlets, hooks etc) , not available liferay's modules/context.
so after short crash-course may have known problem is, still try answer (for points sake :-).
so here is, since jsp-hook modifies liferay's jsp , copied on root
directory falls under liferay's context custom class created inside plugin (portlet or hook or themes) not available jsp, in case login.jsp
.
so either don't use class ;-) inside jsp or put exception class (packaged in jar) in global path i.e. tomcat/ext/lib
available login.jsp
.
here verdict liferay staff on similar issue , answer might drive concept home , in future.
Starting Liferay - >>>>> Download Now
ReplyDelete>>>>> Download Full
Starting Liferay - >>>>> Download LINK
>>>>> Download Now
Starting Liferay - >>>>> Download Full
>>>>> Download LINK Ga