[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)

[Viacheslav Kabanovich (JIRA)]

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

Viacheslav Kabanovich commented on JBIDE-9051:
----------------------------------------------

Error marker is not added because of EL or ? character, but because <exception> can have only one of child tags <http-error> or <redirect>, not both of them. Screenshot displays two error markers - one added by WTP's check of constraint declared in schema, the other complaints about inconsistency caused by that in our internal model (it expects only one such child to be put into map by key 'target' for quick access, and probably we should not add  markers that cannot be clear to customers). 

Ian, if in your example having both http-error and redirect is correct, could you please attach your schema for seam pages xml.

> 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, Seam
>    Affects Versions: 3.2.0.Final
>         Environment: RHEL6, Eclipse 3.6, Current release of JBoss tools
> Also noticed error in JBDS 4.x
>            Reporter: Ian Hands
>            Assignee: Viacheslav Kabanovich
>            Priority: Minor
>             Fix For: 3.3.0.M3
>
>         Attachments: ErrorInPagesXML.png
>
>
> 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