Hi all, I just ran into this while tracking down what might cause the RIFE tests to fail on JBoss. When using the DeploymentBuilder, make sure that when you use addResourceFullpath, you don't start the path with a slash (/). This causes the war zip file to have absolute path names, which cause JBoss' deployer to throw string index out of bounds exceptions when deploying the war. Maybe this will save some time for someone else in case this happens again: http://svn.terracotta.org/fisheye/browse/Terracotta/dso/branches/2.4/code/base/clustered-rife-1.6.0/tests.system/com/tctest/rife/tests/ContinuationsTest.java?r1=3653&r2=3690
On another note, I also found some other weird behavior with JBoss 4.0.5 which could also save someone some time by knowing about it beforehand. If your war name happens to start with a number, your deployment will be different from what you expect. If you, for example, name a WAR like this: '01_helloworld', it'll unpack it to a temp dir with a prefix 'deploy/tmp2635625' (some random number) and adds '01_helloworld' to the name. Then it actually parses the name of the temp dir to find the first non numeric char after tmp, and uses that for the URL of the webapp, so in this case your webapp context URL becomes '_helloworld' instead of '01_helloworld'. Take care, Geert -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
