Dan K. wrote:

> Hi Frederic,
> 
> Hmm..
> Did you ever get the tdk to work in your test environment?  If so then and
> assuming you have not missed anything while you mirrored the directory
> structure then I think you might have a permissions problem (?).  I'd
> check that first, especially if your test environment is in windows and
> the deployment one is unix/linux.  Also check for the turbine.log file in
> your webapp's log directory, if it's there then look for clues in it. If
> it's not there, make sure your libs, tomcat shared or whatever and webapp
> specific ones, are correct and in the proper places.
> 
> If this fails, try puttting a simple "hello world" servlet into your tdk
> webapp directory in the jar file and move it to your deployment area and
> let tomcat unjar it.  Then see if you can access it by
> http://server:8080/your_context/servlet/HelloWorld.  This at least lets
> you know if tomcat is recognizing your context and stuff, so you can
> isolate things to a tdk problem.
> 
> Just some things that comes to mind...hope it helps.
> 
> Regards,
> Dan
> 



Hi Dan

I tried all of your recommendations without any success:
   - My development and deployment environment are both on the same 
linux machine.  I don't think to have any permission problem.

  - The turbine log file is not updated which seems to be consistent with 

the fact that nothing from my app even the turbine code has been executed

   - A simple hello world servlet written and tested in the development
  environment and deployed with the whole application works properly
   - Finally, in my tomcat logs, I only see trace from my hello world 
servlet execution but nothing from my app except traces of my web.xml 
file validation.

Actually, I would like to understand the turbine application execution 
model: a first understanding would lead to the creation of a "MyApp" 
servlet which does not seem to be the case. If I understand how the 
application has been launched and executed in the development 
environment, maybe could i get an idea on how to make it work in the 
deployment environment.

Regards

Frederic


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to