Changing my initial answer – there is no meaningful difference between the two. The tutorial says that backing beans are later declared as managed beans. So, to summarize: a backing bean is the class out of context a managed bean is the backing bean whenever it is declared to be used with the JSF managed … Read more
The binding uses a WeakListener to observe the value of currentWidthPlusTen. Since you don’t keep a reference to the boundNumberProperty, it is eligible for garbage collection as soon as the start(…) method exits. When the garbage collector kicks in, the reference is lost entirely and the binding no longer works. To see this directly, add … Read more
The javax:javaee-api is intended for compiling, not running, including unit tests. If you need classes suitable for running against, run against a Java EE application server. Also, the correct name is Java EE, not JEE.
If you want to use dynamic property names, use the brace notation. <c:forEach items=”${items}” var=”item”> ${item[propertyName]} </c:forEach> See also: Jakarta EE Tutorial – Expression Language – Referencing Object Properties Jakarta EE Tutorial – Expression Language – Examples of EL Expressions
As @Korgen mentioned in comments hibernate-validator-5.x.x isn’t compatible with validation-api-1.0.x. This is because of moving to new specification JSR-303 -> JSR-349. There are two ways to solve this issue: 1. Downgrade hibernate validator version (which is implements JSR-303): <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-validator</artifactId> <version>4.3.1.Final</version> </dependency> 2. If you don’t want to move back from hibernate validator 5 … Read more
Thanks, but that was not the solution. I found it out why it wasn’t working for me. Since I’d done a declaration: ApplicationContext context = new ClassPathXmlApplicationContext(“beans.xml”); I thought I would refer to root directory of the project when beans.xml file was there. Then I put the configuration file to src/main/resources and changed initialization to: … Read more
http://download.oracle.com/otndocs/jcp/7224-javabeans-1.01-fr-spec-oth-JSpec/ http://www.oracle.com/technetwork/java/javase/tech/index-jsp-138795.html Also, a direct link to the (PDF) specification. Section 8.8 in the linked document is entitled “Capitalization of inferred names” and briefly outlines how names of properties are derived.
Suppose you have boolean active; Accessors method would be public boolean isActive(){return this.active;} public void setActive(boolean active){this.active = active;} See Also Java Programming/Java Beans Code Conventions for the Java Programming Language
The correct answer is getxIndex() setxIndex(int value) if you want them to be used as properties according to section 8.8: Capitalization of inferred names of the JavaBeans API specification (e.g. access them via ${object.xIndex} in a JSP.
Lots of potential solutions, but let’s add just one more. Use Jackson (JSON processing lib) to do “json-less” conversion, like: ObjectMapper m = new ObjectMapper(); Map<String,Object> props = m.convertValue(myBean, Map.class); MyBean anotherBean = m.convertValue(props, MyBean.class); (this blog entry has some more examples) You can basically convert any compatible types: compatible meaning that if you did … Read more