Details
Wish
Minor
Description
Currently it is not possible to call a Java class (writen by a user) before or after any panel. This is basic functionality.
I have many examples of use, here is one:
We have a registry file in a set location on the OS that contains information about previous products installed or other products installed. I have an XML parser that will open the file, fetch the information and was hoping to call this class and then determine a flow of panels from there.
I can not call external Java class with anything provided with IzPack and because of this one issue, we are purchasing a commercial installer.
I looked at the documentation and am led to believe this is possible but the documentation is full of ghost features that do not work.
I googled and found many other people trying to attempt the same thing but there was never a resolution on any post.
I posted multiple times on the mailing list but no one could provide a working example. Some people that replied trying to be helpful had never actually accomplished this feat with IzPack.
—
I am requesting the following:
1. the part of the documentation that leads one to believe this is possible, should be removed from the manual until it is a working feature
2. When this feature is implemented, it should be designed in such a way that multiple processes can be called (maybe a panel at the beginning of the install and a panel at the end of the install).
If the current documented way were possible, it would still be impossible to have two of these because of the hard coded values of the files that go with it, namely ProcessPanel.Spec.xml and UserInputSpec.xml.
the ultimate solution would be the ability to put a panel (or multiple panels) and call Java classes at any time. Right now, even if it did work, it would not support multiple Java calls, but only one.
Issue Links
| This issue depends upon: | ||||
| IZPACK-285 | Possible execution of a java class before and after a panel |
|
|
|
If a claim is made that any of the above is possible, then
1. Update the documentation with a working example
2. Attach a working example (entire project with pom.xml) showing that it does work.
Please do not say this simply works because you have imagined it. Writing it down in the documentation does not mean that it actually works. I have seen this before. You actually have to write code, compile and test (THEN DOCUMENT) before you can call it a working feature.
If you can not provide an example (project zipped with a pom.xml) , please delete it from the documentation.