Documentation on exploded deployment?

Hello all,
I am having trouble finding documentation on how to deploy a exploded war file. I read on theserverside that sunone 7 supports it and requires some directory naming conventions to make it work. Could someone point me in the right direction?
Regards,
Joshua

I did not get the meaning of exploded war file. Do you want to deploy a war file from a directory? If that is so, then the doc gives the directory structure for the
hello/ and convertor _1/. You can deploy the directory in S1AS from command line (asadmin) by following command
asadmin deploy --user admin_user [--password admin_password] [--passwordfile password_file] host hostname port adminport [--secure | -s] [--virtualservers virtual_servers] [--type application|ejb|web|connector] [--contextroot contextroot] [--force=true] [--precompilejsp=false] [--verify=false] [--name component_name] [--upload=true] [--retrieve local_dirpath] [--instance instance_name] filepath

Similar Messages

  • Exploded deployment

    Folks:
    We have the option for exploded deployment in Tomcat and Oracle appservers wherein i can have the files on the filesystem in J2EE webmodule format, i.e., WEB-INF/lib, WEB-INF/classes, etc. I can then mention in my appserver config to pick up my webmodule content from the filesystem. We already worked with this option in oc4j for our app.
    Is there a similar option in Websphere? I need to be able to point to a directory on the filesystem from the server config and ask it to consider it as my webapp content, instead of the standard procedure of WAR deployment from console/automation interfaces.
    Thanks.

    Hi Carlos,
    Ever find out how to do exploded deployment in 10.1.3?
    Thanks,
    Avi.

  • Exploded deployment doesn't work in Weblogic 8.1

    Hi
    I have a very weird problem. I am trying to deploy my apllication in Weblogic
    8.1 in exploded format.Well problem is when i deploy it ,on server startup Weblogic
    doesn't deploy it automatically way its mentioned in the release.txt and also
    way it used to do in WLC 6.1.Also when i deploy it using the console i cannot
    get the updated version of my jsp. I have double cked set STARTMODE= false so
    its in development mode.I also noticed the various forms of deployment in WLC
    8.1 nostage,stage...-
    Is there anything i am forgetting.
    Thanks
    Maulik

    Can you show me the server log, the contents of your applications
    directory, and your config.xml?
    If not, you probably should just open a case with [email protected]
    -- Rob
    MAULIK SHAH wrote:
    Yes Rob exactly the same was as its mentioned in WLS.
    Rob Woollen <[email protected]> wrote:
    how are you deploying it? via the applications directory?
    -- Rob
    MAULIK SHAH wrote:
    Hi
    I have a very weird problem. I am trying to deploy my apllication inWeblogic
    8.1 in exploded format.Well problem is when i deploy it ,on serverstartup Weblogic
    doesn't deploy it automatically way its mentioned in the release.txtand also
    way it used to do in WLC 6.1.Also when i deploy it using the consolei cannot
    get the updated version of my jsp. I have double cked set STARTMODE=false so
    its in development mode.I also noticed the various forms of deploymentin WLC
    8.1 nostage,stage...-
    Is there anything i am forgetting.
    Thanks
    Maulik

  • Deserializing exceptions in exploded deployment

    Hi,
    I've got an application exception named "EPCException" that extends java.lang.Exception that I throw from a stateless session bean and catch in a servlet. My application is deployed on WebLogic 6.1sp4/jdk131 in exploded format for both the web app and ejbs. That is, neither the web or ejb components are packaged in archives (war and jar respectively).
    For some reason the state in EPCException (e.g., error code attribute) is not being preserved when the exception is deserialized in the web app and caught in the servlet. The state of the EPCException is that of the default
    To be sure, I log the state of EPCException before I throw the exception in the ejb and after I catch the exception in the servlet and they do not match.
    When I deploy the application as an ear file (no rmi calls, thus no [de]serialization) everything is fine with the state of the EPCException.
    Does RMI treat exception [de]serialization differently than normal serializable objects returned by remote method calls?
    Any help would be appreciated.
    Cheers,
    Scott

    Are you sure the timestamps on the JSP files are not modified by the build process?
              If you compile the files into a destination dir say "bar/WEB-INF/classes" and then copy all the jsp files (w/o preserving the timestamps) to /bar which is then deployed. In this case all the JSPs will be recompiled since the class files contain the timestamp of the original JSP it was compiled against.
              check out http://dev2dev.bea.com/pub/a/2005/01/jsp_reloaded.html which describes a bit about the jsp compilation process

  • Precompiled JSP's in exploded deployment

    We have several applications run in WLS 8.1 SP4 where we have chosen to precompile all JSP pages and package them in the WAR/EAR files. This
              has shortened the time of our deployment imensely, when we deploy the apps in archived format.
              However, we somethimes need to deploy the apps using an exploded format. The server compiles the JSP's even if we deliver an exact copy of what we have in our WAR/EAR-files. Having read postings of problems with this
              in previous versions of Weblogic, I'm curious to know if we are just doing things wrong, or if this is still an issue?
              Thankful for any information about this issue!
              Regards,
              /Eje Thorarinsson

    Are you sure the timestamps on the JSP files are not modified by the build process?
              If you compile the files into a destination dir say "bar/WEB-INF/classes" and then copy all the jsp files (w/o preserving the timestamps) to /bar which is then deployed. In this case all the JSPs will be recompiled since the class files contain the timestamp of the original JSP it was compiled against.
              check out http://dev2dev.bea.com/pub/a/2005/01/jsp_reloaded.html which describes a bit about the jsp compilation process

  • ADF application to be deployed in exploded mode in weblogic

    How can we deploy the ADF Application (EAR) in exploded mode in weblogic server?
    i.e I have ADF based application named Application.EAR. How can i deploy it in exploded mode?
    Thanks in advance,
    Navaneeth

    As far as WebLogic is concerned, we take a standard Java EE deployment module, in either archived or exploded form and deploy it. You point the deployment utility (or the console, or the ant tasks or the Maven plugin) at the source of the deployment and WLS will deploy it.
    There's nothing specific in what WLS requires for exploded deployment, so this is likely to be more a question specific to ADF as to how it is packaged and able to be deployed. I'd post your question to the ADF/JDeveloper forum to ask those folks specifically.
    -steve-

  • JSF 1.2 app is deployed only in exploded archive mode if JSF 2.0 facet used

    Hi.
    I'm developing JSF 1.2 + facelets application. The only way to configure eclipse WTP editors to properly handle xhtml pages is to install JSF 2.0 facet (there was facelets plugin before, but it was superseded by JSF 2.0 facet if I'm not mistaken). When application is deployed on WL, OEPE show message that JSF 2.0 applications can be deployed only in exploded archive mode.
    Is there any way to make OEPE to believe that this application is based on JSF 1.2 (as really is)?
    Regards,
    Vadim.

    Hi, Ian.
    You are stating that it's a JSF 2.0 app by selecting that facet - the tooling relies on your facet selection to determine what features are available.Thought as much. Determining which JSF implementation will be active at deployment time looks like very complicated task and facet version is a reliable source of such kind info. Sadly :)
    What "eclipse WTP editors" are you trying to configure?"HTML editor". Without JSF 2.0 facet it doesn't handle JSF taglibs' namespaces and EL expressions content assist/navigation.
    The other option is to install JBoss Tools richfaces support, but for various reasons I'd like not to.
    After using exploded deployment for a week now I see that it is not that slow as I initially thought (at least for a small project): JSP/XHTML changes picked up, class methods reloaded. Manual republishing is still not as fast as in case of the splitsource deployment, but it don't call it often.
    Thanks.
    Edited by: user3269289 on Apr 8, 2011 2:34 AM

  • 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

  • Deploy exploded WAR file

    Hello!
    I need to deploy a war file extracted into a custom folder. Is it possible in WEB AS to point the deployment to a particular folder of our choice instead of deploying the WAR/EAR file?
    Thanks
    /Ray

    Hi Ray,
    applications on Web AS are deployed in the database, and the corresponding binaries are synchronized to the file system from the DB. Hence, you cannot point the deployment to a custom directory.
    Anyway, why do you need that? Usually, exploded deployment is needed for development environment for the sake of quick update of the changed files? Is that your requirement also? If so, you could try using the Single File Update function of the Web AS Deploy service to update single files in your application. For details, see Deploying exploded EAR in WAS 6.40 thread.
    Hope that helps a bit.

  • Re: Exploded directory format in an EAR

              I am now trying to deploy the ear file in v6.1 sp2. Has anyone managed to deploy
              an ear where util / third party classes are stored in a lib directory of the ear
              and referenced in EJB-jar manifest.mf files using the classpath header?
              ie as documented in bea weblogic server bible on page 614/615
              EntApp/
              accountEJB.jar
              accountManager.war
              /lib/
              xerces.jar
              xalan.jar
              log4j.jar
              /META-INF/
              application.xml
              "erik" <[email protected]> wrote:
              >
              >This is hearsay but I was recommended to use v 6.1 SP 2.
              >/erik
              >
              >"Ivan" <[email protected]> wrote:
              >>
              >>I have a problem wrapping up an exploded directory format application
              >>into an ear
              >>file running weblogic 6.0sp2 on winnt 4. One of the things I would like
              >>to do
              >>is load a config file from a helper class without specifying a path.
              >>
              >>
              >>EAR APP statementapp.ear contains: META-INF/MANIFEST.MF statement.jar
              >>statementwebapp.war
              >>META-INF/application.xml lib/log4j.jar (and other third party jar files
              >>crimson.jar,
              >>jaxp.jar etc.)
              >>
              >>The third party jar files have been manually unjar'ed and re-jar'ed
              >without
              >>compression
              >>(after reading that a suggestion to someone else).
              >>
              >>WEB APP statementwebapp.war contains: all my jsp's at root level WEB-INF/classes/uk/.../servlets
              >>- servlets WEB-INF/classes/uk/.../util - helper classes WEB-INF/tlds
              >>- tag library
              >>descriptors WEB-INF/web.xml & weblogic.xml - deployment descriptors
              >
              >>
              >>Some of the helper classes make use of configuration files (for example
              >>I have
              >>a Logger class that uses Log4j). Here is how I would like to access
              >the
              >>config
              >>file
              >>
              >>... private static final String config = "config.properties" ; PropertyConfigurator.configure(
              >>config ) ; ...
              >>
              >>I have tried putting the config.properties file in the WEB-INF/classes
              >>directory
              >>and in the WEB-INF directory, however they don't seem to be found by
              >>the class
              >>loader.
              >>
              >>EJB statement.jar contains an ejb with the following: uk...business.statement...
              >>- Statement ejb classes with ejbc generated stub and skeleton classes
              >>uk...util
              >>- Several Helper classes
              >>
              >>One such helper is Logger for which the Log4j jar file is needed. I
              >deploy
              >>the
              >>statement.jar file in the ear (as listed above). Weblogic throws an
              >error
              >>message
              >>saying cannot deploy statement (NoClassDefFound...): java.lang.NoClassDefFoundError:
              >>org/apache/log4j/Category ie it cannot find the log4j package which
              >is
              >>referenced
              >>in the Class-Path header of the manifest.mf file and located in the
              >ear
              >>file under
              >>the lib directory.
              >>
              >>The manifest.mf file contains a line with the following: Class-Path:
              >>lib/log4j.jar
              >>lib/crimson.jar lib/jaxp.jar which I have read should allow the enterprise
              >>classloader
              >>to pick up the log4j.jar and xml parsing classes (ref. weblogic server
              >>bible chap
              >>18) without needing to be referenced in the weblogic start up class
              >path.
              >>
              >>
              >>Can manifest class-path references be used like this in weblogic 6.0?
              >>Where should
              >>I put the application properties files in the war and jar files?
              >>
              >>Clarification much appreciated. Ivan.
              >>
              >>PS: I had this application working in exploded directory format with
              >>the jar files
              >>in the system classpath and the properties file locations hardcoded
              >in
              >>the class
              >>files. (not ideal for a clustered production environment!)
              >>
              >
              

              This is hearsay again.
              These people did as you did no compression etc. they were able to put the application's
              utility classes in a lib but not the third party jars. They suspected that the
              ear where to big to deploy so they put all thirdparty jars in the system classpath
              and then the internal utility classes were loaded by using CLASSPATH in the manifest
              file.
              I gave up because I could deploy everything except servlets and I went back to
              exploded deployment. That bloody EAR thing took to much time.
              If you succeed in everything including warfiles with JSPs and servlets (those
              I was talking about only had EJBs)
              let me know.
              I also had a peculiar problem with EARs that a cascading stylesheet was not found
              in the ear but it worked in an exploded it worked fine
              Otherwise I must recommend Orion, which I had up and running in a matter of days
              when ported from WLS 5.1.
              Good luck.
              "Ivan" <[email protected]> wrote:
              >
              >I am now trying to deploy the ear file in v6.1 sp2. Has anyone managed
              >to deploy
              >an ear where util / third party classes are stored in a lib directory
              >of the ear
              >and referenced in EJB-jar manifest.mf files using the classpath header?
              >
              >ie as documented in bea weblogic server bible on page 614/615
              >EntApp/
              > accountEJB.jar
              > accountManager.war
              > /lib/
              > xerces.jar
              > xalan.jar
              > log4j.jar
              > /META-INF/
              > application.xml
              >
              >"erik" <[email protected]> wrote:
              >>
              >>This is hearsay but I was recommended to use v 6.1 SP 2.
              >>/erik
              >>
              >>"Ivan" <[email protected]> wrote:
              >>>
              >>>I have a problem wrapping up an exploded directory format application
              >>>into an ear
              >>>file running weblogic 6.0sp2 on winnt 4. One of the things I would
              >like
              >>>to do
              >>>is load a config file from a helper class without specifying a path.
              >>>
              >>>
              >>>EAR APP statementapp.ear contains: META-INF/MANIFEST.MF statement.jar
              >>>statementwebapp.war
              >>>META-INF/application.xml lib/log4j.jar (and other third party jar files
              >>>crimson.jar,
              >>>jaxp.jar etc.)
              >>>
              >>>The third party jar files have been manually unjar'ed and re-jar'ed
              >>without
              >>>compression
              >>>(after reading that a suggestion to someone else).
              >>>
              >>>WEB APP statementwebapp.war contains: all my jsp's at root level WEB-INF/classes/uk/.../servlets
              >>>- servlets WEB-INF/classes/uk/.../util - helper classes WEB-INF/tlds
              >>>- tag library
              >>>descriptors WEB-INF/web.xml & weblogic.xml - deployment descriptors
              >>
              >>>
              >>>Some of the helper classes make use of configuration files (for example
              >>>I have
              >>>a Logger class that uses Log4j). Here is how I would like to access
              >>the
              >>>config
              >>>file
              >>>
              >>>... private static final String config = "config.properties" ; PropertyConfigurator.configure(
              >>>config ) ; ...
              >>>
              >>>I have tried putting the config.properties file in the WEB-INF/classes
              >>>directory
              >>>and in the WEB-INF directory, however they don't seem to be found by
              >>>the class
              >>>loader.
              >>>
              >>>EJB statement.jar contains an ejb with the following: uk...business.statement...
              >>>- Statement ejb classes with ejbc generated stub and skeleton classes
              >>>uk...util
              >>>- Several Helper classes
              >>>
              >>>One such helper is Logger for which the Log4j jar file is needed. I
              >>deploy
              >>>the
              >>>statement.jar file in the ear (as listed above). Weblogic throws an
              >>error
              >>>message
              >>>saying cannot deploy statement (NoClassDefFound...): java.lang.NoClassDefFoundError:
              >>>org/apache/log4j/Category ie it cannot find the log4j package which
              >>is
              >>>referenced
              >>>in the Class-Path header of the manifest.mf file and located in the
              >>ear
              >>>file under
              >>>the lib directory.
              >>>
              >>>The manifest.mf file contains a line with the following: Class-Path:
              >>>lib/log4j.jar
              >>>lib/crimson.jar lib/jaxp.jar which I have read should allow the enterprise
              >>>classloader
              >>>to pick up the log4j.jar and xml parsing classes (ref. weblogic server
              >>>bible chap
              >>>18) without needing to be referenced in the weblogic start up class
              >>path.
              >>>
              >>>
              >>>Can manifest class-path references be used like this in weblogic 6.0?
              >>>Where should
              >>>I put the application properties files in the war and jar files?
              >>>
              >>>Clarification much appreciated. Ivan.
              >>>
              >>>PS: I had this application working in exploded directory format with
              >>>the jar files
              >>>in the system classpath and the properties file locations hardcoded
              >>in
              >>>the class
              >>>files. (not ideal for a clustered production environment!)
              >>>
              >>
              >
              

  • EAR Deployment Problem with weblogic 10.2. Need help.

    Hi,
    I have a EAR file exported from MyEclipse IDE. When i am deploying the EAR file in weblogic 10.2, i am not seeing classess and properties were not exploded under WEB-INF/classes in the web project. I can see the classes folder but it's empty.
    When i opened i can see EJB project JAR file and web project .war file in the EAR file. I checked the .war file content and i can see all the classes and properties available in the .war file.
    Please help me to find, why the classes and properties are not being exploded when i am deploying as package.
    Note: When i am deploying from myeclipse as exploded deployment i was able to run the application but i am failing when i deploy as a package (.ear file).
    Thank you,
    Vijay M

    I found the answer to this. The documentation is not clear enough, LD_LIBRARY_PATH MUST be set and MUST have a pointer to the directory where the SSL .so modules are. I wrote up a blog article explaining the configuration and detailed this issue.
    http://blogs.oracle.com/irm/2010/06/quick_guide_to_oracle_irm_11g_1.html

  • OC4J Hot Deployment/Extended deployment

    Hi
    Although this question has been asked over and over again, i couldn't find any real solution for my problem... so i'll ask again.
    Context:
    I've started recently using JDeveloper 10.1.2 and it's embedded OC4J server. I was previously working with Eclipse and Tomcat (with tomcat sysdeo plugin).
    In my previous senario, the deployments where made in a directory structure (exploded, not packaged), allowing a more fast reload from the container (when i compiled a class tomcat would automatically reload its context... not always this would work properly, but, still, it mad development a whole lot easear).
    Problem:
    I'm not able to do the same in Jdev/OC4J. Every time i compile a knew class, i have to start the server all over again, witch is a really tedious task... (each start can take more then five minutes, many times only to realize that i had done something wrong and have to restart).
    Question:
    Can this go faster? Can OC4J make extended deployments? If so, will that mean that i don't have to generate the hole ear file each time a make some change in a class?
    Or just, how do you develop in OC4J in a more productive away?
    Thanks in advance
    kim

    Hello,
    It is possible with OC4J to have the application automatically reloading the resources in development. It is documented in the deployment guide:
    - Automatic Deployment
    Regards
    Tugdual Grall[url]

  • Problem in deploying sample application HelloDB application iPlanet.

    I installed iPlanet 6.5 on my windows NT work station and then as per iPlanet documentation I tried deploying the sample HelloDB application. It gives the following error when I say build install
    Searching for build.xml ...
    Buildfile: E:\iPlanet\ias6\ias\ias-samples\database\hellodb\src\build.xml
    install_javadocs:
    [delete] Deleting directory E:\iPlanet\ias6\ias\ias-samples\database\hellodb\docs\api
    [mkdir] Created dir: E:\iPlanet\ias6\ias\ias-samples\database\hellodb\docs\api
    BUILD FAILED
    E:\iPlanet\ias6\ias\ias-samples\database\hellodb\src\build.xml:164: E:\iPlanet\ias6\ias\ias-samples\database\hellodb\build\d
    ocs\api not found.
    Total time: 1 second
    Can you please tell me where I'm doing wrong.

    Hi,
    Could you please post the entire messages that is on the screen right from the time you invoke build followed by the option.
    A quick answer from looking at the posted message that I can guess is that, may be build fails at the stage when the directory is created.
    Regards
    Ganesh .R
    Developer Technical Support
    Sun Microsystems
    http://www.sun.com/developers/support

  • Use of deployment classpath or shared-libraries to pick-up "custom" classes

    Hi,
    I’m trying to determine an approach to dealing with how classes are found in a deployed ADF application via classpath, etc. I’ve tried to explain the situation below as best I can so it’s clear. If you have any comments/suggestions as to how this could be done, it would be much appreciated
    Current Application structure:
    Consists of an application initially deployed to OC4J 10.1.3.4 using an alesco-wss.ear file
    Application contains a single Web Module, initially deployed as wss.war file within the alesco-wss.ear file above.
    The Web Module (wss) was built in JDeveloper 10.1.3.4 using 2 projects, a Model and ViewController project, and uses ADFBC.
    The Model project seems to also generate an alesco-model.jar file in the /WEB-INF/lib/ folder, even though Model classes are in the /WEB-INF/classes/ folder below?
    Exploded structure of application on application server looks something like:
    applications/alesco-wss/META-INF/
    /application.xml <- specifies settings for the Application such as Web Module settings
    /wss/
    /app/ <- directory containing application .jspx pages protected by security
    /images/ <- directory containing application images
    /infrastructure/ <- directory containing .jspx files for login, logout and error reduced security
    /skins/ <- directory containing Skin image, CSS and other files
    /WEB-INF/
    /classes/ <- directory containing application runtime class files as per package sub-directories
    /lib/ <- JAR files used by application (could move some to shared-libaries?) – seems to contain alesco-model.jar
    /regions/ <- directory containing .jspx pages used for Regions within JSPX template page
    /templates/ <- directory containing template .jspx pages used for development (not really required for deployment)
    /adf-faces-config.xml
    /adf-faces-skins.xml
    /faces-config.xml
    /faces-config-backing.xml
    /faces-config-nav.xml
    /region-metadata.xml
    /web.xml
    testpage.jspx <- Publicly accessible page just to test
    The application runs successfully using the above deployment structure.
    We plan to use the exploded deployment structure so that updates to pages, etc. can be applied individually rather than requiring construction and re-deployment of complete .EAR or .JAR files.
    What I’m trying to determine/establish is whether there is a mechanism to cater for a customisation of a class, where such a class would be used instead of the original class, perhaps using a classpath mechanism or shared library?
    For example, say there is a class “talent2.alesco.model.libraries.ModelUtil.class”, this would in the above structure be found under:
    applications/alesco-wss/META-INF/classes/talent2/alesco/model/libraries/ModelUtil.class
    Classes using the above class would import “talent2.alesco.model.libraries.ModelUtil”, so they effectively use that full-reference to the class (talent2.alesco.model.libraries as a path, either expanded or within a JAR).
    From the Oracle Containers for J2EE Developer’s Guide 10.1.3 page 3-17, it lists the following:
    Table 3–1 Configuration Options Affecting Class Visibility
    Classloader Configuration Option
    Configured shared library <code-source> in server.xml
    <import-shared-library> in server.xml
    app-name.root <import-shared-library> in orion-application.xml
    <library> jars/directories in orion-application.xml
    <ejb> JARs in orion-application.xml
    RAR file: all JARs at the root.
    RAR file: <native-library> directory paths.
    Manifest Class-Path of above JARs
    app-name.web.web-mod-name WAR file: Manifest Class-Path
    WAR file: WEB-INF/classes
    WAR file: WEB-INF/lib/ all JARs
    <classpath> jars/directories in orion-web.xml
    Manifest Class-Path of above jars.
    search-local-classes-first attribute in orion-web.xml
    Shared libraries are inherited from the app root.
    We have reasons why we prefer not to use .JAR files for these “non-standard” or “replaced” classes, so prefer an option that doesn’t involve creating a .JAR file.
    Our ideal solution would be to have such classes placed in an alternate directory that is referred to in a classpath such that IF a class exists in that location, it will be used instead of the one in the WEB-INF/classes/ directories, and if not such class is found it would then locate it in the WEB-INF/classes/ directories.
    - Can a classpath be set to look for such classes in a directory?
    - Do the classes have to replicate the original package directory structure within that directory (<dir>/talent2/alesco/model/libraries)?
    - If the class were put in such a directory, without replicating the original package directory structure, I assume the referencing “import” statements would not locate it correctly.
    - Is the classpath mechanism “clever” enough to search the package directory structure to locate the class (i.e. just points to <dir>)?
    - Or would the classpath mechanism require each individual path replicating the package structure to be added (i.e. <dir>/talent2/alesco/model/libraries/ and any other such package path)?
    If we are “forced” to resort to the use of JAR files, does a JAR file used for the purpose of overwrite/extending a sub-set of classes in the original location need to contain ALL related package classes? Or does it effectively “superset” classes it finds in all JAR files, etc. in the whole classpath? That is, it finds talent2.alesco.model.libraries.ModelUtil in the custom.jar file and happily goes on to get the remainder of talent2.alesco.model.libraries classes in the other core JAR/location. Or does it need all of them to be in the first JAR file for that package?
    Any help would be appreciated to understand how these various class visibility mechanisms could be used to achieve what is required would be appreciated.
    Gene

    So, nobody's had any experience with deploying an ADF application, and providing a means for a client to place custom classes in such a way as they're used in preference to the standard application class, effectively to implement a customised class without overwriting the original "standard" class?
    Gene

  • How to create a deployment plan for an existing application?

    Using WebLogic 10MP1.
    I have an existing EAR deployment, and I want to create a deployment plan so I can make changes to it without changing the EAR file itself. My goal is to change the value of the "precompile" flag in all the web modules.
    I've read the documentation on creating deployment plans, and it doesn't seem like it's doing anything. That is, I was able to run "weblogic.PlanGenerator" from the command line, but that's about my only success.
    The doc says that if you make a change to the app config and save it, that will prompt for a place to save the deployment plan. This seems odd, as I'm pretty sure I've never seen a prompt like that before. It didn't happen for me. As a test, I tried changing the "Deployment Order" field. I activated it, and then I changed it back and activated that. No deployment plan prompt.
    I then read that if there is a "plan" subdirectory off the application root containing the deployment plan, WebLogic will use that at deployment. So, I created a "plan" subdir in my EAR tree, put the generated (from "weblogic.PlanGenerator") plan there, and restarted. I didn't notice any log message about the plan, and when I logged into the console to check the "Deployment Plan" tab on the deployment ("Tuning Parameters" subtab), it says "No variables present".
    I must be missing some simple detail.

    In case anyone else ever has this problem, I've been able to resolve this.
    I used "weblogic.planGenerator" on the command line to get a deployment plan to start with. The obstacle I had was actually finding the "Update" button. For some reason I had thought this button the docs refer to was on the "Deployment Plan" tab in the configuration of the deployment. It's actually on the list of the deployments, and is active when the deployment you want to configure is checked.
    Once I got there, I was able to enter the path to my deployment plan, which I edited to produce the result I wanted (turning on "precompile" on most of the modules). Once I stored all that and restarted my server, I was able to verify that the server was precompiling on deployment (although it's hard to tell if I don't have any JSP compile errors. :) ).

Maybe you are looking for