Today we have static deployment and we can deploy -portal.xml and -pages.xml.
Portal deployment defines a portal and can specific a set of pages related to that portal. Page deployment can add pages to a portal.
I am thinking about the portal / page relationship and that they should be closer, i.e the lifecycle should be the same. If the portal does not exist, there are no reason that its pages should exist. And the page deployment is conflicting with that because it can lead to the situation where a page deployment could be deployed before a portal. Of course this can be solved by introducing more complexity via dependencies.
If you think about it, the static deployment is fine for testing your application or for some specific configurations. In that case, the portal deployment is enough. People wanting to create pages attached to a portal will rather use the dynamicity features.
So I am thinking about dropping the -pages.xml and let only the portal deployment mode.
Does it make sense for you ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884849#3884849
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884849
|
