1:02 p.m.
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
1:09 p.m.
The Titan implementation already provides caching. When you say a Map like API, you mean
to access the data on the nodes?
From an intermediate data perspective, you can always get the
underlying vertex from the Framed Vertex, and then write to it like a Map (Key, Value
pair).
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka(a)redhat.com>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
Sent: Friday, July 25, 2014 2:02:06 PM
Subject: [windup-dev] Where to store intermediate data?
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
https://lists.jboss.org/mailman/listinfo/windup-dev
1:11 p.m.
Alternative to adding data to the graph vertex directly, you could create a intermediate
vertex that has a reference to another vertex you are referring to.
IntermediateMapVertex -> SomeOtherVertex
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Brad Davis" <bdavis(a)redhat.com>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
Sent: Friday, July 25, 2014 2:09:57 PM
Subject: Re: [windup-dev] Where to store intermediate data?
The Titan implementation already provides caching. When you say a Map like API, you mean
to access the data on the nodes?
From an intermediate data perspective, you can always get the
underlying vertex from the Framed Vertex, and then write to it like a Map (Key, Value
pair).
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka(a)redhat.com>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
Sent: Friday, July 25, 2014 2:02:06 PM
Subject: [windup-dev] Where to store intermediate data?
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
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
1:21 p.m.
Right, but Lincoln doesn't want the intermediate data in the graph, if I
understand him correctly.
That's why I am looking for some Map in our Java data structures.
Ondra
On 25.7.2014 20:11, Brad Davis wrote:
Alternative to adding data to the graph vertex directly, you could
create a intermediate vertex that has a reference to another vertex you are referring to.
IntermediateMapVertex -> SomeOtherVertex
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Brad Davis" <bdavis(a)redhat.com>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
Sent: Friday, July 25, 2014 2:09:57 PM
Subject: Re: [windup-dev] Where to store intermediate data?
The Titan implementation already provides caching. When you say a Map like API, you mean
to access the data on the nodes?
>From an intermediate data perspective, you can always get the underlying vertex from
the Framed Vertex, and then write to it like a Map (Key, Value pair).
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka(a)redhat.com>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
Sent: Friday, July 25, 2014 2:02:06 PM
Subject: [windup-dev] Where to store intermediate data?
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
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
1:39 p.m.
Oh gotcha. So you mean like a map to pass data along during the execution of a rule
itself?
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka(a)redhat.com>
To: windup-dev(a)lists.jboss.org
Sent: Friday, July 25, 2014 2:21:47 PM
Subject: Re: [windup-dev] Where to store intermediate data?
Right, but Lincoln doesn't want the intermediate data in the graph, if I
understand him correctly.
That's why I am looking for some Map in our Java data structures.
Ondra
On 25.7.2014 20:11, Brad Davis wrote:
Alternative to adding data to the graph vertex directly, you could
create a intermediate vertex that has a reference to another vertex you are referring to.
IntermediateMapVertex -> SomeOtherVertex
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Brad Davis" <bdavis(a)redhat.com>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
Sent: Friday, July 25, 2014 2:09:57 PM
Subject: Re: [windup-dev] Where to store intermediate data?
The Titan implementation already provides caching. When you say a Map like API, you mean
to access the data on the nodes?
>From an intermediate data perspective, you can always get the underlying vertex from
the Framed Vertex, and then write to it like a Map (Key, Value pair).
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka(a)redhat.com>
To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
Sent: Friday, July 25, 2014 2:02:06 PM
Subject: [windup-dev] Where to store intermediate data?
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
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
1:44 p.m.
A rule, or perhaps during whole execution.
Actually those are 2 different things.
Currently, I need whole runtime scope - for Model metadata.
And also, I was thinking about a rule computing a sum of e.g. JMS queues
capacities (or anything such).
That would need an iteration, and within iteration, we have VarStack,
but that's only for WindupVertexFrames, so I was thinking what the user
has to store data like this, which are not to be reported.
Ondra
On 25.7.2014 20:39, Brad Davis wrote:
Oh gotcha. So you mean like a map to pass data along during the
execution of a rule itself?
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka(a)redhat.com>
To: windup-dev(a)lists.jboss.org
Sent: Friday, July 25, 2014 2:21:47 PM
Subject: Re: [windup-dev] Where to store intermediate data?
Right, but Lincoln doesn't want the intermediate data in the graph, if I
understand him correctly.
That's why I am looking for some Map in our Java data structures.
Ondra
On 25.7.2014 20:11, Brad Davis wrote:
> Alternative to adding data to the graph vertex directly, you could create a
intermediate vertex that has a reference to another vertex you are referring to.
>
> IntermediateMapVertex -> SomeOtherVertex
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Brad Davis" <bdavis(a)redhat.com>
> To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
> Sent: Friday, July 25, 2014 2:09:57 PM
> Subject: Re: [windup-dev] Where to store intermediate data?
>
> The Titan implementation already provides caching. When you say a Map like API, you
mean to access the data on the nodes?
>
> >From an intermediate data perspective, you can always get the underlying vertex
from the Framed Vertex, and then write to it like a Map (Key, Value pair).
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Ondrej Zizka" <ozizka(a)redhat.com>
> To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
> Sent: Friday, July 25, 2014 2:02:06 PM
> Subject: [windup-dev] Where to store intermediate data?
>
> 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
> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
1:55 p.m.
If you want something to keep data around for the whole run, it makes sense to put it to
the graph. The idea for the graph is to keep data out of memory full time, because if the
data is being kept around a long time, you want to have the graph purge that from memory
to keep your heap tidy. Otherwise, like Windup 1, large applications or apps with a lot
of meta information in memory can cause a out of memory exception.
So, to me it makes sense to have an in-memory context for the execution of a rule. But,
if you are having data beyond one rule that you plan to keep around to reason on
potentially by other rules, it would get put to the graph.
Example:
You have an XML file ...
You have a rule that says "when i have the root node /example,"
- extract the xml's name to a temporary variable
And a sub-rule that says "for each node //somevalue"
- extract the //somevalue/@somexpath locally for the context
And an outcome for each of those //somevalue nodes: Add in the Hint to the somevalue's
XML Line position in the XML of: "This is an example of $somevalue within the XML
named $xmlName"
So the hint itself would be added to the Graph since you want that to be around for a long
time after this rule runs... but the variable of the XML file's name, and specifically
the local context when it is looping (for each) on some XPath Expression would be in
memory and not written to the graph. Make sense?
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka(a)redhat.com>
To: windup-dev(a)lists.jboss.org
Sent: Friday, July 25, 2014 2:44:51 PM
Subject: Re: [windup-dev] Where to store intermediate data?
A rule, or perhaps during whole execution.
Actually those are 2 different things.
Currently, I need whole runtime scope - for Model metadata.
And also, I was thinking about a rule computing a sum of e.g. JMS queues
capacities (or anything such).
That would need an iteration, and within iteration, we have VarStack,
but that's only for WindupVertexFrames, so I was thinking what the user
has to store data like this, which are not to be reported.
Ondra
On 25.7.2014 20:39, Brad Davis wrote:
Oh gotcha. So you mean like a map to pass data along during the
execution of a rule itself?
Brad Davis
Red Hat Consulting
Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
----- Original Message -----
From: "Ondrej Zizka" <ozizka(a)redhat.com>
To: windup-dev(a)lists.jboss.org
Sent: Friday, July 25, 2014 2:21:47 PM
Subject: Re: [windup-dev] Where to store intermediate data?
Right, but Lincoln doesn't want the intermediate data in the graph, if I
understand him correctly.
That's why I am looking for some Map in our Java data structures.
Ondra
On 25.7.2014 20:11, Brad Davis wrote:
> Alternative to adding data to the graph vertex directly, you could create a
intermediate vertex that has a reference to another vertex you are referring to.
>
> IntermediateMapVertex -> SomeOtherVertex
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Brad Davis" <bdavis(a)redhat.com>
> To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
> Sent: Friday, July 25, 2014 2:09:57 PM
> Subject: Re: [windup-dev] Where to store intermediate data?
>
> The Titan implementation already provides caching. When you say a Map like API, you
mean to access the data on the nodes?
>
> >From an intermediate data perspective, you can always get the underlying vertex
from the Framed Vertex, and then write to it like a Map (Key, Value pair).
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Ondrej Zizka" <ozizka(a)redhat.com>
> To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
> Sent: Friday, July 25, 2014 2:02:06 PM
> Subject: [windup-dev] Where to store intermediate data?
>
> 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
> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
2:39 p.m.
Ah, also, I didn't say I don't want intermediate data in the graph :) That
is an over-generalization. I said I don't think *this* data belongs in the
graph. We do want to be storing the *right* data in the graph. And we need
to be careful about what that data is and where and how it is stored.
On Fri, Jul 25, 2014 at 2:21 PM, Ondrej Zizka <ozizka(a)redhat.com> wrote:
Right, but Lincoln doesn't want the intermediate data in the
graph, if I
understand him correctly.
That's why I am looking for some Map in our Java data structures.
Ondra
On 25.7.2014 20:11, Brad Davis wrote:
> Alternative to adding data to the graph vertex directly, you could
create a intermediate vertex that has a reference to another vertex you are
referring to.
>
> IntermediateMapVertex -> SomeOtherVertex
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Brad Davis" <bdavis(a)redhat.com>
> To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
> Sent: Friday, July 25, 2014 2:09:57 PM
> Subject: Re: [windup-dev] Where to store intermediate data?
>
> The Titan implementation already provides caching. When you say a Map
like API, you mean to access the data on the nodes?
>
> >From an intermediate data perspective, you can always get the
underlying vertex from the Framed Vertex, and then write to it like a Map
(Key, Value pair).
>
> Brad Davis
> Red Hat Consulting
> Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
>
>
> ----- Original Message -----
> From: "Ondrej Zizka" <ozizka(a)redhat.com>
> To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
> Sent: Friday, July 25, 2014 2:02:06 PM
> Subject: [windup-dev] Where to store intermediate data?
>
> 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
> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
> _______________________________________________
> windup-dev mailing list
> windup-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
2:40 p.m.
Additionally, if you're looking for a context. Use
GraphRewrite.getRewriteContext() ... it is a map-like structure, but I
don't think we'll need to use it much so consider the various factors
carefully (and discuss if you are unsure) when thinking about putting
information there.
On Fri, Jul 25, 2014 at 3:39 PM, Lincoln Baxter, III <
lincolnbaxter(a)gmail.com> wrote:
Ah, also, I didn't say I don't want intermediate data in the
graph :) That
is an over-generalization. I said I don't think *this* data belongs in the
graph. We do want to be storing the *right* data in the graph. And we need
to be careful about what that data is and where and how it is stored.
On Fri, Jul 25, 2014 at 2:21 PM, Ondrej Zizka <ozizka(a)redhat.com> wrote:
> Right, but Lincoln doesn't want the intermediate data in the graph, if I
> understand him correctly.
> That's why I am looking for some Map in our Java data structures.
>
> Ondra
>
>
>
> On 25.7.2014 20:11, Brad Davis wrote:
> > Alternative to adding data to the graph vertex directly, you could
> create a intermediate vertex that has a reference to another vertex you are
> referring to.
> >
> > IntermediateMapVertex -> SomeOtherVertex
> >
> > Brad Davis
> > Red Hat Consulting
> > Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
> >
> >
> > ----- Original Message -----
> > From: "Brad Davis" <bdavis(a)redhat.com>
> > To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
> > Sent: Friday, July 25, 2014 2:09:57 PM
> > Subject: Re: [windup-dev] Where to store intermediate data?
> >
> > The Titan implementation already provides caching. When you say a Map
> like API, you mean to access the data on the nodes?
> >
> > >From an intermediate data perspective, you can always get the
> underlying vertex from the Framed Vertex, and then write to it like a Map
> (Key, Value pair).
> >
> > Brad Davis
> > Red Hat Consulting
> > Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
> >
> >
> > ----- Original Message -----
> > From: "Ondrej Zizka" <ozizka(a)redhat.com>
> > To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
> > Sent: Friday, July 25, 2014 2:02:06 PM
> > Subject: [windup-dev] Where to store intermediate data?
> >
> > 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
> > https://lists.jboss.org/mailman/listinfo/windup-dev
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
> > _______________________________________________
> > windup-dev mailing list
> > windup-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/windup-dev
>
> _______________________________________________
> windup-dev mailing list
> windup-dev(a)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."
2:40 p.m.
I am signing off for PTO. Not supposed to be working today. See you all in
a week :)
On Fri, Jul 25, 2014 at 3:40 PM, Lincoln Baxter, III <
lincolnbaxter(a)gmail.com> wrote:
Additionally, if you're looking for a context. Use
GraphRewrite.getRewriteContext() ... it is a map-like structure, but I
don't think we'll need to use it much so consider the various factors
carefully (and discuss if you are unsure) when thinking about putting
information there.
On Fri, Jul 25, 2014 at 3:39 PM, Lincoln Baxter, III <
lincolnbaxter(a)gmail.com> wrote:
> Ah, also, I didn't say I don't want intermediate data in the graph :)
> That is an over-generalization. I said I don't think *this* data belongs in
> the graph. We do want to be storing the *right* data in the graph. And we
> need to be careful about what that data is and where and how it is stored.
>
>
> On Fri, Jul 25, 2014 at 2:21 PM, Ondrej Zizka <ozizka(a)redhat.com> wrote:
>
>> Right, but Lincoln doesn't want the intermediate data in the graph, if I
>> understand him correctly.
>> That's why I am looking for some Map in our Java data structures.
>>
>> Ondra
>>
>>
>>
>> On 25.7.2014 20:11, Brad Davis wrote:
>> > Alternative to adding data to the graph vertex directly, you could
>> create a intermediate vertex that has a reference to another vertex you are
>> referring to.
>> >
>> > IntermediateMapVertex -> SomeOtherVertex
>> >
>> > Brad Davis
>> > Red Hat Consulting
>> > Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
>> >
>> >
>> > ----- Original Message -----
>> > From: "Brad Davis" <bdavis(a)redhat.com>
>> > To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
>> > Sent: Friday, July 25, 2014 2:09:57 PM
>> > Subject: Re: [windup-dev] Where to store intermediate data?
>> >
>> > The Titan implementation already provides caching. When you say a Map
>> like API, you mean to access the data on the nodes?
>> >
>> > >From an intermediate data perspective, you can always get the
>> underlying vertex from the Framed Vertex, and then write to it like a Map
>> (Key, Value pair).
>> >
>> > Brad Davis
>> > Red Hat Consulting
>> > Email: bdavis(a)redhat.com | c: 980.226.7865 | http://www.redhat.com
>> >
>> >
>> > ----- Original Message -----
>> > From: "Ondrej Zizka" <ozizka(a)redhat.com>
>> > To: "Windup-dev List" <windup-dev(a)lists.jboss.org>
>> > Sent: Friday, July 25, 2014 2:02:06 PM
>> > Subject: [windup-dev] Where to store intermediate data?
>> >
>> > 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
>> > https://lists.jboss.org/mailman/listinfo/windup-dev
>> > _______________________________________________
>> > windup-dev mailing list
>> > windup-dev(a)lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/windup-dev
>> > _______________________________________________
>> > windup-dev mailing list
>> > windup-dev(a)lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev(a)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."
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
2:25 p.m.
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> 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
https://lists.jboss.org/mailman/listinfo/windup-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
2:26 p.m.
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 :) 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> 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> 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
> 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."
2:46 p.m.
On 25.7.2014 21:26, Lincoln Baxter, III wrote:
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
2:46 p.m.
Not a format. Other data.
On 25.7.2014 21:25, Lincoln Baxter, III 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."
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
3808
days inactive
3808
days old
13 comments
3 participants
participants (3)
-
Brad Davis -
Lincoln Baxter, III -
Ondrej Zizka