Hey Yuanjia Chi,
Sorry its taken so long to get back to you - the problem you are seeing is because the war that you are deploying contains ALL the jars needed to build and run the platform. All of these jars are not necessary in JBoss, because JBoss has its own version of some of them that it prefers to use. Unfortunately, some of them actually cause JBoss to not deploy your war, but because the war is packaged as generically as possible we don't just exclude these jars.
So the solution is for you to open up the war, delete the necessary jars, repackage the war file and redeploy it. The list of jars that COULD cause trouble are:
activation.jar
concurrent.jar
dom4j-1.5.2.jar
hsqldb.jar
jaxen.jar
mail.jar
saaj.jar
jaxrpc.jar
xercesImpl.jar
xml-apis.jar
cglib-2.1.jar
commons-httpclient-2.0.2.jar
commons-logging.jar
log4j-1.2.8.jar
jsp-api.jar
servlet-api.jar
asm.jar
asm-attrs.jar
ehcache-1.1.jar
hibernate3.jar
jta.jar
foEmitter.jar
htmlEmitter.jar
portlet-api-1.0.jar
The jars that are most likely the root of your problem are servlet-api.jar and jsp-api.jar. I would recommend removing atleast those two, redeploying and seeing if you experience any other troubles. Let me know how it goes for you!
Thanks
Robert Pattinson
Hope you wont mind
Watch Full Mission: Impossible Ghost Protocol Movie Online