You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@deltaspike.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2013/11/02 22:42:17 UTC

[jira] [Assigned] (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 ]

Gerhard Petracek reassigned DELTASPIKE-439:
-------------------------------------------

    Assignee: Gerhard Petracek

> 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
>            Assignee: Gerhard Petracek
>            Priority: Minor
>              Labels: easyfix
>
> if (outcome != null && outcome.contains("."))
> That condition (and optimization) in ViewConfigAwareNavigationHandler effectivly broke my ViewConfig because I neglected to put it into a package. Best solution is simply to never allow the situation to occur and treat it as a definition error.
> 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.



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