Re: Problem with updating and checkout under Tomcat 4

Dariusz Drezno wrote:
>>>And here is my new code (works under Tomcat too!):
>>>
>>>CheckoutCommand cc = new CheckoutCommand();
>>>        cc.setModule(p_module);
>>>        if (client.getEventManager() == null) {
>>>            client.getEventManager().addCVSListener(new
>>
> BasicListener());
> 
>>>        }
>>>        try {
>>>            file://client.executeCommand(cc, globalOption);
>>>            f = new File(client.getLocalPath()   "dsds" );
>>>            tempFile = File.createTempFile("cvsCRLF", "tmp",
>>>f.getParentFile());
>>>        } catch (/*Command*/Exception ce) {
>>>            ce.printStackTrace();
>>>        }
>>
>>So are you saying this doesn't work on Tomcat 4 either? It might be java
> 
> security policy issues - Tomcat 4 is more strict. Have you checked whether
> it is a java security issue?
> 
> 
> 
> That ^ code _works_ under Tomcat (client.execute... is behind commentary).
> Code below doesnt work:
> 
> CheckoutCommand cc = new CheckoutCommand();
>          cc.setModule(p_module);
>          if (client.getEventManager() != null)
>  <-----thanks :), my, typing error
>              client.getEventManager().addCVSListener(new
>              BasicListener());
>          }
>          try {
>              client.executeCommand(cc, globalOption);
>          } catch (CommandException ce) {
>              ce.printStackTrace();
>         }
> 
> I suppose, if it were security policy exception, I wouldn't get "no such
> file or directory", but i.e. "permission denied".
> Am I right?
> 

it can also mean that the new tomcat's VM has the temp directory (one 
that the File.createNewFile() method uses) to a place that doesn't exist..

since the first one works and second one doesn't, seems to prove my 
suspicion..
have you tried to patch the library as I suggested in the previous mail?


Milos