Code changes not reflecting on server

[Sahil Dave]

Hi

I wonder why the code changes in my web app are not getting reflected
on the server automatically.
Is it that, I have to re-publish the application after making every
small piece of change?
I am using Eclipse and Weblogic 9.2

Please Advice.

Thanks
Sahil

 

[Lew]

I wonder why the code changes in my web app are not getting reflected
on the server automatically.
Is it that, I have to re-publish the application after making every
small piece of change?
I am using Eclipse and Weblogic 9.2

There are a few possibilities. Depending on how you deploy to
WebLogic, you might have linked the web app to the WAR file built from
your project. You won't see changes to the WAR file unless you
rebuild. If you have Eclipse set up to build automatically, that
might be happening already, but maybe it isn't set to build
automatically.

Also, you are correct about republishing. I don't know exactly how
Eclipse makes all its decisions, but depending on how you set up the
project explicit publishing can be necessary.

Finally, if you deploy the build output, i.e., the directory tree with
target web pages and .class files, rather than the WAR, you should see
screen changes immediately on the next browser refresh.

This is an area where Eclipse and NetBeans work rather differently.
NB seems to prefer to deploy the build directory by choice, so screen
changes are seen right away by default.

 

[Sahil Dave]

There are a few possibilities.  Depending on how you deploy to
WebLogic, you might have linked the web app to the WAR file built from
your project.  You won't see changes to the WAR file unless you
rebuild.  If you have Eclipse set up to build automatically, that
might be happening already, but maybe it isn't set to build
automatically.

Also, you are correct about republishing.  I don't know exactly how
Eclipse makes all its decisions, but depending on how you set up the
project explicit publishing can be necessary.

Finally, if you deploy the build output, i.e., the directory tree with
target web pages and .class files, rather than the WAR, you should see
screen changes immediately on the next browser refresh.

This is an area where Eclipse and NetBeans work rather differently.
NB seems to prefer to deploy the build directory by choice, so screen
changes are seen right away by default.

No, I haven't setup a war build yet. I am just manually publishing the
project on the server every time.