1/ if I remove all the EClasses but one (say USAddress) , I will be able
to create a .PPO model of it. It works fine, lets say I can create
instance.ppo and populate it with one USAddress
2/ after that I add a second class in the PPO package (say PurchaseOrder),
regenerate etc
3/ then creation of a new .PPO file will fail, *however* the PPOeditor
will allow me to edit the former instance.ppo file correctly
My intuition is that it could be a problem of definition of a DocumentRoot
class or something like that(maybe a default is missing) since editing
directly the XML .ppo models can raise such exceptions.