I can only answer you question about the various X-Application jar files.
If you build X-Application, i.e. run “build.cmd”,
you get lib\debug\xapplication.jar. (build also generates a lib\opt\xapplication.jar file, but we never use it because is does not include debug information – for example, line numbers stack traces would be missing.)
However, web applications do not directly use lib\debug\xapplication.jar. Instead, every web application has its own copy of this jar file.
Example: your web application resides in “c:\tomcat-home\webapps\myapp”. In this case, you have a copy of the original jar file in
“c:\tomcat-home\webapps\myapp\WEB_INF\lib”.
As a consequence, you have to copy the original lib\debug\xapplicaton.jar to all your web-application WEB_INF\lib directories if you have rebuild X-Application. (The examples coming with X-Application work the same way: after a “build”, you have to run “build examples.jsp” to copy the latest xapplication.jar into the various WEB_INF\lib directories). Otherwise, web applications would continue to use the old version of X-Application.
Rationale – why use multiple copies of the same jar file? That’s kind of a deployment step: you
build the original lib\debug\xapplication.jar, maybe run some tests on it, and then deploy it into the web-application to choose. This way, you can switch one web application to a different xapplication version without affecting other web applications.
I am not familiar with tomcathome\lib\common, sorry.
Michael
Software AG Germany, Darmstadt
#webMethods#Tamino#API-Management