[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9051) Tooling shows errors if the view-id parameter in a restrict tag contains a hashtag or Seam EL and no '?' (query param delimiter)

[Ian Hands (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-9051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605768#comment-12605768 ] 

Ian Hands commented on JBIDE-9051:
----------------------------------

Sorry rereading this JIRA I see that I failed to properly explain. The example snippet provided came from a Seam projects pages.xml file.

Here is the error as copied from the eclipse "Problems" console:
Description    Resource    Path    Location    Type
Value target is not unique.    pages.xml    /portal/src/main/webapp/WEB-INF line 32    Constraint Problem

> Tooling shows errors if the view-id parameter in a restrict tag contains a hashtag or Seam EL and no '?' (query param delimiter)
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-9051
>                 URL: https://issues.jboss.org/browse/JBIDE-9051
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jsp/jsf/xml source editing
>         Environment: RHEL6, Eclipse 3.6, Current release of JBoss tools
> Also noticed error in JBDS 4.x
>            Reporter: Ian Hands
>            Assignee: Alexey Kazakov
>            Priority: Minor
>
> I see that the IDE detects errors if I have a URL in a view-id attribute that has a hastag or Seam EL, and does not have any query parameters.
> example:
> <exception class="org.jboss.seam.security.AuthorizationException" log-level="trace">
>   <http-error error-code="403"/>
>   <redirect view-id="/403.xhtml#{restrictHelper.hashTag}"/>
> </exception> 
> A work around would be to simply use:
>   <redirect view-id="/403.xhtml?#{restrictHelper.hashTag}"/>
> This is still a valid URL, and does not cause the tooling to show errors.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira