FYI ... I did add a FAQ about this; but I may change MetaWorker to
expose a CCTW2 rather than implement a CCTW2.

On Tue, Aug 23, 2011 at 9:54 PM, Josh Canfield <[email protected]> wrote:
>>    TAP5-1508: Contributions to CCTW2 must be qualified with @Primary when 
>> using @Contribute, to avoid collision with MetaWorker service
>
> Ack... I just spent an hour trying to figure out why my CCTW2
> contributions started failing between alpha-2 and alpha-13.
>
> Howard, can you (or anyone who understands) elaborate on what this
> means? I think this is going to need some special documentation if
> it's going to be the case going forward.
>
> Josh
>
>
> On Thu, Jul 21, 2011 at 6:37 PM, Hudson (JIRA) <[email protected]> wrote:
>>
>>    [ 
>> https://issues.apache.org/jira/browse/TAP5-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069342#comment-13069342
>>  ]
>>
>> Hudson commented on TAP5-1508:
>> ------------------------------
>>
>> Integrated in tapestry-trunk-freestyle #428 (See 
>> [https://builds.apache.org/job/tapestry-trunk-freestyle/428/])
>>    TAP5-1508: Contributions to CCTW2 must be qualified with @Primary when 
>> using @Contribute, to avoid collision with MetaWorker service
>>
>> hlship : 
>> http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1149416
>> Files :
>> * 
>> /tapestry/tapestry5/trunk/tapestry-hibernate/src/main/java/org/apache/tapestry5/hibernate/HibernateModule.java
>>
>>
>>> Reduce memory utilization of Tapestry page instances
>>> ----------------------------------------------------
>>>
>>>                 Key: TAP5-1508
>>>                 URL: https://issues.apache.org/jira/browse/TAP5-1508
>>>             Project: Tapestry 5
>>>          Issue Type: Improvement
>>>          Components: tapestry-core
>>>    Affects Versions: 5.3
>>>            Reporter: Howard M. Lewis Ship
>>>
>>> This is an umbrella bug for a number of changes aimed at reducing the 
>>> overall memory footprint of a Tapestry page.  Tapestry pages have been seen 
>>> to be quite large in some production sites, and the shared-instance 
>>> strategy introduced in 5.2 is still insufficient. A significant amount of 
>>> space is consumed using Maps and Lists (for bindings, of sub-components, 
>>> etc.) in a way that is optimized for a smaller code base and efficient read 
>>> access, even though most of the information is only read when a page is 
>>> first loaded, and is rarely needed or accessed after that.
>>
>> --
>> This message is automatically generated by JIRA.
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to