Exploded format deployment

Hi,
I am looking into the weblogic documentation here where it says:
http://e-docs.bea.com/wls/docs81/webapp/deployment.html#158848
"You can redeploy a Web application deployed in exploded directory format when using auto-deployment by modifying a special file called REDEPLOY. You can also cause a partial redeploy by copying a new version of a class file over an old in the WEB-INF/classes directory."
The last statement regarding partial redeploy by copying a new version of classfile, Does weblogic poll for changes in classfile timestamps?
If so, what attribute would control this?
(I am referring to regular java class (not servlet-reloadxxx))
Thanks,
Vijay

Hi,
Yes this is possible in WLW8.1Sp2.
Few things to consider for the exploded directory structure to work
1) The top level directory should always be named with a .ear extension
For ex: if you applicatio name is sampleApp
then the toplevel directory should be "sampleApp.ear"
2) You could either create an ear and just unzip it in the production environment
thereby preserving the extension
or
3) You could build the application and copy it into production environment and
rename the top level directory with a .ear extension. Just make sure you don't
have any project folders in your application folder which is not part of the application.
The need for the directory to have a ".ear" is a requirement with the way Workshop
is designed as of now.
Let me know if you have further questions.
Thanks a lot,
Vimala
"garbl" <[email protected]> wrote:
>
Hy ,
id there a way to build a deployable ear in exploded format fully compatible
with
ear standards? I mean creating a true ear structure (no split directory
!) without
archiving everything in an .ear?
We need being able to keep an exploded structure in prod environment
in order
to be able to keep on using app configuration via property / xml files
thanks

Similar Messages

  • Deploying web application in OAS Release 3 (10.1.3.1.0) in exploded format

    How to deploy a web application in exploded format in OAS server.

    Refer these:
    http://download.oracle.com/docs/cd/B31017_01/web.1013/b28221/depapp003.htm#JIEJB00906
    http://download.oracle.com/docs/cd/B31017_01/migrate.1013/b31269/servlets_weblogic.htm#i1018012
    Thanks
    Shail

  • Bug in deploying in exploded format

              when i deploy my whole application in exploded format..the welcome page is not
              picking up from the web.xml file.is it a bug? if anybody knows,i would be appreciated
              if you reply me soon
              thanks
              Seri
              

    [att1.html]
              

  • Deploying Weblogic 8 EAR in exploded format

    Hello,
    Sorry, was lil away from WLS...
    Is there a way I can deploy EAR in the exploded directory structure which means all the WARs included in
    the EAR also need to be in exploded structure.
    Thanks

    I'm not sure I understand exactly what you want to know.
    You can deploy applications via the WebLogic Console, the command-line
    utility weblogic.Deployer, or the ant-task wldeploy.
    Any of these should work fine with an exploded ear.
    -- Rob
    A B wrote:
    Sorry Rob, I did not see the answer..
    What do I need to do to deploy WLS8 ear in exploded format?
    Thanks

  • Deploying Enterprise application in exploded format

    ewsgroup: to weblogic.developer.interest.webserver
    For simplification and to make changes easier
    we want to deploy our EJB's
    and web application in exploded format.
    I created the following directory structure
    in my home area:
    Application/
    deploy/
    META-INF/
    application.xml
    web/
    jsps, html
    WEB-INF/
    *.xml
    classes/
    servlet
    .class files
    lib/
    ejb/
    META-INF/
    *.xml
    com/ .... directory
    structure for EJB.
    I deployed the application using the admin
    console and referencing
    myhome/application/deploy. This results in
    the following error in the log:
    <Dec 18, 2001 5:25:46 PM MST> <Error> <HTTP>
    <[web] Error reading
    Web application "/myhome/application/deploy/web"
    java.net.ConnectException: Tried all: '1' addresses,
    but could not connect
    over HTTP to server : 'java.sun.com', port:
    '80'
    None of my WLS servers are configured to use
    port 80. This particular
    server is configured to listen on port 7009.
    Any help or insight would be greatly appreciated.

    I think I ran into the same problem with using the localhost address on our
    application. Are you using the ip of one of your managed servers?
    Are you upgrading or using WLS 6.1 SP1 ..by the way?
    "Terry Jahelka" <[email protected]> wrote in message
    news:3c20c99e$[email protected]..
    >
    For simplification and to make changes easier we want to deploy our EJB'sand web
    application
    in exploded format.
    I created the following directory structure in my home area:
    Application/
    deploy/
    META-INF/
    application.xml
    web/
    jsps, html
    WEB-INF/
    *.xml
    classes/
    servlet .class files
    lib/
    ejb/
    META-INF/
    *.xml
    com/ .... directory structure for EJB.
    I deployed the application using the admin console and referencingmyhome/application/deploy.
    This results in the following error in the log:
    <Dec 18, 2001 5:25:46 PM MST> <Error> <HTTP> <[web] Error reading Webapplication
    "/myhome/application/deploy/web"
    java.net.ConnectException: Tried all: '1' addresses, but could not connectover
    HTTP to server
    : 'java.sun.com', port: '80'
    None of my WLS servers are configured to use port 80. This particularserver
    is configured
    to listen on port 7009.
    Any help or insight would be greatly appreciated.

  • Deploying application in Exploded format

    For simplification and to make changes easier we want to deploy our EJB's and web
    application
    in exploded format.
    I created the following directory structure in my home area:
    Application/
    deploy/
    META-INF/
    application.xml
    web/
    jsps, html
    WEB-INF/
    *.xml
    classes/
    servlet .class files
    lib/
    ejb/
    META-INF/
    *.xml
    com/ .... directory structure for EJB.
    I deployed the application using the admin console and referencing myhome/application/deploy.
    This results in the following error in the log:
    <Dec 18, 2001 5:25:46 PM MST> <Error> <HTTP> <[web] Error reading Web application
    "/myhome/application/deploy/web"
    java.net.ConnectException: Tried all: '1' addresses, but could not connect over
    HTTP to server
    : 'java.sun.com', port: '80'
    None of my WLS servers are configured to use port 80. This particular server
    is configured
    to listen on port 7009.
    Any help or insight would be greatly appreciated.

    I think I ran into the same problem with using the localhost address on our
    application. Are you using the ip of one of your managed servers?
    Are you upgrading or using WLS 6.1 SP1 ..by the way?
    "Terry Jahelka" <[email protected]> wrote in message
    news:3c20c99e$[email protected]..
    >
    For simplification and to make changes easier we want to deploy our EJB'sand web
    application
    in exploded format.
    I created the following directory structure in my home area:
    Application/
    deploy/
    META-INF/
    application.xml
    web/
    jsps, html
    WEB-INF/
    *.xml
    classes/
    servlet .class files
    lib/
    ejb/
    META-INF/
    *.xml
    com/ .... directory structure for EJB.
    I deployed the application using the admin console and referencingmyhome/application/deploy.
    This results in the following error in the log:
    <Dec 18, 2001 5:25:46 PM MST> <Error> <HTTP> <[web] Error reading Webapplication
    "/myhome/application/deploy/web"
    java.net.ConnectException: Tried all: '1' addresses, but could not connectover
    HTTP to server
    : 'java.sun.com', port: '80'
    None of my WLS servers are configured to use port 80. This particularserver
    is configured
    to listen on port 7009.
    Any help or insight would be greatly appreciated.

  • What is deployment in Exploded Format means??

    What is deployment in Exploded Format means??

    > Like rain on your wedding day?
    Exactly. Like a free ride, when you've already paid.
    > Hey Steve. Long time no see... :) Next time
    I'll try the beer, too.
    I hope "next time" isn't too far off. I'm telling
    you, I'll have to plan a trip to France sometime
    soon... :o) Nice pictures, by the way.Scheduled so far is 2008. I'd be more than happy to welcome you here. The border isn't far away from my place, we could go and have some German beer, too. :) And thanks. Did I mention that you don't look at all like the pic on your blog?

  • Hot swap and JSP debugging for Weblogic in exploded format?

    Hi,
    I'm trying to use JDeveloper for JSF development to be deployed to a weblogic server.
    I must say JDeveloper is a great tool for JSF development as none of the free IDE in the market can do what JDeveloper does.
    However, I have a question on hot swap and JSP debugging.
    I have managed to setup JDeveloper to debug my JSF application deploy to my Weblogic server's applications folder in exploded format.
    I can step through the java code.
    However, I didn't manage to do a hot swap and the break point set in the JSF-JSP does not seems to take effect.
    I would appreciate any advice on the problem.
    Thanks.
    Han Ming

    How did you setup the server to handle exploded format? Appreciate the help. Sorry can't help with your question though.
    Thnx.
    Soni

  • J2ee application in  exploded format in oracle 10g

    sorry: folder structure is like this:
    test_app
    --META-INF
    -----application.xml     
    --test_web
    -----pages
    -------welcome.jsp
    -----WEB-INF
    -------web.xml
    -------lib
    -------src     
    Regards,
    Roopa.
    Message was edited by:
    user447401

    Roopa, it looks like there is no problem with the deployment of your application in exploded format. Have you accessed http://server-ipaddress:7778/test_app/pages/welcome.jsp? Any problem access http://server-ipaddress:7778/j2ee/, the default home page of the default-web-app ?
    When you say the url http://server-ipaddress:7778/test_app is not working, what is the error message if any on the browser, on server console, in the server.log and http-web-access.log of ORACLE_HOME/j2ee/home/log/, ORACLE_HOME/j2ee/home/application-deployments/test_app/application.log?

  • J2ee Web application exploded format in oracle 10g

    Hi,
    I am trying to develop a simple j2ee application in Exploded Format
    in oracle 10g AS. i have created a new OC4J instance called
    TestOC4j for this. A .war file works fine in this instance.
    I have placed the application under applications directory of TestOC4j.
    I have made entries in server.xml, oc4j_mod.conf,
    default-web-site.xml,http-web-site.xml and application.xml in META-INF
    of the application.
    The application get deployed with no errors.gets created in
    application-deployments too.
    But the url http://server-ipaddress:7778/test_app is not working.
    Please help.
    The folder struture is as follows:
    test_app
    --META-INF
    -----application.xml
    --test_web
    -----pages
    -------welcome.jsp
    -----WEB-INF
    -------web.xml
    -------lib
    -------src
    The entries in server.xml is as follows:
    <application name="test_app" path="../applications/test_app" auto-start="true" />
    <web-site path="./http-web-site.xml" />
    The entries in application.xml is as follows :
    <module>
    <web>
    <web-uri>test_web</web-uri>
    <context-root>/test_app</context-root>
    </web>
    </module>
    The entries in default-web-site.xml is as follows:
    <web-app application="test_app" name="test_web" load-on-startup="true" root="/test_app" />
    The entries in http-web-site.xml is as follows:
    <web-app application="test_app" name="test_web" load-on-startup="true" root="/test_app" />
    The entries in oc4j_mod.conf is as follows:
    Oc4jMount /test_app TestOC4j
    Oc4jMount /test_app/* TestOC4j
    Regards,
    Roopa

    Roopa, it looks like there is no problem with the deployment of your application in exploded format. Have you accessed http://server-ipaddress:7778/test_app/pages/welcome.jsp? Any problem access http://server-ipaddress:7778/j2ee/, the default home page of the default-web-app ?
    When you say the url http://server-ipaddress:7778/test_app is not working, what is the error message if any on the browser, on server console, in the server.log and http-web-access.log of ORACLE_HOME/j2ee/home/log/, ORACLE_HOME/j2ee/home/application-deployments/test_app/application.log?

  • How to archive an exploded format into EAR

    Hi all,
    I have my application in the following exploded format:
    c:\bea\...\mydomain\applications\MyApplication
    MyApplication
    \ejb
    \mypackage\....
    \META-INF\ejb-jar.xml, weblogic-...........
    \META-INF\application.cml, weblogic-application.xml
    \web
    \folder1\*.jsp
    \folder2\*.jsp
    \WEB-INF\web.xml
    \WEB-INF\lib\*.jar
    \WEB-INF\tld\*.tld
    \WEB-INF\classes\mypackage1\*.java
    Now, anyone please tell me how to package the above exploded format into .jar
    and war and finally the EAR.
    and also, after deploying the EAR, how can we access the application?
    Thanks in Advance,
    Seshu

    The bottom line is you should use ant.
    If your using a version prior to 8.1 you can use the built in jar/ear tasks,
    if you cant upgrade to 8.1 I reccomend it.
    If your using 8.1 we have an exploded directory structure for development
    known as split-dir (go to http://edocs.bea.com and search) with a set of ant
    tasks to do compilation and deployment. There is also one called wlpackage
    that will create an archived EAR for you as well.
    The basic principle is that in development you want to develop with an
    exploded format as it is much faster to compile and to deploy. When moving
    to production and for distribution you want an archive. You have a couple of
    options for the archive. You can archive EVERYTHING where each module
    inside of the ear is also archived.
    Such as:
    foo.ear
    META-INF/applicaiton.xml
    web.war
    ejb.jar
    I am not a huge fan of this because in development you really want
    everything exploded and if you archive your modules inside the ear you have
    to change the URI's in your applicaiton.xml. I prefer:
    foo.ear
    META-INF/applicaiton.xml
    web/
    WEB-INF/web.xml
    ejb/
    META-INF/ejb-jar.xml
    This is the format of the ear that wlpacage ant task creates for you.
    Cheers
    mbg
    "Seshagiri" <[email protected]> wrote in message
    news:3f08c9ea$[email protected]..
    >
    Hi all,
    I have my application in the following exploded format:
    c:\bea\...\mydomain\applications\MyApplication
    MyApplication
    \ejb
    \mypackage\....
    \META-INF\ejb-jar.xml, weblogic-...........
    \META-INF\application.cml, weblogic-application.xml
    \web
    \folder1\*.jsp
    \folder2\*.jsp
    \WEB-INF\web.xml
    \WEB-INF\lib\*.jar
    \WEB-INF\tld\*.tld
    \WEB-INF\classes\mypackage1\*.java
    Now, anyone please tell me how to package the above exploded format into.jar
    and war and finally the EAR.
    and also, after deploying the EAR, how can we access the application?
    Thanks in Advance,
    Seshu

  • Read XML file in WEB-INF works in exploded format but fails in EAR

    I'm able to read an XML file stored in the WEB-INF when my application is deployed in the exploded format, but when its deployed in an EAR, the reading fails.
              I read from forums that getRealPath could fail, so I added in the getResourceAsStream to fall back on. But in the EAR format, both fails.
              What did I miss out?
              Here's my codes:
                          StringBuffer configFileName = new StringBuffer();
                configFileName.append(File.separatorChar).append("WEB-INF");
                configFileName.append(File.separatorChar).append("app-config.xml");
                String fileName = getServletContext().getRealPath(configFileName.toString());
                if (fileName == null) {
                  request.setAttribute("efs/xmlmappings-is", getServletContext().getResourceAsStream(configFileName.toString()));
                } else {
                  request.setAttribute("efs/xmlmappings-str", fileName);
              

    Hi          > Thread.currentThread().getContextClassLoader().getReso
              > urceAsStream()
              >
              > getClass().getClassLoader().getResourceAsStream()
              > should also work
              > if the file is in WEB-INF/classes
              >
              > regards
              > deepak
              It works, thanks!

  • Redeploy precompiled JSPs to managed server in exploded format without incurring a JSP recompile

         How do you redeploy precompiled JSPs to a managed server in exploded format without
    incurring a JSP recompile?
         Our application is deployed in Two Phase, Stage mode, Exploded Format. We regularly
    update JSPs on our Production application and would like to be able to redeploy
    JSPs without incurring the JSP recompile. I am able to precompile JSPs and redeploy
    the JSP and compiled JSP to the managed server, but the updated page is still
    recompiled.
         I've searched the BEA site, newsgroups, and web and still need some help.
         Additional information:
         - precompile in web.xml is false. we'd prefer not to precompile all the jsps
    at startup to minimize Production downtimes when deploying new major releases
         - the compiled JSPs reside in ~/classes/jsp_servlet and not ~/WEB-INF/classes/jsp_servlet
         - our directory structure looks like:
              ~/app
                   /META-INF
                   /WEB-INF
                   /classes ( compiled source )
                        /hotwire ( java class files )
                        /jsp_servlet ( compiled jsps )
              ~/deploy ( property files )
                   /prod
                        /web.xml
                        /weblogic.xml
              ~/src ( java files )
                   hotwire/
         I found this information on the BEA newsgroup ( http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=582&utag=
    ) regarding the _isStale() method for compiled JSPs, but wasn't able to get it
    to work when the file was in the exact same path ( note: compilation occurred
    on a different machine than the managed view server )
         Do we have to store our compiled JSP files under /WEB-INF/classes for this feature
    to work and in a WAR?
         What am I missing?
         Regards,
              Paul

    Hi Mark,
    Thank you for replying and logging the CR. I've read lots of your posts in researching
    this issue and was hoping you'd reply.
    I used the JSP Precompile Validation Utility ( http://dev2dev.bea.com/resourcelibrary/utilitiestools/adminmgmt.jsp
    ) and tested against WLS8.1sp2 and agree with your assessment. The JSP Time utility
    indicates that the JSP and compiled class are in agreement, yet the server always
    recompiled the JSP after I redeployed that particular file and class. I opened
    Case Ticket #: 473459 that includes a test script, output, and lots of information.
    It's currently being investigated. I'll inform the BEA Relations engineer and
    add my name to the CR you opened.
    Dynamic content updates without recompiles is something we'd really like to be
    able to do. We are hoping to be able to do specific frequent content updates
    in the afternoon as opposed to 1:00 AM :)
    Thanks again,
    Paul
    JSP TIME TOOL:
    Summary
    ====================
    Total JSP Files: 1
    Total JSP that will compile in server because of missing _staticIsStale method:....
    0
    Total JSP that will compile in server because of wrong weblogic version:...........
    0
    Total JSP that will compile in server because jsp is newer than parse date:........
    0
    Total JSP that will compile in server because missing class:.......................
    0
    REDEPLOY COMMAND:
    $JAVA weblogic.Deployer -adminurl t3://localhost:7004 -user <username> -password
    <password> -name phoenixApp -targets phoenixViewWebApp@wlview1 -redeploy web/jsp/customer-care/indexMain.jsp
    WEB-INF/classes/jsp_servlet/_web/_jsp/_customer_45_care/__indexmain.jsp
    WEBLOGIC LOG:
    ####<Jan 13, 2004 3:33:04 PM PST> <Info> <Deployer> <ppjsp01> <wlview1> <ExecuteThread:
    '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module
    phoenixViewWebApp of application phoenixApp is transitioning from active to prepared
    on server wlview1.>
    ####<Jan 13, 2004 3:33:04 PM PST> <Info> <Deployer> <ppjsp01> <wlview1> <ExecuteThread:
    '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149060> <Module
    phoenixViewWebApp of application phoenixApp successfully transitioned from active
    to prepared on server wlview1.>
    ####<Jan 13, 2004 3:33:05 PM PST> <Info> <Deployer> <ppjsp01> <wlview1> <ExecuteThread:
    '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module
    phoenixViewWebApp of application phoenixApp is transitioning from prepared to
    active on server wlview1.>
    ####<Jan 13, 2004 3:33:05 PM PST> <Info> <Deployer> <ppjsp01> <wlview1> <ExecuteThread:
    '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149060> <Module
    phoenixViewWebApp of application phoenixApp successfully transitioned from prepared
    to active on server wlview1.>
    ####<Jan 13, 2004 3:38:13 PM PST> <Info> <HTTP> <ppjsp01> <wlview1> <ExecuteThread:
    '119' for queue: 'default'> <<anonymous>> <> <BEA-101295> <Recompiling JSP [ServletContext(id=31702491,name=phoenixViewWebApp,context-path=)],
    resource [web/jsp/customer-care/indexMain.jsp], because it is stale. It was previously
    compiled using a different version of WebLogic Server.
    JSP build version: 8.1.2.0
    WLS build version: 8.1.2.0.>
    ####<Jan 13, 2004 3:38:13 PM PST> <Info> <HTTP> <ppjsp01> <wlview1> <ExecuteThread:
    '119' for queue: 'default'> <<anonymous>> <> <BEA-101047> <[ServletContext(id=31702491,name=phoenixViewWebApp,context-path=)]
    Generated java file: /opt/p4/phoenix/6.2/app/WEB-INF/classes/jsp_servlet/_web/_jsp/_customer_45_care/__indexmain.java>
    "Mark Griffith" <[email protected]> wrote:
    So this is a scenario that we should support Paul.
    There are a couple of issues.
    1) I dont think our weblogic.Deployer api currently does a very good
    job of
    this at all, since it is MOSTLY concerned with redeployment of applications
    and modules, and in this scenario you dont want app redpeloyment you
    just
    want what are essentially content files distributed. In otherwords the
    api
    I worry wont help you distributing files for this case, at least in this
    current release and SP.
    2) once you get the files to the location, things should in the servlet
    containers.
    Having said that it is easier if you are able to have the application's
    deployed with -no-stage, or no-copying, or shared application, that way
    you
    have one location to copy files to vs. many stage dirs. Either way you'll
    have to copy the jsp's and the classfiles to the webapp directories.
    Additionally I just tried this on 8.1. sp2 and the stale-check by the
    servlet container is busted. :( I opened a bug on this: CR133453.
    Not
    sure if this is in sp1 or not, didnt have time to check it. I suggest
    you
    contact support and get your name added to this CR to raise its priority.
    Cheers
    mbg

  • Help redeploying an application in exploded format

    Hi,
    I am trying to redeploy my application that has been deployed in exploded
    format,
    but it doesn't seem to be working.
    I am following the steps presented in the Admin guide as follows:
    1. I have an empty file named REDEPLOY in the directory where my exploded
    application resides.
    2. I make my changes to my application & compile. The .class files end up
    in a different folder than
    my exploded deployment directory.
    3. I copy the updated .class files to the exploded deployment directory.
    4. Touch the REDEPLOY file to update its timestamp.
    But my new changes are not seen. (Of course they are seen if I restart the
    server).
    My environment is W2K; WL6.1, SP1.
    Any ideas?
    Thanks,
    Beth

    The REDEPLOY file is inside the WEB-INF directory and we still couldn't get
    it to work.
    Our Web Application resides outside the Weblogic Home directory and we are
    compiling
    directly into this directory now (the original message stated we were
    compiling to a different
    directory, then copying the .class files).
    We were able to get the hot redeploy working by using the Weblogic Console
    and unchecking &
    rechecking the check box that said whether or not the application was
    deployed- the current environment
    that this is working is WL6.1 (we backed out the Service Pack for a
    different reason). We did
    find that we do need to shut down any existing browser sessions; but as long
    as we start a new browser
    session we don't need to restart the WL server and all the new changes are
    picked up.
    Even though the hot redeploy is working for us without touching the REDEPLOY
    file, I'm
    still curious if we are missing something here about how this works. If
    anyone has any ideas,
    I'd like to hear them.
    Thanks,
    Beth
    "Mihir Kulkarni" <[email protected]> wrote in message
    news:[email protected]..
    The REDEPLOY file should be inside the WEB-INF directory of the exploded
    webapp.
    http://e-docs.bea.com/wls/docs61////webapp/deployment.html#138990
    - mihir
    Beth wrote:
    Hi,
    I am trying to redeploy my application that has been deployed in
    exploded
    format,
    but it doesn't seem to be working.
    I am following the steps presented in the Admin guide as follows:
    1. I have an empty file named REDEPLOY in the directory where myexploded
    application resides.
    2. I make my changes to my application & compile. The .class files endup
    in a different folder than
    my exploded deployment directory.
    3. I copy the updated .class files to the exploded deploymentdirectory.
    4. Touch the REDEPLOY file to update its timestamp.
    But my new changes are not seen. (Of course they are seen if I restartthe
    server).
    My environment is W2K; WL6.1, SP1.
    Any ideas?
    Thanks,
    Beth

  • Exploded EAR deployment supported?

    Hi,
    I am currently developing with the MyEclipse IDE. Does Sun Java Studio Enterprise 8.1 support exploded deployment of EARs, and can it 'hot deploy' changes into the running Application Server?
    Thank You

    Hi.
    SJSE 8.1 doesn't support exploded deployment of EAR projects. It currently supports exploded deployment of WAR projects.
    I know that folks have extended NetBeans to support exploded EAR deployment in NB 6.0...
    You can find out more about that in this blog entry and screencast:
    http://blogs.sun.com/vkraemer/entry/new_glassfish_integration_feature_directory
    http://serverplugins.netbeans.org/screencasts/pfsc1.html
    Can you clarify what you mean by 'hot deploy'? Different folks have different definitions of this phrase... I think SJSE 8.1 does 'hot deploy' as I understand it... but my understanding may not match your vision of this feature...
    vbk

Maybe you are looking for