Skip to content

CommandExceptionResolver beans should have order #634

Closed
@jvalkeal

Description

@jvalkeal

Currently we have only one added as bean that being CommandParserExceptionResolver. It was always meant that this would pick CommandParserExceptionsException and then user could create their own resolvers. Issue is that if user creates resolver which handles everything it's not possible make sure if that is used before/after default ones from spring-shell itself.

That's why CommandParserExceptionResolver needs an order as it defaults to lowest precedence.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions