Collaborative Development / Hot Deployment?

We are a small development team (5-7 people) and have a need to develop collaboratively because each of us is working on small parts of a large application, and we have code dependencies upon eachother. We are looking for suggestions on how to develop collaboratively.
We have attempted to use 9iAS to develop on - but every time we change any class files, we have to restart the OC4J container for them to be recognized error free. JDeveloper is out of the question because our current PC's cannot handle it (PII ~ 350mhz, 256RAM) and we cannot get new PC's for another year. We have attempted to run a standalone instance of OC4J on the server, but that still requires restarting the instance anytime classes are changed.
Does anyone have any suggestions for collaborative development? Does anyone know of an environment that has a working hot deployment feature? We are not developing any EJB's, it is strictly a JSP/Servlet solution with Data Access classes for database interaction.

Semi-speculation on my part follows:
 My understanding of "hot deployment" is that if a new ear file was placed in
 the applications directory it wouldn't supercede the old ear file until it
 was manually deployed. It may however get staged to managed servers but not
 actually deployed. i.e moved but not available.
 -Brett
 "Josh Garcia" <[email protected]> wrote in message
 news:3e1deefc$[email protected]..
 >
 > As I understand, hot deployment should ONLY occur when server(s) are in
 development
 > mode. Are there any cases where hot deployment can occur even when
 servers are
 > in production mode?
 >
 > A little more detail:
 >
 > We are running a WLS 7 SP1 cluster, and, even though our administration
 and managed
 > servers are all in production mode, our EAR is automatically deployed to
 managed
 > servers when placed in the 'applications' directory. Should this be the
 case?
 > I thought that I had to physically redeploy through the console if I was
 in prduction
 > mode.
 >
 > Josh

Similar Messages

Servlet Hot-Deploy with a WebApp

Hi everybody,
Does anybody know something about hot deployment of servlets in a web
application (.war) ?
I tried many things (setting reloadCheckSecs in properties, in web.xml,
hot-deploy from console...) but nothing really worked.
So I have to register a servlet for hot deployment in the properties, but
then it doesn't belong to the application.
Thanx,
Markus.

Are u saying that WARs are redeployed automatically but not individual servlets,
or neither?
Thanks.
Viresh Garg wrote:
Currently the automatic hot deployment of a servlet/JSP from exploaded WAR is
broken. We are in the process of fixing it for next release. You have to
redeploy your web application right now, for the change to take place.
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
"M. Hammer" wrote:
Hi everybody,
Does anybody know something about hot deployment of servlets in a web
application (.war) ?
I tried many things (setting reloadCheckSecs in properties, in web.xml,
hot-deploy from console...) but nothing really worked.
So I have to register a servlet for hot deployment in the properties, but
then it doesn't belong to the application.
Thanx,
Markus.

JSF (RI) app hot-deploy memory leak

I have a standard JSF (RI) based web app that appears to be working just fine in terms of functionality. However, I believe that there is a memory leak associated with the sort of frequent hot-deploy cycles that are typical during a normal development cycle. I have been monitoring the app via the jvmstat 3.0 tools and have witnessed NO memory growth in the young or old generation areas - regardless of useage pattern. All of the growth seems to happen in the perm area of memory and be directly coincidental with the occurence of a deploy. Eventually, continued hot-deply cycles will result in an OutOfMemory error on the container - please note that continued and extensive use of the app WITHOUT the aforementioned hot-deploys does NOT result in the OutOfMemory error.
From my research so far, I have discovered the following thread:
http://forum.hibernate.org/viewtopic.php?t=935948&postdays=0&postorder=asc&start=75
It refers to a similar problem with hiberate (which I am NOT using) as well as a commons-logging and several others. From the looks of it, I strongly suspect that there may be an issue with JSF when it's implementation is bundled inside the WEB-INF/lib dir - i.e. inside the specific web app's ClassLoader.
Based on the above, I have implemented a SessionContextListener that invokes the org.apache.commons.logging.LogFactory.release() inside the contextDestroyed( ServletContextEvent e ) method. This does appear to free up some perm memory but there is still large growth that appears to be directly related to the FacesServlet initialization (navigation handlers, etc). I looked into calling the FacesContext.release() method which seems to have purpose similar to that of the LogFactory.release() method. However, at the time of the contextDestroyed() invocation, FacesContext.getCurrentInstance() always returns null, so I do not ever have an opportunity to invoke the release method that I am aware of. If my suspicions are correct, than I would likely be able to avoid this problem entirely by simply placing the JSF implementation jars in the conatiner's shared lib dir - instead of bundling it inside WEB-INF/lib. However, this is not an option for this container as multiple web apps (which require the flexibility to use differing JSF implementations and versions - i.e. RI vs MyFaces, etc) will run on this container.
I don't believe it is at all related to the problem at hand, but my container is JBoss 4.0.2.
Any and all assistance and suggestion will be greatly appreciated! Has anyone else seen this sort of behavior? Are there any work arounds or corrective actions?
TIA

Has anyone else run into this? I'd greatly appreciate any assistance as I cannot seem to resolve this hot-deploy related leak.

Hot deployment in WL 8.1

Hi All,
I am deploying the application from my development dir "c:\development" as
exploded for WAR file and EJB modules as JAR files. What should I do to make
the hot deployment work?
My environment is: Win XP, IDE is JBuilder(also use Eclipse3.0), Weblogic
8.1
When I was googling, it brought me the CLASS-LOADER article in bea docs and
I applied that making different nested class-loaders for EJB, WAR in one and
the EJB module which is under development in a separate class-loader. It did
not work. But I think there should be an easy way for hot deployment. If
there is any link that talks about this please let me know. Your response is
appreciated.
Thanks,
senthil

Also adding to that, the server is started in development mode.
"Senthil" <[email protected]> wrote in message
news:[email protected]...
I am not sure this a way to go for hot deployment. But what I did was
changing the application and weblogic-application.xml files.
My application.xml is like
===========application.xml===========
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE
Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>AppName</display-name>
<module>
<web>
<web-uri>Web</web-uri> 
<context-root>/</context-root>
</web>
</module>
<module>
<ejb>EJB1</ejb>
</module>
<module>
<ejb>EJB2</ejb>
</module>
</application>
=============END==========
weblogic-application.xml is given below
==============weblogic-application.xml==========
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-application PUBLIC "-//BEA Systems, Inc.//DTD WebLogic
Application 8.1.0//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic-application_2_0.dtd">
<weblogic-application>
<classloader-structure>
<module-ref>
<module-uri>EJB1.jar</module-uri>
</module-ref>
<classloader-structure>
<module-ref>
<module-uri>EJB2.jar</module-uri>
</module-ref>
</classloader-structure>
</classloader-structure>
</weblogic-application>
=========End===========
Thanks,
senthil
"Senthil" <[email protected]> wrote in message
news:[email protected]...
Hi All,
I am deploying the application from my development dir
"c:\development"
as
exploded for WAR file and EJB modules as JAR files. What should I do tomake
the hot deployment work?
My environment is: Win XP, IDE is JBuilder(also use Eclipse3.0),
Weblogic
8.1
When I was googling, it brought me the CLASS-LOADER article in bea docsand
I applied that making different nested class-loaders for EJB, WAR in oneand
the EJB module which is under development in a separate class-loader. Itdid
not work. But I think there should be an easy way for hot deployment. If
there is any link that talks about this please let me know. Your
response
is
appreciated.
Thanks,
senthil

Obaccess.dll causes link error on hot deploy

I'm doing web services development with AccessServerSDK 10G, Glassfish v3, on windows XP using Eclipse. It works fine except whenever I change my code and eclipse attempts to hot deploy the application, the following error occurs and the deploy bombs:
"org.apache.catalina.LifecycleException: org.apache.catalina.LifecycleException: java.lang.UnsatisfiedLinkError: Native Library C:\NetPoint\AccessServerSDK\oblix\lib\obaccess.dll already loaded in another classloader"
It seems that the obaccess.dll reloads without checking whether if it is already loaded. The only way to redeploy the application is to shutdown Glassfish and restart it for every change I make. It's impeding my progress.
So far I've tried the following:
--removing jobaccess.jar from inside my application and putting it into Glassfish_HOME/domain/domain1/lib; it didn't help.
--put an ObConfig.shutdown before the ObConfig.initialize; it didn't help.
--catching the exception and ignoring it, but then the application gets a null pointer exception when it runs.
I can't find anyone else in cyberspace complaining about this problem. I hope it isn't an issue with Windows because we do all our development on our desktops, but I wouldn't be surprised.
Anyone else having this problem or found a fix for it?

Hi,
I already faced with this problem on WLS11gR3 (10.3.4) and I try with all your workaround.
The solution I found was to install on separate server chain in order to reboot the server instead of use Hot Deploy.
We have also think to migrate the application to J2SE.
It seam that it is not possible to remove Jni 'till jvm is up and running.
Wile summer have you found any solution?

Obaccess.dll causes link error on hot deploys

I'm doing web services development with AccessServerSDK, Glassfish v3, on windows XP using Eclipse. It works fine except whenever I change my code and eclipse attempts to hot deploy the application, the following error occurs and the deploy bombs:
"org.apache.catalina.LifecycleException: org.apache.catalina.LifecycleException: java.lang.UnsatisfiedLinkError: Native Library C:\NetPoint\AccessServerSDK\oblix\lib\obaccess.dll already loaded in another classloader"
It seems that the obaccess.dll reloads without checking whether if it is already loaded. The only way to redeploy the application is to shutdown Glassfish and restart it for every change I make. It's impeding my progress.
So far I've tried the following:
--removing jobaccess.jar from inside my application and putting it into Glassfish_HOME/domain/domain1/lib; it didn't help.
--put an ObConfig.shutdown before the ObConfig.initialize; it didn't help.
--catching the exception and ignoring it, but then the application gets a null pointer exception when it runs.
I can't find anyone else in cyberspace complaining about this problem. I hope it isn't an issue with Windows because we do all our development on our desktops, but I wouldn't be surprised.
Anyone else having this problem or found a fix for it?

Hi,
I already faced with this problem on WLS11gR3 (10.3.4) and I try with all your workaround.
The solution I found was to install on separate server chain in order to reboot the server instead of use Hot Deploy.
We have also think to migrate the application to J2SE.
It seam that it is not possible to remove Jni 'till jvm is up and running.
Wile summer have you found any solution?

Previous unanswered Hot deploy of non EJB, non JSP classes

 Subject to my last post I've since seen my questions has appeared twice on this
 newsgroup, March 2001, and Nov 2000 and no responses to it those times. Aren't
 there BEA engineers reading this newsgroup who would know the answer to that question?
 http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=3776&utag=
 http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=5171&utag=


 Firstly I already did call BEA support before coming here, this is my last resort.
 I can't get a definitive answer from support. They were the ones that actually
 suggested to me that I post here in the first place. I did search the BEA edocs
 and couldn't find anything on it.
 Secondly, I am using WL 6.1 SP1, and in the thread just beneath this one, which
 I referred to directly in my opening post on this thread, I do mention this in
 the opening paragraph, in fact I give considerable detail.
 Thirdly, I never implied there was an onus on any BEA engineer to answer anything
 here. What I did mean was that given that they do read these posts and they do
 answer posts, I was merely a bit concerned that as I'm third person to ask, it
 would be strange to still get no response given that they answer other questions.
 I mean if they don't know, then who does? It's a real simple yes/no answer, it
 would take 5 seconds.
 Paul
 Robert Patrick <[email protected]> wrote:
 >
 >
 >The answer is simple -- move to WLS 6.x and use enterprise applications
 >(or web applications or an EJB jar file)
 >to package everything up into a single deployment unit and hot deploy
 >the whole deployment unit. WLS 5.1 and
 >earlier do not support hot deployment of non-servlet/non-JSP/non-EJB
 >classes.
 >
 >Mike Reiche wrote:
 >
 >> You can always call BEA Support - 1.888.232.7878 to get the help you
 >need. This
 >> newsgroup is not official BEA Support. It is out of the goodness of
 >their hearts
 >> that BEA engineers help people out here.
 >>
 >> I don't really think you wanted everyone that read your email and didn't
 >know
 >> if such a feature was available, to send you an email saying 'No, I
 >don't know
 >> if such a feature is available'. That's why there were zero responses.
 >>
 >> None of the posts you listed mention what version of WL. That makes
 >a difference.
 >> Also read the online documentation at edocs.bea.com, search for 'hot
 >deploy'.
 >>
 >> Mike Reiche
 >>
 >> "Paul H" <[email protected]> wrote:
 >> >
 >> >Subject to my last post I've since seen my questions has appeared
 >twice
 >> >on this
 >> >newsgroup, March 2001, and Nov 2000 and no responses to it those times.
 >> >Aren't
 >> >there BEA engineers reading this newsgroup who would know the answer
 >> >to that question?
 >> >
 >> >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=3776&utag=
 >> >
 >> >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=5171&utag=
 >
 >
 ><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 ><html>
 >The answer is simple -- move to WLS 6.x and use enterprise applications
 >(or web applications or an EJB jar file) to package everything up into
 >a single deployment unit and hot deploy the whole deployment unit.
 >WLS 5.1 and earlier do not support hot deployment of non-servlet/non-JSP/non-EJB
 >classes.
 >Mike Reiche wrote:
 ><blockquote TYPE=CITE>You can always call BEA Support - 1.888.232.7878
 >to get the help you need. This
 > newsgroup is not official BEA Support. It is out of the goodness
 >of
 >their hearts
 > that BEA engineers help people out here.
 >I don't really think you wanted everyone that read your email and
 >didn't
 >know
 > if such a feature was available, to send you an email saying 'No,
 >I
 >don't know
 > if such a feature is available'. That's why there were zero responses.
 >None of the posts you listed mention what version of WL. That makes
 >a difference.
 > Also read the online documentation at edocs.bea.com, search
 >for
 >'hot deploy'.
 >Mike Reiche
 >"Paul H" <[email protected]> wrote:
 > >
 > >Subject to my last post I've since seen my questions has appeared
 >twice
 > >on this
 > >newsgroup, March 2001, and Nov 2000 and no responses to it those
 >times.
 > >Aren't
 > >there BEA engineers reading this newsgroup who would know the answer
 > >to that question?
 > >
 > >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=3776&utag=
 > >
 > >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=5171&utag=</blockquote>
 ></html>
 >
 >

Hot deployment using the REDEPLOY feature

Hi
I am rather confused regarding the usage of the HOT DEPLOYMENT in WLS 6.1 sp2
- Win2000.
According to the documentation - "deployment.pdf" p. 31 you should be able to
simply touch the REDEPLOY file and the entire application should then be redeployed
by WLS. However according to the following link:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.management&item=2095
the usage of the REDEPLOY feature is only for WebApp's not EJB's.
So my question in short terms: What am I supposed to belive ? the BEA documentation
or the BEA support team ?
I have tried using the REDEPLOY feature as suggested by the documentation however
the WLS fails to do the redeployment with an execption.
Kind regards
Jorgen Fastrup

From my experience REDEPLOY does work for EJBs as well. You need to meet two conditions: REDEPLOY file should be in META-INF and your application should be deployed under the domain/application. I was not able to get it to work when the application is deployed elsewhere. If somebody knows how to it, please let me know.
Alexander.

Auto Deployment versus Hot Deployment

Hi,
Can anyone one please tell me what the real difference is between auto deployment versus hot deployment in WLS 8.1 SP4 as I am confused after reading the documentation.
Can they both be individually enabled or disabled?
Can I just disable Auto deployment and only use Hot deployment (or is hot deployment another name for manual deployment).
I know in Jrun that you can add hot-deploy directories in Jrun console, where now when a developers put a new WAR file or an updated WAR file - the server automatically deploys/redeploys it at that moment (this hot deploy directory could be any directory on the server or even on a different NTFS drive on same server).
Can this be achieved with WLS 8.1?
Thanks
J

AutoDeployment automatically deploy/redeploy or undeploy the application when the application is put or removed from the applications folder under the wls domain directory. It is only available in Admin Server while it is running in development mode (default mode). It is not available if the Admin Server is running in Production mode.
Hot deployment deals with updating the application modules like ejb or war inside an ear without redeploying the complete application. This is dependent on the classloader structure of the given application. So if a ear has a webapp and a ejb with default classloader structure, then only the webapp can be hot redeployed without complete application redeploy. It can be used for apps deployed on both Admin and Managed servers and is available for both production and development mode.
Autodeployment is mainly to save the developer from running the deploy command every time while the app is being developed iteratively. Just copying the updated application in the applications folder will redeploy the app on the Admin server.
Hot deployment is mainly used to update the individual modules or jsps/servlets/classes in a module without redeploying the complete app.

Hot Deploy Servlet in JAR file problem

I've been playing with hot deploying servlets in WLS 5.1. I have SP2
          installed. I have things working fine with individual servlet class files. I
          decided to try hot deploying with jar files.
          I created a servlet, added it to a jar file, and then added the jar file to
          the 'weblogic.http.servlet.classpath'. I then restarted the server. I
          started the console and was able to hot deploy the servlet. So far so good.
          My next test is what failed. I modified the servlet, and rebuilt the jar
          file. I went back to the console, selected the servlet and hit the redeploy
          button. I went back to the browser and hit refresh - nothing, still the old
          servlet.
          It appears that WLS isn't reloading the jar file and the updated servlet.
          Everything works with individual class files.
          Does anyone know how I can cause the reload of updated servlets embedded
          within a jar file?
          Weblogic group - If there is no way now, will support be added soon?
          Thanks,
          Rick


Hi,
          If I use weblogic.servlet.ServletServlet to try just the servlet , It
          works correctly.But When I develop it in a web application , there is a lot
          of hypelink to this servlet,thus I can't use the relative path reference to
          that servlet.I try to set the name of weblogic.servlet.ServletServlet same
          as the webapp,It doesn't work,how do I solve this problem?
          Thank you
          Pan
          Subject: Re: Hot deploy Servlet in webapp
          > http://www.weblogic.com/docs51/classdocs/API_servlet.html#134798
          >
          > It even explains why you shouldn't use it in production environment.
          >
          > Dimitri

Hot Deployment & ClassLoader Re-Use

I've implemented a service that observes changes to a jar file's timestamp, and utilizes a new UrlClassLoader to hot deploy class changes. It's working well in isolation, but I wonder how it will perform in production. The work is based on the October 31, 2000 JDC Tech Tips ( http://java.sun.com/developer/TechTips/2000/tt1027.html ).
I've tried to improve on the example code and I wonder if my change will help or haunt me. The example creates a new URLClassLoader every time the class is requested by name. In comparison, I wanted to only create a new class loader when necessary. To do so, I collect the class loader used for a given class name and re-use it on the next request if the underlying jar file has not changed. Is this a wise approach? Anything else I should be thinking about?
Here's some sample code to illustrate:
    protected HashMap jarMap = null;
    protected HashSet classesUpgraded = null;
    protected HashMap classLoaders = null;
    protected IUpgradeObserver observer = null;
    public Class getClass(String xtlClassName) throws ClassNotFoundException {
        Class c = null;
        File f = getJar(xtlClassName);
        observer.notifyIfChanged(f);
        try {
            if(f != null) {
                lazyInitClassesUpgraded();
                if(classesUpgraded.contains(xtlClassName)) {
                    // the jar has changed, so create a new class loader
                    Dbug.print(dbugTag, "Reloading " + xtlClassName + " from jar with timestamp " + f.lastModified());
                    ClassLoader loader = new URLClassLoader(new URL[]{f.toURL()});
                    c = loader.loadClass(xtlClassName);
                    if (c != null) {
                        classesUpgraded.remove(xtlClassName);
                        lazyInitClassLoaders();
                        classLoaders.put(xtlClassName, loader);
                } else {
                    // the class has already been loaded from the current jar - reuse the existing class loader
                    lazyInitClassLoaders();
                    ClassLoader loader = (ClassLoader)classLoaders.get(xtlClassName);
                    c = loader.loadClass(xtlClassName);
        } catch (MalformedURLException urle) {
            urle.printStackTrace();
        if(c == null) {
            throw new ClassNotFoundException("The Xtencil jars did not contain " + xtlClassName);
        } else {
            return c;
    }

legosa - Sure, some portion of getClass must be synchronized to reduce the likelihood of an additional new class def being created when two threads enter getClass at the same time. The other points you make are good as well, and I initially became aware of them in reading the Sun example. As far as I can tell, they shouldn't affect us. I'm not writing a general-purpose class loader. My work is only used to load a specific type of "map" that is frequently updated. We always go through the same factory function to create these maps by name. No singletons will be generated through the utility, and it should be fine for two class objects to exist for a given class name. Basically, the software looks up a map implementation by name, runs it, marks the map as garbage, and moves on to the next. If I plug my class loader into our other web-based container, I have more concerns, since many users may be requesting maps and the old class definitions are less likely to be garbage at any given time.
pekoe - Thanks for the heads up on HotSwap. Unfortunately, as I understand it, the work is intended for development environments, not production servers. For example, it requires the JVM be in debug mode!

Exploded (hot) deployment on a Weblogic cluster

AFAIK, exploded hot deployment on a Weblogic cluster is not supported through OEPE.
When deploying an application on a cluster, each change, no matter how small, forces you to republish these changes, ultimately causing the application to be redeployed by OEPE. Turnaround time for this (depending on the app) can take some time.
Is there a workaround available for this ?
I'm looking for a way to minimize the turnaround time between developing code, and actual seeing the code changes on the screen. The requirement however is that deployments should be possible on a managed instance / cluster (non AdminServer).
Does Oracle Weblogic support such "hot deployment" capabilities from an IDE like Eclipse ? Does anybody here have such a process in place ? (perhaps using ant / maven2 tooling)

Hi
I want to clarify that the application has to be deployed to a cluster of two managed servers, amandad_Server_1 (On Windows server hosting console) and amandad_Server_2 which is running in other Windows server.
I deployed the application following your recdommendations and the resulta is as follows:
Windows server (running the console)
1 EAR file was copied to ... \user_projects\domains\amanda_domain\servers\amandad_Server_1\stage
2. The application files extractected from the EAR files were copied to   \user_projects\domains\amanda_domain\servers\amandad_Server_1\tmp
Windows Server not runn ing the console
No files were copied to neither
... \user_projects\domains\amanda_domain\servers\amandad_Server_2\stage
     \user_projects\domains\amanda_domain\servers\amandad_Server_2\tmp
Questions
1 Windows server not running the console the files were not copied....What might cause this behaviour....? how to fixi it...?
2. Do I have to manaully copy the files to folders
...\user_projects\domains\amanda_domain\servers\amandad_Server_2\stage
   ... \user_projects\domains\amanda_domain\servers\amandad_Server_2\tmp

Hot deployment and JMX

Hi,
I need to know how classes are loaded in hot deployment. my problem is that I'm using a JMX server that has some MBeans registered into it, but when I redeploy an application, and the JMX server is recreated as are the MBeans, the JMX agent clearly points to the old instances of the MBeans instead of the redployed ones. It seems that only restarting the OC4J would fix the pointers.
Is there any way to fix this? or do I have to restart the server every time I deploy an application?

What option are you using for deployment ? Are you choosing re-deploy ? We recommend Oracle9iAS install in a test/production environment when
the application has stabilized.
Also if you are in a development mode and constantly changing your applications you should consider deploying your apps in standalone OC4J. You can choose to do open-expanded directory deployment.
If you are using OC4J standalone:
1) you can replace the EAR file in applications directory and it redeploys
2) you can replace a Servlet class and change the time stamp on web.xml and it redeploys the srvlets
3) It automatically redeploys the JSP files
4) If your EJBs are changed, replace your EJBs and change the timestamp on application.xml and it redeploys
Some of these options are disabled in OC4J embedded in Oracle9iAS to provide a stable environment for production applications.
If you still have problems in hot-deployment in OC4J please send me a test case at [email protected]
thanks
Debu

Hot deploy Servlet in webapp

Can I hot deploy a servlet within a web application ?How should I do it?
          (When I compile my servlet into MyApp/web-inf/classes,user this URI -
          http://localhost:7001/MyApp/mypackage.myclass to invocate it ,It does not
          work correctly(error 404))


Hi,
          If I use weblogic.servlet.ServletServlet to try just the servlet , It
          works correctly.But When I develop it in a web application , there is a lot
          of hypelink to this servlet,thus I can't use the relative path reference to
          that servlet.I try to set the name of weblogic.servlet.ServletServlet same
          as the webapp,It doesn't work,how do I solve this problem?
          Thank you
          Pan
          Subject: Re: Hot deploy Servlet in webapp
          > http://www.weblogic.com/docs51/classdocs/API_servlet.html#134798
          >
          > It even explains why you shouldn't use it in production environment.
          >
          > Dimitri

Hot deployment not playing along with coherence-tx.rar

I would like to setup my application so that the coherence and tangosol jars are owned by the application. Under this setup it will aid in hot deployment so that the coherence classloader is destroyed along with the application. Using the transaction services requires that I put the tangosol and coherence jars on the boot classpath of weblogic. I could live with this if there is an easy way to tell coherence to clear all caches that I can call from a startup servlet when my application redeploys.
     Is there some other way of setting this up so that hot deployments destroy all caches and coherence-tx.rar can still be utilized?

In a development environment where classes can change structure it is more semantically correct to destroy all references to the old class structure otherwise you get IncompatibleClassChangeErrors.
     It is also more convenient for us to deploy the application without any external references. It makes setting up a QA server much easier, for example, if we don't have to install coherence and modify classpaths to get it up.
     There is nothing special about the architecture just a standard EAR deployment with all 3rdparty classes packaged into the EAR.

Collaborative Development / Hot Deployment?

Similar Messages

Maybe you are looking for