That DataResourceType is for data that comes from a URL. When a
DataResource with that type is rendered it looks at the info string on
the DataResource to get the URL, and then gets the data from the URL.
I'm not sure if this would apply...
-David
On Jan 7, 2009, at 5:33 PM, Hans Bakker wrote:
How about using the existing dataresource entity with the
dataresourcetype "URL_RESOURCE" ?
the key can be stored in the DataResourceAttribute .....
On Wed, 2009-01-07 at 19:34 +0100, 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
--
Antwebsystems.com: Quality OFBiz services for competitive prices
