Re: Error getting configuration dir.

It was fixed in CVS.  You may need to refresh keel-client.

I have removed my keel.config.override from ant.properties, and things 
are working well.(Sorry Ramin, forgot about that one)


Michael Nash wrote:
> Ramin:
> 
> Ah - I think that's a problem we've seen before (Gene?) with the
> override thing. Thought it was fixed - I guess not.
> 
> The db connect error should be giving you the reason, but it's probably
> related to the config override, as if you comment out keel.override it
> will look in WEB-INF/keel/server/conf for keel.properties. Try copying
> your keel.properties to that dir, you may find it solves the db
> connection problem.
> 
> Mike
> 
> On Thu, 2005-02-10 at 09:16, Ramin wrote:
> 
>>I tried playing around with the web.xml config declarations and
>>finally managed to make that error go away. All I did was comment out
>>this block:
>>
>>  <context-param>
>>       <param-name>keel.config.override</param-name>
>>       <param-value>E:/Development/projects/port113/ramin/myworkspace/app-yaram</param-value>
>>  </context-param>
>>
>>So the problem seems to be coming from there. I even tried changing
>>the "\" to "/", but it still complained.
>>
>>Now the next problem I'm having is when I try to access this url to
>>initialize my DB:
>>http://localhost:8080/default/model.do?model=createdb
>>
>>I get the following error:
>>Could not return a reference to the Component
>>(Key='org.keel.services.persist.PersistentFactory/*')
>>
>>
>>On Thu, 10 Feb 2005 09:02:43 -0500, Ramin <[email protected]> wrote:
>>
>>>Mike,
>>>
>>>Here are the two blocks regarding the config locaiton in my web.xml
>>>file... not sure if these are correct or not...
>>>
>>><context-param>
>>>       <param-name>keel.config.dir</param-name>
>>>       <param-value>WEB-INF/keel/server/conf</param-value>
>>>  </context-param>
>>>
>>>  <context-param>
>>>        <param-name>keel.config.override</param-name>
>>>        <param-value>E:/Development/projects/port113/ramin/myworkspace/app-yaram</param-value>
>>>  </context-param>
>>>
>>>
>>>On Thu, 10 Feb 2005 08:10:07 -0500, Michael Nash
>>><[email protected]> wrote:
>>>
>>>>Ramin:
>>>>
>>>>Check your WEB-INF/web.xml and see if the path for keel.config.dir might
>>>>perhaps be being built incorrectly. That's what the error seems to be
>>>>saying. I've seen situations where the path ended up with a drive letter
>>>>in the middle of it or something similar...
>>>>
>>>>Mike
>>>>
>>>>On Wed, 2005-02-09 at 21:33, Ramin wrote:
>>>>
>>>>>Has anyone been able to install and run Keel's default webapp on
>>>>>windows? I get the whole thing to build successfully and everything
>>>>>seems fine. I start tomcat and navigate to localhost:8080/default and
>>>>>everything is still good. As soon as I try to run the next step (the
>>>>>db initialization step), i get some nasty errors:
>>>>>
>>>>>
>>>>>HTTP Status 500 -
>>>>>
>>>>>type Exception report
>>>>>
>>>>>message
>>>>>
>>>>>description The server encountered an internal error () that prevented
>>>>>it from fulfilling this request.
>>>>>
>>>>>exception
>>>>>
>>>>>javax.servlet.ServletException: Exception during model execution:
>>>>>      org.keel.clients.struts.ModelAction.execute(ModelAction.java:82)
>>>>>      org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
>>>>>      org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
>>>>>      org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
>>>>>      org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
>>>>>      javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
>>>>>      javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>
>>>>>root cause
>>>>>
>>>>>org.keel.clients.ClientException: Error getting configuration dir.:
>>>>>The filename, directory name, or volume label syntax is incorrect
>>>>>      org.keel.clients.webapp.AbstractWebappClientConnector.getWebappPath(AbstractWebappClientConnector.java:413)
>>>>>      org.keel.clients.webapp.AbstractWebappClientConnector.parseInitParameters(AbstractWebappClientConnector.java:363)
>>>>>      org.keel.clients.webapp.AbstractWebappClientConnector.execute(AbstractWebappClientConnector.java:66)
>>>>>      org.keel.clients.struts.StrutsClientConnector.execute(StrutsClientConnector.java:106)
>>>>>      org.keel.clients.struts.ModelAction.execute(ModelAction.java:70)
>>>>>      org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
>>>>>      org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
>>>>>      org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
>>>>>      org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
>>>>>      javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
>>>>>      javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>>>>
>>>>>note The full stack trace of the root cause is available in the Apache
>>>>>Tomcat/5.0.28 logs.
>>>>>Apache Tomcat/5.0.28
>>>>
>>>>http://keelframework.org/documentation.shtml
>>>>Keelgroup mailing list
>>>>[email protected]
>>>>http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>>>>
>>>
>>>--
>>>- Ramin
>>>
>>
> 
> http://keelframework.org/documentation.shtml
> Keelgroup mailing list
> [email protected]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
> 
http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com