Weblogic Deployment Descriptor for CMP EJB

Hi all,
Am new to EJB, CMP. Pls help me how to write deployment descriptors for the CMP EJB for Weblogic.
Give me the list of the Deployment descriptors needed and also pls give me some samples
thanks in advance
rgds
Ravi Bharathi

The easiest way is to go through some tutorial or refer the code samples. If you have installed weblogic, there are examples provided in the weblogic installation folder itself for each type of bean. Basically for cmp you have to provide the table names and mapping between the class variables to db fields in weblogic_cmp_rdbms.xml deployment descriptor.

Similar Messages

  • How To Define Security in the deployment descriptor for an ejb

    Hi All
    Pls help!
    I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
    But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
    Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
    Thanks
    Yours in Java

    Hi All
    Pls help!
    I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
    But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
    Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
    Thanks
    Yours in Java

  • Plugin to migrate deployment descriptors for J2EE apps

    I was told there is a JDev 10g plugin that deals with migration of deployment descriptors for different kinds of J2EE application servers.
    If it is true, what is the plugin name? Is it already contained within JDev or we are supposed to download and install it?
    Regards,
    Eduardo Gouvea.

    Have a look at the deployment desriptor category in the JDeveloper new gallery - you'll see support for OC4J, JBoss, and Weblogic built-in.

  • Failed to save deployment descriptor for: EEdnc cause: null

    I am getting nowhere fast trying to deploy an ear with 1 EJB jar and a war file.
    The war deploys by itself ok. So the EJB jar has 2 stateless beans and an MDB
    configured for mqseries. I deployed a sample with some EJBs so the configuration
    must be ok. It verifies with no errors, compiles with ejbc, javac and rmi ok. then I get
    this error...
    I was wondering if anyone has run into this before or if an expert knows what it is.
    I have been using the admin console to deploy as well as asadmin.
    \j2ee-apps\EEdnc\com\boeing\bca\ednc\ejbcontainer\services\imsaccess\_IMSAccess_Stub.class
    [24/Sep/2003:10:47:33] INFO ( 1564): DPL5110: EJBC - END of EJBC for [EEdnc]
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]uid: 69758199598546944
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: BoltsReceiver
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546944
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: IMSAccess
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546945
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: JmsEjb
    [24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546946
    [24/Sep/2003:10:47:33] FINE ( 1564): Saving the app descriptor....................
    [24/Sep/2003:10:47:33] WARNING ( 1564): DPL5035:Error while running ejbc
    com.iplanet.ias.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: EEdnc
    cause: null
         at com.iplanet.ias.deployment.backend.EJBCompiler.wrapException(EJBCompiler.java:589)
         at com.iplanet.ias.deployment.backend.EJBCompiler.compile(EJBCompiler.java:186)
         at com.iplanet.ias.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:215)
         at com.iplanet.ias.deployment.backend.AppDeployer.deploy(AppDeployer.java:98)
         at com.iplanet.ias.deployment.backend.AppDeployer.doRequest(AppDeployer.java:50)
         at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(ManagedServerInstance.java:745)
         at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInstance.java:667)
         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 com.iplanet.ias.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:188)
         at com.iplanet.ias.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:137)
         at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:222)
         at com.iplanet.ias.admin.servermodel.controllers.SOMRequestDispatcher.invoke(SOMRequestDispatcher.java:88)
         at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.doDeploy(AppServerInstanceController.java:2244)
         at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.deployApplication(AppServerInstanceController.java:1099)
         at com.iplanet.ias.admin.servermodel.AppServerInstance.deployApplication(AppServerInstance.java:249)
         at com.iplanet.ias.admin.server.gui.jato.DeployEARApplicationViewBean.add(DeployEARApplicationViewBean.java:111)
         at com.iplanet.ias.admin.server.gui.jato.IASViewBean.handleOkRequest(IASViewBean.java:235)
         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 com.iplanet.jato.view.command.DefaultRequestHandlingCommand.execute(DefaultRequestHandlingCommand.java:183)
         at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:299)
         at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:811)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:749)
         at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:596)
         at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:772)
         at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:446)
         at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:324)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
         at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
         at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
         at org.apache.catalina.core.StandardHostValve.invoke(Standar
    [24/Sep/2003:10:47:34] WARNING ( 1564): Deployment Error
    com.iplanet.ias.deployment.backend.IASDeploymentException: Error while running ejbc -- Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: EEdnc
    cause: null

    I don't remember exactly what it was, but I think it was a JNDI name. I resolved it by using
    <ejb-link></ejb-link> in the ejb-local-ref in the ejb-jar.xml. I made the ejb-link match the
    ejb-name in the same descriptor. This seemed to work better than changing the jndi-name in the sun-ejb-jar.xml.
    One thing you can do is set the logging for server1 to finest, then bounce the server and deploy.
    Shut down the server and look at the log with wordpad. Start at the bottom and work your
    way up looking for stack traces. They get more and more detailed as you go up and may
    point you to the exact problem. Works most of the time.

  • Weblogic 12 deployment failure for an EJB

    EJBAn ear deployment is failing while trying to deploy on Weblogic 12.1.1 whereas it is getting deployed on Weblogic 11
    Unable to deploy EJB: /opt/app/bbnms/cim/domains/JEE/cim/WLS/cim/servers/sync_server1/tmp/_WL_user/ATT_Discovery_Service/yx56mr/ndc-ejb-jar.jar from ndc-ejb-jar.jar:
    011113
    weblogic.application.ModuleException: Exception preparing module: EJBModule(ndc-ejb-jar.jar)
    Unable to deploy EJB: /opt/app/bbnms/cim/domains/JEE/cim/WLS/cim/servers/sync_server1/tmp/_WL_user/ATT_Discovery_Service/yx56mr/ndc-ejb-jar.jar from ndc-ejb-jar.jar:
    011113
            at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:447)
            at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:188)
            at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:83)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
            at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:172)
            at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:167)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
            at weblogic.application.internal.flow.ModuleStateDriver.prepare(ModuleStateDriver.java:38)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:139)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:55)
            at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:706)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
            at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:237)
            at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:61)
            at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:158)
            at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
            at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:155)
            at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
            at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
            at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
            at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
            at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
            at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
            at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:186)
            at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:94)
            at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: 011113 NestedException Message is :011113
    at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.<init>(MessageDrivenBeanInfoImpl.java:739)
            at weblogic.ejb.container.deployer.BeanInfoFactory.createBeanInfoImpl(BeanInfoFactory.java:36)
            at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:546)
            at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:242)
            at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:864)
            at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:419)

    If Message Driven Beans implements more than one interface, the error "011113 NestedException Message is :011113" occurs
    For example:
    class OurMDB implements javax.jms.MessageListener, Interface2
       public void onMessage(Message msg)
    Its a bug in 12c...
    To solve the issue, apply patch provided in the Defect 13984579.
    Hope it helps!!
    Vijaya
    =====

  • Deployment Descriptor for SOA-SAR files on weblogic?

    Hi,
    i want to access a shared library (that i deployed separately) from within a SOA Project with an SCA composite that is deployed as a SOA-SAR.
    I am using JDeveloper 11.1.1.3 along with the according Weblogic Server and SOA Suite.
    My shared library is deployed correctly, because i can access it from e.g. other web applications. These are deployed as war files and therefore i have a weblogic.xml file, where i define my library-refs. The problem is, that weblogic.xml as well as weblogic-application.xml seem not to be processed when deploying the SOA-SAR file. Is there another descriptor for that, or is it just not possible to access shared libraries from within a SOA Project deployed as SOA-SAR?
    For some more background information, i have my entities deployed as a shared library in weblogic (deployed as a web application(war file)). Now i want to create an SCA composite with a Spring component. A Bean defined in the Spring context shall access the entities from within the shared library.
    I hope someone has a solution for this, because i already spent a lot of time on searching for a solution and did not even get close to one. The closest solution i found was deploying the SCA composite as a web application using in Spring the sca:service tag. In that case i have the problem that i want to use the SCA composite from within another SCA composite and i want it to use a local call, not a SOAP request for performance reasons. So this solution unfortunately doesn't fit my requirements.

    Please ask this in the SOA Suite forum:
    SOA Suite
    You might also find the answer in the SOA Suite 11g docs:
    http://download.oracle.com/docs/cd/E12839_01/soa.htm

  • 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

  • Problems in configuring deployment descriptors to use EJB in JSP

              Hello,
              I've been trying to use an EJB in a JSP on Weblogic 8.1. The relevent part of
              my web.xml and weblogic.xml look like this:
              =====================================
              web.xml -
              <ejb-ref>
              <description>Purchase order bean deployed</description>
              <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
              <ejb-ref-type>Entity</ejb-ref-type>
              <home>mypackage2.PurchaseorderHome</home>
              <remote>mypackage2.Purchaseorder</remote>
              <ejb-link>/PO.jar#Purchaseorder</ejb-link>
              </ejb-ref>
              <ejb-local-ref>
              <description>purchase order</description>
              <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
              <ejb-ref-type>Entity</ejb-ref-type>
              <local-home>mypackage2.PurchaseorderLocalHome</local-home>
              <local>mypackage2.PurchaseorderLocal</local>
              <ejb-link>/PO.jar#Purchaseorder</ejb-link>
              </ejb-local-ref>
              =====================================
              weblogic.xml -
              <ejb-reference-description>
              <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
              <jndi-name>Purchaseorder</jndi-name>
              </ejb-reference-description>
              </reference-descriptor>
              =================================
              My ejb-jar.xml file looks like this (this EJB jar is already deployed on Weblogic):
              <description>Entity Bean ( CMP )</description>
              <display-name>Purchaseorder</display-name>
              <ejb-name>Purchaseorder</ejb-name>
              <home>mypackage2.PurchaseorderHome</home>
              <remote>mypackage2.Purchaseorder</remote>
              <local-home>mypackage2.PurchaseorderLocalHome</local-home>
              <local>mypackage2.PurchaseorderLocal</local>
              <ejb-class>mypackage2.PurchaseorderBean</ejb-class>
              ==============================================
              Finally, my weblogic-ejb-jar.xml looks like this:
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
              <ejb-name>Purchaseorder</ejb-name>
              <jndi-name>Purchaseorder</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              ===============================================
              But despite many many efforts, I keep getting the following error:
              Could not setup environment - with nested exception: [weblogic.deployment.EnvironmentException:
              [J2EE:160101]Error: The ejb-link '/PO.jar#Purchaseorder' declared in the ejb-ref
              or ejb-local-ref 'ejb/Purchaseorder' in the application module 'public_html' could
              not be resolved. The target EJB for the ejb-ref could not be found. Please ensure
              the link is correct.] weblogic.deployment.EnvironmentException: [J2EE:160101]Error:
              The ejb-link '/PO.jar#Purchaseorder' declared in the ejb-ref or ejb-local-ref
              'ejb/Purchaseorder' in the application module 'public_html' could not be resolved.
              The target EJB for the ejb-ref could not be found. Please ensure the link is correct.
              at
              I have changed around a lot of things. I've a classes directory under web-inf
              where I have mypackage2\all-the-class-files. I've also made available PO.jar file
              (which contains Purchaseorder) at various levels to ensure that the class can
              be found. I've changed the "/PO.jar#Purchaseorder" value of <ejb-link> tag accordingly
              to try various things. (e.g ejb/Purchaseorder, mypackage2.Purchaseorder, and a
              lot of other things) but of no avail. I keep getting the same error over and over
              again. (Do you think banging my head on the wall would do the trick?)
              Any help would be greatly appreciated. Thanks.
              

              Sam, thanks for the explanation. It makes sense now that why it's not working.
              But is this specific to Weblogic? I'm actually using JDevloper to develop my
              EJB (CMP) and JSP. Within JSP, I can use the tag library ejbtag provided by Oracle
              to specify home, create instance, and get collection back from an EJB. I've specify
              the tag lib URI in the web.xml but I kept getting the error message in Weblogi
              when running the test to load JSP saying that it could not find the EJB (Purchaseorder)
              specified. That led me to do some research and I came accross the <ejb-ref> and
              <ejb-link> tags.
              If it is a restriction only posed by Weblogic then I guess I'll have to create
              a JavaBean to interact with EJB first and then get the collection.
              Thanks.
              Sam Pullara <[email protected]> wrote:
              >You can only use ejb-links when connecting to EJBs that are in the same
              >
              >application (ear). If you want to have them separate you will have to
              >
              >use a global JNDI name for the EJB and look up that.
              >
              >Sam
              >
              >A Roman wrote:
              >> Michael,
              >>
              >> I'm not deploying EJB as an .ear application that'd include web app
              >and .jar.
              >> Instead I have deployed .jar as stand alone EJB and want to deploy
              >.war (exploded
              >> directory structure) as a seperate web app. Both .jar and .war will
              >be deployed
              >> on the same server. That's exactly why I cannot use the syntax that's
              >used in
              >> the samples.
              >>
              >> Thanks.
              >>
              >> "Michael Kovacs" <[email protected]> wrote:
              >>
              >>>I guess to start off with I'm making the assumption that your PO.jar
              >>>is your
              >>>EJB module
              >>>and that it is contained in the same EAR as your webapp module, looking
              >>>something like
              >>>this:
              >>>
              >>>myEAR.ear
              >>> |_ PO.jar
              >>> |_ webapp
              >>> |_ jspCallingEJB.jsp
              >>>
              >>>If this is correct, the first thing I'd suggest trying is to remove
              >your
              >>>"/"
              >>
              >>>from the front of your <ejb-link> and
              >>
              >>>just make the value <ejb-link>PO.jar#Purchaseorder</ejb-link>
              >>>
              >>>The EJB example that ships with 8.1 platform makes use of an EJB from
              >>>a jsp
              >>>page so you could
              >>>look to that example for some guidance, which references the EJB in
              >this
              >>>same way in the web.xml ejb-local-ref element.
              >>>hope that helps.
              >>>--
              >>>Michael Kovacs
              >>>Senior Software Engineer
              >>>BEA Systems
              >>>"ARoman" <[email protected]> wrote in message
              >>>news:[email protected]...
              >>>
              >>>>Hello,
              >>>>
              >>>>I've been trying to use an EJB in a JSP on Weblogic 8.1. The relevent
              >>>
              >>>part
              >>>of
              >>>
              >>>>my web.xml and weblogic.xml look like this:
              >>>>=====================================
              >>>>web.xml -
              >>>>
              >>>> <ejb-ref>
              >>>> <description>Purchase order bean deployed</description>
              >>>> <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
              >>>> <ejb-ref-type>Entity</ejb-ref-type>
              >>>> <home>mypackage2.PurchaseorderHome</home>
              >>>> <remote>mypackage2.Purchaseorder</remote>
              >>>> <ejb-link>/PO.jar#Purchaseorder</ejb-link>
              >>>>
              >>>> </ejb-ref>
              >>>>
              >>>> <ejb-local-ref>
              >>>> <description>purchase order</description>
              >>>> <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
              >>>> <ejb-ref-type>Entity</ejb-ref-type>
              >>>> <local-home>mypackage2.PurchaseorderLocalHome</local-home>
              >>>> <local>mypackage2.PurchaseorderLocal</local>
              >>>> <ejb-link>/PO.jar#Purchaseorder</ejb-link>
              >>>> </ejb-local-ref>
              >>>>=====================================
              >>>>
              >>>>weblogic.xml -
              >>>><ejb-reference-description>
              >>>><ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
              >>>><jndi-name>Purchaseorder</jndi-name>
              >>>></ejb-reference-description>
              >>>></reference-descriptor>
              >>>>=================================
              >>>>My ejb-jar.xml file looks like this (this EJB jar is already deployed
              >>>
              >>>on
              >>>Weblogic):
              >>>
              >>>>
              >>>> <description>Entity Bean ( CMP )</description>
              >>>> <display-name>Purchaseorder</display-name>
              >>>> <ejb-name>Purchaseorder</ejb-name>
              >>>> <home>mypackage2.PurchaseorderHome</home>
              >>>> <remote>mypackage2.Purchaseorder</remote>
              >>>> <local-home>mypackage2.PurchaseorderLocalHome</local-home>
              >>>> <local>mypackage2.PurchaseorderLocal</local>
              >>>> <ejb-class>mypackage2.PurchaseorderBean</ejb-class>
              >>>> ==============================================
              >>>>Finally, my weblogic-ejb-jar.xml looks like this:
              >>>>
              >>>><weblogic-ejb-jar>
              >>>> <weblogic-enterprise-bean>
              >>>> <ejb-name>Purchaseorder</ejb-name>
              >>>> <jndi-name>Purchaseorder</jndi-name>
              >>>> </weblogic-enterprise-bean>
              >>>></weblogic-ejb-jar>
              >>>>===============================================
              >>>>
              >>>>But despite many many efforts, I keep getting the following error:
              >>>>
              >>>>Could not setup environment - with nested exception:
              >>>
              >>>[weblogic.deployment.EnvironmentException:
              >>>
              >>>>[J2EE:160101]Error: The ejb-link '/PO.jar#Purchaseorder' declared
              >in
              >>>
              >>>the
              >>>ejb-ref
              >>>
              >>>>or ejb-local-ref 'ejb/Purchaseorder' in the application module
              >>>
              >>>'public_html' could
              >>>
              >>>>not be resolved. The target EJB for the ejb-ref could not be found.
              >>>
              >>>Please
              >>>ensure
              >>>
              >>>>the link is correct.] weblogic.deployment.EnvironmentException:
              >>>
              >>>[J2EE:160101]Error:
              >>>
              >>>>The ejb-link '/PO.jar#Purchaseorder' declared in the ejb-ref or
              >>>
              >>>ejb-local-ref
              >>>
              >>>>'ejb/Purchaseorder' in the application module 'public_html' could
              >not
              >>>
              >>>be
              >>>resolved.
              >>>
              >>>>The target EJB for the ejb-ref could not be found. Please ensure the
              >>>
              >>>link
              >>>is correct.
              >>>
              >>>>at
              >>>>
              >>>>I have changed around a lot of things. I've a classes directory under
              >>>
              >>>web-inf
              >>>
              >>>>where I have mypackage2\all-the-class-files. I've also made available
              >>>
              >>>PO.jar file
              >>>
              >>>>(which contains Purchaseorder) at various levels to ensure that the
              >>>
              >>>class
              >>>can
              >>>
              >>>>be found. I've changed the "/PO.jar#Purchaseorder" value of <ejb-link>
              >>>
              >>>tag
              >>>accordingly
              >>>
              >>>>to try various things. (e.g ejb/Purchaseorder, mypackage2.Purchaseorder,
              >>>
              >>>and a
              >>>
              >>>>lot of other things) but of no avail. I keep getting the same error
              >>>
              >>>over
              >>>and over
              >>>
              >>>>again. (Do you think banging my head on the wall would do the trick?)
              >>>>
              >>>>Any help would be greatly appreciated. Thanks.
              >>>>
              >>>
              >>>
              >>
              >
              >
              

  • Additional field in join table for CMP EJB

    Hello,
    I'm trying to perform this task using CMP entity beans:
    The entity A has a CMR relation of cardinality m-n with entity B (bidirectional) (This is working fine).
    I want to add a parameter to the relation.
    Ex : When I find that A1 is linked to B1, I need to perform "x" times an action. x would be my parameter, and I would have kept this parameter as an additional column in the join table A_TO_B.
    Could anyone provide an example of how to perform this with CMP EJB?
    NOTE: I'm using OC4J 10g 9.0.4 standalone (and cannot change my version).
    Thanks
    Tanguy

    Manohar,
    You need to create an append structure for table VBAP (for example ZAVBAP) using SE11. In this structure you create your ZZ fields. If you need a non-SAP domain/data element for your field then you need to create it first using the same transaction and activate it. Attach ZAVBAP to VBAP so the SE11 shows:
    .APPEND in the Fields column and
    ZAVBAP in the Field type column.
    Your ZZ fields will be shown automatically.
    When you have finished then activate your ZAVBAP structure. You will notice when you go VA01 (for example) that a lot of programs are being recompiled. Don't worry. It will be ok.
    The user-exit screen number for items is 8459 (in program SAPMV45A).
    Thanks,
    Wojtek

  • Problem with weblogic deployment descriptor tool (DDInit)

    Hi,
    I'm just playing with weblogic ... following their tutorual but I can't seem to run their deployment descriptor tool:
    java weblogic.ant.taskdefs.war.DDinit <folderName> gives me a NoClassDefFoundError.
    I have weblogic6.0sp1 installed with an evaluation license which has not yet expired. I have d:\bea\wlserver6.0sp1\lib in mt classpath so weblogic.jar is n there.
    When I check out the contents of the weblogic.jar file .. I can't seem to find this tool.
    Can anyone give me a clue as to what I am doing wrong?

    Here's a link describing the process. If this is what you are doing then your problem may be that 6.0 doesn't support this.
    http://edocs.bea.com/wls/docs61/programming/packaging.html#pack004

  • Problem: Editing a deployment descriptor of an EJB or WAR inside of an EAR sends things to hell

    Hello,
    I've got an EAR with utility classes in lib/ (like log4j and some other
    goodies).
    Inside my EJBs, I have manifests that have class-path entries that reference
    this and they all work upon initial load (I when they don't work because my
    beans don't load).
    When I edit my descriptors using the WebLogic console and persist my
    changes, my EJBs crap out because they can no longer load log4j. When I
    shutdown WebLogic and looked at the manifest inside the EJB inside of the
    EAR, sure enough, the class-path entry that kept the whole thing working was
    gone. WebLogic decided to instead detail a bunch of classes.
    Any workaround for this (other than to include all classes in all EJBs)?
    This prevents customers and deployers from doing their jobs. :(
    How do I report this to BEA? I poked around the website and could nary find
    a "report bug" link.
    thanks,
    greg

    Yes - getting to support should be easier ...
    www.bea.com -> Services -> Customer Support Services -> Learn More about WebSupport
    -> Register for Web Account
    Then you can follow the WebSupport link at the bottom of any page.
    Mike
    "Gregory Gerard" <[email protected]> wrote:
    Hello,
    I've got an EAR with utility classes in lib/ (like log4j and some other
    goodies).
    Inside my EJBs, I have manifests that have class-path entries that reference
    this and they all work upon initial load (I when they don't work because
    my
    beans don't load).
    When I edit my descriptors using the WebLogic console and persist my
    changes, my EJBs crap out because they can no longer load log4j. When
    I
    shutdown WebLogic and looked at the manifest inside the EJB inside of
    the
    EAR, sure enough, the class-path entry that kept the whole thing working
    was
    gone. WebLogic decided to instead detail a bunch of classes.
    Any workaround for this (other than to include all classes in all EJBs)?
    This prevents customers and deployers from doing their jobs. :(
    How do I report this to BEA? I poked around the website and could nary
    find
    a "report bug" link.
    thanks,
    greg

  • NullPointerException: setting value for CMP EJB with 1:n relationship

    Hi all,
    I have two CMP Entity EJB with relatioship 1:n.
    Setting any value for second entity throws NullPointerException
    I'm using SAP NWDS 7.0.16
    server-side: sap.com/SAP-JEE 7.00 SP16
    So far I've seen [this|CMR Nullpointer Exception; thread, discussing the same problem, but as I understood, SPs higher than SP14 should solve this problem.
    Any ideas about this?
    Renat
    Thanks in advance

    Hi,
    Can you please check your JDK version,update to latest.
    Hi,
    May be these notes might help you.
    Note 1225262 - java.lang.NullPointerException in the screen
    Note 987509 - Update of NWDS causes problems
    regards
    nag

  • JDev 10.1.3 generates incorrect getter/setter for CMP EJB 3.0 - Please help

    Hi,
    I am using JDev 10.1.3 Production and using the EJB3.0 CMP wizard to generate the code from a MySQL database. No matter what type I specify for my database columns in schema, code generator always generates the properties of type String only. e.g if a column called Age is specified as Integer in schema, the generator generates setters/getters with String type.
    Can somebody please help me.
    Regards
    Vimal

    I was able to reproduce the problem and logged bug 5035459 for now. -- thanks

  • WebLogic Deployment Descriptor

    Two questions:
    1. weblogic-ejb-jar.xml and ejb-jar.xml both have the
    resource reference elements. Why we need these elements
    in weblogic-ejb-jar.xml?
    2. In ejb-jar.xml, if you have the following:
    <ejb-ref>
    <ejb-ref-name>ejb/account/Account</ejb-ref-name>
    <ejb-ref-type>Entity</ejb-ref-type> <home>com.sun.j2ee.blueprints.customer.account.ejb.AccountHome</home>
    <remote>com.sun.j2ee.blueprints.customer.account.ejb.Account</remote>
    <ejb-link>TheAccount</ejb-link>
    </ejb-ref>
    then, in weblogic-ejb-jar.xml, you can have the following:
    <ejb-reference-description>
    <ejb-ref-name>ejb/account</ejb-ref-name>
    <jndi-name>estore/account</jndi-name>
    </ejb-reference-description>
    Why the <ejb-ref-name> has the value of "ejb/account" instead
    of "ejb/account/Account"?
    Thanks!
    Jerry

    1.
    it tells the weblogic the jndi name of the referenced ejb. You can lookup this ejb in two way. By name as using(java:comp/env/...) or by jndi lookup directly.
    2. Both should be same. have run ejbc on it, isnt gives any errors ?
    --Ashwani                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Deployment descriptor "weblogic.xml" is malformed. in managed server

    Hi All,
              Appreciate if anyone can help.
              I have set up a cluster containing two nodes - one local and other
              remote machine on weblogic 8.1.4
              then i install my application this cluster setup its working fine.
              for my requirement i upgrade the the weblogic version from 8.1.4 to
              8.1.6 .
              i upgrade through the smart update from the bea site . i upgraded both
              the node.
              i started the admin server.it started with no issue.
              my problem comes when i start the my managed server on the cluster .it
              gives me this exception.
              <HTTP> <BEA-101296> <Unable to load the default compiler class
              "com.sun.tools.javac.Main". Using the default javac compiler to compile
              JSPs.>
              i checked the classpath it has the same jdk that i used for 8.1.4
              (jdk1.4.05 from sun.)
              should i used new jdk that comes with the upgrade package of 8.1.6 like
              (jdk1.4.11)
              my class path having the weblogic jar also.
              this is my class path.:
              E:\bea\weblogic81\server\lib\weblogic.jar and other my application
              jars.
              complete exception it is shown like :
              <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
              <Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
              Module: 'Nexaweb': Public ID references the old version of the Servlet
              DTD. You must change the public ID in web.xml file to "-//Sun
              Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
              <[Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?br>Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
              Check against the DTD: org.xml.sax.SAXParseException: The content of
              element type "weblogic-web-app" must match
              "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?t*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?ontainer-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?ap?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
              (line 26, column 20).>
              Compiler class: 'com.sun.tools.javac.Main', not found
              java.lang.ClassNotFoundException: com.sun.tools.javac.Main
              at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
              at java.security.AccessController.doPrivileged(Native Method)
              at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
              at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
              at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:141)
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?6)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
              <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
              will have better performance if it is enabled. To enable
              call-by-reference, set the enable-call-by-reference element to True in
              the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
              <Failed to initialize the application Xellerate due to error
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1658)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
              at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
              at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
              at weblogic.Server.main(Server.java:32)
              ><Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
              <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
              to initialize due to failed deployments.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
              <The deployment framework was unable to resume accepting requests.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
              <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
              deployment framework was unable to resume accepting
              requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
              is unable to initialize due to failed deployments.>
              hope the scope of the questions is not too broad. Kindly let me know
              if you need more information.
              Thanks a lot.

    ram ram <> wrote:
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    Add tools.jar from your Java installation to the classpath.
    Bart
    Schelstraete Bart
    http://www.schelstraete.org
    http://www.mqseries.be

Maybe you are looking for

  • How can I find out the new row.

    I use below coding to create a new row, row =vo.createRow(); vo.insertRow(row); row.setNewRowState(Row.STATUS_INITIALIZED); My question is how I can find out it later? thx.

  • System Generator on ISE 13.1

    Hello everybody. I am experiencing problems trying to run System Generator within ISE v13.1. In order to isolate the problem I implemented a very simple design, which is only one In gateway, one Out gateway and one AddSub block. It happens that Syste

  • Color becomes corrupt when I use Image Processor

    I always use the image processor (file>scripts>image processor) to format my photos after editing. Last night in the middle of batching several sets, the processor starting saving my photos with colors that were really off. I tried closing the progra

  • Inputs required for Sales & Service scenario

    Hi All I have a situation here. I have to charge my customer for the services period. Let us say for Example my company has provided services to a customer worth 1000 dollars and now i have to invoice to the customer. But the customer pays 25% for it

  • Icloud control panel and vista

    i cant install icloud control panel 3 in my laptop that running vista and i cant find a previous one also some webpages of yours doesnt appear in ie 9 what settings must do