Changing weblogic-application.xml

I deploy an EAR file which contains <prefer-application-packages> at weblogic-application.xml. Then, I deploy other applications. According to CAT, I need to modify weblogic.xml. Can I add new contents to that file without redeployment?

Step1). Deploy your Application as it is at present on the Server. Suppose your Web Application name is “SessionTimeoutWebApp” (I am assuming it as a Exploded WAR file you can work with Archived WAR file as well in the same way)
Step2). Anywhere in your file system Just paste the following “plan.xml” file: (Suppose Location is “F:\SessionTimeout_PlanDemo” )
step3:
<?xml version='1.0' encoding='UTF-8'?>
02     <deployment-plan xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-deployment-plan.xsd" global-variables="false">
03     
04     <application-name>SessionTimeoutWebApp</application-name> <!-- You need to change this Line and Put your Web Application Name -->
05     <variable-definition>
06     <variable>
07     <name>NewSessionValue</name>
08     <value>100000</value>
09     </variable>
10     </variable-definition>
11     
12     <module-override>
13     <module-name>SessionTimeoutWebApp</module-name> <!-- You need to change this Line and Put your Web Application Name -->
14     <module-type>war</module-type>
15     <module-descriptor external="true">
16     <root-element>web-app</root-element>
17     <uri>WEB-INF/web.xml</uri>
18     <variable-assignment>
19     <name>NewSessionValue</name>
20     <xpath>/web-app/session-config/session-timeout</xpath>
21     </variable-assignment>
22     </module-descriptor>
23     </module-override>
24     <config-root>F:\SessionTimeout_PlanDemo</config-root> <!-- You need to change this Line and Put the location of plan.xml file wherever u have pasted it -->
25     </deployment-plan>
Step4). Login to AdminConsole and goto deployments page—-> the select your Application (After Pressing Lock & Edit Button) –> update (click this button)—> browse your “plan.xml” file location and then finish.
Once the changes will be activated ….Next time your will see that your <session-timeout> value is changed from the AdminConsole or through any other technique like JMX or WLST.

Similar Messages

  • Difference betwwen weblogic.xml & weblogic-application.xml

    Hi,
    Can someone explain the Difference betwwen weblogic.xml & weblogic-application.xml in a portal application with some sample examples relavant to portal use cases.
    Regards

    Those files are not specific to portal applications. WEB-INF/weblogic.xml configures WebLogic specific settings for web applications. META-INF/weblogic-application.xml configures WebLogic specific settings for JEE applications.
    http://download.oracle.com/docs/cd/E21764_01/web.1111/e13706/overview.htm#i1067610 has lots of information about applications in WLS.

  • Weblogic-application.xml

    Is there a way I can get the contents of "application-param" element from weblogic-application.xml
    in a J2EE bean ?
    Are the contents of weblogic-application.xml bound to the JNDI tree?
    I am using WLS/WLI 8.1 SP2.
    Vishwa

    BEA Folks!!!
    Could someone respond please....with any pointers...
    Vishwa
    "Vishwa" <[email protected]> wrote:
    >
    Is there a way I can get the contents of "application-param" element
    from weblogic-application.xml
    in a J2EE bean ?
    Are the contents of weblogic-application.xml bound to the JNDI tree?
    I am using WLS/WLI 8.1 SP2.
    Vishwa

  • Weblogic-application.xml and prefer-application-packages tag issue.

    Hi All,
    To solve one of the issue I have mentioned already in
    http://forums.bea.com/bea/thread.jspa?threadID=300000394 post.
    I am planning to use prefer-application-packages tag in weblogic-application.xml but it says XML is invalid and shows following error in workshop 9.2.1.
    Severity     Description     Resource     In Folder     Location     Creation Time     Id
    2     cvc-complex-type.2.4.a: Invalid content was found starting with element 'wls:prefer-application-packages'. One of '{"http://www.bea.com/ns/weblogic/90":library-ref, "http://www.bea.com/ns/weblogic/90":fair-share-request, "http://www.bea.com/ns/weblogic/90":response-time-request, "http://www.bea.com/ns/weblogic/90":context-request, "http://www.bea.com/ns/weblogic/90":max-threads-constraint, "http://www.bea.com/ns/weblogic/90":min-threads-constraint, "http://www.bea.com/ns/weblogic/90":capacity, "http://www.bea.com/ns/weblogic/90":work-manager, "http://www.bea.com/ns/weblogic/90":application-admin-mode-trigger, "http://www.bea.com/ns/weblogic/90":session-descriptor, "http://www.bea.com/ns/weblogic/90":library-context-root-override}' is expected.     weblogic-application.xml     wivApp/EarContent/META-INF     line 22     June 13, 2007 9:12:51 AM     191
    This is my weblogic-application.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-application.xsd">
    <wls:application-param>
    <wls:param-name>webapp.encoding.default</wls:param-name>
    <wls:param-value>UTF-8</wls:param-value>
    </wls:application-param>
    <wls:library-ref>
    <wls:library-name>beehive-controls-1.0</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:implementation-version>1.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>wls-commonslogging-bridge</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:implementation-version>1.0</wls:implementation-version>
    </wls:library-ref>
    <wls:library-ref>
    <wls:library-name>weblogic-controls-1.0</wls:library-name>
    <wls:specification-version>1.0</wls:specification-version>
    <wls:implementation-version>1.0</wls:implementation-version>
    </wls:library-ref>
    <wls:prefer-application-packages>
         <wls:package-name>org.apache.log4j.*</wls:package-name>
    </wls:prefer-application-packages>
    </wls:weblogic-application>

    Hi Hitesh,
    Got the same problem.
    What I did to fix it was to switch both declarations :
    Before :
    http://www.bea.com/ns/weblogic/90
    http://www.bea.com/ns/weblogic/90/weblogic-application.xsd
    After :
    http://www.bea.com/ns/weblogic/90/weblogic-application.xsd http://www.bea.com/ns/weblogic/90
    And the Workshop error's gone.
    Note that I don't think it would have prevented your filtering class loader from working.
    Regards

  • Difference between prefer-application-packages in weblogic.xml and weblogic-application.xml?

    Hi!
    When deploying a WAR to WebLogic 10.3.5, what is the difference between the prefer-application-packages element in the files weblogic.xml and weblogic-application.xml?
    In my WARs WEB-INF/lib/ I have a JAR that contains classes that are already provided by the container (but older versions).
    If I do not use prefer-application-packages then my app gets the classes provided by the container.
    If I use prefer-application-packages in weblogic.xml then I get the classes from WAR/WEB-INF/lib which is expected.
    But if I use prefer-application-packages in weblogic-application.xml then I get the container versions. Why?
    Is there a difference between those two options?
    The exact data I use is:
    (foo.bar.* is the conflicting package; I add or remove the linex marked with XXXX)
    WEB-INF/weblogic.xml :
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-web-app
        xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd">
        <wls:container-descriptor>
            <wls:show-archived-real-path-enabled>true</wls:show-archived-real-path-enabled>
            <wls:prefer-application-packages> <!-- XXXX -->
                <wls:package-name>foo.bar.*</wls:package-name> <!-- XXXX -->
            </wls:prefer-application-packages> <!-- XXXX -->
            <wls:prefer-application-resources>
                <wls:resource-name>META-INF/services/some....</wls:resource-name>
                <wls:resource-name>META-INF/services/unrelated...</wls:resource-name>
                <wls:resource-name>META-INF/services/stuff...</wls:resource-name>
            </wls:prefer-application-resources>
        </wls:container-descriptor>
        <wls:jsp-descriptor>
            <wls:page-check-seconds>-1</wls:page-check-seconds>
            <wls:precompile>true</wls:precompile>
            <wls:precompile-continue>true</wls:precompile-continue>
            <wls:keepgenerated>true</wls:keepgenerated>
        </wls:jsp-descriptor>
        <wls:session-descriptor>
            <wls:persistent-store-type>replicated_if_clustered</wls:persistent-store-type>
        </wls:session-descriptor>
    </wls:weblogic-web-app>
    META-INF/weblogic-application.xml :
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-application
        xmlns="http://xmlns.oracle.com/weblogic/weblogic-application"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.2/weblogic-application.xsd">
        <application-param>
            <param-name>webapp.encoding.default</param-name>
            <param-value>UTF-8</param-value>
        </application-param>
        <xml>
            <parser-factory>
                <saxparser-factory>
                    org.apache.xerces.jaxp.SAXParserFactoryImpl
                </saxparser-factory>
                <document-builder-factory>
                    org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
                </document-builder-factory>
                <transformer-factory>
                    org.apache.xalan.processor.TransformerFactoryImpl
                </transformer-factory>
            </parser-factory>
        </xml>
        <prefer-application-packages>
            <package-name>foo.bar.*</package-name> <!-- XXXX -->
            <package-name>javax.jws.*</package-name>
            <package-name>javax.xml.ws.*</package-name>
            <package-name>org.apache.cxf.*</package-name>
            <package-name>antlr.*</package-name>
            <package-name>org.xmlsoap.schemas.wsdl.*</package-name>
        </prefer-application-packages>
    </weblogic-application>

    weblogic-application.xml has no meaning in WARs, it is only used in EARs.

  • Deploy given EAR file having application.xml and change context-root

    hi
    Please consider deploying a given EAR file on WebLogic Server 10.3.5 (part of JDeveloper 11.1.1.6.0) and changing the context-root for its web-module.
    For example an EAR file with only a web-module (ReviewContextRootFirstApp.ear [1]) or an EAR file with a web-module and an ejb-module (ReviewContextRootSecondApp.ear [2]).
    Given documentation appendix B section "context-root" [3] saying
    "... A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml. ..."
    and documentation section "Typical Deployment Configuration Workflows" [4] saying
    "Oracle does not support using a deployment plan to change the context-root in an application.xml file. However, if an application is deployed as a library, you can either change the context-root through an weblogic-application.xml file or use the deployment plan to change the context-root in an weblogic-application.xml file. "
    Some observed behaviour:
    - scenario (sc1) : deploy ReviewContextRootFirstApp.ear without deployment plan, results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc2) : deploy ReviewContextRootFirstApp.ear with deployment plan fa-plan.xml (tries to configure "/rcrfaweb11"), results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc3) : deploy ReviewContextRootSecondApp.ear without deployment plan, results in context-root "/rcrsaweb" (as in application.xml)
    - scenario (sc4) : deploy ReviewContextRootSecondApp.ear with deployment plan sa-plan.xml (tries to configure "/rcrsaweb21"), results in context-root "/rcrsaweb" (as in application.xml)
    The blog post "Defining the context root of a web application in Oracle WebLogic server" [5] by Silviu Leahu in its section "Defining the context root in deployment plan" suggests to
    "Remove the META-INF/application.xml DD from the EAR"
    - scenario (sc5) : remove application.xml from ReviewContextRootFirstApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan fa-plan.xml, results in context-root "/rcrfaweb11" (as in fa-plan.xml)
    - scenario (sc6) : remove application.xml from ReviewContextRootSecondApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan sa-plan.xml, results in context-root "/rcrsaweb21" (as in sa-plan.xml)
    One could expect that using a deployment plan (like in scenario's (sc2) and (sc4)) would allow to configure/change the context-root, whithout having to make changes to the EAR file to make this possible. (Somewhat like "Figure 4-2 Single Deployment Plan Workflow")
    Only in scenario's (sc5) and (sc6) I see something close to what I would like to achieve, but there the application.xml file has been removed from the EAR file.
    So ...
    - (q1) Is it impossible to change the context-root at deploy-time for a web-module in a given EAR file that includes an application.xml file, without changing the EAR file?
    - (q2) Is working with EAR files that don't have an application.xml file a supported approach (to change the context-root at deploy-time)?
    Seems like a simple goal, but I must be missing something that is required to achieve it.
    - [1] ReviewContextRootFirstApp/deploy/ReviewContextRootFirstApp.ear in the ZIP file
    at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
    - [2] ReviewContextRootSecondApp/deploy/ReviewContextRootSecondApp.ear in the (same) ZIP file
    at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
    - [3] http://docs.oracle.com/cd/E21764_01/web.1111/e13712/weblogic_xml.htm#WBAPP623
    - [4] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
    - [5] http://blog.leahu.net/it/2011/01/04/defining-the-context-root-of-a-web-application-in-oracle-weblogic-server/
    many thanks
    Jan Vervecken

    Thanks for your reply René van Wijk.
    René van Wijk wrote:
    You can use deployment plans in order to change the context-root ...That is what I tried and describe in scenario's (sc2), (sc4), (sc5) and (sc6) in this forum thread.
    Because the application.xml file (in the "given EAR file"), added by JDeveloper 11.1.1.6.0 when deploying to an EAR file, doesn't have id attributes on its application/module elements, I first tried a different XPath expression:
    "/application/module/web[web-uri/text()="WebProject.war"]/context-root"
    But, that didn't work.
    Although the "given EAR file" does not have the suggested id attributes, I tried adding a deployment descriptor application.xml file that does have such id attributes [2], allowing an XPath expression like the one suggested:
    "/application/module[id="WebProject"]/web/context-root"
    - scenario (sc7) : deploy ReviewContextRootFirstApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan fa-plan-application-xml-with-id.xml (tries to configure "/rcrfaweb14"), results in context-root "/rcrfaweb" (as in application.xml)
    - scenario (sc8) : deploy ReviewContextRootSecondApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan sa-plan-application-xml-with-id.xml (tries to configure "/rcrsaweb24"), results in context-root "/rcrsaweb" (as in application.xml)
    So, it does not seem to work.
    ... you have to use a variable assignment in the right part of the deployment plan (in this case the application.xml) ...My observations I describe above (that it does not seem to work) seem to confirm the Oracle documentation [1] I referred to in this forum thread before:
    "Oracle does not support using a deployment plan to change the context-root in an application.xml file. ... "
    ... By using an xpath expression, you can define which part of the xml has to be changed. ...The values for the deployment-plan xpath elements seem to be "peculiar".
    Although it should not be a problem in an XPath expression, using single quotes (like module[id='WebProject'] ) instead of double quotes (like module[id="WebProject"] ) results in:
    "java.lang.AssertionError: Attributes must be defined as name value pairs, eg, name="value" -- [id='WebProject']"
    Because an XPath predicate expression would use an "@" to refer to an attribute, I also tried to replace what you suggested module[id="Web"] with something like module[@id="Web"] but that also did not make a difference.
    - [1] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
    - [2] http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.02.zip
    regards
    Jan Vervecken

  • WebLogic 11g: Weblogic-Application-Version not taken into account

    Hello,
    I'm trying to set up Production Redeployment on my EAR, under WebLogic 10.3.6.
    However, I can't figure out how to make Weblogic-Application-Version work in MANIFEST.MF
    Here is my EAR structure:
    MyApplication
    --- APP-INF
    --- --- lib
    --- --- classes
    --- META-INF
    --- --- application.xml
    --- --- weblogic-application.xml
    --- --- MANIFEST.MF <- file I update
    --- WebApp1
    --- --- META-INF
    --- --- --- MANIFEST.MF
    --- --- WEB-INF
    --- --- --- classes
    --- --- --- lib
    --- --- --- web.xml
    --- --- --- weblogic.xml
    --- WebApp2
    --- --- same as WebApp1
    MANIFEST.MF content is the following:
    Manifest-Version: 1.0
    Weblogic-Application-Version: VERSION_1
    The problem is that it's not taken into account when I deploy the application in the WebLogic console.
    When I use staged mode, the line Weblogic-Application-Version: VERSION_1 is removed from the staged MANIFEST.MF file.
    The only way to manage to version my application is to add the flag -appversion to weblogic.Deployer, but I don't want to use that on a Production environment (and it's not recommended in the documentation!).
    Any idea why Weblogic-Application-Version not taken into account? I tried to add debug mode to node weblogic/debug but with no success.
    Thanks by advance,
    Julien

    I tested it at my end and was able to redeploy it successfully with the application versions.
    Are you saying that by deploying through weblogic console,the archive version is not honoring/getting picked up .is that correct?
    if yes, what does your weblogic console shows for archive version,when you first try to deploy your application with the VERSION_1.
    I mean,when you are on the "Optional Settings" Page.Do you see the Archive Version as VERSION_1?
    Deployments >> Click on the Install >> select your application ( MyAPP)>> Install this deployment as an application >> Select deployment targets >> Optional Settngs
    Example from the Optional settings Page for My application
    What do you want to name this deployment?
    Name: MyAPP     
    Archive Version:     
    VERSION_1
    This can confirm that the application being deployed is versioned one and if it doesn't shows up,then you need to check why its not getting picked up.?
    Moreover,You can enable the "deploy" debug flag to see whats going wrong in your case during the deployment process
    Server > Debug > Weblogic > Deploy
    Do refer the below viewlet on the Production Redeployment
    http://download.oracle.com/otn_hosted_doc/wls/redeployment/wls-side-by-side-non-annotation_viewlet_swf.html

  • 'weblogic.application.ModuleException:'while deploying the EAR file to WLS

    Hi
    i am trying to deploy the ADf11g app on to external WLS 10.3 server.
    My WLS is having the shared libraries .so i didn't include the liibraries in WAR.
    while deploying i am facing errors.
    My domain log:
    Nov 12, 2008 2:40:30 PM EST     J2EE     Warning     BEA-160195     The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Dep2EARapplication1 is not versioned.
         Nov 12, 2008 2:40:30 PM EST     HTTP     Error     BEA-101371     There was a failure when processing annotations for application F:\oracleWls\user_projects\domains\sailu1base_domain\servers\AdminServer\tmp\_WL_user\Dep2EARapplication1\6e738n\Dep2webapp1.war. Please make sure that the annotations are valid. The error is org.apache.myfaces.trinidad.webapp.ResourceServlet
         Nov 12, 2008 2:40:30 PM EST     Deployer     Error     BEA-149265     Failure occurred in the execution of deployment request with ID '1226518830484' for task '4'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root'' weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:227) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
         Nov 12, 2008 2:40:30 PM EST     Deployer     Warning     BEA-149004     Failures were detected while initiating deploy task for application 'Dep2EARapplication1'.
         Nov 12, 2008 2:40:30 PM EST     Deployer     Warning     BEA-149078     Stack trace for message 149004 weblogic.application.ModuleException: Failed to load webapp: 'usrDep2Application1-ViewController-context-root' at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.ResourceServlet at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:227) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1287) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
         Nov 12, 2008 2:40:30 PM EST     Console     Error     BEA-240003     init>(WebAppServletContext.java:412) at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
         Nov 12, 2008 2:41:04 PM EST     netuix     Warning     BEA-423420     Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=DiagnosticsViewDomainLogTablePage&DiagnosticsViewDomainLogTablePortlethandle=com.bea.console.handles.LogDispatchHandle%28%22AdminServer%3BDomainLog%22%29.
    Can anyone plz tell me why i am getting errors.
    what is the 'weblogic.application.ModuleException:' error.
    and the HTTP error.

    Hi,
    My EAR file size is about 25 MB.this size is becoz of libraries.so i decided to make a jar file of all libraries.and i installed that jar as library on wls10.3. so that my ear apps later refer this jar.by this no need to include the libraries in every EAR and also size of ear is reduced.
    In my weblogic-application.xml file i refer this jar using the <library-ref> tag.when i am trying to install ear file i am facing this weblogic.application.ModuleException: error as posted above .
    Can you tell me where i went wrong.
    Is the way i am doing is right or not.

  • Unresolved application library references, defined in weblogic-application.

    Hi ,,
    Iam getting the following error while deploying the application . please help
    [10:12:41 AM] ADF shared library is not available, implicitly deploying library ADF Controller Runtime
    [10:24:00 AM] ---- Deployment started. ----
    [10:24:00 AM] Target platform is (Weblogic 10.3).
    [10:24:02 AM] Retrieving existing application information
    [10:24:02 AM] Running dependency analysis...
    [10:24:02 AM] Building...
    [10:24:07 AM] Deploying 2 profiles...
    [10:24:08 AM] Wrote Web Application Module to C:\JDeveloper\mywork\SupplierApp1\SupplierApp1\ViewController\deploy\SupplierApp1_ViewController_webapp1.war
    [10:24:08 AM] Wrote Enterprise Application Module to C:\JDeveloper\mywork\SupplierApp1\SupplierApp1\deploy\SupplierApp1_application1.ear
    [10:24:09 AM] Deploying Application...
    [10:24:11 AM] [Deployer:149191]Operation 'deploy' on application 'SupplierApp1_application1' is initializing on 'OBIEE_DEV'
    [10:24:15 AM] [Deployer:149193]Operation 'deploy' on application 'SupplierApp1_application1' has failed on 'AdminServer'
    [10:24:15 AM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application SupplierApp1_application1 on AdminServer,OBIEE_DEV.: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false]..
    [10:24:16 AM] Weblogic Server Exception: weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false].
    [10:24:16 AM] See server logs or server console for more details.
    [10:24:16 AM] weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false].
    [10:24:16 AM] #### Deployment incomplete. ####
    [10:24:16 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    [10:25:48 AM] ---- Deployment started. ----
    [10:25:48 AM] Target platform is (Weblogic 10.3).
    [10:25:50 AM] Retrieving existing application information
    [10:25:50 AM] Running dependency analysis...
    [10:25:50 AM] Building...
    [10:25:55 AM] Deploying 2 profiles...
    [10:25:56 AM] Wrote Web Application Module to C:\JDeveloper\mywork\SupplierApp1\SupplierApp1\ViewController\deploy\SupplierApp1_ViewController_webapp1.war
    [10:25:56 AM] Wrote Enterprise Application Module to C:\JDeveloper\mywork\SupplierApp1\SupplierApp1\deploy\SupplierApp1_application1.ear
    [10:25:57 AM] Deploying Application...
    [10:25:59 AM] [Deployer:149193]Operation 'deploy' on application 'SupplierApp1_application1' has failed on 'AdminServer'
    [10:25:59 AM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application SupplierApp1_application1 on AdminServer.: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false]..
    [10:25:59 AM] Weblogic Server Exception: weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false].
    [10:25:59 AM] See server logs or server console for more details.
    [10:25:59 AM] weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: adf.oracle.domain, exact-match: false].
    [10:25:59 AM] #### Deployment incomplete. ####
    [10:25:59 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)

    Jan 31, 2012 7:32:23 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1328018543109' for task '2'. Error is: 'weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: *oracle.webcenter.skin*, Specification-Version: *11.1.1*, exact-match: false].'
    try to look at your weblogic-application.xml and check if it has code like this
    <library-ref>
    <library-name>oracle.webcenter.skin</library-name>
    <specification-version>11.1.1</specification-version>
    <exact-match>false</exact-match>
    </library-ref>
    If it has, then You might want to deploy oracle.webcenter.skin as a library in your Weblogic server.

  • Application.xml in ear file

    Hi
    When we deploy to ear file the application.xml file is created with the following root tag:
    <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee">
    Previously (Jdev10.1.2) it was created with only:
    <application>
    We are running on an older app server which does not accept the new tag. Any way to set up 10.1.3 to deploy the same tag as the previous version?
    If I manually edit the ear file and change the application.xml file, it runs fine on the older app server. We do not want this manual intervention.
    Thank you

    Does setting a target platform in the deployment profile that points to a 10.1.2 application server works?
    Also you can create a 1.3 application.xml using New->deployment descriptor->J2EE deployment descriptor wizard

  • Application.xml

    I created a basic webdynpro application with just one text view, and tried to deploy and run it.
    I get the following error :
    404   Not Found
    The requested resource does not exist.
    Do I have to make changes to application.xml before i deploy and run a Webdynpro application?
    Jayanth

    Hi Armin,
    Thanks for the quick reply.
    I dont get build errors on rebuilding the project.
    When I deploy and Run the application I get a pop up that says "Eclipse Autobuild must be switched On in order to allow the correct creation of a deployable archive. Do you want to Switch On autobuild."
    When I Enable Autobuild the application deploys sucessfully. but when it tries to run the application I get an error that "The requested resource does not exist."

  • Weblogic Deployment weblogic-applciation.xml

    Hello,
    Do i need weblogic-application.xml for ordinary deployment keeping .war, .ear, .jar files in applications folder under webglogic, if so what is the structure of my source file i have to keep ?. I mean where i have to keep the application.xml and weblogic-application.xml in conjunction with my beans META-INF/ejb-jar.xml, weblogic-ejb-jar.xml
    thanks,
    kuru

    weblogic-application.xml file is not mandatory for deploying application. It is used for setting additional vendor specific options.
    For example in your 'Test' directory, there are three folder 1) web 2) META-INF 3) ejb
    Put weblogic.xml and weblogic-application.xml inTest / META-INF.
    Put ejb-jar.xml and weblogic-ejb-jar.xml in test / ejb / META-INF directory.
    + Mihir

  • Weblogic with XML-RPC RuntimeModelerException

    I am having problems invoking a SOAP Web Service from an XML-RPC Web Service. They are both deployed on WebLogic.
    Here are the details:
    We have ported a JBOSS .esb application that implements XML-RPC Web Services to a WebLogic .ear application. The porting was successful. Bellow you can see the the .ear archive structure:
        xmlrpc-services-app.ear
            + lib
                + aopalliance-1.0.jar
                + aspects-5.2.0.jar
                + commons-codec-1.3.jar
                + commons-collections-3.2.jar
                + commons-lang-2.4.jar
                + commons-logging-1.1.jar
                + container-common-api-5.2.0.jar
                + jettison-1.2.jar
                + junit-3.8.1.jar
                + log4j-1.2.16.jar
                + mysql-connector-java-5.1.12.jar
                + openads-api-xmlrpc-1.xmlrpc3.cmt_fix.2.jar
                + snmpTrapAppender-1.2.9.jar
                + spring-aop-3.0.1.RELEASE.jar
                + spring-asm-3.0.1.RELEASE.jar
                + spring-beans-3.0.1.RELEASE.jar
                + spring-context-3.0.1.RELEASE.jar
                + spring-context-support-3.0.1.RELEASE.jar
                + spring-core-3.0.1.RELEASE.jar
                + spring-expression-3.0.1.RELEASE.jar
                + spring-jdbc-3.0.1.RELEASE.jar
                + spring-ldap-1.2.1.jar
                + spring-security-core-2.0.5.RELEASE.jar
                + spring-tx-3.0.1.RELEASE.jar
                + spring-web-3.0.1.RELEASE.jar
                + lib-common-tools-1.5.jar
                + lib-security-1.5.jar
                + stax-api-1.0.1.jar
                + ws-commons-util-1.0.2.jar
                + xml-apis-1.0.b2.jar
                + xmlrpc-client-3.1.3.jar
                + xmlrpc-common-3.1.3.jar
                + xmlrpc-server-3.1.3.jar
            + META-INF
                + MANIFEST.MF
                + application.xml
                + weblogic-application.xml
            + xmlrpc-services-app.war
                + META-INF - generated by Maven
                + WEB-INF
                    + classes
                    + jboss-web.xml
                    + lib
                        + apache-mime4j-0.6.1.jar
                        + commons-codec-1.4.jar
                        + commons-logging-1.1.jar
                        + httpclient-4.2-beta1.jar
                        + httpcore-4.2-beta1.jar
                        + httpmime-4.2-beta1.jar
                        + servlet-api-2.3.jar
                        + offersService-Client-1.0.jar
                    + web.xml
                + index.jsp - not really usedThe `offersService-Client-1.0.jar` contains a Web Service definition (not the implementation) and is used to invoke the Offers Web Service. The WS client and the jar were created using JDeveloper. The key files inside this jar are:
        GetOfferRequest.class
        ObjectFactory.class
        Offer.class
        OffersPortType.class
        OffersSchema.xsd
        OffersService.class
        OffersService.wsdl
        OffersService.xmlWhen invoking this WS from a class in the xmlrpc-services-app.ear, I get the following error:
        com.sun.xml.ws.model.RuntimeModelerException: A WebService annotation is not present on class: offers.OffersPortType
                at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:237)
                at com.sun.xml.ws.client.WSServiceDelegate.buildRuntimeModel(WSServiceDelegate.java:762)
                at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.buildRuntimeModel(WLSProvider.java:982)
                at com.sun.xml.ws.client.WSServiceDelegate.createSEIPortInfo(WSServiceDelegate.java:746)
                at com.sun.xml.ws.client.WSServiceDelegate.addSEI(WSServiceDelegate.java:737)
                at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:361)
                at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.internalGetPort(WLSProvider.java:934)
                at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate$PortClientInstanceFactory.createClientInstance(WLSProvider.java:1039)
                at weblogic.wsee.jaxws.spi.ClientInstancePool.takeSimpleClientInstance(ClientInstancePool.java:376)
                at weblogic.wsee.jaxws.spi.ClientInstancePool.take(ClientInstancePool.java:232)
                at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.getPort(WLSProvider.java:852)
                at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:344)
                at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.getPort(WLSProvider.java:792)
                at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:326)
                at javax.xml.ws.Service.getPort(Service.java:92)
                at offers.OffersService.getOffersPort(OffersService.java:68)HOWEVER, when I invoke it from a simple Web Service created in JDeveloper and deployed on WebLogic or even from the command line (so outside the WebLogic context), I do not get this error.
    Here is how I create the client for the service:
    OffersService offersService = new OffersService();
    OffersPortType offersPortType = offersService.getOffersPort(); // it crashes hereDo you have any idea of what might be wrong?
    If you need any other details, please do not hesitate to ask.

    carYang wrote:
    > Can you use cfinvoke with XML-RPC arguments or is it
    just for SOAP methods?
    >
    > Does anyone have an example of passing XML-RPC?
    http://www.fusionteam.co.uk/blog/2008/02/19/xml-rpc-using-coldfusion-and-microsoftxmlhttp- com-object/
    But you can also do it with CFHTTP.
    Mack

  • EAR descriptor weblogic-application Example

    I have an EAR file containing EJBs packaged in a JAR as well as a startup class. Without the weblogic-application.xml file the EJB deploy fine, however as soon as I include the file in the EAR package my EJBs are no longer deployed. I want to use the weblogic-application.xml file to define a startup class, so the option of simply leaving this file out will not work for me.
    Any suggestion what I have to configure in this file for the EJB's to be also deployed ?
    Current weblogic-application.xml file:
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-application
    xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
    http://www.bea.com/ns/weblogic/90/weblogic-application.xsd">
        <
        <startup>
            <startup-class>com.thunderhead.weblogic.StartupService</startup-class> 
            <startup-uri>SimpleLIBS.jar</startup-uri> 
        </startup>   
    </weblogic-application>Thanks in advance.
    Alex

    You should define the EJB module in you weblogic-application.xml, for example:
         <module>
         <ejb>your ejb name</ejb>
         </module>
    or the deployer unable to find the EJB which you want to deploy.
    Without weblogic-application.xml, the whole EAR will be scanned to generate depolyment view so that EJB can be deployed. With weblogic-application.xml, the deployer will only deploy the modules which are defined in weblogic-application.xml

  • After Making Changes In Log4j.xml Application Needs Recompilation?

    Hello,
    I am using log4j in my jsp pages and for that I instantiating Logger class like this
    Logger logger = Logger.getLogger("test.jsp");
    {code}
    And I have log4j.xml in the classpath.
    I believe, priority levels can be changed and log level can be changed without re-compiling.
    Change the log4j.xml and re-run jsp pages.
    However I need to re-compile after making changes in log4j.xml file. Without re-compilation changes are not getting reflected.
    Why I need to re-compile application in order to see the changes I have made in log4j.xml?
    Appreciate any help in this regard.
    Regards                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    This is the contents of my log4j.xml, its under WEB-INF/lib
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
    <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
      <!-- A1 is set to be a ConsoleAppender -->
      <appender name="sout" class="org.apache.log4j.ConsoleAppender">
        <!-- A1 uses PatternLayout -->
        <layout class="org.apache.log4j.PatternLayout">
          <param name="ConversionPattern" value="%d [%c] %p - %m%n"/>
        </layout>
      </appender>
      <root>
        <!-- Set root logger level to DEBUG and its only appender to A1 -->
        <priority value="off"/>
        <appender-ref ref="sout"/>
      </root>
    </log4j:configuration>

Maybe you are looking for