[
http://jira.jboss.com/jira/browse/JBPORTAL-1004?page=comments#action_1234... ]
Sverker Abrahamsson commented on JBPORTAL-1004:
-----------------------------------------------
I've done some more investigations and see that the first solution with separate
contexts is the way to go. Why? Because isolation is needed between the applications.
With the implementation where the virtual-host/context-path information is bound to the
Portal object then if I deploy my portal to
http://portaltest.abrahamsson.com then I can
access the default portal on
http://portaltest.abrahamsson.com/portal/default/. Well, sort
of since the portlets are rendered but images etc can't be loaded, since they are in a
different web application context.
That is essentially the point, like the servlet container maintains different contexts to
isolate different applications so does the portal server need to do. This turned out to
work supprisingly well in the first approach I did, the rest of the app seams to be
designed with multiple contexts in mind even if the model isn't.
What needs to be discussed is how it should be specified in the *-object.xml file which
context a portal should be deployed to. I find that the most logical is that unless a
parent ref is specified then it should be bound to the context created by the war. If the
parent ref is empty (i.e. <parentref/>) then the portal is bound to the default
context and if a specific parent is specified then the it is bound to that context. This
is also consistent with how things have worked historically.
I've done some basic testing on letting the portals having different security domains
which seams to work fine but needs further analysis, especially how it affects the cms.
Note that the ObjectNodes still form a tree, with the default context as root and the
other contextes as children to it.
Jboss Portal to support virtual hosts
-------------------------------------
Key: JBPORTAL-1004
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1004
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Sverker Abrahamsson
Attachments: jboss-portal-2.4-2.patch, jboss-portal-2.4.patch, new.files.zip
Time Spent: 1 week
Remaining Estimate: 0 minutes
JBoss Portal is today unable to support multiple virtual hosts, i.e. it's not
possible to create a portal bound to the address
www.foo.com and one that is bound to
www.bar.com.
This is a major problem for real world usage of JBoss Portal
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira