Hello, Thanks for that. But there is another issue... I caught the same mistake in the Standalone.java and fixed it myself... Infact the same change that was made.
Now that problem is Red5 is looking for the Application jars and classes in the /opt/red5/webapps directory when they are being compiled in the /opt/red5/dist/webapps directory. Seeing this, I added the "dist" directory to the red5 root path and it started... But when I tried to stream a file I got a whole mess of exceptions. Another issue is that ant is instructed to delete everything in the "dist" directory and recompile. This should not happen because if you have this running on a production server doing so will wipe out all the files being kept in the /streams/ directory of each app. It would be very easy for someone to run "ant" and have the builder wipe everything out. I don't get why it has to be in a "dist" directory. The way it worked before was just fine where it was in the /webapps/ directory and just replaced the classes/jars. -Luke On Aug 27, 2007, at 3:14 PM, Joachim Bauch wrote: > Hi Luke, > > Luke Scott schrieb: > [...] >> It looks like something is seriously messed up because that path >> should be "/opt/red5/webapps/red5-default.xml". > [...] > > this is now fixed on the trunk in r2249. > > Joachim > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
