[CONF] Apache Tapestry IndexV2

2010-12-19 Thread confluence







IndexV2
Page edited by Katia Aresti


 Changes (1)
 



...
{div3}  
[!twitterTapestry.png!|http://twitter.com/apachetapestry]  
More on [Tapestry philosophy|TAPESTRY:Principles] - Who uses [Tapestry |TAPESTRY:Applications] ?  
...

Full Content







Latest news 




Friday, 17 December 2010



Announcing Tapestry 5.2


Last changed Dec 18, 2010 19:11 by Katia Aresti


 I'm very proud to announce that the next major release of Tapestry, release 5.2, is now available as Tapestry version 5.2.4.

Read more

Posted at Dec 17, 2010 by

Howard M. Lewis Ship|

0 comments
|
Edit





Thursday, 16 December 2010



Tapestry 5.2 Released


Last changed Dec 16, 2010 12:55 by Howard M. Lewis Ship


 Tapestry 5.2.4 has been voted up as the stable version for Tapestry 5.2; we can now recommend that all users upgrade from 5.1.0.5 to 5.2.4.

Read more

Posted at Dec 16, 2010 by

Howard M. Lewis Ship|

0 comments
|
Edit





Friday, 19 November 2010



Live Tapestry Hotel Booking Demo


Last changed Dec 18, 2010 19:10 by Katia Aresti


 Curious to see a real Tapestry application live?  Your wish is fulfilled; the Hotel Booking Demo is now available.

Read more

Posted at Nov 19, 2010 by

Howard M. Lewis Ship|

0 comments
|
Edit





 









Download the latest Tapestry 5.2.4 binary release. 
MORE DOWNLOADS




	Tynamo
	Chenillekit
	Tapx



MORE EXTENSIONS



	Hotel-Booking Demo



MORE DEMO'S




What is Tapestry ?


 Pure Java and Polyglot

Written in pure Java: code your pages and components in Java, Groovy or Scala.

 Convention over configuration

Say goodbye to endless XML configuration files: dependency injection and meta-programming through annotations.


 Highly productive

Live class reloading means that the time between seeing an error and providing the fix is seconds, not minutes.

 Testable

Committed to testability thoughout design; built-in utilities to enhance TDD. See Tapestry's code coverage report



 Fast

Pure Java; no reflection, not even for property expressions. Built to cleanly support large numbers of concurrent threads without contention. Automatic GZip content compression, _javascript_ aggregation, and client-side caching.


 Advanced Exception Reporting

Gives you all the tools you need to fix your problem: not just a  stack trace, but every bit of information you need to know about what Tapestry  was doing, why it was doing it, what went wrong, and how to fix it.



 Scalable

Scales up big on a single server, and offers great options in a cluster. Ready for REST, suitable for the most stateless or stateful applications.


 Adaptable and modular

Architecture is open and extensible. There's a clean way to add your own extensions, or override built-in logic. Provides  integration   with Hibernate and Spring. Third-party integrations with other tools, such as Quartz.




More on Tapestry philosophy - Who uses Tapestry  ?




Change Notification Preferences

View Online
|
View Changes









[CONF] Apache Tapestry IndexV2

2010-12-19 Thread confluence







IndexV2
Page edited by Katia Aresti


 Changes (2)
 



...
 {div9:class=more} 
[MORE DEMOS|TAPESTRY:Demos] 
{div9} {div8} 
...
h3. !Web.png! Scalable  
Scales up big on a single server, and offers great options in a cluster. Ready for *REST*, suitable for the most stateless or stateful applications. 
 {div4} 
...

Full Content







Latest news 




Friday, 17 December 2010



Announcing Tapestry 5.2


Last changed Dec 18, 2010 19:11 by Katia Aresti


 I'm very proud to announce that the next major release of Tapestry, release 5.2, is now available as Tapestry version 5.2.4.

Read more

Posted at Dec 17, 2010 by

Howard M. Lewis Ship|

0 comments
|
Edit





Thursday, 16 December 2010



Tapestry 5.2 Released


Last changed Dec 16, 2010 12:55 by Howard M. Lewis Ship


 Tapestry 5.2.4 has been voted up as the stable version for Tapestry 5.2; we can now recommend that all users upgrade from 5.1.0.5 to 5.2.4.

Read more

Posted at Dec 16, 2010 by

Howard M. Lewis Ship|

0 comments
|
Edit





Friday, 19 November 2010



Live Tapestry Hotel Booking Demo


Last changed Dec 18, 2010 19:10 by Katia Aresti


 Curious to see a real Tapestry application live?  Your wish is fulfilled; the Hotel Booking Demo is now available.

Read more

Posted at Nov 19, 2010 by

Howard M. Lewis Ship|

0 comments
|
Edit





 









Download the latest Tapestry 5.2.4 binary release. 
MORE DOWNLOADS




	Tynamo
	Chenillekit
	Tapx



MORE EXTENSIONS



	Hotel-Booking Demo



MORE DEMOS




What is Tapestry ?


 Pure Java and Polyglot

Written in pure Java: code your pages and components in Java, Groovy or Scala.

 Convention over configuration

Say goodbye to endless XML configuration files: dependency injection and meta-programming through annotations.


 Highly productive

Live class reloading means that the time between seeing an error and providing the fix is seconds, not minutes.

 Testable

Committed to testability thoughout design; built-in utilities to enhance TDD. See Tapestry's code coverage report



 Fast

Pure Java; no reflection, not even for property expressions. Built to cleanly support large numbers of concurrent threads without contention. Automatic GZip content compression, _javascript_ aggregation, and client-side caching.


 Advanced Exception Reporting

Gives you all the tools you need to fix your problem: not just a  stack trace, but every bit of information you need to know about what Tapestry  was doing, why it was doing it, what went wrong, and how to fix it.



 Scalable

Scales up big on a single server, and offers great options in a cluster. Ready for REST, suitable for the most stateless or stateful applications.


 Adaptable and modular

Architecture is open and extensible. There's a clean way to add your own extensions, or override built-in logic. Provides  integration   with Hibernate and Spring. Third-party integrations with other tools, such as Quartz.




More on Tapestry philosophy - Who uses Tapestry  ?




Change Notification Preferences

View Online
|
View Changes









[CONF] Apache Tapestry IndexV2

2010-12-19 Thread confluence







IndexV2
File attached by  Katia Aresti




twitterTapestry.png
(5 kB image/png)
-
follow tapestry



   
Change Notification Preferences
   
   View Attachments









[CONF] Apache Tapestry IndexV2

2010-12-19 Thread confluence







IndexV2
File removed by  Katia Aresti




twitterTapestry.png (6 kB image/png)
-
follow tapestry




   
Change Notification Preferences
   
   View Attachments










[CONF] Apache Tapestry Component Parameters

2010-12-19 Thread confluence







Component Parameters
Page edited by Bob Harner


Comment:
Combined the mostly-redundant "Informal Parameters" and "Supporting Informal Parameters" sections.


 Changes (4)
 



...
Some components support _informal parameters_, additional parameters beyond the formally defined parameters. Informal parameters will be rendered into the output as additional attributes on the tag rendered by the component. Generally speaking, components that have a 1:1 relationship with a particular HTML tag (such as TextField and input will support informal parameters.  
Only components whose class is annotated with [...@supportsinformalparameters|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/SupportsInformalParameters.html] will support informal parameters. Tapestry silently drops informal parameters that are specified for components that do not have this annotation. 
 Informal parameters are often used to set the CSS class of an element, or to specify client-side event handlers.  
The default binding prefix for informal parameters depends on _where_ the parameter binding is specified. If the parameter is bound inside a Java class, within the [...@component|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Component.html] annotation, then the default binding prefix is prop:. If the parameter is bound inside the component template, then the default binding prefix is literal:. This reflects the fact that a parameter specified in the Java class, using the annotation, is most likely a computed value, whereas a value in the template should simply be copied, as is, into the result HTML stream.  
 
If your component should render informal parameters, just inject the [ComponentResources|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/ComponentResources.html] for your component and invoke the {{renderInformalParameters()}} method.  
h1. Asset Bindings  
...
Tapestry will adjust the URL of the image so that it is processed by Tapestry, not the servlet container. It will gain a URL that includes the applications version number, it will have a far-future expires header, and (if the client supports it) its content will be compressed before being sent to the client.  
h1. Supporting Informal Parameters  *Only* components which area annotated with [...@supportsinformalparameters|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/SupportsInformalParameters.html] may have informal parameters. Tapestry silently drops informal parameters that are specified for components that do not have this annotation.  To render informal parameters, inject the [ComponentResources|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/ComponentResources.html] for your component and invoke the {{renderInformalParameters()}} method.  
h1. Parameters Are Bi-Directional  
...
In Tapestry 5.0, you would define a parameter of the outer component, and use the inherit: binding prefix to connect the inner components parameter to the outer components parameter. This is somewhat clumsy, as it involves creating an otherwise unused field just for the parameter; in practice it also leads to duplication of the documentation of the parameter.  
In Tapestry 5.1 and later, you may use the publishParameters attribute of the [...@component|http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/annotations/Component.html] annotation. List one or more parameters separated by commas: those parameters of the inner/embedded component become parameters of the outer component. You should *not* define a parameter field in the outer component. 
 There are still cases where you want to use the inherit: binding prefix. For example, if you have several components that need to share a parameter, then you must do it the Tapestry 5.0 way: a true parameter on the outer component, and inherit: bindings on the embedded components. You can follow a similar pattern to rename a parameter in the outer component. 

Full Content


Related Articles


 
 Component Parameters





 
 Component Templates





 
 Page And Component Classes




   

<    1   2