我有一个命名的会话范围bean CustomerRegistration
,它有一个命名的生成方法getNewCustomer
,它返回一个Customer
对象。还有CustomerListProducer
类,它将所有客户作为数据库中的列表生成。在selectCustomer.xhtml页面上,用户可以选择其中一个客户并将选择提交给应用程序,然后只需打印出所选客户的姓氏。
现在,仅当我通过#{customerRegistration.newCustomer}
在facelets页面上引用所选客户时,此功能才有效。当我只使用#{newCustomer}
时,每当我提交表单时,姓氏的输出都是null
。
这里发生了什么?这是符合JSR-299规范第7.1章对bean实例的限制的预期行为吗?
它说:
...但是,如果应用程序直接实例化bean类, 而不是让容器执行实例化,结果 实例不是由容器管理的,也不是上下文的 实例,如第6.5.2节“bean的上下文实例”所定义。 此外,第2.1节“功能性”中列出的功能 由容器提供给bean“将无法使用 特殊情况。在已部署的应用程序中,它是容器 负责实例化bean并初始化它们 依赖。 ...
以下是代码:
Customer.java:
@javax.persistence.Entity
@Veto
public class Customer implements Serializable, Entity {
private static final long serialVersionUID = 122193054725297662L;
@Column(name = "first_name")
private String firstName;
@Column(name = "last_name")
private String lastName;
@Id
@GeneratedValue()
private Long id;
public String getFirstName() {
return firstName;
}
public void setFirstName(String firstName) {
this.firstName = firstName;
}
public String getLastName() {
return lastName;
}
public void setLastName(String lastName) {
this.lastName = lastName;
}
@Override
public String toString() {
return firstName + ", " + lastName;
}
@Override
public Long getId() {
return this.id;
}
}
CustomerListProducer.java:
@SessionScoped
public class CustomerListProducer implements Serializable {
@Inject
private EntityManager em;
private List<Customer> customers;
@Inject
@Category("helloworld_as7")
Logger log;
// @Named provides access the return value via the EL variable name
// "members" in the UI (e.g.,
// Facelets or JSP view)
@Produces
@Named
public List<Customer> getCustomers() {
return customers;
}
public void onCustomerListChanged(
@Observes(notifyObserver = Reception.IF_EXISTS) final Customer customer) {
// retrieveAllCustomersOrderedByName();
log.info(customer.toString());
}
@PostConstruct
public void retrieveAllCustomersOrderedByName() {
CriteriaBuilder cb = em.getCriteriaBuilder();
CriteriaQuery<Customer> criteria = cb.createQuery(Customer.class);
Root<Customer> customer = criteria.from(Customer.class);
// Swap criteria statements if you would like to try out type-safe
// criteria queries, a new
// feature in JPA 2.0
// criteria.select(member).orderBy(cb.asc(member.get(Member_.name)));
criteria.select(customer).orderBy(cb.asc(customer.get("lastName")));
customers = em.createQuery(criteria).getResultList();
}
}
CustomerRegistration.java:
@Named
@SessionScoped
public class CustomerRegistration implements Serializable {
@Inject
@Category("helloworld_as7")
private Logger log;
private Customer newCustomer;
@Produces
@Named
public Customer getNewCustomer() {
return newCustomer;
}
public void selected() {
log.info("Customer " + newCustomer.getLastName() + " ausgewählt.");
}
@PostConstruct
public void initNewCustomer() {
newCustomer = new Customer();
}
public void setNewCustomer(Customer newCustomer) {
this.newCustomer = newCustomer;
}
}
不工作selectCustomer.xhtml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:ui="http://java.sun.com/jsf/facelets">
<h:head>
<title>Auswahl</title>
</h:head>
<h:body>
<h:form>
<h:selectOneMenu value="#{newCustomer}" converter="customerConverter">
<f:selectItems value="#{customers}" var="current"
itemLabel="#{current.firstName}, #{current.lastName}" />
</h:selectOneMenu>
<h:panelGroup id="auswahl">
<h:outputText value="#{newCustomer.lastName}" />
</h:panelGroup>
<h:commandButton value="Klick"
action="#{customerRegistration.selected}" />
</h:form>
</h:body>
</html>
使用selectCustomer.xhtml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:ui="http://java.sun.com/jsf/facelets">
<h:head>
<title>Auswahl</title>
</h:head>
<h:body>
<h:form>
<h:selectOneMenu value="#{customerRegistration.newCustomer}" converter="customerConverter">
<f:selectItems value="#{customers}" var="current"
itemLabel="#{current.firstName}, #{current.lastName}" />
</h:selectOneMenu>
<h:panelGroup id="auswahl">
<h:outputText value="#{newCustomer.lastName}" />
</h:panelGroup>
<h:commandButton value="Klick"
action="#{customerRegistration.selected}" />
</h:form>
</h:body>
</html>
CustomerConverter.java:
@SessionScoped
@FacesConverter("customerConverter")
public class CustomerConverter implements Converter, Serializable {
private static final long serialVersionUID = -6093400626095413322L;
@Inject
EntityManager entityManager;
@Override
public Object getAsObject(FacesContext context, UIComponent component,
String value) {
Long id = Long.valueOf(value);
return entityManager.find(Customer.class, id);
}
@Override
public String getAsString(FacesContext context, UIComponent component,
Object value) {
return ((Customer) value).getId().toString();
}
}
答案 0 :(得分:2)
想一想@Producer
是如何注册的。在部署期间,容器会扫描您的类以获取注释以及您在@Producer
bean中声明了@SessionScoped @Named
方法的事实,并不意味着您将拥有与该Bean实例一样多的生成器,也不意味着容器将从你希望它被调用的实例中调用生成器。
这里发生的是 - 您的生产者方法始终返回Customer
的同一个实例,即@PostConstruct
方法在部署期间创建的实例,即在@Producer
注册期间。
这是预期的行为。
您似乎希望每个会话都能为您提供一个新的Customer
实体。在这种情况下,正确的方法是:
public class CustomerProducer {
@Produces @Named @SessionScoped
public Customer getNewCustomer(@New Customer customer) {
// do some custom init if need be
return customer;
}
}
然后从会话范围bean中删除@Producer
相关注释。现在你可以使用`#{newCustomer},它会在每个会话中为你提供一个新的容器管理实例。