[
http://jira.jboss.com/jira/browse/JBPORTAL-1004?page=comments#action_1234... ]
Sverker Abrahamsson commented on JBPORTAL-1004:
-----------------------------------------------
Well, the idea I had was that since a different web application is essentially a different
context then create new contexts under the root would be the right way to go. If you have
only one context then you can optimize it away, it doesn't add any value to the data
model.
Not that it matters though, I think it should be possible to map ContextPath to Portal
instead. The only issue I can think of from the top of my head is how to decide which is
the default portal if several portals is deployed in the same *-object.xml without parent
references but that can be handled by being a bit picky when deploying.
I don't really care which, the only thing I care about is the functionality in the
end.
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.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