Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

ContextHub SessionStore (AEM 6.1 sp1)

Avatar

Avatar
Validate 1
Level 2
bmccurdy1
Level 2

Likes

8 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Boost 5
Boost 3
View profile

Avatar
Validate 1
Level 2
bmccurdy1
Level 2

Likes

8 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Boost 5
Boost 3
View profile
bmccurdy1
Level 2

29-09-2016

We are implementing a custom data store in AEM 6.1 ContextHub for a client's site and trying to use the SessionStore. According to the Adobe documentation, the SessionStore should use the in-memory persistence and only be available for that browser session. Our custom store inherits from the SessionStore:

ContextHub.Utils.inheritance.inherit(myStore, ContextHub.Store.SessionStore);

Our store is registered and available to the developers to read/write data. However, upon further inspection, it appears the custom store is using the HTML5 local persisted storage and not the session storage. Data is being stored clientside and persisted far longer than the browser session.

Looking at all the ContextHub stores, examples and custom, they all appear to be using the default Local persistence. Is there a configuration missing, a variable that should be set, or something I am overlooking to get our custom store to use the in-memory session store? Or are we looking at a bug in AEM 6.1?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 2
bmccurdy1
Level 2

Likes

8 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Boost 5
Boost 3
View profile

Avatar
Validate 1
Level 2
bmccurdy1
Level 2

Likes

8 likes

Total Posts

13 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Boost 5
Boost 3
View profile
bmccurdy1
Level 2

31-08-2017

We eventually reached out to DayCare, and while we did not get a reference to proper documentation, below is what was suggested from DayCare, which ultimately resolved our issue.

this.persistence = new ContextHub.Utils.Persistence({mode : ContextHub.Utils.Persistence.Modes.SESSION});

Answers (2)

Answers (2)

Avatar

Avatar
Validate 1
Level 2
BHAVYA_S
Level 2

Likes

7 likes

Total Posts

16 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Applaud 5
View profile

Avatar
Validate 1
Level 2
BHAVYA_S
Level 2

Likes

7 likes

Total Posts

16 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Applaud 5
View profile
BHAVYA_S
Level 2

31-08-2017

Can you please share the link for the solution here

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,406 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,406 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

29-09-2016

I am checking into this - it should be as documented.