Bob Morley wrote:
Will do. I seem to recall that I had to change a number of signatures
in the entity pkg to float down appropriate context so default would
not be used. I will dig up my work on Monday and compare to latest
ofbiz trunk.
Adam -- I took a look at the changes that I
One of the things to keep in mind during these discussions is the
forthcoming ExecutionContext - a part of the security redesign. Instead
of passing a delegator around the framework, the current delegator is
assigned to the current thread and a static method exists to retrieve it
at any point
Adrian Crum wrote:
One of the things to keep in mind during these discussions is the
forthcoming ExecutionContext - a part of the security redesign. Instead
of passing a delegator around the framework, the current delegator is
assigned to the current thread and a static method exists to
Adam Heath wrote:
Adrian Crum wrote:
One of the things to keep in mind during these discussions is the
forthcoming ExecutionContext - a part of the security redesign. Instead
of passing a delegator around the framework, the current delegator is
assigned to the current thread and a static method
Adrian Crum wrote:
Consider something stored into the cache, then referenced from another
thread. What is the correct delegator?
Huh?
Entity caches store EntityCondition as key, and ListGenericValue as
the value. Fetching from the cache can still be made to work, because
the in-memory
On Apr 5, 2010, at 2:11 PM, Adrian Crum wrote:
Adam Heath wrote:
Adrian Crum wrote:
One of the things to keep in mind during these discussions is the
forthcoming ExecutionContext - a part of the security redesign.
Instead
of passing a delegator around the framework, the current delegator
Adam Heath wrote:
Adrian Crum wrote:
Consider something stored into the cache, then referenced from another
thread. What is the correct delegator?
Huh?
Entity caches store EntityCondition as key, and ListGenericValue as
the value. Fetching from the cache can still be made to work, because
That way the entities will only be loaded when the default delegator is
loaded on install.
there already is a discussion on how to load tenants data that does not
included the demo data for the TenantDemoData.xml
and entry in the ofbiz-componets would reference the tenant entity as
BJ Freeman wrote:
That way the entities will only be loaded when the default delegator is
loaded on install.
there already is a discussion on how to load tenants data that does not
included the demo data for the TenantDemoData.xml
and entry in the ofbiz-componets would reference the tenant
Adam Heath wrote:
BJ Freeman wrote:
That way the entities will only be loaded when the default delegator is
loaded on install.
there already is a discussion on how to load tenants data that does not
included the demo data for the TenantDemoData.xml
and entry in the ofbiz-componets would
not sure we are on the same page
the reader code is modified to not only looke for are reader specified
(seed, demo, seed-intial,ext) but those readers with the delegator
appended to them.
when the install for the default delegator is done
it will look for seed-default readers, as well as just
Somewhat related, when we implemented our multi-tenant support we
found a number of places where the default delegator was hardcoded
or assumed. When we had differences in the entity models for our
deployment delegator vs. tenant delegators these issues surfaced.
I admit I have not yet
Robert Morley wrote:
Somewhat related, when we implemented our multi-tenant support we found
a number of places where the default delegator was hardcoded or
assumed. When we had differences in the entity models for our deployment
delegator vs. tenant delegators these issues surfaced.
I fixed
Adam Heath wrote:
Robert Morley wrote:
Somewhat related, when we implemented our multi-tenant support we found
a number of places where the default delegator was hardcoded or
assumed. When we had differences in the entity models for our deployment
delegator vs. tenant delegators these issues
Will do. I seem to recall that I had to change a number of signatures
in the entity pkg to float down appropriate context so default would
not be used. I will dig up my work on Monday and compare to latest
ofbiz trunk.
Bob
On 2010-04-04, at 12:03 AM, Adam Heath doo...@brainfood.com wrote:
15 matches
Mail list logo
