As I was trying to communicate yesterday, I'm not sure why you
need
another storage location for this when we already have the data stored
in the GraphTypeManager :)
No we don't. As I told yesterday. It's other
data.
I *am* open to ideas on this, but I need to see a technical reason to
duplicate the info.
On Fri, Jul 25, 2014 at 3:25 PM, Lincoln Baxter, III
<lincolnbaxter(a)gmail.com <mailto:lincolnbaxter@gmail.com>> wrote:
Hey Ondra,
The model Metadata is already available via the
GraphTypeRegistry/etc. I would recommend that if there is some
other view or format that you need for this data, then consider
extending the existing API to support your use case - e.g. Return
a map view, for example.
~Lincoln
On Fri, Jul 25, 2014 at 2:02 PM, Ondrej Zizka <ozizka(a)redhat.com
<mailto:ozizka@redhat.com>> wrote:
Hi,
where should I cache intermediate data? E.g. the model metadata.
I expected GraphContext to have some Map-like API, there's none.
Should I add it? Or should I clutter the API with it? Or will
it be
better to store it in the graph afterall?
Thanks,
Ondra
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org <mailto:windup-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/windup-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev