[blaplante]

I have inherited a JRun project and I am having the worst time trying to get the configuration to work with a webmodule. JRun uses a different folder structure for deployment than other servers and the webmodule keeps wanting to put files in the standard WEB-INF/classes hierarchy that is used by other containers.

Here is what I have done so far.

1. Opened window >> preferences >> MyEclipse >> Application Servers >> JRun 4 and set the server name to empty so that when it builds the project it will not append the server name to my project name ie… servers/myproject/myproject/etc….

The above choice means that I can not start the server from within eclipse because it will start all JRun servers consecutively.

2. Opening project >> properties, I set the default output folder to
myProject/WebRoot/default-ear/default-war/WEB-INF/classes, so that the folder structure will match JRun’s folder structure.

It seems that there is nothing I can do about the extra WEB-INF folder that is created directly below the WebRoot and I suppose that JRun does not care that it gets put into the servers/myProject/ folder.

3. Created a server in JRun before trying to deploy to it, I imported all of the folders from the server that are not represented by the deployer into the project so that when I deploy they will not be over written.

4. Went to project >> MyEclipse >> Add and Remove Project Deployments and Chose Exploded Archive.

Now somewhere I choose not to have the project automatically add jars from the lib directory to my class path because the project still wanted to use the project root/WEB-INF/lib directory even though I jumped through all of the hoops above to set up a webmodule to play friendly with JRun.

If anyone has a better way to set this up. I would love to hear about it.

[Scott Anderson]

From your description, it appears that you’re trying to deploy your application either inside of or as the default web application on the JRun 4 server. While I can see why you’d want to configure your JRun server this way for production, I’d recommend that you not do this for development.

For normal development deployment and debugging, JRun 4 recognizes exploded web applications just fine. For example, I configured JRun to start the default server (or, you can create your own empty one if you wish) and then deployed my test web application (the struts expression library demo app) using our exploded deployer, in standard exploded format. I can then reference it at http://localhost:8100/StrutsELTest with no problem.

Is there some overriding reason that this won’t work for you?

[Author]

Posts