P
Peter Judge
Guest
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. Basically, yes. WAR files are a standard Tomcat artifact. PAAR files are OpenEdge-specific. If you look at the PASOE URL below, basically the war file (the ABL webapp) contains - a named context (URL path) - a set of ABL services, grouped by transport - security (authentication and authorisation) for those services - a way to run ABL code (to the ABL application below) PAAR files are service descriptors for rest-transport-based services. So in the URL below, you'd have a CustomerBE.paar which would describe which resources are available, and what the ABL code is behind them. You can have multiple PAAR files for different services. If you had an OrderBE service defined like the CustomerBE service, you'd have an OrderBE.paar file too, in the ABL webapp's WEB-INF/adapters/rest/OrderBE/ folder. Services that use other transports have different service descriptors (WSM files, WebHandlers etc) and don't always follow the pattern on disk that the rest transport does. There's some more info at docs.progress.com/.../PAS-for-OpenEdge-architecture.html
Continue reading...
Continue reading...