tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Closed: (TAP5-221) Add option to generate service outer proxies at build time
Date Fri, 02 Jan 2009 23:21:44 GMT

     [ https://issues.apache.org/jira/browse/TAP5-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Howard M. Lewis Ship closed TAP5-221.

    Resolution: Won't Fix
      Assignee: Howard M. Lewis Ship

My work doing some performance analysis of Tapestry is that this will cause far more headaches
than the minute amount of runtime processing it will save.

> Add option to generate service outer proxies at build time
> ----------------------------------------------------------
>                 Key: TAP5-221
>                 URL: https://issues.apache.org/jira/browse/TAP5-221
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-ioc
>    Affects Versions:
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
> It occured to me that the way tapestry-ioc generates outer service proxies is something
that could be done statically, at build time. An Ant task or Maven plugin could locate all
the service interfaces and generate the proxies for them, using a naming convention.  At runtime
the static proxy class could be located and used if present.
> Premature optimization?  Probably.  Class generation, even with all the overhead of Javassist,
is stil very, very fast.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message