Matti Tahvonen 9 Years Ago BTW. If you have only one liferay setup on you development machine, you can also activate the liferay profile by default: <activeProfiles> <activeProfile>liferay</activeProfile> </activeProfiles>Then you don't need to explicitly enable it per project in you IDE. Please sign in to reply. Reply as... Cancel
David H Nebinger 9 Years Ago So what is involved w/ switching from "self-contained" to "shared"?Clearly in a production environment with a lot of Vaadin portlets you're going to want to be in shared mode, but if you've created your portlets in "self-contained" mode you'll want to switch them to shared...Worst thing I can think of is a page w/ V7 portlets on it, one running 7.1.1, another running 7.1.2, another running 7.1.3, another running 7.1.4, ...The idea of "self-contained" may seem appealing from a management perspective, but the runtime implications of all of these different versions floating around to me would be a nightmare. Please sign in to reply. Reply as... Cancel Matti Tahvonen David H Nebinger 9 Years Ago Server is using different class loader for different portlets, so only problem at runtime is that there are n+1 classes loaded by the JVM, so there is just slightly more memory used. I wouldn't be concerned about that until it is a problem. In most cases actual sessions consume more memory than loaded class implementations.I'd guess the "nightmare" might start earlier on client side, in case you have multiple different Vaadin portlets, from different war files, visible on the same page. Each new Vaadin app, adds its own widget set -> the amount of loaded JS files grows linearly. Please sign in to reply. Reply as... Cancel David H Nebinger Matti Tahvonen 9 Years Ago Server side is not my concern. Even four V6 portlets end up w/ four copies of the classes loaded.But it's totally the client side browser impact that is my concern. At least when all 4 are using the same version, the theme, js, and the engine are only loaded once...That's why, for my production system, I'd rather switch out of 'self contained' mode and roll back to the single system Vaadin + control panel, just so I can limit the impact on the browser side. Please sign in to reply. Reply as... Cancel alan brito delgado David H Nebinger 9 Years Ago David could you help me with this issue please https://www.liferay.com/es/community/forums/-/message_boards/message/38439950 Please sign in to reply. Reply as... Cancel Matti Tahvonen David H Nebinger 9 Years Ago Agreed, we'll definitely need to cover some best practices for this in upcoming articles. In one don't want to use the Vaadin control panel, one way would be to use a shared "my-company-vaadin-dependencies" project that would define used Vaadin version, possible add-ons and build the shared widget set to be placed into portal wide /html/ directory like to day. Then individual portlet projects would just depend to this project and use the shared widget set like before. Please sign in to reply. Reply as... Cancel
Matti Tahvonen David H Nebinger 9 Years Ago Server is using different class loader for different portlets, so only problem at runtime is that there are n+1 classes loaded by the JVM, so there is just slightly more memory used. I wouldn't be concerned about that until it is a problem. In most cases actual sessions consume more memory than loaded class implementations.I'd guess the "nightmare" might start earlier on client side, in case you have multiple different Vaadin portlets, from different war files, visible on the same page. Each new Vaadin app, adds its own widget set -> the amount of loaded JS files grows linearly. Please sign in to reply. Reply as... Cancel David H Nebinger Matti Tahvonen 9 Years Ago Server side is not my concern. Even four V6 portlets end up w/ four copies of the classes loaded.But it's totally the client side browser impact that is my concern. At least when all 4 are using the same version, the theme, js, and the engine are only loaded once...That's why, for my production system, I'd rather switch out of 'self contained' mode and roll back to the single system Vaadin + control panel, just so I can limit the impact on the browser side. Please sign in to reply. Reply as... Cancel alan brito delgado David H Nebinger 9 Years Ago David could you help me with this issue please https://www.liferay.com/es/community/forums/-/message_boards/message/38439950 Please sign in to reply. Reply as... Cancel Matti Tahvonen David H Nebinger 9 Years Ago Agreed, we'll definitely need to cover some best practices for this in upcoming articles. In one don't want to use the Vaadin control panel, one way would be to use a shared "my-company-vaadin-dependencies" project that would define used Vaadin version, possible add-ons and build the shared widget set to be placed into portal wide /html/ directory like to day. Then individual portlet projects would just depend to this project and use the shared widget set like before. Please sign in to reply. Reply as... Cancel
David H Nebinger Matti Tahvonen 9 Years Ago Server side is not my concern. Even four V6 portlets end up w/ four copies of the classes loaded.But it's totally the client side browser impact that is my concern. At least when all 4 are using the same version, the theme, js, and the engine are only loaded once...That's why, for my production system, I'd rather switch out of 'self contained' mode and roll back to the single system Vaadin + control panel, just so I can limit the impact on the browser side. Please sign in to reply. Reply as... Cancel alan brito delgado David H Nebinger 9 Years Ago David could you help me with this issue please https://www.liferay.com/es/community/forums/-/message_boards/message/38439950 Please sign in to reply. Reply as... Cancel Matti Tahvonen David H Nebinger 9 Years Ago Agreed, we'll definitely need to cover some best practices for this in upcoming articles. In one don't want to use the Vaadin control panel, one way would be to use a shared "my-company-vaadin-dependencies" project that would define used Vaadin version, possible add-ons and build the shared widget set to be placed into portal wide /html/ directory like to day. Then individual portlet projects would just depend to this project and use the shared widget set like before. Please sign in to reply. Reply as... Cancel
alan brito delgado David H Nebinger 9 Years Ago David could you help me with this issue please https://www.liferay.com/es/community/forums/-/message_boards/message/38439950 Please sign in to reply. Reply as... Cancel
Matti Tahvonen David H Nebinger 9 Years Ago Agreed, we'll definitely need to cover some best practices for this in upcoming articles. In one don't want to use the Vaadin control panel, one way would be to use a shared "my-company-vaadin-dependencies" project that would define used Vaadin version, possible add-ons and build the shared widget set to be placed into portal wide /html/ directory like to day. Then individual portlet projects would just depend to this project and use the shared widget set like before. Please sign in to reply. Reply as... Cancel
Rahul Pharande 9 Years Ago Hi Matti, I like the idea about self-contained approach, however I'm more concerned about scenario - I have old portal applications deployed on LR 6.2 having vaadin 6.8 as "global" way along with "custom-widget" and "custom-theme" now, I want to develop new portal having "vaadin 7" and "new-portal-specific-widget" and "newer-style" in "self-contained" mode. Is it possible to run both "newer-vaadin7" portal and "old-vaadin" portal on same page? Please sign in to reply. Reply as... Cancel Matti Tahvonen Rahul Pharande 9 Years Ago It works perfectly that you have both versions within same portals that way, but there might be some issues with "theme leaking". I haven't tested it, but I'd bet with Valo in Vaadin 7 portlet you should be doing just fine though. Please sign in to reply. Reply as... Cancel David Nebinger Matti Tahvonen 9 Years Ago Typically, though, in portlet development you complete one and move on, you don't go back to it unless there is some sort of defect to be resolved.So I believe, over time, you would end up w/ a portlet at 7.0.5 (latest when it was released), one at 7.1.7, one at 7.2.2, one at 7.3.1, ... Without the shared vaadin concept, I think over time your portal can get polluted with many different Vaadin versions, not just the global 6.8 and others at self contained yet different versions of Vaadin 7.That's the part that I don't believe has been addressed - what is the impact of multiple Vaadin versions on the server and in the browser... Please sign in to reply. Reply as... Cancel Rahul Pharande David Nebinger 9 Years Ago Ya, I agree that moving ahead with "self-contained" approach when you have multiple portal applications is not good. But to start with migration towards newer Vaadin version of single portal application you can easily do and test it with "self-contained" way.My original problem is : I have LR 6.2 with multiple portal applications using existing configured theme, widgets and vaadin 6.8 in "global" way. Now, I started porting/migrating one of the portal application with Vaadin 7 + newer widget + newer theme in "self-contained-way" but, it is not working and failing due to failure in loading widgets/theme. So, I want to know whether such thing works and tried by any one? If yes, please guide/hint it. Please sign in to reply. Reply as... Cancel David Nebinger Rahul Pharande 9 Years Ago That's a different issue altogether. If you can move the issue over to the forum, it's probably a better place to solve it than here. Be sure to include "Vaadin" in the subject line and I'll chime in... Please sign in to reply. Reply as... Cancel
Matti Tahvonen Rahul Pharande 9 Years Ago It works perfectly that you have both versions within same portals that way, but there might be some issues with "theme leaking". I haven't tested it, but I'd bet with Valo in Vaadin 7 portlet you should be doing just fine though. Please sign in to reply. Reply as... Cancel David Nebinger Matti Tahvonen 9 Years Ago Typically, though, in portlet development you complete one and move on, you don't go back to it unless there is some sort of defect to be resolved.So I believe, over time, you would end up w/ a portlet at 7.0.5 (latest when it was released), one at 7.1.7, one at 7.2.2, one at 7.3.1, ... Without the shared vaadin concept, I think over time your portal can get polluted with many different Vaadin versions, not just the global 6.8 and others at self contained yet different versions of Vaadin 7.That's the part that I don't believe has been addressed - what is the impact of multiple Vaadin versions on the server and in the browser... Please sign in to reply. Reply as... Cancel Rahul Pharande David Nebinger 9 Years Ago Ya, I agree that moving ahead with "self-contained" approach when you have multiple portal applications is not good. But to start with migration towards newer Vaadin version of single portal application you can easily do and test it with "self-contained" way.My original problem is : I have LR 6.2 with multiple portal applications using existing configured theme, widgets and vaadin 6.8 in "global" way. Now, I started porting/migrating one of the portal application with Vaadin 7 + newer widget + newer theme in "self-contained-way" but, it is not working and failing due to failure in loading widgets/theme. So, I want to know whether such thing works and tried by any one? If yes, please guide/hint it. Please sign in to reply. Reply as... Cancel David Nebinger Rahul Pharande 9 Years Ago That's a different issue altogether. If you can move the issue over to the forum, it's probably a better place to solve it than here. Be sure to include "Vaadin" in the subject line and I'll chime in... Please sign in to reply. Reply as... Cancel
David Nebinger Matti Tahvonen 9 Years Ago Typically, though, in portlet development you complete one and move on, you don't go back to it unless there is some sort of defect to be resolved.So I believe, over time, you would end up w/ a portlet at 7.0.5 (latest when it was released), one at 7.1.7, one at 7.2.2, one at 7.3.1, ... Without the shared vaadin concept, I think over time your portal can get polluted with many different Vaadin versions, not just the global 6.8 and others at self contained yet different versions of Vaadin 7.That's the part that I don't believe has been addressed - what is the impact of multiple Vaadin versions on the server and in the browser... Please sign in to reply. Reply as... Cancel Rahul Pharande David Nebinger 9 Years Ago Ya, I agree that moving ahead with "self-contained" approach when you have multiple portal applications is not good. But to start with migration towards newer Vaadin version of single portal application you can easily do and test it with "self-contained" way.My original problem is : I have LR 6.2 with multiple portal applications using existing configured theme, widgets and vaadin 6.8 in "global" way. Now, I started porting/migrating one of the portal application with Vaadin 7 + newer widget + newer theme in "self-contained-way" but, it is not working and failing due to failure in loading widgets/theme. So, I want to know whether such thing works and tried by any one? If yes, please guide/hint it. Please sign in to reply. Reply as... Cancel David Nebinger Rahul Pharande 9 Years Ago That's a different issue altogether. If you can move the issue over to the forum, it's probably a better place to solve it than here. Be sure to include "Vaadin" in the subject line and I'll chime in... Please sign in to reply. Reply as... Cancel
Rahul Pharande David Nebinger 9 Years Ago Ya, I agree that moving ahead with "self-contained" approach when you have multiple portal applications is not good. But to start with migration towards newer Vaadin version of single portal application you can easily do and test it with "self-contained" way.My original problem is : I have LR 6.2 with multiple portal applications using existing configured theme, widgets and vaadin 6.8 in "global" way. Now, I started porting/migrating one of the portal application with Vaadin 7 + newer widget + newer theme in "self-contained-way" but, it is not working and failing due to failure in loading widgets/theme. So, I want to know whether such thing works and tried by any one? If yes, please guide/hint it. Please sign in to reply. Reply as... Cancel David Nebinger Rahul Pharande 9 Years Ago That's a different issue altogether. If you can move the issue over to the forum, it's probably a better place to solve it than here. Be sure to include "Vaadin" in the subject line and I'll chime in... Please sign in to reply. Reply as... Cancel
David Nebinger Rahul Pharande 9 Years Ago That's a different issue altogether. If you can move the issue over to the forum, it's probably a better place to solve it than here. Be sure to include "Vaadin" in the subject line and I'll chime in... Please sign in to reply. Reply as... Cancel