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.

Sign up for GitHub

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

Jump to bottom

Return JobExecution by copying DB value rather than providing a link/ref to the current value #41

Open
scottkurz opened this issue Oct 8, 2015 · 0 comments
Open

Return JobExecution by copying DB value rather than providing a link/ref to the current value #41

scottkurz opened this issue Oct 8, 2015 · 0 comments

Comments

@scottkurz
Copy link
Member

Perhaps we should switch to copying a JobExecution by value (i.e. caching the DB data within a JobExecution instance) rather than providing a more current view.

See Spec Bug 4834.

As the RI, I think we want to discourage this practice since we've agreed it's not portable.
@scottkurz scottkurz changed the title https://java.net/bugzilla/show_bug.cgi?id=4834 Return JobExecution by copying DB value rather than providing a link/ref to the current value Oct 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@scottkurz