Alex, Steven, Juris, Tim, Thanks a lot for the quick response. so, as I understand - correct me if I am wrong -
# I can get around instrumenting classes at run time using annotations, but if a new boot jar has to be created, I HAVE to bounce the app after updating the tc-config. # The boot jar is OS-specific & as such it might not be a good idea to use something like the Maven plugin in our windows-based devp. environment to generate the boot jar & then SCP it to our Linux boxes - just like we ship our build/jars from Windows to Linux. So as we do our bulids on windows & run stuff on Linux, I am wondering if I can make use of the Maven-plugin for anything more than running tests while doing the builds. # I will look into breaking up the tc-config.xml into multiple modules. Thanks again... Prasad >>> "Alex Miller" <[EMAIL PROTECTED]> 9/25/2007 9:01 PM >>> Hi Prasad... On #1, if I recall, the issue you guys had with this was adding new instrumented classes later during hot deploy. I believe you could get around that by using annotation instrumentation instead so that you would specify a static tc-config based on annotations and then new applications would instrument by using those well-known annotations (defined by you or you could use some example ones we have defined). There is a new forge project that gives an example of how to do this at http://terracotta.org/confluence/display/labs/Annotations Alex ----- Original Message ----- From: "Steven Harris" <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, September 25, 2007 7:45:06 PM (GMT-0600) America/Chicago Subject: Re: [tc-dev] few Terracotta questions On Sep 25, 2007, at 4:30 PM, Prasad Bopardikar wrote: > 1. Can we make run time changes to the tc-config.xml? > We have built a platform on which we deploy various > applications (kinda like deploying war files in Tomcat). We will > have a tc-config for the platform-application. I was wondering if > we deploy applications on this platform, can we modify the tc- > config.xml at runtime? Can it generate a new dso-boot-jar at run time? Boot-jar must be done in advance, config options are currently static but we will probably change this so describing your requirements around this and getting it into the group is a good idea > > 2. Can we break tc-config into multiple xml files - like spring > config? A spring config (xml) can source other xml files - Can > Terracotta do the same with tc-config.xml? Sort of, you would break it up into multiple config modules > > 3. Is there ANY difference in the boot jar created on Windows & > Linux - except the name? > > 4. Are there any best practices that can be followed for boot jar > creation? Currently, we create the boot jar using make-boot-jar.sh > towards the beginning of the script that launches our app (TC client). That's reasonable. If you use our maven stuff it can be done automagically as a stage > > 5. We use Maven for our builds. Is the Terracotta-Maven-Plugin only > meant for creating boot jar, starting DSO server to enable running > tests while doing MVN INSTALL? Does it do anything more? Downloads config modules, has a config module archetype, starts clients, surefire tests, cargo integration is coming (in addition to what you listed) > > Thanks in advance > > > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
