Project:
View Revisions: Issue #52859 | [ Back to Issue ] | ||
Summary | 0052859: It is not possible to have computed columns both in m_product and m_offer_product | ||
Revision | 2023-06-28 10:05 by AugustoMauch | ||
Description | If we try to have computed columns both in the m_product and m_offer_product tables, the datasource response for both of those tables will fail. For m_product: - java.lang.ClassCastException: class org.openbravo.model.pricing.priceadjustment.Product_ComputedColumns$HibernateProxy$GcoEEn1j cannot be cast to class org.openbravo.model.common.plm.Product_ComputedColumns (org.openbravo.model.pricing.priceadjustment.Product_ComputedColumns$HibernateProxy$GcoEEn1j and org.openbravo.model.common.plm.Product_ComputedColumns are in unnamed module of loader org.apache.catalina.loader.ParallelWebappClassLoader @51e7ffe5) For m_offer_product: - org.openbravo.base.util.CheckException: Property testOffer does not exist for entity Product_ComputedColumns The cause is that when generating the entities for the computed columns, the names of the entities are built using <className>_ComputedColumns, and the name for both m_product and m_offer_product classes is Product, resulting in two entities with the same name (Product_ComputedColumn). |
||
Revision | 2023-06-27 18:14 by AugustoMauch | ||
Description | If we try to have computed columns both in the m_product and m_offer_product tables, the datasource response for both of those tables will fail. For m_product: - java.lang.ClassCastException: class org.openbravo.model.pricing.priceadjustment.Product_ComputedColumns$HibernateProxy$GcoEEn1j cannot be cast to class org.openbravo.model.common.plm.Product_ComputedColumns (org.openbravo.model.pricing.priceadjustment.Product_ComputedColumns$HibernateProxy$GcoEEn1j and org.openbravo.model.common.plm.Product_ComputedColumns are in unnamed module of loader org.apache.catalina.loader.ParallelWebappClassLoader @51e7ffe5) For m_offer_product: - org.openbravo.base.util.CheckException: Property testOffer does not exist for entity Product_ComputedColumns The cause is that when generating the entities for the computed columns, we names of the entities are built using <className>_ComputedColumns, and the name for both m_product and m_offer_product classes is Product, resulting in two entities with the same name (Product_ComputedColumn). |
Copyright © 2000 - 2009 MantisBT Group |