H
hutcj
Guest
Hi Keerthy, I have attempted usage of the CatalogGeneration task as advised. While I was able to successfully generate .json catalog files for each service, it required manually listing out each class file in the build.xml that was to be associated with a given service. Can this not be done automatically by referencing the .services/Expose/rest/ /*.xml files? All of this information is contained in there, and PDSOE uses it to create the .pidl and .json files when editing a service. Also, I am confused as to how to generate .war/.paar files if there is no available task to create the .pidl files. Yes, I can successfully generate the correct .war and .paar files, but if and only if the .pidl files are present and up to date with the source code (the contents of the .pidl files are subject to change based upon annotations in the class files, and compiling the code does not update the .pidl files). If I cannot generate the .pidl files, how then can I generate the .war or .paar files? To clarify, my understanding of the relationship between .paar and .war files is as follows (correct me if I am wrong): A .war file is an archive much like a .zip file that contains all the .paar files for deployment of all services, in addition to other resources. Individual .paar files can be generated for incremental deployment of specific services.
Continue reading...
Continue reading...