[
https://issues.apache.org/jira/browse/OFBIZ-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hans Bakker updated OFBIZ-2107:
-------------------------------
Attachment: getWebSiteId.patch
The attached patch just does what is proposed in this issue...
Additional thing we can think about is to add fields to the website which are
available in the 'ofbiz' fields in web.xml like the localDispatcherName,
entityDelegatorName and mainDecoratorLocation.
with this patch, the webSiteId will be taken from the WebSite entity when they
are not defined in web.xml.
Or should be better use 'web.xml' as the default which can be overridden in the
Website entity?
> run many websites from one webapplication/dynamically add websites to ofbiz
> ---------------------------------------------------------------------------
>
> Key: OFBIZ-2107
> URL: https://issues.apache.org/jira/browse/OFBIZ-2107
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: SVN trunk
> Environment: any
> Reporter: Hans Bakker
> Assignee: Hans Bakker
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: getWebSiteId.patch
>
>
> I was always wondering why the 'webSiteId' is hardcoded in the web.xml.
> If a request comes in, the domainname and port is normally known and
> depending on this information the websiteId can be found in the website
> entity.
> If this would be implemented a new website can be dynamically configured and
> many websites can be run from the same webapplication within a component and
> no configuration and/or restart is required to make the website active with
> ofbiz.
> Am i overlooking something or is there a reason that the websiteId is
> harcoded in web.xml?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
