Hello Everyone, *Problem*
- As it stands ,if a Jaggery application needs to be updated the user
must manually copy the required files
- This introduces a number of problems
- If several files need to be changed it will become a chore
- A user may forget to copy one or more files
- It departs from the normal way in which patches are applied to
other WSO2 products
- The files that could be included in a patch to a Jaggery file could
include (but is not limited ) to the following;
1. JAG files
2. JS files
3. Jaggery Modules ( These will be JS files)
4. Images and CSS files
5. JSON files
*Suggestion*
- Package the files to be replaced in a zip format
- All Jaggery App patches could be placed in the
repository/components/patches/jaggeryapps similar to the way existing
patches are applied
- *Structure of the patch*
- Please refer to attached image
- The files to be updated would need to be organized according to
structure of the app or module to be patched
- Before the application is deployed the archive is extracted and the
files copied over to the mirrored location in the app or module to be
patched
*Open Questions*
- How do we handle reverting a patch?
- How can we apply the patch before Jaggery app is deployed?
Thank You,
Sameera
--
Sameera Medagammaddegedara
Software Engineer
Contact:
Email: [email protected]
Mobile: + 94 077 255 3005
<<attachment: jagpatch.png>>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
