Fórumok

Nyitólap » Liferay Portal » English » 3. Development

RSS hírcsatorna (Új ablakot nyit)

Kombinált nézet Egyszerű nézet Fa-nézet
Szálak [ Előző | Következő ]
Névtelen
Portlet deployed successfully but not showing up in liferay portal
2012. január 16. 2:07
Válasz

Névtelen

Hi there,

I'm working in Netbeans and have recently been working on a portlet. Everything was going quite well, code-deploy-test-etc etc. But now when I tried to deploy it, the console says that the portlet has been deployed successfully. But when I go into the liferay portal, there's nothing there??

In the output it says the following: 0 portlets for MedelogGetAdmin(project name) are available for use The full console output is as follows:

Extracted : C:\Users\dean.grobler\Documents\NetBeansProjects\MedelogGetAdmin\dist\MedelogGetAdmin.war
09:18:17,644 INFO [AutoDeployDir:167] Processing MedelogGetAdmin.xml
09:18:17,658 INFO [PortletExplodedTomcatListener:59] Modifying portlets for C:\Users\dean.grobler\Documents\Liferay 2\liferay-portal-6.0.6\deploy\MedelogGetAdmin.xml
Copying 1 file to C:\Users\DEAN~1.GRO\AppData\Local\Temp\portalpack\1326705493028\WEB-INF\classes
Copying 1 file to C:\Users\DEAN~1.GRO\AppData\Local\Temp\portalpack\1326705493028\WEB-INF\classes
09:18:18,482 INFO [PortletExplodedTomcatListener:65] Portlets for C:\Users\dean.grobler\Documents\Liferay 2\liferay-portal-6.0.6\deploy\MedelogGetAdmin.xml modified successfully
09:18:18,483 INFO [BaseExplodedTomcatListener:45] Copying file C:\Users\dean.grobler\Documents\Liferay 2\liferay-portal-6.0.6\deploy\MedelogGetAdmin.xml to ../conf/Catalina/localhost
C:\Users\dean.grobler\Documents\NetBeansProjects\MedelogGetAdmin\dist\MedelogGetAdmin.war file updated successfully.
Time taken for massaging : 5 sec
09:18:30,293 WARN [PluginPackageUtil:1186] Unable to reindex unistalled package MedelogGetAdmin: Unable to communicate with repository http://plugins.liferay.com/official
09:18:30,314 INFO [ExtHotDeployListener:205] Extension environment for MedelogGetAdmin will not be undeployed
09:18:30,315 INFO [PortletHotDeployListener:404] Unregistering portlets for MedelogGetAdmin
09:18:30,323 INFO [PortletHotDeployListener:440] 0 portlets for MedelogGetAdmin was unregistered
Error in annotation processing: java.lang.NoClassDefFoundError: org/springframework/transaction/PlatformTransactionManager
Error in annotation processing: java.lang.NoClassDefFoundError: org/springframework/transaction/PlatformTransactionManager
09:18:32,861 INFO [PortletHotDeployListener:220] Registering portlets for MedelogGetAdmin
09:18:33,005 ERROR [PortletBagFactory:115] java.lang.ClassNotFoundException: co.za.lancet.medelogget.MedelogGetAdmin
java.lang.ClassNotFoundException: co.za.lancet.medelogget.MedelogGetAdmin
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at org.glassfish.web.loader.WebappClassLoader.findClass(WebappClassLoader.java:959)
at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1430)
at com.liferay.portlet.PortletBagFactory.create(PortletBagFactory.java:112)
at com.liferay.portal.deploy.hot.PortletHotDeployListener.initPortlet(PortletHotDeployListener.java:456)
at com.liferay.portal.deploy.hot.PortletHotDeployListener.doInvokeDeploy(PortletHotDeployListener.java:253)
at com.liferay.portal.deploy.hot.PortletHotDeployListener.invokeDeploy(PortletHotDeployListener.java:101)
at com.liferay.portal.kernel.deploy.hot.HotDeployUtil._doFireDeployEvent(HotDeployUtil.java:109)
Deployment of application MedelogGetAdmin
All operations completed successfully
at com.liferay.portal.kernel.deploy.hot.HotDeployUtil._fireDeployEvent(HotDeployUtil.java:182)
at com.liferay.portal.kernel.deploy.hot.HotDeployUtil.fireDeployEvent(HotDeployUtil.java:38)
at com.liferay.portal.kernel.servlet.PortletContextListener.doPortalInit(PortletContextListener.java:99)
at com.liferay.portal.kernel.util.BasePortalLifecycle.portalInit(BasePortalLifecycle.java:42)
at com.liferay.portal.kernel.util.PortalLifecycleUtil.register(PortalLifecycleUtil.java:52)
at com.liferay.portal.kernel.util.BasePortalLifecycle.registerPortalLifecycle(BasePortalLifecycle.java:50)
at com.liferay.portal.kernel.servlet.PortletContextListener.contextInitialized(PortletContextListener.java:55)
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:4664)
at com.sun.enterprise.web.WebModule.contextListenerStart(WebModule.java:535)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5266)
at com.sun.enterprise.web.WebModule.start(WebModule.java:499)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:928)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:912)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:694)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1947)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1619)
at com.sun.enterprise.web.WebApplication.start(WebApplication.java:90)
at org.glassfish.internal.data.EngineRef.start(EngineRef.java:126)
at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:241)
at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:236)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:339)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:365)
at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:204)
at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166)
at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
at java.lang.Thread.run(Thread.java:662)
09:18:33,012 INFO [PortletHotDeployListener:374] 0 portlets for MedelogGetAdmin are available for use
Loading application MedelogGetAdmin at /MedelogGetAdmin
Loading application MedelogGetAdmin at /MedelogGetAdmin
Loading application MedelogGetAdmin at /MedelogGetAdmin
MedelogGetAdmin was successfully deployed in 13,321 milliseconds.
PortalPack Message : Deployed Successfully.



Also worth mentioning that there's no syntax erros and I've also one nothing to the server. No idea why this should happen just all of a sudden.

Any help?

--------------------------------------UPDATE------------------------------------------

With my previous portlets that worked perfectly I see in the directory 'whereYouInstalledLiferay/liferay-portal-6.0.6/deploy' there are .xml files(projectName.xml) that are missing with the portlet that I'm having problems with now. Are these xml files supposed to be automatically generated and are they relevant to my problem that I'm experiencing at the moment?
Jelölés
Gaurang Sheladia
RE: Portlet deployed successfully but not showing up in liferay portal
2012. január 16. 3:59
Válasz

Gaurang Sheladia

Rangsorolás: Regular Member

Hozzászólások: 158

Csatlakozás dátuma: 2009. február 15.

Legújabb hozzászólások

Hi Dean,

In liferay 6 yes it will generate automatically...whenever you are deploying any portlet it will create your-portlet.xml dynamically under /tomcat/conf/root/localhost/

Please let me know for any query.

Thanks,
Gaurang
Jelölés
Névtelen
RE: Portlet deployed successfully but not showing up in liferay portal
2012. január 16. 5:56
Válasz

Névtelen

Hi Gaurang,

Thanks for the reply. And if I'm using Glassfish? Where exactly would that file be saved? Also, if that file is missing could that be a likely problem that it's not showing in liferay portal? And any idea of how I could fix it or trouble shoot on how to fix the problem so that the file can be automatically generated again?

PS - Is liferay usually this unstable? I've been having tons and tons of problems with it...
Jelölés
Ram Manusani
RE: Portlet deployed successfully but not showing up in liferay portal
2012. január 16. 9:55
Válasz

Ram Manusani

Rangsorolás: Regular Member

Hozzászólások: 124

Csatlakozás dátuma: 2011. október 27.

Legújabb hozzászólások

I use tomcat for all development I do and I come across this issue sometimes. But once I clean my temp, work directory and undeploy and deploy the portlet it works.

Well, about the catalina/localhost directory, the xml file is not always generated and that shouldn't be the problem in your case.

Thanks
Jelölés
Jan van der Kaaden
RE: Portlet deployed successfully but not showing up in liferay portal
2012. január 16. 13:01
Válasz

Jan van der Kaaden

Rangsorolás: New Member

Hozzászólások: 20

Csatlakozás dátuma: 2011. március 20.

Legújabb hozzászólások

Hi dean
Did you ever succeed to deploy the portlet without problems or did it went wrong from the first time you tried to deploy it?
Do you have more portlets that use Spring?
Jelölés
Névtelen
RE: Portlet deployed successfully but not showing up in liferay portal
2012. január 16. 22:47
Válasz

Névtelen

Hello Jan,

Nope I haven't got it working yet. I have successfully been deploying this porlet for the past couple of weeks. Then all of a sudden when I deployed it again one day it completely dissapeared off the portal and I haven't been able to redeploy it successfully again.
Jelölés
Névtelen
RE: Portlet deployed successfully but not showing up in liferay portal
2012. január 17. 0:49
Válasz

Névtelen

Just an update here,

I think it what might be the problem is that because I'm working behind a proxy, I can't connect to this: http://plugins.liferay.com/official.

Since the console output says this:
07:34:43,938 WARN [PluginPackageUtil:1186] Unable to reindex unistalled package MedelogGetAdmin: Unable to communicate with repository http://plugins.liferay.com/official
07:34:43,965 INFO [ExtHotDeployListener:205] Extension environment for MedelogGetAdmin will not be undeployed
07:34:43,966 INFO [PortletHotDeployListener:404] Unregistering portlets for MedelogGetAdmin
07:34:43,975 INFO [PortletHotDeployListener:440] 0 portlets for MedelogGetAdmin was unregistered


Please can you let me know if this might be a potential reason why my portlet is being properly deployed?

Thanks in advance,
Jelölés
Jan van der Kaaden
RE: Portlet deployed successfully but not showing up in liferay portal
2012. január 17. 1:32
Válasz

Jan van der Kaaden

Rangsorolás: New Member

Hozzászólások: 20

Csatlakozás dátuma: 2011. március 20.

Legújabb hozzászólások

Hi Dean,

if you want to solve this see the thread:
Unable to Communicate with Repository

I think Ram Manusani has a point, did you succeed to cleanup Tomcat? ( ..../tomcat-x/work/Catalina/localhost )

Regards,
Jan
Jelölés
Gaurav Shirbhate
RE: Portlet deployed successfully but not showing up in liferay portal
2012. október 3. 6:18
Válasz

Gaurav Shirbhate

Rangsorolás: New Member

Hozzászólások: 24

Csatlakozás dátuma: 2012. szeptember 26.

Legújabb hozzászólások

Actually i am having one trigger portlet and receiver portlet. When i am accessing liferay portal as a administrator at this time listener portlet is giving output whatever it has to show, but when i log out. When i am accessing portal as a user at that time listener portlet not showing output whatever it is giving while login. Please give me solution for this.
Jelölés