Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Hot deployment in Bea Weblogic.

 
Er. Rohit Sharma
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi! all,
I am using weblogic in my current project and infact this is my first time...so for many of you this issue can be funny but I request you to please look at it even it sounds funny I noticed that that even I make changes in Jsp the war had to be build and published to server again. But for tomcat we dont have to publish the jsp elated changes.
Can we achieve this in weblogic..this can certainly save development time.
Thanks in advance.

 
Joe Ess
Bartender
Posts: 9279
10
Linux Mac OS X Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Auto-Deploying Applications in Development Domains
Personally, I prefer to have the same build and deploy process in my development environment and my production environment. This minimizes the differences between environments so it's easier to replicate production conditions for debugging.
 
Lavanya Halliwell
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
for what it's worth...

when I use netbeans & tomcat, I build and deploy and run all within netbeans ide....so I never ran into this.

when I use eclipse (j2ee version) and sun java app server 8.2, I always build and export to a war file. Then I deploy using sun app server admin console.

when I just started using web logic, I would create an app in netbeans and deploy it manually using the weblogic admin console.

I would say, when in doubt, build and deploy separately. (netbeans makes it easy with tomcat but can be a pain for other servers)
 
Don't get me started about those stupid light bulbs.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic