Yes, you will have to keep track of the version number. But you do use cvs (or something) and ant don't you? Then you will have your processdefinition.xml and your properties file in cvs. And the properties file goes into the ear. This way only one file gets deployed (the ear) and you "only" have yourself to blame if things go out of sync.
Oh, this means the rest of your production system must always work with the latest version... I don't think you want another properties file with the version number to use for the rest of your system. I'm more worried about the static initializer. It only gets invoked if your class gets loaded, not so? And the class only gets loaded if it is needed. So what will need your class to be loaded, mmm? Maybe the idea about an application server-specific service that loads at startup is not a bad one... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916857#3916857 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916857 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
