You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the currently displayed page had the URL http://localhost/html/index and an instance of LandingPage is created there would be no problem since the context path matches the expectation.
If the currently displayed page had the URL http://localhost/html/main an exception would be thrown as soon as a LandingPage instance is being created.
For page definitions without @ContextPath every URL is valid
The text was updated successfully, but these errors were encountered:
slu-it
changed the title
Automatic validation of Pages in PostConstruct by Context Path
Idea: Automatic validation of Pages in PostConstruct by Context Path
Aug 10, 2016
slu-it
changed the title
Idea: Automatic validation of Pages in PostConstruct by Context Path
Automatic validation of Pages in PostConstruct by Context Path
Aug 31, 2016
In a similar fashion as with
@Mapping
forPageFragement
subclasses we could validate if aPage
was initialized for a valid context path / url.Examples
http://localhost/html/index
and an instance ofLandingPage
is created there would be no problem since the context path matches the expectation.http://localhost/html/main
an exception would be thrown as soon as aLandingPage
instance is being created.@ContextPath
every URL is validThe text was updated successfully, but these errors were encountered: