Questions et réponses d'entretien les plus demandées et tests en ligne
Plateforme d'apprentissage pour la preparation aux entretiens, les tests en ligne, les tutoriels et la pratique en direct

Developpez vos competences grace a des parcours cibles, des tests blancs et un contenu pret pour l'entretien.

WithoutBook rassemble des questions d'entretien par sujet, des tests pratiques en ligne, des tutoriels et des guides de comparaison dans un espace d'apprentissage reactif.

Preparation a l'entretien
Accueil / Sujets d'entretien / Apache Tapestry
Entretiens blancs LIVE WithoutBook Apache Tapestry Sujets d entretien associes: 39

Questions et reponses d'entretien

Decouvrez les meilleures questions et reponses d entretien Apache Tapestry pour les debutants et les profils experimentes afin de preparer vos entretiens.

Total 9 questions Questions et reponses d'entretien

Le meilleur entretien blanc en direct a voir avant un entretien

Decouvrez les meilleures questions et reponses d entretien Apache Tapestry pour les debutants et les profils experimentes afin de preparer vos entretiens.

Questions et reponses d'entretien

Recherchez une question pour afficher la reponse.

Questions et reponses niveau intermediaire / 1 a 5 ans d experience

Question 1

How do we write components in Apache Tapestry?

Retrieving bound properties: When writting a component, you often require various properties to be supplied by the component user. At some point during rendering, you will want to use the value of this property.
You can do this by accessing the Binding. Assume we have a component with one property called 'values'. Our component will use this list in its preRenderCommponent() method to setup some model, for use elsewhere.

.... if(getValues() == null) {
  IBinding binding = getBindings("values"); if(binding.getObject() == null) {
      throw new RequestCycleException("The value for 'values' cannot be null", this);
  } setValues((List)values.getObject());
}

The binding itself will ensure that the object value is the correct type (assuming of course, it's been setup right).
Performing Lazy Instantiation of state based upon component properties: In some cases, the output of a component may be based upon the state of some other property of the same component. For example, imagine a form where the user can choose the type of product to view. When they choose a product, the form makes a query to the database for products matching this type, and reshows the list on the same page. (the list would be included outside of the form element itself).
Lets assume that the page object exposes it's products via a getProductModel(), which is an instance of IPropertySelectionModel.
We will also assume that the remainder of the page has the other components necessary to render correct HTML, using the value supplied by the getProductModel() result.
Here, it is helpful to know when in the rendering process you can rely on the value of selectedProduct to be set correctly, so that you can instantiate a ProductModel based on the provided value, for use in the form rendering. The best place to setup state is in the preRenderComponent() method. This is called by Tapestry just before it renders any component, but AFTER it has set component properties. So, we might write:

protected void preRenderComponent() {
  String selected = getSelectedProduct();
  List products = getMatchingProducts(selectedProduct);
  productModel = new ProductModel(products);
  .. other initialization code ...
Enregistrer pour revision

Enregistrer pour revision

Ajoutez cet element aux favoris, marquez-le comme difficile ou placez-le dans un ensemble de revision.

Ouvrir ma bibliotheque d'apprentissage
Est-ce utile ?
Ajouter un commentaire Voir les commentaires

Les plus utiles selon les utilisateurs :

Copyright © 2026, WithoutBook.