Hi all,
Over the past few days I’ve been
trying to get red5 working on tomcat. As I understand it, this goal
should be reachable…but no luck so far. My knowledge of tomcat is
better than spring, but neither are anything to brag about. So, here I am
with cap in hand: Could someone maybe spell out a bit more specifically what steps
I need to take to get red5 running on a clean tomcat installation? Alls I
want to do is be able to stream files (oflaDemo)…nothing sexy!
Two problems experienced so far include:
a) an error message about “No bean
named 'default.context' is defined”. This is clearly spring related
and I’m off to RTFM some more after this email…but any insight
would be appreciated.
b) getting to grips with the red5 and
tomcat config files. This has left me more perplexed. As I understand
it, there are three groups of files: jetty, red5 and webapp. I should be
able to just ditch the jetty files and modify tomcat files as appropriate,
correct? As for the red5 server config files, there are references to
jetty in them and I am confused about where they should go.
Thanks in advance for any input…even
if is “go read this link and then come
back to us, you clueless fool” !!! <:)
Stu
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of northwood Lee
Sent: 25 July 2006 04:48
To: [email protected]
Subject: Re: [Red5] port to tomcat
Hi, I tried.
but with no luck.
so, we decide to move to jetty for now.
but, still, I hope there is a standard war version of Red5 so we can deploy it
in any standard webcontainer.(I noticed that you plan to release the war in 0.6
could it be earlier. I know it shouldn't take too much time, may be just a
section in ant build.xml so I can build it myself)
also, I want to ask about the distribute deployment.Any information?
On 7/21/06, Luke
Hubbard < [EMAIL PROTECTED]> wrote:
Hi,
Red5 *should* ( has not been tested ) run in any servlet engine. You might need
to fiddle with security policy and possibly move some of the jars into a common
classloader and make some changes to a few bits of config but in theory things
should work.
In red5 applications are just webapps. They have a web.xml and can be accessed
via http. We use red5-web.properties to configure the same hosts and paths to
be exposed via rtmp too. This is a shortcut in jetty. Basically you will need
to register your app with the global red5 scope.
Spring is loaded using a servlet listener like usual, but it does some special
trick to locate a root spring context. If its not available it will be loaded
by the first app which needs it, this loads red5 core server, mina, and the
rest. When other apps load they will get the same root context sharing the
networking and other services.
Let us know how you get on. Ideally we would like to provide a war version of
red5 for people wanting to deploy to other servlet engines. I still dont think
you can beat jetty for development though. When running in jetty red5 starts up
in ~ 3 sec.
- Luke
Hi,
I am new to red5
just want to ask, if it will take a lot of time to port this red5 from jetty to
tomcat?
I mean, because jetty and tomcat are all web containers. so I might guess it
would be easy to port the current release to tomcat.
but,if there are something I should pay attention to , please let me know it.
thanks everyone.
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
