[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3771) URL Rewriting Not Occurring
[
https://jira.jboss.org/jira/browse/JBSEAM-3771?page=com.atlassian.jira.pl...
]
Stephen Friedrich commented on JBSEAM-3771:
-------------------------------------------
Found the culprit:
The session id _should_ be added when a JSF renderer calls
context.getExternalContext().encodeResourceURL(urlText);
However as soon as you have Seam's rewrite filter enabled in components.xml
<web:rewrite-filter view-mapping="*.seam"/>
then the encoding is done by
org.jboss.seam.web.RewritingResponse.encode(String)
and that method returns the (possibily rewritten) URL without ever adding the session id.
URL Rewriting Not Occurring
---------------------------
Key: JBSEAM-3771
URL: https://jira.jboss.org/jira/browse/JBSEAM-3771
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.1.CR1
Environment: Windows Vista, JBoss 4.2.0, JRockit 1.5
Reporter: Dave Everson
Assignee: Norman Richards
We have just updated Seam to 2.1.1CR1
We started to use the rewrite functionality within pages.xml.
We have the following pages defined:
<page view-id="/pages/account/check.xhtml">
<rewrite pattern="/newFamilyAccount" />
<begin-conversation join="true"/>
<action execute="#{registerFamily.startEdit}"/>
<navigation from-action="#{registerFamily.doAccountCheck}">
<rule if-outcome="exists">
<redirect view-id="/pages/account/existing.xhtml"/>
</rule>
<rule if-outcome="new">
<redirect view-id="/pages/account/new.xhtml"/>
</rule>
</navigation>
</page>
<page view-id="/pages/account/existing.xhtml">
<rewrite pattern="/existingAccounts" />
<begin-conversation join="true"/>
</page>
We are able to access /newFamilyAccount without issue and a conversation is started
After entering data that already exists in the database, we should be taken to the
/existingAccounts (/pages/account/existing.xhtml) view. We are taken to the view, however
the URL shows: https://localhost/a/pages/account/existing.seam?cid=9.
We have tried several things and can't see to ever have the rewritten URL appear.
Does anyone have any suggestions on what we are doing incorrectly. Thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira