Skip to content

Revisit restrictions in SpEL position handling [SPR-17625] #22157

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
Closed
spring-projects-issues opened this issue Dec 25, 2018 · 0 comments
Closed

Revisit restrictions in SpEL position handling [SPR-17625] #22157

spring-projects-issues opened this issue Dec 25, 2018 · 0 comments
Assignees
@jhoeller
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: task A general task
Milestone
5.2 M1

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Dec 25, 2018 •
edited
Loading

Juergen Hoeller opened SPR-17625 and commented

As indicated #22137, position handling in SpEL nodes is historically, sharing an integer value for both start and end position in 16 bits each. This should get refactored into dedicated integer values for start and end position across all nodes, refactoring the current single-int constructors into double-int constructors.

Affects: 5.1.4

Issue Links:
@spring-projects-issues spring-projects-issues added in: core Issues in core modules (aop, beans, core, context, expression) type: task A general task labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 5.2 RC1 milestone Jan 11, 2019
This was referenced Jan 11, 2019
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhoeller jhoeller

Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: task A general task
Projects
None yet
Milestone
5.2 M1
Development

No branches or pull requests
2 participants
@jhoeller @spring-projects-issues