[gatein-issues] [JBoss JIRA] (GTNWSRP-287) Add ability to deactivate URL rewriting on producer

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on GTNWSRP-287:
-------------------------------------------------

Jared MORGAN <jmorgan at redhat.com> made a comment on [bug 824907|https://bugzilla.redhat.com/show_bug.cgi?id=824907]


    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1,2 @@
-Cause: No possibility to disable url rewriting
+In the current WSRP implementation, the producer URL is rewritten at consumer side so it can be accessed remotely. 
-Consequence: URL rewriting cannot be disabled.
+If users have static content at both the producer and consumer sides, they do not expect those resources to be accessed from a remote producer. In these circumstances, it was desirable to disable URL rewriting, however no such mechanism existed. The fix includes enhancements to the WSRP, with the addition of the "org.gatein.wsrp.producer.deactivateURLRewriting". If the parameter is set to true, URL rewriting is disabled.-Fix: Upgrade WSRP
-Result: URL rewriting is disabled with parameter as expected.
                
> Add ability to deactivate URL rewriting on producer
> ---------------------------------------------------
>
>                 Key: GTNWSRP-287
>                 URL: https://issues.jboss.org/browse/GTNWSRP-287
>             Project: GateIn WSRP
>          Issue Type: Feature Request
>          Components: Producer
>    Affects Versions: 2.1.5-GA
>            Reporter: Chris Laprun
>            Assignee: Chris Laprun
>             Fix For: 2.1.7-GA, 2.2.0-Beta01, 2.2.0
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira