[JBoss JIRA] Created: (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)
8:21 a.m.
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
8:27 a.m.
New subject: [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)
[
https://issues.jboss.org/browse/JBIDE-9051?page=com.atlassian.jira.plugin...
]
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
11:38 a.m.
New subject: [JBoss JIRA] Updated: (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)
[
https://issues.jboss.org/browse/JBIDE-9051?page=com.atlassian.jira.plugin...
]
Alexey Kazakov updated JBIDE-9051:
----------------------------------
Assignee: Viacheslav Kabanovich (was: Alexey Kazakov)
Affects Version/s: 3.2.0.Final
Component/s: Seam
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
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
11:38 a.m.
New subject: [JBoss JIRA] Updated: (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)
[
https://issues.jboss.org/browse/JBIDE-9051?page=com.atlassian.jira.plugin...
]
Alexey Kazakov updated JBIDE-9051:
----------------------------------
Fix Version/s: 3.3.0.M3
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
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
2:03 p.m.
New subject: [JBoss JIRA] Updated: (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)
[
https://issues.jboss.org/browse/JBIDE-9051?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich updated JBIDE-9051:
-----------------------------------------
Attachment: ErrorInPagesXML.png
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
2:23 p.m.
New subject: [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)
[
https://issues.jboss.org/browse/JBIDE-9051?page=com.atlassian.jira.plugin...
]
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
7:52 p.m.
New subject: [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)
[
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
1:19 p.m.
New subject: [JBoss JIRA] Resolved: (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)
[
https://issues.jboss.org/browse/JBIDE-9051?page=com.atlassian.jira.plugin...
]
Ian Hands resolved JBIDE-9051.
------------------------------
Resolution: Rejected
Closing as Rejected as this is not a bug. Feel free to change the resolution if there is a
more appropriate choice (looking for NOTABUG).
Thanks for the help.
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
10:38 a.m.
New subject: [JBoss JIRA] Closed: (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)
[
https://issues.jboss.org/browse/JBIDE-9051?page=com.atlassian.jira.plugin...
]
Vlado Pakan closed 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)
--------------------------------------------------------------------------------------------------------------------------------
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 2
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
4683
days inactive
4782
days old
jbosstools-issues@lists.jboss.org
8 comments
4 participants
participants (4)
-
Alexey Kazakov (JIRA) -
Ian Hands (JIRA)
-
Viacheslav Kabanovich (JIRA)
-
Vlado Pakan (JIRA)