[Scott Ryan]

I am trying to switch over to eclipse to support , run and test some BEA Weblogic 8.1 applications with their split directory structure. I noticed first that the source directory is inside the Web Root directory and that your documentation states that this is not supported for automatic deployment.

I then tried to move the source folder above the Web Root directory and when I deployed no files were sent to the Application Server.

Two questions:

1) Is there any way to support BEA’s suggested development structure with the source files in side the Web Root?

2) What can I check to see why the files from the WEB-INF and not being pushed out when i deploy the application to the 8.1 server.

Thanks for your help and support of a great product.

Scott Ryan
scott@theryansplace.com

[Scott Anderson]

Scott,

re: 1) Placing the source under the web root will cause it to be deployed, and that’s not what you really want. The standard setup has the java source outside the root and the output folder for it is WEB-INF/classes.

re: 2) This might be caused because you don’t have the proper preference set. Check the setting of Window > Preferences > Workbench > Perform Build Automatically on Resoure Modification and ensure that it is set.

Does a ‘Redeploy’ cause the project to be deployed? Can you post the answers to all the questions we ask in the Posting Guidelines thread to help us get started?

–Scott
MyEclipse Support

[MichaelRieser]

I was going to attempt the same thing. I’m evaluating MyEclipse, but must use Weblogic 8.1. Weblogic provides suggestions and tools (ant tasks) which will work to generate and build J2EE applications with weblogic.

http://e-docs.bea.com/wls/docs81/programming/environment.html

Besides the source/..xyz../WEB-INF/src -> build/…xyz../WEB-INF/classes directory switch noted above, the Weglogic suggestion is to have essentially the EAR as a parent project to the WebApp and the EJB project (in a parent directory). I’ve tried this with MyEclipse (3.8.4 with Eclipse 3.0.2), but it doesn’t like projects to have any directory overlap. MyEclipse wants them all to be siblings, but Weblogic wants them to be parent-child to the EAR.

Is the directory structure restriction a MyEclipse characteristic, or does it come from Eclipse?

I realize that Bea has joined the Eclipse group and is going to support Eclipse in the future, any idea whether they will have to adjust to the siblings scheme (because it’s intrinsic to eclipse)?

Any other help or suggestions would be appreciated.

Thanks,
Mike

[Scott Anderson]

Is the directory structure restriction a MyEclipse characteristic, or does it come from Eclipse?

A response for that one is here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-6986-highlight-classloaders+project.html

I realize that Bea has joined the Eclipse group and is going to support Eclipse in the future, any idea whether they will have to adjust to the siblings scheme (because it’s intrinsic to eclipse)?

If you think about their model, it’s rather short-sighted as it doesn’t allow a web or ejb project to be used by more than one EAR, since they try to enforce a parent-child relationship. The model we espouse allows reuse of any combination of projects into one or more EARs. I predict BEA will change their recommendations, as Sun finally has, to be more like ours. However, we’re working on removing this restriction, along with BEA and IBM, through our involvement in the Eclipse Web Tools Project. We (Genuitec) wrote the requirements for what a truly flexible project structure would look like and a team from IBM/Rational has almost completed the implementation and it will support both these discussed models and more. The next major release of MyEclipse will be built on the WTP project model, as will the next generation of tools from all major vendors.

[MichaelRieser]

@support-scott wrote:

I realize that Bea has joined the Eclipse group and is going to support Eclipse in the future, any idea whether they will have to adjust to the siblings scheme (because it’s intrinsic to eclipse)?

[…] The next major release of MyEclipse will be built on the WTP project model, as will the next generation of tools from all major vendors.

Great reply!

Thanks!
Mike

[MichaelRieser]

@support-scott wrote:

If you think about their model, it’s rather short-sighted as it doesn’t allow a web or ejb project to be used by more than one EAR, since they try to enforce a parent-child relationship.

Originally, I let this one go by, because I didn’t think it was that important to mention, but I’ve been reading more posts on the MyEclipse website about directory/project structures. And some of them are recent.

http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-6874.html

In that one it mentions putting your projects into CVS as one big source tree.

Recently I did a major reorganization of source code for some J2SE projects where modules were shared across products and were in a parent-child directory structure whenever they showed up in a project.

In CVS it would be easy to define each of your J2EE components as separate modules in CVS and construct a sandbox which uses those components. (Take a look at Ampersand Modules and the Module file from the CVS docs.)

The parent-child relationship would exist in the developer’s sandbox, but they would be siblings on the CVS server.

FYI,
Mike

[Author]

Posts