Page History

{scrollbar}

Contents

Tapestry Version 5.0.19

Bugs Fixed

...

• TAPESTRY-1294 – Tapestry does not set an output encoding which prevents Unicode content from being output correctly
• TAPESTRY-1423 – Tapestry IoC fails to get the correct class from javassist.CtClass when the instance is already a proxy
• TAPESTRY-1425 – Eager Loaded service (builder) cannot use object injection
• TAPESTRY-1434 – Service builder methods do not allow services to be defined in terms of non-interface class, even though ServiceBinder does
• TAPESTRY-1443 – org.apache.tapestry5.annotations.Service annotation is ignored
• TAPESTRY-1447 – Headers are not set appropiately to allow the browser to cache javascript resources.
• TAPESTRY-1451 – T5 website: Broken Link to script.aculo.us
• TAPESTRY-1464 – Cannot Subclass TapestryFilter to add custom init() and destroy() logic
• TAPESTRY-1465 – BeanEditForm and Grid are not extensible in terms of supported property types to be editted or viewed
• TAPESTRY-1480 – Implement Radio component
• TAPESTRY-1481 – ActionLink and PageLink render an id attribute, but don't provide a clientId property, making it impossible to reference them in JavaScript
• TAPESTRY-1491 – No way to get the logical page name for a page instance
• TAPESTRY-1494 – Artifact snapshots are being deployed to the tapestry-repository, not the tapestry-snapshot-repository
• TAPESTRY-1497 – EagerLoad is too early for a normal Tapestry application
• TAPESTRY-1498 – nbsp in template causes exception in SAX Parser.
• TAPESTRY-1504 – When a Map is converted to a SelectModel, the keys are converted unnecessarily to strings
• TAPESTRY-1511 – VerifyError when using inner classes inside components
• TAPESTRY-1528 – No way to cleanup the thread without access to the Registry
• TAPESTRY-1537 – Release notes for 5.0.4 claim that TAPESTRY-1294 is fixed, which it isn't
• TAPESTRY-1559 – application package initializer removed while merging svn
• TAPESTRY-1562 – Spurious warnings about missing component ids due to case-sensitive checking of template ids vs. declared components
• TAPESTRY-1571 – CheckForUpdatesFilter can cause deadlock
• TAPESTRY-1583 – The "block:" binding prefix may only reference blocks that appear before the reference in the template, an error occurs if the block is defined later in the template
• TAPESTRY-1585 – tapestry-upload has an incorrect manifest entry for the module class
• TAPESTRY-1590 – Page templates in WEB-INF located based on logical page name (which may not match the class name)
• TAPESTRY-1593 – Various typos in docs/comments
• TAPESTRY-1596 – Contributing a service to the Alias service configuration fails if the service uses a non-standard scope, such as perthread
• TAPESTRY-1614 – No "expires" header should be set in asset download requests, as that can confuse the browser, preventing changes versions of assets from being downloaded

...

• TAPESTRY-1276 – If component should include an optional negate parameter
• TAPESTRY-1284 – Tapestry Spring integration module
• TAPESTRY-1292 – Allow lists to be used as select models
• TAPESTRY-1302 – JavaScript support
• TAPESTRY-1311 – Identify type of component via tag element name in templates
• TAPESTRY-1319 – tapestry.InfrastructureOverrides is not yet implemented
• TAPESTRY-1325 – Add an "asset:" object provider, to simplfy injecting assets into services
• TAPESTRY-1341 – Allow service builders named "build" and determine service id from the result type

{scrollbar}