Generating a code EventBody, usually com.vitria.jct.EventLib the createEventFromJavaObjects () method that prototype for static com.vitria.fc.flow.EventBody createEventFromJavaObjects (com.vitria.fc.meta.ParameterContainerDef def, java .lams) com.vitria.fc.meta.ParameterContainerDef Describes the information that changes EventBody, java.lang.Object [] params is the parameters required for this eventbody. PrameterContainerDef I have 2 methods I found: 1. Using the Eventbody class Helper class We said that EventBody is actually an interface, the system generates the default Class, to generate this Class, must with the help of Helper class . Some Helper classes can generate different EventBody depending on the incoming parameters. This is a custom implementation of EventBody: static com.vitria.fc.meta.ParameterContainerDef exceptionRequest_def = (com.vitria.fc.meta.ParameterContainerDef) com.CCB.ShangHai.EAI.ExceptionHelper.getMetaObject () findDef ( "ExceptionRequest. "); this is achieved in a standard EventBody: static com.vitria.fc.meta.ParameterContainerDef stringEventDef = (com.vitria.fc.meta.ParameterContainerDef) (vtEvents.BasicEventsHelper.getMetaObject () findDef. (" stringEvent ")) 2, use the com.vitria.fc.meta.metarunninglib MetarunningLib class for information on the registered Class, the standard class is definitely no problem, the custom class does not know if it is also required to register. Example: ParameterContainerdef = metarunninglib.getParaterContainerDeffRompath ("com.vitria.types.types.xmlevents.xmlenvelopevent") feels that the Helper class should be quick.
