[
https://issues.apache.org/jira/browse/OFBIZ-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970607#comment-14970607
]
Jacques Le Roux commented on OFBIZ-2813:
----------------------------------------
Hi David, I want to commit Bob's work.
But it's unclear to me: what is
{quote}
much more consistent with the other settings...
{quote}
?
It seems to me that the property in start.properties
{code}
# -- The default time zone for this OFBiz instance.
#ofbiz.timeZone.default=GMT
{code}
Can only set 1 time zone and, as Bob explained above, an instance may need more
than 1 time zone
> ProductStore did not allow the default timezone to be set
> ---------------------------------------------------------
>
> Key: OFBIZ-2813
> URL: https://issues.apache.org/jira/browse/OFBIZ-2813
> Project: OFBiz
> Issue Type: Improvement
> Components: product
> Affects Versions: Trunk
> Reporter: Bob Morley
> Assignee: Jacques Le Roux
> Priority: Minor
> Attachments: OFBIZ-2813.patch, OFBIZ-2813.patch
>
>
> The ProductStore has the defaultLocaleString and the defaultCurrencyUomId but
> does not have a defaultTimeZoneString. What happens when a store is selected
> (from e-commerce or the pos) is that it will look to the user for a
> lastTimeZone and if that is not set, it would simply revert to the
> TimeZone.getDefault() (so the timezone based on the server).
> The trouble we had was that you may have an application server that is
> running in a completely different timezone than what is desired for the store.
> I will be attaching a patch to this ticket with changes related to this
> improvement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
