Dynamic update of EJB/Web deployment descriptors

In 8.1SP3, is there any provision to allow for dynamic update of EJB/Web deployment descriptors? I'm specifically looking at env var changes.
I noticed that there are some mentions of the ability to dynamically update deployment descriptors, but it appears that the general facility has been deprecated, and they've incorporated all of the WebLogic-specific descriptor information directly into the console.
When I dig through the JMX namespace and some of the MBean classes, I also see mentions of "deployment descriptor editors", but it's not clear how to utilize that.
I'm aware of the fact that my application would have to be aware of possible dynamic updates to the descriptors, so I'd have to be able to implement some sort of listener for that.

I have the same question but for a different purpose. I am part of a hosting group and we have app teams that have defined init-params in the web.xml that have to be changed as the app is promoted up through test environments and ultimately to production - only we need to be able to do this WITHOUT "cracking open" the archive.
I was hoping to be able to script something to do the update after deployment.
So any help at all would be appreciated. In the meantime will continue to poke around in the WLST and MBean docs.
Thanks,
Ed

Similar Messages

  • JNDI environment properties for EJB in deployment descriptor

    Is it possible to deploy an EJB on weblogic 6.0 such that the EJBHome
    object is bound using JNDI to a different JNDI server such as ldap
    server instead of the weblogic server by specifying JNDI env.
    properties like PROVIDER_URL, INITIAL_CONTEXT_FACTORY in the
    deployment descriptor? That is use the weblogic built-in deployer but
    bind the JNDI names to a different JNDI server. For this, can the
    EJBHome objects be treated as just RMI (over IIOP) objects and bind
    them (stubs of the RMI objects) using the Sun's JNDI service provider.
    The goal is that thereafter the Home JNDI names can be looked up by
    RMI clients and the interface methods invoked.
    Thanks,
    ... arun

    Must I put the war and jar files in the same ear ?
    oh..ft...my boss is killing me ..
    package..repackage...package..repackage..and test ??
    Could anybody tell me how to refer a SLSB without put the webApp
    and the EjbApp together in an Ear file ??
    thanks very much!!!!

  • Web Deployment Descriptor

    Hi!
    1.)How can I stop directory browsing in tomcat.
    I am using jboss/tomcat
    2.)Where can I find documentation on web.xml
    3.)I want the request in the address bar to stay same
    //localhost:8080/myapp all the time.
    And every time the user does something I want the request to go to my request handler servlet. I used
    <servlet-mapping>
    <servlet-name>requesthandler</servlet-name>
    <url-pattern>/</url-pattern>
    </servlet-mapping>
    this makes all the requests to come to the servlet but how do i redirect the requests for images and other static contents back to the web server
    Thanx for the any help in advance.

    1) Check the security docs in Tomcat at:
    http://localhost:8080/tomcat-docs/security-manager-howto.html when you tomcat server is running.
    2) Check out the Servlet 2.3 Spec API at:
    http://java.sun.com/products/servlet/download.html
    All Web developers should read it even if it is 10 times larger than the 2.2 spec.
    3) try: <url-pattern>/*</url-pattern>
    as quoted:
    SRV.11.2 Specification of Mappings
    In the web application deployment descriptor, the following syntax is used to define
    mappings:
    � A string beginning with a �/� character and ending with a �/*� postfix is used
    for path mapping.
    � A string beginning with a �*.� prefix is used as an extension mapping.
    � A string containing only the �/� character indicates the "default" servlet of the
    application. In this case the servlet path is the request URI minus the context
    path and the path info is null.
    � All other strings are used for exact matches only.
    Cheers,
    Anthony

  • XML deployment descriptor generation

    How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
    By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
    Thanks.

    How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
    By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
    Thanks. Hi,
    there is no way (so far as I know) that an J2EE Application server (what oc4j is) makes the deployment descriptors, that's why they are called deployment descriptors, without them you can't deploy on any Application server.
    I personally use JDeveloper, but most current JAVA IDE's support generation of deployment descriptors.
    Basically my approach is to define the architecture within Rational Rose, which generates for me the stubs for the classes and for every ejb a deployment descriptor, later I copy all of them into one ejb-jar.xml and open the whole bunch with JDeveloper, it works fine with 903 preview, although there are some problems with the 902 version of JDeveloper.
    Which IDE are you using?
    --hery                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Clobbered manifest when editing deployment descriptors

    I'm running WebLogic server 6.1. I deploy an ear file that consists of one EJB
    module (a session bean) and several extra jars, which contain client classes to
    other beans and some utility classes. The session bean jar's manifest file includes
    a classpath entry listing the extra jars in the ear. However, when I edit some
    environment variables in the EJB's deployment descriptors through the console,
    this manifest file is replaced and the classpath entry does not appear in the
    new manifest. This makes the ear file undeployable. Is this a documented bug?
    Is there a fix or workaround?

    I'm running WebLogic server 6.1. I deploy an ear file that consists of one EJB
    module (a session bean) and several extra jars, which contain client classes to
    other beans and some utility classes. The session bean jar's manifest file includes
    a classpath entry listing the extra jars in the ear. However, when I edit some
    environment variables in the EJB's deployment descriptors through the console,
    this manifest file is replaced and the classpath entry does not appear in the
    new manifest. This makes the ear file undeployable. Is this a documented bug?
    Is there a fix or workaround?

  • Referencing EJB on remote server AND using deployment descriptor

    We're using Weblogic 6.1sp2 under Windows 2000.
    We have a web application on server A and several EJBs running on server B -
    some of these may in the future be moved to different servers.
    We would like to ensure that this only requires reconfiguring the deployment
    descriptors.
    In our web app, we access the EJB's like this:
    AccountHome accHome = (AccountHome) (new
    InitialContext()).lookup("java:comp/env/ejb/AccountHome")
    - we then map ejb/AccountHome to the JNDI name in the weblogic.xml file in
    the web app - the JNDI name will usually (but not always) be the class name
    of the implementing class, e.g. system.billing.accounting.AccountHome
    However, to make this work when the EJB is on server B, we must put a
    jndi.properties file in the server A classpath containing
    java.naming.provider.url=t3://server_b:7001/
    to point to server B.
    Now, this makes ALL JNDI lookups on server A go to server B - this is not
    what we want. Especially not in the case where some EJB's move to server C -
    B and C may be in separate clusters and will not be clustering the JNDI
    tree. Also, other web applications on the server will need to go to
    different servers.
    Alternatively, we could specify a property set in the InitialContext
    constructor with a provider url. But in that case, the mapping from
    web.xml/weblogic.xml is apparently not applied - or rather, if we look up
    "java:comp/env/ejb/AccountHome", weblogic maps it to
    "system.billing.accounting.AccountHome" and then tries to look it up on the
    local machine, server A.
    If we look up "system.billing.accounting.AccountHome", it does correctly
    look it up on the server specified in the provider url and finds the entry.
    However, this would mean that we would have to specify the exact jndi name.
    In addition, we would have to hard-code the server name for each lookup.
    An alternative would be to "copy" the JNDI entries from server B to server A
    (or to some other shared, global JNDI registry). But these would need to be
    kept in sync - especially since server B is really a cluster, where
    different servers may come online at different times and register their EJBs
    as clusterable, so the stubs would need to be continously updated.
    My best idea is to bypass the whole web.xml/weblogic.xml mapping scheme and
    just add our own config file with stuff like
    <mappings>
    <map entry="java:comp/env/ejb/AccountHome">
    <jndi-properties>
    java.naming.provider.url=t3://server_b:7001/
    java.naming.security.principal=jndiuser
    java.naming.security.credentials=mysecretpassword
    </jndi.properties>
    <jndi-name>sysmte.billing.accounting.AccountHome</jndi-name>
    </map>
    </mappings>
    We then need to wrap all the lookups in our own lookup mechanism which first
    checks the config file to find any mappings.
    However, this seems like reinventing the wheel and will also confuse most
    deployment tools etc.
    Does anybody have any suggestions where we
    1. Don't put a jndi.properties file in the server classpath
    2. Lookup ejb's using "java:comp/env/ejb/SomeEJB" - not the JNDI name.
    3. Don't hardcode the server names in the application - but potentially
    in the deployment descriptor.
    4. Can look up different EJB's on different machines
    Niels Harremoës

    There is an article on dev2dev that may explain what you are seeing...
    http://dev2dev.bea.com/articlesnews/discussion/thread.jsp?thread=142
    HTH
    dwfa
    "Niels Ull Harremoës" <[email protected]> wrote in message
    news:[email protected]...
    It turns out that we can make it work by entering the url of the server in
    the weblogic.xml entry - e.g. instead of having
    <reference-descriptor>
    <ejb-reference-description>
    <ejb-ref-name>ejb/AccountHome</ejb-ref-name>
    <jndi-name>system.billing.accounting.AccountHome</jndi-name>
    </ejb-reference-description>
    </reference-descriptor>
    we enter
    <reference-descriptor>
    <ejb-reference-description>
    <ejb-ref-name>ejb/AccountHome</ejb-ref-name>
    <jndi-name>t3://server_b:7001/system.billing.accounting.AccountHome</jndi-na
    me>
    </ejb-reference-description>
    </reference-descriptor>
    However, we are unsure on whether this will establish a new JNDIconnection
    to server_b on every lookup? And it's not documented anywhere?
    Does anybody have any other suggestions?
    "Niels Ull Harremoës" <[email protected]> wrote in message
    news:[email protected]...
    We're using Weblogic 6.1sp2 under Windows 2000.
    We have a web application on server A and several EJBs running on serverB -
    some of these may in the future be moved to different servers.
    We would like to ensure that this only requires reconfiguring thedeployment
    descriptors.
    In our web app, we access the EJB's like this:
    AccountHome accHome = (AccountHome) (new
    InitialContext()).lookup("java:comp/env/ejb/AccountHome")
    - we then map ejb/AccountHome to the JNDI name in the weblogic.xml file
    in
    the web app - the JNDI name will usually (but not always) be the classname
    of the implementing class, e.g. system.billing.accounting.AccountHome
    However, to make this work when the EJB is on server B, we must put a
    jndi.properties file in the server A classpath containing
    java.naming.provider.url=t3://server_b:7001/
    to point to server B.
    Now, this makes ALL JNDI lookups on server A go to server B - this is
    not
    what we want. Especially not in the case where some EJB's move to serverC -
    B and C may be in separate clusters and will not be clustering the JNDI
    tree. Also, other web applications on the server will need to go to
    different servers.
    Alternatively, we could specify a property set in the InitialContext
    constructor with a provider url. But in that case, the mapping from
    web.xml/weblogic.xml is apparently not applied - or rather, if we look
    up
    "java:comp/env/ejb/AccountHome", weblogic maps it to
    "system.billing.accounting.AccountHome" and then tries to look it up onthe
    local machine, server A.
    If we look up "system.billing.accounting.AccountHome", it does correctly
    look it up on the server specified in the provider url and finds theentry.
    However, this would mean that we would have to specify the exact jndiname.
    In addition, we would have to hard-code the server name for each lookup.
    An alternative would be to "copy" the JNDI entries from server B to
    server
    A
    (or to some other shared, global JNDI registry). But these would need tobe
    kept in sync - especially since server B is really a cluster, where
    different servers may come online at different times and register theirEJBs
    as clusterable, so the stubs would need to be continously updated.
    My best idea is to bypass the whole web.xml/weblogic.xml mapping schemeand
    just add our own config file with stuff like
    <mappings>
    <map entry="java:comp/env/ejb/AccountHome">
    <jndi-properties>
    java.naming.provider.url=t3://server_b:7001/
    java.naming.security.principal=jndiuser
    java.naming.security.credentials=mysecretpassword
    </jndi.properties>
    <jndi-name>sysmte.billing.accounting.AccountHome</jndi-name>
    </map>
    </mappings>
    We then need to wrap all the lookups in our own lookup mechanism whichfirst
    checks the config file to find any mappings.
    However, this seems like reinventing the wheel and will also confuse
    most
    deployment tools etc.
    Does anybody have any suggestions where we
    1. Don't put a jndi.properties file in the server classpath
    2. Lookup ejb's using "java:comp/env/ejb/SomeEJB" - not the JNDIname.
    3. Don't hardcode the server names in the application - butpotentially
    in the deployment descriptor.
    4. Can look up different EJB's on different machines
    Niels Harremoës

  • The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing

    Hello,
    I want to create web service from ejb but everytime I want to do it, I get the following error:
    I'm using NWDS 7.2 and JDK 1.6
    [004]Deployment aborted
    Settings
    SDM host : XXX
    SDM port : 50118
    URL to deploy : file:/C:/DOCUME1/XXXX/LOCALS1/Temp/temp3760382784932063822XXXWSProjectEar.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/XXX/LOCALS1/Temp/temp3760382784932063822XXX/WSProjectEar.ear
    Aborted: development component 'XXXWSProjectEar'/'sap.com'/'localhost'/'2011.01.06.15.48.31'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/XXXWSProjectEar.. Reason: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing. ; nested exception is:      com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    Can anyone tell me why am I getting this error.
    Thnx for your help.
    Best regards.

    Hello Decio Junior,
    Actually yes, I resolved my problem.
    I'm developing an EJB 3.0 project. I'm using NWDS 7.2 and JDK 1.6 as I said.
    The problem is that my server was using JDK 1.4 and that was the problem.
    EJB 1.1 and 2.1 need ejb-jar.xml but EJB 3.0 use the annotations instead.
    Check your server JDK Version. It should be JDK 1.5 or higher.
    Something else that you should check, in your project properties :
    In the Build PATH : Use JDK 1.5
    In the Java Compiler : Set the java compiler compliance level to 1.6 and check use default compliance settings
    Hope it would help.
    If you need more explanations, I'm here
    Good luck.

  • Ejb accessing the deployment descriptor

    My ejb needs to be able to access the deployment descriptor to retrieve some user information needed to connect to a web service. What is the best way to do this? I know servletts can do this, and if necessary, I could have my servlet retrieve the info and pass it to the bean, but I was hoping to avoid this.
    Thanks
    Matt

    Well, sure I think that is easy. In your <entity> or <session> deployment descriptor you can have:
    <env-entry>
    <env-entry-name>WebServiceLogins</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>su, dan, bob, steve, richard, suzie, carla</env-entry-value>
    </env-entry>
    <env-entry>
    <env-entry-name>WebServicePasswords</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>drs100, vfdds2, ajk14, pass411, richard23, q4lty, uo738ww1</env-entry-value>
    </env-entry>
    Then in your intial-context in your session or entity ejb.....
    InitialContext ic = new InitialContext();
    String logins = (String) ic.lookup("java:comp/env/WebServiceLogins");
    String passwords = (String) ic.lookup("java:comp/env/WebServicePasswords");

  • Weblogic vendor specific EJB deployment descriptor

    Hi All,
    I have been trying to get weblogic-ejb.xml working to provide the names where I want my EJB3 beans accessable in JNDI, but this has not been working for me.
    I have been looking through the web - there are not too many mentions of the deployment descriptor. If there any tutorials or official documents from BEA on this, links would be highliy appreciated.
    I am using WL10_01 if it helps.
    Thanks,
    Kirill.

    Did you try <business-interface-jndi-name-map> tag in weblogic-ejb-jar.xml?
    With the following example setup, you should be able to look up the Session bean that implements service.JPAService interface in JNDI tree with "JPAService".
    <weblogic-enterprise-bean>
        <ejb-name>JPAServiceBean</ejb-name>
         <stateless-session-descriptor>
          <business-interface-jndi-name-map>
               <business-remote>service.JPAService</business-remote>
            <jndi-name>JPAService</jndi-name>
          </business-interface-jndi-name-map>
        </stateless-session-descriptor>     
        <enable-call-by-reference>true</enable-call-by-reference>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>

  • Ejb-ref in the deployment descriptor

    Could someone help me on how to configure an ejb-reference in the 3 xml
    files.
    ejb-jar.xml, weblogic-ejb-jar.xml and web.xml
    These are the entries for my application, but I get some exception. Can
    somebody help me pls?
    ejb-jar.xml
    <enterprise-beans>
    <session id="Abcd">
    <small-icon></small-icon>
    <ejb-name>ABCD</ejb-name>
    <home>AbcdHome</home>
    <remote>AbcdRemote</remote>
    <ejb-class>AbcdBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    web.xml contains the foll,
    <ejb-ref>
    <ejb-ref-name>ejb/abcd</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <home>AbcdHome</home>
    <remote>AbcdRemote</remote>
    <ejb-link>ABCD</ejb-link>
    </ejb-ref>
    weblogic.ejb-jar.xml contains,
    <weblogic-enterprise-bean>
    <ejb-name>ABCD</ejb-name>
    <caching-descriptor>
    <max-beans-in-free-pool>100</max-beans-in-free-pool>
    </caching-descriptor>
    <reference-descriptor>
    <ejb-reference-description>
    <ejb-ref-name>ejb/abcd</ejb-ref-name>
    <jndi-name>ejb/ABCD</jndi-name>
    </ejb-reference-description>
    </reference-descriptor>
    </weblogic-enterprise-bean>
    But when i run the application, I get the foll exception,
    In EJB RemotePlatform, a session or entity bean that has a remote home m
    ust be given a JNDI name in the weblogic-ejb-jar.xml descriptor file.
    at weblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChe
    cker.java:256)
    at weblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJ
    BComplianceChecker.java:220)
    at weblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:4
    52)
    at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:409)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:202)
    at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
    at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:676)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:843)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:279)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:233)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy34.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
    yments(ServerMBean_CachingStub.java:2706)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
    er(ApplicationManager.java:360)
    at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
    nManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy48.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
    .start(ApplicationManagerMBean_CachingStub.java:479)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
    at weblogic.management.Admin.finish(Admin.java:561)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
    at weblogic.Server.main(Server.java:35)
    >
    <Jan 31, 2002 3:56:18 PM PST> <Error> <J2EE> <Error deploying application
    Defaul
    tVoiceApp: Could not load DefaultVoiceApp>
    java.lang.reflect.UndeclaredThrowableException:
    weblogic.xml.dom.DOMProcessingEx
    ception: Could not setup environment for EJBReference or ResourceReference.
    Can
    not find WEB-INF/weblogic.xml in the Web application.
    at weblogic.servlet.internal.WebAppServletContext.initFromDescriptors(We
    bAppServletContext.java:1509)
    at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletCont
    ext.java:871)
    at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletCo
    ntext.java:806)
    at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:413)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:144)
    at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServe
    r.java:76)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy35.addWebDeployment(Unknown Source)
    at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDe
    ployment(WebServerMBean_CachingStub.java:1093)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:315)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:279)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:233)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy34.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
    yments(ServerMBean_CachingStub.java:2706)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
    er(ApplicationManager.java:360)
    at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
    nManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy48.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
    .start(ApplicationManagerMBean_CachingStub.java:479)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
    at weblogic.management.Admin.finish(Admin.java:561)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
    at weblogic.Server.main(Server.java:35)
    --------------- nested within: ------------------
    weblogic.j2ee.DeploymentException: Could not load DefaultVoiceApp - with
    nested
    exception:
    [weblogic.xml.dom.DOMProcessingException: Could not setup environment for
    EJBRef
    erence or ResourceReference. Cannot find WEB-INF/weblogic.xml in the Web
    applic
    ation.]
    at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:416)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:144)
    at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServe
    r.java:76)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy35.addWebDeployment(Unknown Source)
    at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDe
    ployment(WebServerMBean_CachingStub.java:1093)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:315)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:279)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:233)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy34.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
    yments(ServerMBean_CachingStub.java:2706)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
    er(ApplicationManager.java:360)
    at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
    nManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy48.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
    .start(ApplicationManagerMBean_CachingStub.java:479)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
    at weblogic.management.Admin.finish(Admin.java:561)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
    at weblogic.Server.main(Server.java:35)
    Can someone help me on what to set in sequence please. Any help would highly
    be appreciated.
    Thanks in advance.
    Regards
    Aru

    Aaru,
    Verify the document structure @
    http://e-docs.bea.com/wls/docs61/ejb/reference.html#1026457
    jndi-name is of the ejb is missing in your WEJ.xml
    and the jndi-name defined under
    <reference-descriptor><ejb-reference-description>
    </reference-descriptor></ejb-reference-description>
    is the reference jndi-name(referenced by this bean)
    For more info refere
    the weblogic 6.x dtd
    http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd
    Venki..
    Aru wrote:
    As per the doc that you referred, the doc too says that the jndi-name should
    be within the ejb-reference-description which in turn is inside the
    reference-descriptor. I don't get what you tried to say. Am I missing
    anything? Could you please make sure that for me.
    Just with curiosity I even tried your suggestion but it gives me the
    exception as expected,
    The XML parser encountered an error in your deployment descriptor. Please
    ensure
    that your deployment descriptor corresponds to the format in the DTD. The
    error
    was:
    org.xml.sax.SAXParseException: The content of element type
    "ejb-reference-descr
    iption" is incomplete, it must match "(ejb-ref-name,jndi-name)".
    "Venki Seshaadri" <[email protected]> wrote in message
    news:[email protected]...
    Aaru,
    <jndi-name> should be outside <reference-descriptor>
    refer to http://e-docs.bea.com/wls/docs61/ejb/reference.html#1026457
    <weblogic-enterprise-bean>
    <reference-descriptor>...</reference-descriptor>
    <jndi-name>ejb/ABCD</jndi-name>
    </weblogic-enterprise-bean>
    Hope this helps,
    Venki
    [email protected]
    Aru wrote:
    FYI, I am using Weblogic 6.1
    "Aru" <[email protected]> wrote in message
    news:[email protected]...
    Could someone help me on how to configure an ejb-reference in the 3 xml
    files.
    ejb-jar.xml, weblogic-ejb-jar.xml and web.xml
    These are the entries for my application, but I get some exception. Can
    somebody help me pls?
    ejb-jar.xml
    <enterprise-beans>
    <session id="Abcd">
    <small-icon></small-icon>
    <ejb-name>ABCD</ejb-name>
    <home>AbcdHome</home>
    <remote>AbcdRemote</remote>
    <ejb-class>AbcdBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    web.xml contains the foll,
    <ejb-ref>
    <ejb-ref-name>ejb/abcd</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <home>AbcdHome</home>
    <remote>AbcdRemote</remote>
    <ejb-link>ABCD</ejb-link>
    </ejb-ref>
    weblogic.ejb-jar.xml contains,
    <weblogic-enterprise-bean>
    <ejb-name>ABCD</ejb-name>
    <caching-descriptor>
    <max-beans-in-free-pool>100</max-beans-in-free-pool>
    </caching-descriptor>
    <reference-descriptor>
    <ejb-reference-description>
    <ejb-ref-name>ejb/abcd</ejb-ref-name>
    <jndi-name>ejb/ABCD</jndi-name>
    </ejb-reference-description>
    </reference-descriptor>
    </weblogic-enterprise-bean>
    But when i run the application, I get the foll exception,
    In EJB RemotePlatform, a session or entity bean that has a remote home m
    ust be given a JNDI name in the weblogic-ejb-jar.xml descriptor file.
    at weblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChe
    cker.java:256)
    at weblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJ
    BComplianceChecker.java:220)
    at weblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:4
    52)
    at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:409)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:202)
    at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
    at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:676)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:843)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:279)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:233)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy34.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
    yments(ServerMBean_CachingStub.java:2706)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
    er(ApplicationManager.java:360)
    at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
    nManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy48.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
    .start(ApplicationManagerMBean_CachingStub.java:479)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
    at weblogic.management.Admin.finish(Admin.java:561)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
    at weblogic.Server.main(Server.java:35)
    <Jan 31, 2002 3:56:18 PM PST> <Error> <J2EE> <Error deploying
    application
    Defaul
    tVoiceApp: Could not load DefaultVoiceApp>
    java.lang.reflect.UndeclaredThrowableException:
    weblogic.xml.dom.DOMProcessingEx
    ception: Could not setup environment for EJBReference or
    ResourceReference.
    Can
    not find WEB-INF/weblogic.xml in the Web application.
    at weblogic.servlet.internal.WebAppServletContext.initFromDescriptors(We
    bAppServletContext.java:1509)
    at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletCont
    ext.java:871)
    at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletCo
    ntext.java:806)
    at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:413)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:144)
    at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServe
    r.java:76)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy35.addWebDeployment(Unknown Source)
    at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDe
    ployment(WebServerMBean_CachingStub.java:1093)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:315)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:279)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:233)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy34.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
    yments(ServerMBean_CachingStub.java:2706)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
    er(ApplicationManager.java:360)
    at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
    nManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy48.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
    .start(ApplicationManagerMBean_CachingStub.java:479)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
    at weblogic.management.Admin.finish(Admin.java:561)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
    at weblogic.Server.main(Server.java:35)
    --------------- nested within: ------------------
    weblogic.j2ee.DeploymentException: Could not load DefaultVoiceApp - with
    nested
    exception:
    [weblogic.xml.dom.DOMProcessingException: Could not setup environment
    for> >>>>EJBRef>>>>erence or ResourceReference. Cannot find WEB-INF/weblogic.xml in the Web>>>>applic>>>>ation.
    at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:416)
    at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:144)
    at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServe
    r.java:76)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy35.addWebDeployment(Unknown Source)
    at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDe
    ployment(WebServerMBean_CachingStub.java:1093)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
    oymentTarget.java:315)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
    loymentTarget.java:279)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
    ments(DeploymentTarget.java:233)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
    DeploymentTarget.java:193)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy34.updateDeployments(Unknown Source)
    at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
    yments(ServerMBean_CachingStub.java:2706)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
    er(ApplicationManager.java:360)
    at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
    nManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy48.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
    .start(ApplicationManagerMBean_CachingStub.java:479)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
    at weblogic.management.Admin.finish(Admin.java:561)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
    at weblogic.Server.main(Server.java:35)
    Can someone help me on what to set in sequence please. Any help would
    highly
    be appreciated.
    Thanks in advance.
    Regards
    Aru

  • Deployment descriptor error for an EJB 3.0 entity bean module

    Hi all,
    i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
    The application is composed as follows:
    WASEnterprise.ear
    |-META-INF
    |-application.xml
    |-WAS.jar
    |-META-INF
    |-persistence.xml
    In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
    <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
    The persistence.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence>
    <persistence-unit name="CNT4">
    <non-jta-data-source>cnt5ds</non-jta-data-source>
    <class>it.eni.italgas.was.db.entity.AsiDisco</class>
    <class>it.eni.italgas.was.db.entity.AsiErrori</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
    <class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
    </persistence-unit>
    </persistence>
    and the application.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
    <display-name>WASEnterprise</display-name>
    <module id="myeclipse.1188512259959">
    <ejb>WAS.jar</ejb>
    </module>
    </application>
    I don't use any other weblogic specific deployment descriptor.
    Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
    Thanks inadvance.
    Denis Maggiorotto

    Hi all,
    i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
    The application is composed as follows:
    WASEnterprise.ear
    |-META-INF
    |-application.xml
    |-WAS.jar
    |-META-INF
    |-persistence.xml
    In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
    <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
    The persistence.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence>
    <persistence-unit name="CNT4">
    <non-jta-data-source>cnt5ds</non-jta-data-source>
    <class>it.eni.italgas.was.db.entity.AsiDisco</class>
    <class>it.eni.italgas.was.db.entity.AsiErrori</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
    <class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
    </persistence-unit>
    </persistence>
    and the application.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
    <display-name>WASEnterprise</display-name>
    <module id="myeclipse.1188512259959">
    <ejb>WAS.jar</ejb>
    </module>
    </application>
    I don't use any other weblogic specific deployment descriptor.
    Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
    Thanks inadvance.
    Denis Maggiorotto

  • Problem generating stubs for Java EJB web service deployed in OAS

    I created an EJB web service and I've successfully deployed it in my Oracle App Server. Some of the methods work fine but others produce the ff error:
    org.apache.soap.SOAPException - java.lang.IllegalArgumentException: No Serializer found to serialize [classname] using encoding style [encoding]It seems that the objects specified as parameters in the web service methods exposed are the only ones that had stubs generated for them. Other objects I use, which are usually wrapped inside a Vector, did not have generated stubs.
    Example:
         public String loginUser(UserDTO userDTO) throws RemoteException, NamingException, SQLException;
    public String addItems (Vector vecItems) throws RemoteException, NamingException, SQLException; // where vecItems is a collection of ItemDTO objects     In this scenario, stubs were generated for the UserDTO class, but not for the ItemDTO class. In effect, calling the addItems method resulted to the exception I mentioned above.
    I did a workaround wherein I declared a dummy method which accepted all the types of objects I needed as parameters so all the necessary stubs can be generated, but this fix doesn't feel like it's the proper solution to my problem.
    If anyone can help me, it would be greatly appreciated. Thanks!

    Crossposted:
    Problem generating stubs for Java EJB web service deployed in OAS

  • Alternate deployment descriptor for an exploded war (web.xml/weblogic.xml)

    Hi.
    I believe this is a simple question: Am i able to deploy an exploded war directory using an alternate deployment descriptor (web.xml outside the directory structure of my application)? According to the docs, I can do it for an ear, but I'm not sure if it can be done for an war.
    http://download.oracle.com/docs/cd/E13222_01/wls/docs81b/deployment/concepts.html#1001945
    http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/Application.html#AltDescriptorPath
    Thanks in advance.
    Best regards,
    Daniel.

    Or should i use a deployment plan?
    http://download.oracle.com/docs/cd/E13222_01/wls/docs103/deployment/config.html#wp1057141

  • How to edit web.xml deployment descriptor from console in weblogic 8.1?

    In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
    console, but on weblogic 8.1 I can't find a way to do so.
    Is this function taken out? Why is it taken out? Do I have an alternative to edit
    it without unpacking and packing the EAR or WAR?
    Thanks in advance.
    Bill

    In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
    console, but on weblogic 8.1 I can't find a way to do so.
    Is this function taken out? Why is it taken out? Do I have an alternative to edit
    it without unpacking and packing the EAR or WAR?
    Thanks in advance.
    Bill

  • J2EE:160043]Missing deployment descriptor "WEB-INF/web.xml"

    Hi ,
    When I try to deploy using admin console i get the following error msg.
    J2EE:160043]Missing deployment descriptor "WEB-INF/web.xml"
    The war file has web.xml.
    Can some give me the reason for the above error.
    LOG content:
    weblogic.management.ApplicationException: [J2EE:160043]Missing deployment descriptor
    "WEB-INF/web.xml" at "C:\bea8\user_projects\domains\eConnect\applications\myEconnect.war"
         at weblogic.j2ee.J2EEApplicationContainerFactory.handleError(J2EEApplicationContainerFactory.java:729)
         at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:470)
         at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:833)
         at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:63)
         at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1499)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1490)
         at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:186)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.runtime.DeployerRuntimeMBean_Stub.activate(DeployerRuntimeMBean_Stub.java:1064)
         at weblogic.management.console.actions.mbean.WebAppComponentDeployAction.prePerform(WebAppComponentDeployAction.java:141)
         at weblogic.management.console.actions.mbean.DoMBeanWizardAction.perform(DoMBeanWizardAction.java:215)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

    You'll have to at least show me the out contents of that WAR file.
    -- Rob
    Sowjanya wrote:
    Suppose the directory structure of the appl is c:\myroot\webapp\...
    then we need to go to webapp and then build the war file.
    C:\myroot\webapp>jar -cvf abc.war *
    then copy the war file and paste it in applicaitons folder.
    "sowjanya" <[email protected]> wrote:
    Hi ,
    When I try to deploy using admin console i get the following error msg.
    J2EE:160043]Missing deployment descriptor "WEB-INF/web.xml"
    The war file has web.xml.
    Can some give me the reason for the above error.
    LOG content:
    weblogic.management.ApplicationException: [J2EE:160043]Missing deployment
    descriptor
    "WEB-INF/web.xml" at "C:\bea8\user_projects\domains\eConnect\applications\myEconnect.war"
         at weblogic.j2ee.J2EEApplicationContainerFactory.handleError(J2EEApplicationContainerFactory.java:729)
         at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:470)
         at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:833)
         at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:63)
         at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1499)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1490)
         at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:186)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.runtime.DeployerRuntimeMBean_Stub.activate(DeployerRuntimeMBean_Stub.java:1064)
         at weblogic.management.console.actions.mbean.WebAppComponentDeployAction.prePerform(WebAppComponentDeployAction.java:141)
         at weblogic.management.console.actions.mbean.DoMBeanWizardAction.perform(DoMBeanWizardAction.java:215)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Maybe you are looking for

  • Reg: Getting started with Predictive Workbench

    Hello All, I am a newbie to Business Objects. I have Business Objects XI 3.1 installed. I am using Web Intelligence Rich Client to create reports. I just checked that Predictive Workbench is a tool which can be used for statistical analysis. This wil

  • Cloning 11.5.10.2 from RHEL3 to RHEL5

    Hi My application is running fine on RHEL3 and can to cloned to the same OS. Now I got new servers and wanted to shift on RHEL5. I can INSTALL a new instance on it using Rapid Wizard which works fine but when I try to clone my existing instance it gi

  • Exception jsp custom tag in IBM AIX

              Hello, this is the scenario.           WebLogic Server 5.1 sp6 on IB AIX           The WLS is standalone; there is a servlet that make a forward to a frameset with           three frame; each frame has a jsp which take data by an http sessi

  • Had to reformat my hard drive- PLEASE HELP!

    Hi everyone, I hope someone can somehow help me. I tried tech support but they didn't have much to offer in the way of iTunes support. I own a video ipod. I manually loaded each of the albums I had stored in my "my music" folder on my laptop into iTu

  • Why do my emails not show images?

    I recently downloaded os x 10.9.  Today, all incoming emails are not showing any images.  Can you help me fix this?  I have tried everything I can think of and don't see any settings that might be set wrong.  But, there must be.  Please help