p：commandButton事件的执行顺序

Question

我正在使用PrimeFaces 6.0组件：

<p:commandButton type="submit" value="Create Customer"
    icon="ui-icon-check"
    actionListener="#{newCustomerBean.saveNewCustomer}"
    update = "@form"
    oncomplete="ajaxUploadFile();"/>

<p:inputText id="saveCustomerId" value ="#{newCustomerBean.savedKundeId}"/>

我想对它们执行以下操作序列：

1.）在备用bean上执行actionListener方法以保存客户；

2.）用在步骤（1）中保存的客户的ID更新表单字段saveCustomerId。 在成功保存和存储后，actionListener方法将生成一个客户ID，并将其作为bean属性存储。

3.）执行Java Script方法ajaxUploadFile（）

根据链接

按下PrimeFaces p：commandButton时事件的执行顺序

这个顺序应该是我想象的。

但是实际上

ajaxUploadFile（）

在更新ID为saveCustomerId的输入字段之前被调用。

您能帮我按正确的顺序吗？

这是支持bean：

@ManagedBean
@ViewScoped
public class NewCustomerBean implements Serializable {


    public enum KundeTyp {

        TYP_NATPERS("Nat. Person"), TYP_FIRMA("Firma");

        private String value;

        private KundeTyp(String value) {
            this.value = value;
        }

        @Override
        public String toString() {
            return value;
        }

    }

    private KundeTyp custmerType;
    private Map<String, KundeTyp> custmerTypes;

    private long savedKundeId;

    @Inject
    private KundeDBService kundeService;

    private String vorname;

    private String addresse;

    private String steuerNummer;

    private String kundeTyp = Integer.MIN_VALUE + "";

    @PostConstruct
    public void init() {
        custmerTypes = new HashMap<String, KundeTyp>();
        custmerTypes.put(KundeTyp.TYP_NATPERS.value, KundeTyp.TYP_NATPERS);
        custmerTypes.put(KundeTyp.TYP_FIRMA.value, KundeTyp.TYP_FIRMA);
    }

    public KundeTyp getCustmerType() {
        return custmerType;
    }

    public void setCustmerType(KundeTyp custmerType) {
        this.custmerType = custmerType;
    }

    public Map<String, KundeTyp> getCustmerTypes() {
        return custmerTypes;
    }

    public void setCustmerTypes(Map<String, KundeTyp> custmerTypes) {
        this.custmerTypes = custmerTypes;
    }

    public String getVorname() {
        return vorname;
    }

    public void setVorname(String vorname) {
        this.vorname = vorname;
    }

    public String getAddresse() {
        return addresse;
    }

    public void setAddresse(String addresse) {
        this.addresse = addresse;
    }

    public String getSteuerNummer() {
        return steuerNummer;
    }

    public void setSteuerNummer(String steuerNummer) {
        this.steuerNummer = steuerNummer;
    }

    public String getKundeTyp() {
        return kundeTyp;
    }

    public void setKundeTyp(String kundenTyp) {
        this.kundeTyp = kundenTyp;
    }

    public String saveNewCustomer(ActionEvent e) {


        Kunde neuerKunde = null;

        switch (this.custmerType) {
        case TYP_NATPERS: {
            neuerKunde = new NatuerlichePerson();
            break;
        }

        case TYP_FIRMA: {
            neuerKunde = new Firma();
            ((Firma) neuerKunde).setSteuerNummer("123456");
            break;
        }
        }

        neuerKunde.setVorname(vorname);
        neuerKunde.setAdresse(this.addresse);

        try {
            savedKundeId = kundeService.saveKunde(neuerKunde);

        } catch (ServiceException se) {

            FacesContext.getCurrentInstance().addMessage(null, new FacesMessage(FacesMessage.SEVERITY_ERROR, "Error",
                    "Unable to save the new customer: " + se.getMessage()));
        }

        return null;
    }

    public long getSavedKundeId() {
        return savedKundeId;
    }

    public void setSavedKundeId(long savedKundeId) {
        this.savedKundeId = savedKundeId;
    }
}

Answer 1

由于找不到解决方案，我将在此处提出解决方法。 我们没有在前端更新customerId，而是将其作为会话属性放在HttpSession中。

然后，在处理文件上传的UploadServlet中，我们读取此属性并将图像保存在此customerId下。