Run change detection explicitly after the change: import { ChangeDetectorRef } from ‘@angular/core’; constructor(private cdRef:ChangeDetectorRef) {} ngAfterViewChecked() { console.log( “! changement de la date du composant !” ); this.dateNow = new Date(); this.cdRef.detectChanges(); }
Generally speaking, extending the component tends to be done strictly to use the component. This severely limits your options in unnecessary ways in terms of design, so that your classes can’t extend different classes, you can’t hide the JFrame’s methods causing it to be more difficult to maintain and easier to trigger unexpected bugs when … Read more
You should use it if you want to have access to the entire UIComponent instead of just only its value. For example, to access some methods which can’t be invoked/bound in the view. This is answered in the 1st question you found: JSF component binding – some confusion The 2nd question which you found, component … Read more
It should be noted that it is an anti-pattern to copy properties that never change to the state (just access .props directly in that case). If you have a state variable that will change eventually but starts with a value from .props, you don’t even need a constructor call – these local variables are initialized … Read more
What is it? I think the definition in your answer covers this question well. Although, I question why the definition includes that a component needs to explicitly define its dependencies. A canonical example of a component is an ActiveX control – do they need to explicitly define their dependencies? What problems does it solve? Management … Read more
You can transfer data using service. Make a service that holds the data while you switch components. Below is an example. import { Injectable } from ‘@angular/core’; @Injectable() export class TransfereService { constructor( private router:Router, private companyServiceService:CompanyServiceService ) { } private data; setData(data){ this.data = data; } getData(){ let temp = this.data; this.clearData(); return temp; … Read more
Duplicate component ID errors may occur when: Same ID is used on different components inside the same NamingContainer. Physically different components are bound to the same property of the same bean. The <f:subview> is been declared in the include page instead of the parent page. The same include page is included multiple times inside the … Read more
If you are trying to communicate from a parent component to a child component, this is pretty clearly described using @Input and EventEmitters with @Output in the angular docs. Angular 2 component interaction As for communication across siblings, I posted an answer in a similar question that might help with the issue of sharing data … Read more
Since the origin is actually not XML, but a Javabean, and the other answer doesn’t deserve to be edited into a totally different flavor (it may still be useful for future references by others), I’ll add another answer based on a Javabean-origin. I see basically three options when the origin is a Javabean. Make use … Read more
Yes, use the rendered attribute. <h:form rendered=”#{some boolean condition}”> You usually tie it to the model rather than letting the model grab the component and manipulate it. E.g. <h:form rendered=”#{bean.booleanValue}” /> <h:form rendered=”#{bean.intValue gt 10}” /> <h:form rendered=”#{bean.objectValue eq null}” /> <h:form rendered=”#{bean.stringValue ne ‘someValue’}” /> <h:form rendered=”#{not empty bean.collectionValue}” /> <h:form rendered=”#{not bean.booleanValue and … Read more