You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Karl Kildén (JIRA)" <ji...@apache.org> on 2013/11/02 22:38:17 UTC

[jira] [Updated] (DELTASPIKE-439) ViewConfigs not residing in packages should be treated as a definition error

     [ https://issues.apache.org/jira/browse/DELTASPIKE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Kildén updated DELTASPIKE-439:
-----------------------------------

    Summary: ViewConfigs not residing in packages should be treated as a definition error  (was: ViewConfigAwareNavigationHandler assumes all ViewConfigs resides in packages but silently lets them neglect it)

> ViewConfigs not residing in packages should be treated as a definition error
> ----------------------------------------------------------------------------
>
>                 Key: DELTASPIKE-439
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-439
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: JSF-Module
>    Affects Versions: 0.5
>         Environment: TomEE 1.6-SNAPSHOT Deltaspike 0.5
>            Reporter: Karl Kildén
>            Priority: Minor
>              Labels: easyfix
>
> if (outcome != null && outcome.contains("."))
> That condition in ViewConfigAwareNavigationHandler effectivly broke my ViewConfig because I neglected to put it into a package.
> Obviously it's not that far fetched to assume that all ViewConfigs are in fact in packages but when users like myself are just evaluating the feature HelloWorld style it could easily happen and it resulted in some confusion.
> I wouldn't mind keeping the condition as is but I would recommend treating no package name as a definition error.



--
This message was sent by Atlassian JIRA
(v6.1#6144)