War file created in Eclipse works, but fails when created by Ant

Question

Hi,
I am having trouble getting my flex war file to work when I create it using Ant, even though the same war works fine when I create it from my Eclipse Export War function. This is a critical problem and any ideas or suggestions would be greatly appreciated.
I have a working installation of LCDS running under JBoss 4.0.5 (in a CENTOS (Red Hat) environment). I have implemented a datatier in Java to interact with my PostgreSQL 8.x database. The Java code, plus the necessary flex jars and xml files and some mxml test programs, are all in an Eclipse J2EE project that I created from the flex samples.war file. It all works fine when I use Eclipse to create a WAR from the project and deploy it in JBoss. My problem is this: When I create a WAR piece by piece using Ant, then deploy it to JBoss, that WAR does not work. The error I get is this:
javax.servlet.ServletException: Invalid Configuration: see previous failures. flex.webtier.util.ServiceUtil.setupFlexService(ServiceUtil.java:55) flex.webtier.server.j2ee.MxmlServlet.init(MxmlServlet.java:57), etc.
When I look at the log I see this problem:
"You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.",
but that error is in the server log even when I use the good WAR file.
I have compared the two wars but cannot find any substantial difference between them.
Thanks in advance!

Answer 1

Have you tried enabling debug level logging and removing the category filters in services-config.xml? It should show all the destinations being created, and if any are failing. To get the maximum level of log detail, something like this should work:
><logging>
>
> <target class="flex.messaging.log.ConsoleTarget" level="Debug">
>
> <properties>
>
> <prefix>[Flex] </prefix>
>
> <includeDate>false</includeDate>
>
> <includeTime>false</includeTime>
>
> <includeLevel>false</includeLevel>
>
> <includeCategory>false</includeCategory>
>
> </properties>
>
> </target>
>
> </logging>
Have a check that your remoting destinations are shown starting correctly for both WAR files, and see if there are any messages in the log that might be relevant.