[jira] Commented: (TAP5-627) Allow injection of named spring beans

2010-06-16 Thread Baptiste Autin (JIRA)
[ https://issues.apache.org/jira/browse/TAP5-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12879292#action_12879292 ] Baptiste Autin commented on TAP5-627: - +1 Several beans of the same type in the same

[CONF] Apache Tapestry Content Type and Markup

2010-06-16 Thread confluence
Content Type and Markup Page added by Ulrich Stärk Content Type and Markup Output Tapestry reads well-formed XML template files and renders its output as XML, with minor caveats: The ?xml? XML declaration is omitted. Most element render

[CONF] Apache Tapestry CSS

2010-06-16 Thread confluence
CSS Page added by Ulrich Stärk Tapestry CSS Support Cascading Style Sheets (CSS) is an important technology, even with Tapestry. Tapestry works best when the rendered HTML is simple and semantic semantic meaning HTML that goes back to its

[CONF] Apache Tapestry Environmental Services

2010-06-16 Thread confluence
Environmental Services Page added by Ulrich Stärk Environmental Services Environmental services represent yet another, distinct form of injection. Unlike service injection (injection via a service implementation's constructor) or normal

[CONF] Apache Tapestry DOM

2010-06-16 Thread confluence
DOM Page added by Ulrich Stärk Document Object Model Tapestry 5 takes a very different approach to markup generation than Tapestry 4, or most other frameworks. Tapestry 4 Approach In Tapestry 4, markup generation was based on generating a

[CONF] Apache Tapestry HTTPS

2010-06-16 Thread confluence
HTTPS Page added by Ulrich Stärk Securing your application with HTTPS Tapestry assumes your application will be primarily deployed as a standard web application, using HTTP (not HTTPS) as the transport mechanism. However, many applications

[CONF] Apache Tapestry Input Validation

2010-06-16 Thread confluence
Input Validation Page added by Ulrich Stärk Form Input and Validation The life's blood of any application is form input; this is the most effective way to gather significant information from the user. Whether it's a search form, a login

[CONF] Apache Tapestry Layout Component

2010-06-16 Thread confluence
Layout Component Page added by Ulrich Stärk Layout Component You may see frequent reference to a Layout Component, but you won't find it in the component reference|../tapestry-core/ref/index.html. Layout isn't a component, it's a component

[CONF] Apache Tapestry Logging

2010-06-16 Thread confluence
Logging Page added by Ulrich Stärk Logging of Tapestry Components and Pages Tapestry makes extensive use of SLF4J to log details about the creation and operation of your page and component classes. The default configuration for logging

[CONF] Apache Tapestry Page Lifecycle

2010-06-16 Thread confluence
Page Lifecycle Page added by Ulrich Stärk Page Lifecycle In Tapestry, you are free to develop your presentation objects, page and components classes, as ordinary objects, complete with instance variables and so forth. This is somewhat

[CONF] Apache Tapestry Page Navigation

2010-06-16 Thread confluence
Page Navigation Page added by Ulrich Stärk Page Navigation In essense, a Tapestry application is a number of related pages, working together. To some degree, each page is like an application unto itself. Any individual request will be

[CONF] Apache Tapestry Persistent Page Data

2010-06-16 Thread confluence
Persistent Page Data Page added by Ulrich Stärk Persistent Page Data Most instance variables in Tapestry are automatically cleared at the end of each request. This is important, as it pertains to how Tapestry pages are pooled and shared,

[CONF] Apache Tapestry Persistent State

2010-06-16 Thread confluence
Persistent State Page added by Ulrich Stärk Persistent State Often, you will have a situation where you have a bit of data that is needed across multiple pages. Perhaps you are creating a multi-page wizard, or perhaps you have an object

[CONF] Apache Tapestry Project Layout

2010-06-16 Thread confluence
Project Layout Page added by Ulrich Stärk Project Layout This is the suggested layout for your Tapestry project; it is the layout of folders and files created by the Tapestry Quickstart Archetype|../../quickstart/. If you are creating your

[CONF] Apache Tapestry Project Layout

2010-06-16 Thread confluence
Project Layout Page edited by Ulrich Stärk Changes (3) ... !../images/projectlayout.png!Project Layouth2. Main source files

[CONF] Apache Tapestry Project Layout

2010-06-16 Thread confluence
Project Layout File attached by Ulrich Stärk projectlayout.png (50 kB image/png) Change Notification Preferences View Attachments

[CONF] Apache Tapestry Project Layout

2010-06-16 Thread confluence
Project Layout Page edited by Ulrich Stärk Changes (2) ... !../images/projectlayout.png!Project Layout

[CONF] Apache Tapestry Request Processing

2010-06-16 Thread confluence
Request Processing Page added by Ulrich Stärk Request Processing Understanding the request processing pipeline is very important, as it is one of the chief extension points for Tapestry. Much of the early stages of processing are in the

[CONF] Apache Tapestry Response Compression

2010-06-16 Thread confluence
Response Compression Page added by Ulrich Stärk Response Compression Starting in Tapestry 5.1, the framework automatically GZIP compresses content streamed to the client. This can signifcantly reduce the amount of network traffic for a

[CONF] Apache Tapestry Service Status

2010-06-16 Thread confluence
Service Status Page added by Ulrich Stärk IoC Services Status Using Tapestry there will often be a large number of services defined in the registry; a mix of the builtin services provided by the framework and your own. Built in to every

[CONF] Apache Tapestry Service Status

2010-06-16 Thread confluence
Service Status File attached by Ulrich Stärk servicestatus.png (142 kB image/png) Change Notification Preferences View Attachments

[CONF] Apache Tapestry Type Coercion

2010-06-16 Thread confluence
Type Coercion Page added by Ulrich Stärk Parameter Type Coercions Tapestry automatically handles type coercions for parameters. Type coercions occur when a value passed into a parameter (as bound in template or in an annoation) does not

[CONF] Apache Tapestry Unit testing pages or components

2010-06-16 Thread confluence
Unit testing pages or components Page added by Ulrich Stärk Unit testing pages or components You can easily unit test a certain page or a component. Follow the simple tasks below. Setting up a driving environment In order to unit test a

[CONF] Apache Tapestry URL rewriting

2010-06-16 Thread confluence
URL rewriting Page added by Ulrich Stärk Tapestry URL Rewriting Support Since 5.1.0.1, Tapestry has basic support for URL rewriting. Incoming requests and links generated by Tapestry can be rewritten using exactly the same API. It is based

[CONF] Apache Tapestry Input Validation

2010-06-16 Thread confluence
Input Validation File attached by Ulrich Stärk validation_errors.png (33 kB image/png) Change Notification Preferences View Attachments

[CONF] Apache Tapestry Input Validation

2010-06-16 Thread confluence
Input Validation File attached by Ulrich Stärk validation_initial.png (25 kB image/png) Change Notification Preferences View Attachments

[CONF] Apache Tapestry Input Validation

2010-06-16 Thread confluence
Input Validation File attached by Ulrich Stärk validation_minlength.png (32 kB image/png) Change Notification Preferences View Attachments

[CONF] Apache Tapestry Input Validation

2010-06-16 Thread confluence
Input Validation File attached by Ulrich Stärk validation_password.png (31 kB image/png) Change Notification Preferences View Attachments

[CONF] Apache Tapestry Input Validation

2010-06-16 Thread confluence
Input Validation Page edited by Ulrich Stärk Changes (12) ... Next, all the fields inside the form are activated to pull values out of the incoming

[jira] Created: (TAP5-1189) Invoke JavaScript with LinkSubmit

2010-06-16 Thread sakshi (JIRA)
Invoke JavaScript with LinkSubmit - Key: TAP5-1189 URL: https://issues.apache.org/jira/browse/TAP5-1189 Project: Tapestry 5 Issue Type: Question Components: tapestry-component-report Affects

[jira] Created: (TAP5-1190) New page-level events to decorate component event and page render links

2010-06-16 Thread Howard M. Lewis Ship (JIRA)
New page-level events to decorate component event and page render links - Key: TAP5-1190 URL: https://issues.apache.org/jira/browse/TAP5-1190 Project: Tapestry 5 Issue