Re: [Keelgroup] New Build System - no openjms

Gene:

I'll do what I can to help out! Comments embedded below....

On Wed, 12 May 2004 13:28:33 -0500
Gene McCullough <[email protected]> wrote:

> At my wits end, didn't take long either.
> 
> I've downloaded the latest cvs, and followed the manual's directions for
> setting up a project.  Everything seems to build ok. (I have to manually
> copy my webapp to my tomcat installation.  I don't know if there is
> already a setting somewhere to do that, or if it needs added.  I had it
> working fine with old build system)

The new build system uses a directory within your project directory called "webapp", and puts the webapp in there. You shouldn't need to copy the webapp to your Tomcat directory until/unless you want to deploy it as a ".war" file. During development/build, it references your ./webapp directory.

> Now i get this message:
> 
> 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:484)
> 	org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
> 	org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
> 	org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
> 
> root cause
> 
> org.keel.clients.ClientException: null, org.keel.comm.openjms.clients.KeelJmsClientOpenJMS
> 	org.keel.clients.AbstractClientConnector.createClients(AbstractClientConnector.java:133)

Sounds like the client (e.g. Struts) is looking for OpenJMS, but no OpenJMS lib is there for some reason. This could be because of the above: if you're running a webapp that is not the one in project/webapp, it might be an old copy?

> -----------------------------------------
> java.lang.ClassNotFoundException: org.keel.comm.openjms.clients.KeelJmsClientOpenJMS
> 
> i added:
> 
> comm.internal=true

Ok - if you use comm.internal, make sure you don't also have any other comm.* entries. E.g. *only* comm.internal.

> to my projects ant.properties, which seems to be what would include the comm layer i prefer.
> 
> at one point I added comm.openjms=true, and got a little further in the webapp, but as I know basically nothing about openjms, i had nothing configured and got a JNDI lookup error.

If you don't want/need OpenJMS, you should just be able to put comm.internal=true and leave out any other comm.* entries.

> help please.  I dove head first into this new build.  I belief it will make development much faster between builds, but I can't get a working deployment now.
> I run ant build-all, then copy the webapp dir to my /usr/local/tomcat/webapps/myapp dir.

I think that last step might be what's confusing Tomcat. If you delete /usr/local/tomcat/webapps/myapp, then restart Tomcat, the app should still be available, as a conf file is being written to conf/Catalina/.... in the Tomcat dir that "points" to the local webapp directory.

> ps Is the list moderator out of town?  I posted a few days ago, sending accidentally as the wrong user, and have not seen it show up on the list yet.

Hmm - no, as far as I know, he's been around.

Let me know if the above gets you a bit further, and I'll help whereever I can to get you underway. Just FYI, I'm just in the process of adding some more detail to the manual about the build system, and I'll go add some notes to the section about the webapp dir to make that clearer.

Thanks!

-- 
Michael Nash

JGlobal Ltd 
Next-Generation Web Application Development and Open Source Support
http://www.jglobal.com

Bahamas Commerce and Trade
Offshore eCommerce Hosting and Business Services
http://www.bahamascommerce.com