[jira] [Commented] (TAP5-1894) Rosetta Stone

["Chris Mylonas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154942#comment-14154942 ] 

Chris Mylonas commented on TAP5-1894:
-------------------------------------

Link rewriting for a proxy, i.e. when tapestry page is embedded in another application (like php)

from the mailing list
You can do that using the LinkRewriter API or the old Tapestry URL rewriter API (for incoming URLs, the old API is easier to use than LinkRewriter): https://github.com/thiagohp/tapestry-url-rewriter.
 
<dependency>
    <groupId>br.com.arsmachina</groupId>
    <artifactId>tapestry-url-rewriter</artifactId>
    <version>2.0.0</version>
</dependency>

and

Tapestry has built-in support for rendering links to a proxy via the
BaseUrlSource.
 
If you contribute the following symbols to match your PHP server
- SymbolConstants.HOSTNAME
- SymbolConstants.HOSTPORT
- SymbolConstants.HOSTPORT_SECURE
 
All links (and form post endpoints) generated by tapestry will point to the
PHP server rather than the tapestry container.


Or you could decorate the BaseUrlSource service to check for request
headers etc.

> Rosetta Stone
> -------------
>
>                 Key: TAP5-1894
>                 URL: https://issues.apache.org/jira/browse/TAP5-1894
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: documentation
>            Reporter: Chris Mylonas
>            Priority: Minor
>              Labels: documentation
>
> There are equivalent ways for doing numerous things in Tapestry 5.
> An equivalence table, or rosetta stone, or icon that links "tagged" features within the documentation would be a treat for new to intermediate developers.  A double rainbow or double unicorn for giggles.
> For example:
> 1)  @Property bindings within the template, or in the page's java class file.
> 2)  contributeApplicationDefaults VS command line parameters / symbols
> 3)  component templating (MarkupWriter element&end/writeRaw VS .tml VS streamResponse)
> 4)  JS & CSS inclusions within .tml files or in java classes.  Further, inclusion of contexts versus relative
> I've read the above 4 examples time and again over the last 12 months as I've part-timed my way through Tapestry deving, but it's just not that easy to find what I'm looking for in a quick enough time.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)