Jacques,
Could you describe more about this, perhaps where the data comes from
and how it is used? What other data in the system does it relate to
and how?
In general for settings that could go into a properties file, or that
are now in a properties file and are business (not system) related, we
have talked about putting them in the database. To do so and properly
organize the data into new fields on new or existing entities the
basic information above is needed. For the most part they'll probably
go into generic entities like the preferences, or in big new entities
with sets of fields for different sets of properties.
Back to this... basically more info would be helpful.
-David
On Jan 7, 2009, at 10:34 AM, Jacques Le Roux wrote:
Hi,
I'm trying to finally commit our GoePoint entities related
modelling. For that, I need to introduce the Google Map API key
concept (a key corresponding to an URL). I previsously suggested
general.properties. But maybe an entity like the one below would be
more convenient in case the user would have to deal with more than
an handle of URLs
<entity entity-name="GoogleMapApiKey" package-
name="org.ofbiz.common.geo" default-resource-name="CommonEntityLabels"
title="Google Map API key">
<field name="UrlId" type="id"></field>
<field name="ApiKey" type="long-varchar"></field><!-- As generated
from UrlId at http://code.google.com/intl/fr/apis/maps/signup.html,
note that it works for http://localhost !-->
<prim-key field="UrlId"/>
</entity>
What do you think ?
Thanks
Jacques
From: "Jacques Le Roux" <jacques.ler...@9business.fr>
This is related to https://issues.apache.org/jira/browse/OFBIZ-1923
I don't know for Yahoo and other, but I guess it's the same than
for Google. You need a key to use their Map API. For Google this
key is related to the domain used and allow to use the API only on
this domain. So we need to store this information somewhere. I
think about general.properties
Jacques
