Skip to content

Commit 0d3aeeb causes many neccessary changes to use the VaadinSessionScoped Context again #506

@OriginalFelix

Description

@OriginalFelix

The Issue is that the Following line was adapted to check for the Session-Lock.

Image

This should not happen here. Instead the Places where the Session is actually need to determine the Lock-State.
Otherwise you'll always receive a ContextNotActive exception. In our Project we've like 4500 Places to fix - This is nothing for a minor patch.
Since CDI should be automatically managed, the lock needs to be taken, if necessary.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    🪵Product backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions