We are planning to upgrade our current JBoss 3.2.3 servers to JBoss 4.0.1 but if we deploy JBoss 3.2.3 ear files, the applications cannot find their properties and config files any more that are just sitting on the root of the application.
Example structure : | -com | ---abc | ------def.class | ... | -a.properties | -cache.ccf | -config.xml | | What are we doing wrong and how can we resolve this? The ear file works like a charm in JBoss 3.2.3 version but not in the version 4.0.1 Where do we put the config files if the root of the app is not reached any more ? Are there any best practices in JBoss? TIA View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861380#3861380 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861380 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
