• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 436
  • Last Modified:

Need weblogic to see java file changes automatically without doing an ANT build everytime

I've recently been assigned to a project that is using weblogic 9.2.
Its a j2ee application that has several ejb's.  I'm using eclipse editor and everything is installed locally on my linux box.

In past projects i've used tomcat, and I have been able to point tomcat at the projects source (in my eclipse workspace) and then when I change a .java file the changes are picked up automatically (reloadable).  On this project however the other developers do an ant build each time a file is changed which can take a minute or more!  There has to be a way to point weblogic at the source or do something that allows changes to be seen by the server automatically.  Weblogic is in developer mode ( i read you need that for autodeploy to work ), but i'm not sure how to get weblogic setup to "see" my changes.  

I'm not so familiar with weblogic or ejb's but if anyone out there can help me get a reloadable type setup with this project I would be greatful!
  • 2
1 Solution
Your project seems to be using teh correct methodology. Running WebLogic in a development mode means that you can redeploy your application without restarting the server. It does not mean however, that WebLogic can detect source-level changes. Deployment of an EJB application involves the entire EAR file with its JAR and WAR file containing EJB and Web applications. After you change the source, you must recreate the archives which then need to be deployed to WebLogic using its admin console, admin tools or by copying the archive to the appropriate directory.
jacklin10Author Commented:
Doh!  I was doing some research and I thought maybe if I deployed in exploded archive format to the autodeploy folder in weblogic that maybe that might work.... but in the end I guess when I change a file I would need to move the resulting class into that folder in order for it to be "seen" by weblogic.  

Although using a task to do that might be faster than doing a build where it recreates all the archives and then moves them over.  Do you agree?
This is the description of your case (exploded directory format):


I would agree that if you can update a class file in the exploded archive directory rather than recreating all the archives, it is a worthwhile undertaking. I would still do it through Ant. It is trivial to write a copy task and invoke it in Eclipse. You do not even need to compile since Eclispe does it for you automatically.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now