Modifier un formulaire de création d'objet

Code:

export admin command * into file c:\temp\commands.exp;

• Utiliser les objets de base,
  
• Faire hériter ses types du standard,
  
• Utiliser les JPO *base tant que c'est possible, ils existent pour pouvoir faire du spécifique par héritage et surcharge de méthode,
  
• Copier les pages JSP standards dans le répertoire custom filter afin de pouvoir les modifier sans risque,
  
• Créer les pages JSP spécifique dans le répertoire custom filter

Il vaut mieux :

* Utiliser les objets de base,
* Faire hériter ses types du standard,

Description:
I created a subtype of Model called "Mission System-Component" and then created an object of this type.

Yet when I try to display it, Tomcat crashes with a "stack overflow" error.

I finally found that the problem comes from emxPRCCommonBase.getStructureListForType which is called to get the hierarchy of the objects underneath my "Mission System-Component" object.

Actually, emxPRCCommonBase.getStructureListForType calls emxPRCCommonBase.getJPOForType(context, objectType) with objectType set to "Mission System-Component". Because there is no associated JPO, it calls getJPOForType(context, objectParentType), with objectParentType set to "Model", and get the name of the JPO "emxModel" (wich is good).

It then calls JPO.invoke(context, "emxModel" , null, "getStructureList", args, Maplist.class), where args is the unchanged parameter that emxPRCCommonBase.getStructureListForType received.

The method emxModel.getStructureList gets the objectId from args:

HashMap programMap = (HashMap) JPO.unpackArgs(args);
HashMap paramMap = (HashMap)programMap.get("paramMap");
String objectId = (String)paramMap.get("objectId");

and the type of the object (which is still "Mission System-Component"):

DomainObject modelObj = DomainObject.newInstance(context, objectId);
String objectType = modelObj.getInfo(context, DomainConstants.SELECT_TYPE);

it then compares the object type found with ProductCentralDomainConstants.TYPE_MODEL and fails because ProductCentralDomainConstants.TYPE_MODEL equals "Model" and objectType equals "Mission System-Component". So the else block is executed and emxPRCCommonBase.getStructureListForType is called again, with the exact same parameters:

if(objectType != null && objectType.equals(ProductCentralDomainConstants.TYPE_MODEL))
{
...
}
else
{
modelStructList = (MapList) ${CLASS:emxPRCCommon}.getStructureListForType(context, args);
}

So emxPRCCommonBase.getStructureListForType calls emxModel.getStructureList which calls emxPRCCommonBase.getStructureListForType, which calls emxModel.getStructureList, etc .. until the stack is full and Tomcat crashes.

Thus it seems impossible to create and use a subtype of a Model.

Am I wrong somewhere or is there really a problem in the code?

If you agree, could you please report it to ENOVIA?

Steps to Reproduce:
Just create a subtype of Model and create an object of that new type under a Product Line. In the thin client, display the parent Product Line and click on the expand button of the new "Mission System-Component" object.

Code:

strNewObjId = productlineBean.create(context,formBean);
String strNewAttributeValues = (String)formBean.getElementValue("txtNewAttributeValues");

      String strAttributeNewAttributeValues = PropertyUtil.getSchemaProperty( context, "attribute_NewAttributeValues" );
     
      if (strNewAttributeValues != null && ! strNewAttributeValues .equals("")) {
      productlineBean.setId(strNewObjId);     
      productlineBean.setAttributeValue(context, strAttributeNewAttributeValues , strNewAttributeValues );
      }


Code:

if(objectType != null && objectType.equals(ProductCentralDomainConstants.TYPE_MODEL))

Code:

if(objectType != null && modelObj.isKindOf(context, ProductCentralDomainConstants.TYPE_MODEL))

Francois Birot a écrit:
if(objectType != null && modelObj.isKindOf(context, ProductCentralDomainConstants.TYPE_MODEL))