Generating a schema using the Message Composer sometimes take a lot of time. Some schema's take up to an hour to get generated.
In most cases, once generated we only do small changes tot he schema, adding or removing some elements.
But even if only a single attribute was added, the generation process generates the whole subset.
If only the changes are re-generated then the whole process could be cut down to seconds. This would of course only be a valid course of action if the datamodel itself hasn't been changed.
Possible solution:
When generating, store the schema info in the destination package. Package.Element.Runstate might be a good candidate to store that info.
When re-generating, check if the previous schema info is present in the destination package.
Compare the current schema with the previous schema info
Ask the user if he wants a complete re-generation or only the changed parts
Generating a schema using the Message Composer sometimes take a lot of time. Some schema's take up to an hour to get generated.
In most cases, once generated we only do small changes tot he schema, adding or removing some elements. But even if only a single attribute was added, the generation process generates the whole subset.
If only the changes are re-generated then the whole process could be cut down to seconds. This would of course only be a valid course of action if the datamodel itself hasn't been changed.
Possible solution: