Stuart-Palin-BAES
commented
6 years ago OSETS is not particularly robust to errors in the design - particularly if elements are not completed (i.e. some information is omitted).
Some assistance in tracing errors can be obtained by downloading Eclipse XML tools and the ECOA meta-model (from the ECOA website) - and using the Eclipse XML tools to validate generated XML against the ECOA meta-model.
Some further assistance can be gained by running the OSETS tool from the project source using Run As and Eclipse Application". This creates a new instance of Eclipse (with OSETS). Load the problematic project into this new instance and run repeat the action causing the Java exception. Viewing the Console window on the parent instance of Eclipse usually gives some information on progress - which may help identify the area in which the problem exists.
Not sure these warnings are significant, but may be significant to the issue "Null Pointer Exception at Assembly Stage"
The two errors types in full are 1) Type null of the last argument to method invoke(Object, Object...) doesn't exactly match the vararg parameter type. Cast to Object[] to confirm the non-varargs invocation, or pass individual arguments of type Object for a varargs invocation.
2) Type null of the last argument to method invoke(Object, Object...) doesn't exactly match the vararg parameter type. Cast to Object[] to confirm the non-varargs invocation, or pass individual arguments of type Object for a varargs invocation.