Denis Signoretto 9年 前 Hi Jorge,great news, in particular the possibilty to implement DDM field types as OSGI modules! (Is there a way to get the same result on 6.2 or we still need an ext plugin to get the same result?. Is there a forecast for Standalone Apps avalability (which mileston can we expect to get it included) ?Many Thanks,Denis. 投票するためにはログインが必要です。 次として送信する: キャンセル Jorge Ferrer Denis Signoretto 9年 前 Thanks Denis, I'm glad you liked it.Regarding Standalone Apps, it encompasses many ideas of how to develop frontend apps. What specific idea are you looking forward to? Is it the concept of full page apps? REST services? Datastore service? something else? 投票するためにはログインが必要です。 次として送信する: キャンセル Gustav Novotný Jorge Ferrer 9年 前 For me it'd be great to have more info on SPA enabler support (maybe some API description, example or whatever else). Thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル Christoph Rabel Denis Signoretto 9年 前 DDM Fields in 6.2:Well you can "kinda sorta" avoid using an ext plugin.Note: In earlier builds "liferay-ddm-structure_6_2_0.xsd" in portal-impl enforced a check on the datatypes used in DDMs. Not sure when this check was removed. At least in SP 7 it isn't there anymore. Before that patch it's more complicated.You need to hook/html/portlet/dynamic_data_mapping/js/main.js/html/portlet/dynamic_data_mapping/custom_fields.jspfand add your own field to Formbuilder. That covers the "admin part", adding a field to a structure.Alas, when a formfield is shown to the user it is rendered using ftl templates in portal-impl.jar. You need to add your own ftl into the template folder. And that requires an ext plugin ...The only thing I found as a workaround was to put my ftl files into the classes folder instead:/webapps/ROOT/WEB-INF/classes/com/liferay/portlet/dynamicdatamapping/dependencies/mydatatype.ftlhth 投票するためにはログインが必要です。 次として送信する: キャンセル
Jorge Ferrer Denis Signoretto 9年 前 Thanks Denis, I'm glad you liked it.Regarding Standalone Apps, it encompasses many ideas of how to develop frontend apps. What specific idea are you looking forward to? Is it the concept of full page apps? REST services? Datastore service? something else? 投票するためにはログインが必要です。 次として送信する: キャンセル Gustav Novotný Jorge Ferrer 9年 前 For me it'd be great to have more info on SPA enabler support (maybe some API description, example or whatever else). Thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Gustav Novotný Jorge Ferrer 9年 前 For me it'd be great to have more info on SPA enabler support (maybe some API description, example or whatever else). Thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Christoph Rabel Denis Signoretto 9年 前 DDM Fields in 6.2:Well you can "kinda sorta" avoid using an ext plugin.Note: In earlier builds "liferay-ddm-structure_6_2_0.xsd" in portal-impl enforced a check on the datatypes used in DDMs. Not sure when this check was removed. At least in SP 7 it isn't there anymore. Before that patch it's more complicated.You need to hook/html/portlet/dynamic_data_mapping/js/main.js/html/portlet/dynamic_data_mapping/custom_fields.jspfand add your own field to Formbuilder. That covers the "admin part", adding a field to a structure.Alas, when a formfield is shown to the user it is rendered using ftl templates in portal-impl.jar. You need to add your own ftl into the template folder. And that requires an ext plugin ...The only thing I found as a workaround was to put my ftl files into the classes folder instead:/webapps/ROOT/WEB-INF/classes/com/liferay/portlet/dynamicdatamapping/dependencies/mydatatype.ftlhth 投票するためにはログインが必要です。 次として送信する: キャンセル
Daniel Niklas 9年 前 Great news!Whats about support for Wildfly? Best regardsDaniel :-) 投票するためにはログインが必要です。 次として送信する: キャンセル
Ivano Carrara 9年 前 Each article of Jorge Ferrer puts me in a good mood !!Thank you Jorge !Ivano C. 投票するためにはログインが必要です。 次として送信する: キャンセル
Ruud Kluivers 9年 前 This is great news and progress. I am sure our current and future customers will appreciate the hard work and results fro Liferay 7.0.Thinking about Document Management, obviously integrating Google Drive will be superb, but how about also adding Microsoft OneDrive and Apple iCloud. support? Maybe a wild idea but both Microsoft and Apple are opening up their cloud storage solutions to others. 投票するためにはログインが必要です。 次として送信する: キャンセル
Lukas Kornprobst 9年 前 Hi Jorge,you write in one of your Blogs that in Liferay 7 it is possible to configure mail notification templates in multiple languages. (Very nice and long-awaited feature ;))I have see this function only for apps/portlets, which send mails.But what about the general mails like "member request" for a site or something else? I don't find this for that.Would it not make sense to make it possible to change also all other global mails, like member request, how you can do that for Password Reset Notification, Password Changed Notification, etc. under "Control Panel->Portal Settings->Email Notifications"?This would fit well under the point "Email Notifications".We have do that in 6.2 with an Ext-Plugin for all mail templates, but this is very bad to handle.I hope you know what I mean and if I have overlook this, can you please tell me where I can find this?Kind regards,Lukas 投票するためにはログインが必要です。 次として送信する: キャンセル Jorge Ferrer Lukas Kornprobst 9年 前 Hey Lukas,I think it was only done for portlets and not in the places you mention. However it might not be difficult to do it as well leveraging the infrastructure built already. I will forward your feedback to the team responsible for this improvement. 投票するためにはログインが必要です。 次として送信する: キャンセル Lukas Kornprobst Jorge Ferrer 9年 前 Hi Jorge,thank you very much for your reply and that you forward the feedback from me.I think that it would be perfect if you could customize all emails in Liferay also system/general mails without to build an ext or something else.I'm looking forward for the next Milestone release. 投票するためにはログインが必要です。 次として送信する: キャンセル Sergio González Lukas Kornprobst 9年 前 Hey Lukas,Thanks for your feedback. In 7.0 we include the feature to be able to localize mail templates in every place we had an interface to do so. However, there are some places that didn't have an UI to localize templates and it could only be done via modifications in the source code.I guess that's the case you are referring to. We will evaluate the possibility of including this for 7.0 to make sure that all email templates can be modified and localized from the User interface.Thanks! 投票するためにはログインが必要です。 次として送信する: キャンセル Lukas Kornprobst Sergio González 9年 前 Hey Sergio,thank you for your reply, it was a pleasure for me.Yes that's exactly what I mean.Best regards,Lukas 投票するためにはログインが必要です。 次として送信する: キャンセル
Jorge Ferrer Lukas Kornprobst 9年 前 Hey Lukas,I think it was only done for portlets and not in the places you mention. However it might not be difficult to do it as well leveraging the infrastructure built already. I will forward your feedback to the team responsible for this improvement. 投票するためにはログインが必要です。 次として送信する: キャンセル Lukas Kornprobst Jorge Ferrer 9年 前 Hi Jorge,thank you very much for your reply and that you forward the feedback from me.I think that it would be perfect if you could customize all emails in Liferay also system/general mails without to build an ext or something else.I'm looking forward for the next Milestone release. 投票するためにはログインが必要です。 次として送信する: キャンセル Sergio González Lukas Kornprobst 9年 前 Hey Lukas,Thanks for your feedback. In 7.0 we include the feature to be able to localize mail templates in every place we had an interface to do so. However, there are some places that didn't have an UI to localize templates and it could only be done via modifications in the source code.I guess that's the case you are referring to. We will evaluate the possibility of including this for 7.0 to make sure that all email templates can be modified and localized from the User interface.Thanks! 投票するためにはログインが必要です。 次として送信する: キャンセル Lukas Kornprobst Sergio González 9年 前 Hey Sergio,thank you for your reply, it was a pleasure for me.Yes that's exactly what I mean.Best regards,Lukas 投票するためにはログインが必要です。 次として送信する: キャンセル
Lukas Kornprobst Jorge Ferrer 9年 前 Hi Jorge,thank you very much for your reply and that you forward the feedback from me.I think that it would be perfect if you could customize all emails in Liferay also system/general mails without to build an ext or something else.I'm looking forward for the next Milestone release. 投票するためにはログインが必要です。 次として送信する: キャンセル Sergio González Lukas Kornprobst 9年 前 Hey Lukas,Thanks for your feedback. In 7.0 we include the feature to be able to localize mail templates in every place we had an interface to do so. However, there are some places that didn't have an UI to localize templates and it could only be done via modifications in the source code.I guess that's the case you are referring to. We will evaluate the possibility of including this for 7.0 to make sure that all email templates can be modified and localized from the User interface.Thanks! 投票するためにはログインが必要です。 次として送信する: キャンセル Lukas Kornprobst Sergio González 9年 前 Hey Sergio,thank you for your reply, it was a pleasure for me.Yes that's exactly what I mean.Best regards,Lukas 投票するためにはログインが必要です。 次として送信する: キャンセル
Sergio González Lukas Kornprobst 9年 前 Hey Lukas,Thanks for your feedback. In 7.0 we include the feature to be able to localize mail templates in every place we had an interface to do so. However, there are some places that didn't have an UI to localize templates and it could only be done via modifications in the source code.I guess that's the case you are referring to. We will evaluate the possibility of including this for 7.0 to make sure that all email templates can be modified and localized from the User interface.Thanks! 投票するためにはログインが必要です。 次として送信する: キャンセル Lukas Kornprobst Sergio González 9年 前 Hey Sergio,thank you for your reply, it was a pleasure for me.Yes that's exactly what I mean.Best regards,Lukas 投票するためにはログインが必要です。 次として送信する: キャンセル
Lukas Kornprobst Sergio González 9年 前 Hey Sergio,thank you for your reply, it was a pleasure for me.Yes that's exactly what I mean.Best regards,Lukas 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi 9年 前 Drag-and-Drop portlets into new location does not work; but I was able to make it working after installing fake 'classic'-based theme built in Liferay M3 SDK. Which means bug in a theme in M4. 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 The bug is in "portlet.css" file; the (temporary) fix is to copy this file from Liferay 7 M3 into Liferay 7 M4.Sorry to hear about such trivial (and critical!!! how can I manage portal without moving portlets on a page?) issues ;) fortunately fix was found quickly. 投票するためにはログインが必要です。 次として送信する: キャンセル Nate Cavanaugh Fuad Efendi 9年 前 Hi Faud,Do you have any details on this, such as browser and version, if this happens in the Classic theme (or is it only in your custom theme), and if it's all portlets, or only some portlets?We haven't ever seen this in portal, but I'm interesting in seeing if we can spot a cause Thanks Faud! 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate,It happens with all browser versions I have, with the default Liferay theme (which is "classic"); note that I removed LiferayWelcomeTheme and I configured MySQL before first/initial Liferay startup. The same happened in both, MacOS and Windows. Solution for me was to create "classic"-based theme in Liferay 7 M4 SDK, and to copy there "portlet.css" file from Liferay 7 M3 "classic" theme.- Fuad 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 I mean: I installed Liferay & SDK in MacOS and followed the same steps; and in WIndows (on different machine) and followed the same steps; everything was installed locally, at "localhost" 投票するためにはログインが必要です。 次として送信する: キャンセル Nate Cavanaugh Fuad Efendi 9年 前 Hi Faud,I actually took a look, and this was fixed in https://issues.liferay.com/browse/LPS-53739So you can still drag and drop portlets in M4, but you need to do so by clicking on the title of the text.Again, sorry it popped up, but we've squashed it Thanks for the feedback! 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate, Thanks for the research;I tried clicking on the title text of the portlet... it works! But it is absolutely non-intuitive because cursor icon is everywhere else is "four-arrows" (corresponding to "drag-and-drop" action), but on a text title it is "pointer" (corresponding to "click" action)But it does work; thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi Fuad Efendi 9年 前 The bug is in "portlet.css" file; the (temporary) fix is to copy this file from Liferay 7 M3 into Liferay 7 M4.Sorry to hear about such trivial (and critical!!! how can I manage portal without moving portlets on a page?) issues ;) fortunately fix was found quickly. 投票するためにはログインが必要です。 次として送信する: キャンセル Nate Cavanaugh Fuad Efendi 9年 前 Hi Faud,Do you have any details on this, such as browser and version, if this happens in the Classic theme (or is it only in your custom theme), and if it's all portlets, or only some portlets?We haven't ever seen this in portal, but I'm interesting in seeing if we can spot a cause Thanks Faud! 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate,It happens with all browser versions I have, with the default Liferay theme (which is "classic"); note that I removed LiferayWelcomeTheme and I configured MySQL before first/initial Liferay startup. The same happened in both, MacOS and Windows. Solution for me was to create "classic"-based theme in Liferay 7 M4 SDK, and to copy there "portlet.css" file from Liferay 7 M3 "classic" theme.- Fuad 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 I mean: I installed Liferay & SDK in MacOS and followed the same steps; and in WIndows (on different machine) and followed the same steps; everything was installed locally, at "localhost" 投票するためにはログインが必要です。 次として送信する: キャンセル Nate Cavanaugh Fuad Efendi 9年 前 Hi Faud,I actually took a look, and this was fixed in https://issues.liferay.com/browse/LPS-53739So you can still drag and drop portlets in M4, but you need to do so by clicking on the title of the text.Again, sorry it popped up, but we've squashed it Thanks for the feedback! 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate, Thanks for the research;I tried clicking on the title text of the portlet... it works! But it is absolutely non-intuitive because cursor icon is everywhere else is "four-arrows" (corresponding to "drag-and-drop" action), but on a text title it is "pointer" (corresponding to "click" action)But it does work; thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Nate Cavanaugh Fuad Efendi 9年 前 Hi Faud,Do you have any details on this, such as browser and version, if this happens in the Classic theme (or is it only in your custom theme), and if it's all portlets, or only some portlets?We haven't ever seen this in portal, but I'm interesting in seeing if we can spot a cause Thanks Faud! 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate,It happens with all browser versions I have, with the default Liferay theme (which is "classic"); note that I removed LiferayWelcomeTheme and I configured MySQL before first/initial Liferay startup. The same happened in both, MacOS and Windows. Solution for me was to create "classic"-based theme in Liferay 7 M4 SDK, and to copy there "portlet.css" file from Liferay 7 M3 "classic" theme.- Fuad 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 I mean: I installed Liferay & SDK in MacOS and followed the same steps; and in WIndows (on different machine) and followed the same steps; everything was installed locally, at "localhost" 投票するためにはログインが必要です。 次として送信する: キャンセル Nate Cavanaugh Fuad Efendi 9年 前 Hi Faud,I actually took a look, and this was fixed in https://issues.liferay.com/browse/LPS-53739So you can still drag and drop portlets in M4, but you need to do so by clicking on the title of the text.Again, sorry it popped up, but we've squashed it Thanks for the feedback! 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate, Thanks for the research;I tried clicking on the title text of the portlet... it works! But it is absolutely non-intuitive because cursor icon is everywhere else is "four-arrows" (corresponding to "drag-and-drop" action), but on a text title it is "pointer" (corresponding to "click" action)But it does work; thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate,It happens with all browser versions I have, with the default Liferay theme (which is "classic"); note that I removed LiferayWelcomeTheme and I configured MySQL before first/initial Liferay startup. The same happened in both, MacOS and Windows. Solution for me was to create "classic"-based theme in Liferay 7 M4 SDK, and to copy there "portlet.css" file from Liferay 7 M3 "classic" theme.- Fuad 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 I mean: I installed Liferay & SDK in MacOS and followed the same steps; and in WIndows (on different machine) and followed the same steps; everything was installed locally, at "localhost" 投票するためにはログインが必要です。 次として送信する: キャンセル Nate Cavanaugh Fuad Efendi 9年 前 Hi Faud,I actually took a look, and this was fixed in https://issues.liferay.com/browse/LPS-53739So you can still drag and drop portlets in M4, but you need to do so by clicking on the title of the text.Again, sorry it popped up, but we've squashed it Thanks for the feedback! 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate, Thanks for the research;I tried clicking on the title text of the portlet... it works! But it is absolutely non-intuitive because cursor icon is everywhere else is "four-arrows" (corresponding to "drag-and-drop" action), but on a text title it is "pointer" (corresponding to "click" action)But it does work; thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi Fuad Efendi 9年 前 I mean: I installed Liferay & SDK in MacOS and followed the same steps; and in WIndows (on different machine) and followed the same steps; everything was installed locally, at "localhost" 投票するためにはログインが必要です。 次として送信する: キャンセル Nate Cavanaugh Fuad Efendi 9年 前 Hi Faud,I actually took a look, and this was fixed in https://issues.liferay.com/browse/LPS-53739So you can still drag and drop portlets in M4, but you need to do so by clicking on the title of the text.Again, sorry it popped up, but we've squashed it Thanks for the feedback! 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate, Thanks for the research;I tried clicking on the title text of the portlet... it works! But it is absolutely non-intuitive because cursor icon is everywhere else is "four-arrows" (corresponding to "drag-and-drop" action), but on a text title it is "pointer" (corresponding to "click" action)But it does work; thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Nate Cavanaugh Fuad Efendi 9年 前 Hi Faud,I actually took a look, and this was fixed in https://issues.liferay.com/browse/LPS-53739So you can still drag and drop portlets in M4, but you need to do so by clicking on the title of the text.Again, sorry it popped up, but we've squashed it Thanks for the feedback! 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate, Thanks for the research;I tried clicking on the title text of the portlet... it works! But it is absolutely non-intuitive because cursor icon is everywhere else is "four-arrows" (corresponding to "drag-and-drop" action), but on a text title it is "pointer" (corresponding to "click" action)But it does work; thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi Nate Cavanaugh 9年 前 Hi Nate, Thanks for the research;I tried clicking on the title text of the portlet... it works! But it is absolutely non-intuitive because cursor icon is everywhere else is "four-arrows" (corresponding to "drag-and-drop" action), but on a text title it is "pointer" (corresponding to "click" action)But it does work; thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi 9年 前 Cannot add WIKI to the Public Page. No error message output; page becomes broken/empty; I am going to create JIRA ticket for this if it does not exist yet.I noticed that WIKI is deployed as OSGI module, and I couldn't find related *.class files in Tomcat "temp" folder. 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 I think this is problem specific to OSGI modules not having precompiled JSPs inside; same problem with Polls Display. 投票するためにはログインが必要です。 次として送信する: キャンセル Ivan Zaera Fuad Efendi 9年 前 Fuad:As of version 7, OSGi module's JSPs are no longer precompiled. This is because you need the full OSGi runtime up and running to resolve all dependencies. That's the reason why you don't see the JSP class files.Regarding the error about the wiki page, can you provide more info? Any logs or any error message?Thanks,Ivan 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Ivan Zaera 9年 前 No any error logs.Simply: download Tomcat-based distribution, start it, and try to add WIKI to a page. The same with few other OSGI-based portlets.Trying to refresh a page after that: empty page shown, no any error message.Easy to reproduce.No any error logs; perhaps someone tried to swallow Throwable Also, M4 distribution has broken Docs archive (yes, some people need it to configure IDE) 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 Perhaps this is the root of the problem, OSGI simply stops after that:17:37:38,342 ERROR [com.liferay.portal.log.bridge.internal.LogBridge@59ca3022][com_liferay_social_networking_web:75] FrameworkEvent ERRORorg.osgi.framework.BundleException: Could not resolve module: com.liferay.social.networking.web [87]_ Unresolved requirement: Import-Package: com.liferay.ip.geocoder_ [Sanitized] at org.eclipse.osgi.container.Module.start(Module.java:434) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:242) at org.eclipse.osgi.container.Module.doStart(Module.java:571) at org.eclipse.osgi.container.Module.start(Module.java:439) at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:172) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:392) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:411) at org.eclipse.osgi.launch.Equinox.start(Equinox.java:115) at com.liferay.portal.bootstrap.ModuleFrameworkImpl.startFramework(ModuleFrameworkImpl.java:322) at com.liferay.portal.module.framework.ModuleFrameworkUtilAdapter.startFramework(ModuleFrameworkUtilAdapter.java:85) at com.liferay.portal.spring.context.PortalContextLoaderListener.contextInitialized(PortalContextLoaderListener.java:252) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4939) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5434) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:656) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1635) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Apr 01, 2015 5:37:38 PM org.apache.catalina.core.ApplicationContext log 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 Today I tried to recompile GIT "master" version, and WIKI works fine.Though, this is mandatory:theme.jsp.override.enabled=trueWithout that WIKI will output log messages regarding not available JSPs from tag library. 投票するためにはログインが必要です。 次として送信する: キャンセル Ivan Zaera Fuad Efendi 9年 前 Hi Fuad:As you found out, the issue is fixed in master, as stated here: https://dev.liferay.com/web/liferay-7-community-expedition/feedback/-/message_boards/view_message/403987#_19_message_403987Thanks a lot for your feedback, anyway. :-)Nevertheless, I would suggest that for further feedback you use the feedback forums in the link I'm sending you so that you can get a faster response and everybody knows of your findings.Thanks again,Ivan 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi Fuad Efendi 9年 前 I think this is problem specific to OSGI modules not having precompiled JSPs inside; same problem with Polls Display. 投票するためにはログインが必要です。 次として送信する: キャンセル Ivan Zaera Fuad Efendi 9年 前 Fuad:As of version 7, OSGi module's JSPs are no longer precompiled. This is because you need the full OSGi runtime up and running to resolve all dependencies. That's the reason why you don't see the JSP class files.Regarding the error about the wiki page, can you provide more info? Any logs or any error message?Thanks,Ivan 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Ivan Zaera 9年 前 No any error logs.Simply: download Tomcat-based distribution, start it, and try to add WIKI to a page. The same with few other OSGI-based portlets.Trying to refresh a page after that: empty page shown, no any error message.Easy to reproduce.No any error logs; perhaps someone tried to swallow Throwable Also, M4 distribution has broken Docs archive (yes, some people need it to configure IDE) 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 Perhaps this is the root of the problem, OSGI simply stops after that:17:37:38,342 ERROR [com.liferay.portal.log.bridge.internal.LogBridge@59ca3022][com_liferay_social_networking_web:75] FrameworkEvent ERRORorg.osgi.framework.BundleException: Could not resolve module: com.liferay.social.networking.web [87]_ Unresolved requirement: Import-Package: com.liferay.ip.geocoder_ [Sanitized] at org.eclipse.osgi.container.Module.start(Module.java:434) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:242) at org.eclipse.osgi.container.Module.doStart(Module.java:571) at org.eclipse.osgi.container.Module.start(Module.java:439) at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:172) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:392) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:411) at org.eclipse.osgi.launch.Equinox.start(Equinox.java:115) at com.liferay.portal.bootstrap.ModuleFrameworkImpl.startFramework(ModuleFrameworkImpl.java:322) at com.liferay.portal.module.framework.ModuleFrameworkUtilAdapter.startFramework(ModuleFrameworkUtilAdapter.java:85) at com.liferay.portal.spring.context.PortalContextLoaderListener.contextInitialized(PortalContextLoaderListener.java:252) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4939) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5434) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:656) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1635) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Apr 01, 2015 5:37:38 PM org.apache.catalina.core.ApplicationContext log 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 Today I tried to recompile GIT "master" version, and WIKI works fine.Though, this is mandatory:theme.jsp.override.enabled=trueWithout that WIKI will output log messages regarding not available JSPs from tag library. 投票するためにはログインが必要です。 次として送信する: キャンセル Ivan Zaera Fuad Efendi 9年 前 Hi Fuad:As you found out, the issue is fixed in master, as stated here: https://dev.liferay.com/web/liferay-7-community-expedition/feedback/-/message_boards/view_message/403987#_19_message_403987Thanks a lot for your feedback, anyway. :-)Nevertheless, I would suggest that for further feedback you use the feedback forums in the link I'm sending you so that you can get a faster response and everybody knows of your findings.Thanks again,Ivan 投票するためにはログインが必要です。 次として送信する: キャンセル
Ivan Zaera Fuad Efendi 9年 前 Fuad:As of version 7, OSGi module's JSPs are no longer precompiled. This is because you need the full OSGi runtime up and running to resolve all dependencies. That's the reason why you don't see the JSP class files.Regarding the error about the wiki page, can you provide more info? Any logs or any error message?Thanks,Ivan 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Ivan Zaera 9年 前 No any error logs.Simply: download Tomcat-based distribution, start it, and try to add WIKI to a page. The same with few other OSGI-based portlets.Trying to refresh a page after that: empty page shown, no any error message.Easy to reproduce.No any error logs; perhaps someone tried to swallow Throwable Also, M4 distribution has broken Docs archive (yes, some people need it to configure IDE) 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 Perhaps this is the root of the problem, OSGI simply stops after that:17:37:38,342 ERROR [com.liferay.portal.log.bridge.internal.LogBridge@59ca3022][com_liferay_social_networking_web:75] FrameworkEvent ERRORorg.osgi.framework.BundleException: Could not resolve module: com.liferay.social.networking.web [87]_ Unresolved requirement: Import-Package: com.liferay.ip.geocoder_ [Sanitized] at org.eclipse.osgi.container.Module.start(Module.java:434) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:242) at org.eclipse.osgi.container.Module.doStart(Module.java:571) at org.eclipse.osgi.container.Module.start(Module.java:439) at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:172) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:392) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:411) at org.eclipse.osgi.launch.Equinox.start(Equinox.java:115) at com.liferay.portal.bootstrap.ModuleFrameworkImpl.startFramework(ModuleFrameworkImpl.java:322) at com.liferay.portal.module.framework.ModuleFrameworkUtilAdapter.startFramework(ModuleFrameworkUtilAdapter.java:85) at com.liferay.portal.spring.context.PortalContextLoaderListener.contextInitialized(PortalContextLoaderListener.java:252) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4939) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5434) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:656) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1635) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Apr 01, 2015 5:37:38 PM org.apache.catalina.core.ApplicationContext log 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 Today I tried to recompile GIT "master" version, and WIKI works fine.Though, this is mandatory:theme.jsp.override.enabled=trueWithout that WIKI will output log messages regarding not available JSPs from tag library. 投票するためにはログインが必要です。 次として送信する: キャンセル Ivan Zaera Fuad Efendi 9年 前 Hi Fuad:As you found out, the issue is fixed in master, as stated here: https://dev.liferay.com/web/liferay-7-community-expedition/feedback/-/message_boards/view_message/403987#_19_message_403987Thanks a lot for your feedback, anyway. :-)Nevertheless, I would suggest that for further feedback you use the feedback forums in the link I'm sending you so that you can get a faster response and everybody knows of your findings.Thanks again,Ivan 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi Ivan Zaera 9年 前 No any error logs.Simply: download Tomcat-based distribution, start it, and try to add WIKI to a page. The same with few other OSGI-based portlets.Trying to refresh a page after that: empty page shown, no any error message.Easy to reproduce.No any error logs; perhaps someone tried to swallow Throwable Also, M4 distribution has broken Docs archive (yes, some people need it to configure IDE) 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 Perhaps this is the root of the problem, OSGI simply stops after that:17:37:38,342 ERROR [com.liferay.portal.log.bridge.internal.LogBridge@59ca3022][com_liferay_social_networking_web:75] FrameworkEvent ERRORorg.osgi.framework.BundleException: Could not resolve module: com.liferay.social.networking.web [87]_ Unresolved requirement: Import-Package: com.liferay.ip.geocoder_ [Sanitized] at org.eclipse.osgi.container.Module.start(Module.java:434) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:242) at org.eclipse.osgi.container.Module.doStart(Module.java:571) at org.eclipse.osgi.container.Module.start(Module.java:439) at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:172) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:392) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:411) at org.eclipse.osgi.launch.Equinox.start(Equinox.java:115) at com.liferay.portal.bootstrap.ModuleFrameworkImpl.startFramework(ModuleFrameworkImpl.java:322) at com.liferay.portal.module.framework.ModuleFrameworkUtilAdapter.startFramework(ModuleFrameworkUtilAdapter.java:85) at com.liferay.portal.spring.context.PortalContextLoaderListener.contextInitialized(PortalContextLoaderListener.java:252) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4939) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5434) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:656) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1635) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Apr 01, 2015 5:37:38 PM org.apache.catalina.core.ApplicationContext log 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 Today I tried to recompile GIT "master" version, and WIKI works fine.Though, this is mandatory:theme.jsp.override.enabled=trueWithout that WIKI will output log messages regarding not available JSPs from tag library. 投票するためにはログインが必要です。 次として送信する: キャンセル Ivan Zaera Fuad Efendi 9年 前 Hi Fuad:As you found out, the issue is fixed in master, as stated here: https://dev.liferay.com/web/liferay-7-community-expedition/feedback/-/message_boards/view_message/403987#_19_message_403987Thanks a lot for your feedback, anyway. :-)Nevertheless, I would suggest that for further feedback you use the feedback forums in the link I'm sending you so that you can get a faster response and everybody knows of your findings.Thanks again,Ivan 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi Fuad Efendi 9年 前 Perhaps this is the root of the problem, OSGI simply stops after that:17:37:38,342 ERROR [com.liferay.portal.log.bridge.internal.LogBridge@59ca3022][com_liferay_social_networking_web:75] FrameworkEvent ERRORorg.osgi.framework.BundleException: Could not resolve module: com.liferay.social.networking.web [87]_ Unresolved requirement: Import-Package: com.liferay.ip.geocoder_ [Sanitized] at org.eclipse.osgi.container.Module.start(Module.java:434) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:242) at org.eclipse.osgi.container.Module.doStart(Module.java:571) at org.eclipse.osgi.container.Module.start(Module.java:439) at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:172) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:392) at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:411) at org.eclipse.osgi.launch.Equinox.start(Equinox.java:115) at com.liferay.portal.bootstrap.ModuleFrameworkImpl.startFramework(ModuleFrameworkImpl.java:322) at com.liferay.portal.module.framework.ModuleFrameworkUtilAdapter.startFramework(ModuleFrameworkUtilAdapter.java:85) at com.liferay.portal.spring.context.PortalContextLoaderListener.contextInitialized(PortalContextLoaderListener.java:252) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4939) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5434) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:656) at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1635) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Apr 01, 2015 5:37:38 PM org.apache.catalina.core.ApplicationContext log 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Fuad Efendi 9年 前 Today I tried to recompile GIT "master" version, and WIKI works fine.Though, this is mandatory:theme.jsp.override.enabled=trueWithout that WIKI will output log messages regarding not available JSPs from tag library. 投票するためにはログインが必要です。 次として送信する: キャンセル Ivan Zaera Fuad Efendi 9年 前 Hi Fuad:As you found out, the issue is fixed in master, as stated here: https://dev.liferay.com/web/liferay-7-community-expedition/feedback/-/message_boards/view_message/403987#_19_message_403987Thanks a lot for your feedback, anyway. :-)Nevertheless, I would suggest that for further feedback you use the feedback forums in the link I'm sending you so that you can get a faster response and everybody knows of your findings.Thanks again,Ivan 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi Fuad Efendi 9年 前 Today I tried to recompile GIT "master" version, and WIKI works fine.Though, this is mandatory:theme.jsp.override.enabled=trueWithout that WIKI will output log messages regarding not available JSPs from tag library. 投票するためにはログインが必要です。 次として送信する: キャンセル Ivan Zaera Fuad Efendi 9年 前 Hi Fuad:As you found out, the issue is fixed in master, as stated here: https://dev.liferay.com/web/liferay-7-community-expedition/feedback/-/message_boards/view_message/403987#_19_message_403987Thanks a lot for your feedback, anyway. :-)Nevertheless, I would suggest that for further feedback you use the feedback forums in the link I'm sending you so that you can get a faster response and everybody knows of your findings.Thanks again,Ivan 投票するためにはログインが必要です。 次として送信する: キャンセル
Ivan Zaera Fuad Efendi 9年 前 Hi Fuad:As you found out, the issue is fixed in master, as stated here: https://dev.liferay.com/web/liferay-7-community-expedition/feedback/-/message_boards/view_message/403987#_19_message_403987Thanks a lot for your feedback, anyway. :-)Nevertheless, I would suggest that for further feedback you use the feedback forums in the link I'm sending you so that you can get a faster response and everybody knows of your findings.Thanks again,Ivan 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi 9年 前 Really Cool:- moving from Struts to MVCPortlet (I love it!!!) 投票するためにはログインが必要です。 次として送信する: キャンセル Jorge Ferrer Fuad Efendi 9年 前 Hey Fuad, Have you signed up to the Liferay 7 Community Expedition?This feedback you are providing is very useful and doing it in the Expedition site will ensure it gets the best visibility: https://dev.liferay.com/web/liferay-7-community-expedition 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Jorge Ferrer 8年 前 Yes, signed up; nice environment for collaborators, thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Jorge Ferrer Fuad Efendi 9年 前 Hey Fuad, Have you signed up to the Liferay 7 Community Expedition?This feedback you are providing is very useful and doing it in the Expedition site will ensure it gets the best visibility: https://dev.liferay.com/web/liferay-7-community-expedition 投票するためにはログインが必要です。 次として送信する: キャンセル Fuad Efendi Jorge Ferrer 8年 前 Yes, signed up; nice environment for collaborators, thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル
Fuad Efendi Jorge Ferrer 8年 前 Yes, signed up; nice environment for collaborators, thank you! 投票するためにはログインが必要です。 次として送信する: キャンセル