[
https://issues.jboss.org/browse/JBIDE-9051?page=com.atlassian.jira.plugin...
]
Ian Hands commented on JBIDE-9051:
----------------------------------
but because <exception> can have only one of child tags
<http-error> or <redirect>, not both of them.
Wow right on the money. I must say this clarifies the issue, and makes the error
description make _much_ more sense. Thank you so much for pointing this out.
I am completely resolved here I believe, but I do find the following situation troubling.
Why did adding the '?' seem to resolve the error. Funny, but I am having trouble
reproducing the situation where a <http-error> and <redirect> elements
coexisted without error. Maybe I am mistaken and that case never worked.
Thanks again for pointing out the obvious... I was so focused on the query param delimiter
aspect that I overlooked the simple explanation.
I will try again tomorrow to recreate the non error state with <http-error> and
<redirect> elements in one <exception> element, but again I may have fudged up
the details in my head.
Thanks,
-Ian Page Hands
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