Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lazy deserialize while executing entry-processor #5301

Closed
gurbuzali opened this issue May 13, 2015 · 1 comment

Comments

Projects
None yet
3 participants
@gurbuzali
Copy link
Member

commented May 13, 2015

Currently key/value are deserialized prior to execution of entry-processor by default
This leads to need to the domain object at server-side, even if entry-processor never uses it

@gurbuzali gurbuzali added this to the 3.4.3 milestone May 13, 2015

@gurbuzali gurbuzali self-assigned this May 14, 2015

@mesutcelik

This comment has been minimized.

Copy link
Contributor

commented May 14, 2015

Can we also check that if following methods are requiring domain objects in the classpath?

  • ClienMapProxy.keySet(Predicate predicate)
  • ClienMapProxy.entrySet(Predicate predicate)
  • ClientMapProxy. executeOnEntries(EntryProcessor entryProcessor)

@sancar ,
I think you can comment on this as well. I know you already checked and have some findings.

@gurbuzali gurbuzali modified the milestones: 3.5.1, 3.4.3 May 25, 2015

@ahmetmircik ahmetmircik assigned ahmetmircik and unassigned gurbuzali Jun 25, 2015

@ahmetmircik ahmetmircik modified the milestones: 3.6, 3.5.1 Jun 25, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.