|
If you were logged in you would be able to see more operations.
|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
There should be a way to model "custom" pages which will be included within a flow of generated pages. If for some reason a UI screen cannot be fully generated, then it can be marked as custom in the model and generated under the src directory (not target which should only have generated JSPs).
|
|
I see your point, but after spending time on this I must say I think it should be handled differently; I have the feeling that implementing your proposed solution would lead to confusion: the fact that a file is to be overwritten or not should be determined in the configuration (andromda-cartridge.xml or cartridge namespace) and not in the UML model
the proper solution to this problem would be to introduce protected sections and analyze earlier version using diffs, a merge can be applied afterwards
|
|
New Feature
Closed
Critical
Ability to create custom JSPs in the flow with generated JSPs