Tag Archives: deploy

Class Not Found exception while deploying the application


If you are getting class not found exception for a particular library upon deploying the application then check If the ‘Deploy by default’ option is checked for the library in your application.

If the library is referred in the Weblogic-application.xml then make sure that the library has to be deployed to the server. This will be referred in you Weblogic-application.xml as

<library-ref>
<library-name>adf.oracle.domain</library-name>
</library-ref>
Advertisements

Ojdeploy – how to include taskflow related files to include


When you build trough ojdeploy the task flow related files like page-template.xml, task-flow-registry.xml are not added in the deployed adf library.

to include that we have remove the entry in the ojdeploy snippet

<ora:parameter name="nocompile" value="true"/>

more information is here

http://one-size-doesnt-fit-all.blogspot.com/2010/11/using-ojdeploy-and-ant-for-creating-adf.html


Creating a simple extension for jdeveloper


First you have to create a generic Application by selecting from File -> New -> General -> Generic Application

Name the application and create a new Extension project for the application by selecting File -> New -> Projects -> Extension Project

The Create Extension Project wizard will help you specify the project details

The new Extension project will have the structure like

The properties of the project is to be configured as shown in the figure

Open the extension.xml from META-INF folder. In the overview tab you will find General, Dependencies and Hooks panels

General – Will have all general information like name, version, owner etc

source:

Dependencies – Will have references to the extension dependencies. The classpath reference is also included

source:

Hooks – Will have the points at which the extension will be added to the Jdeveloper ide.

Each individual hook allows an extension to provide specific binding information to plug into different areas of an IDE. Here are the main areas where extensions plug-in:

  1. Menus and commands through the menu-hook,
  2. Document model through the document-hook,
  3. IDE events through the ide-listener-hook,
  4. Custom editors through the editor-hook,
  5. IDE preferences and project settings through the property-hook,
  6. Log pages through the log-hook
  7. New wizards through the wizard-hook, and
  8. The compiler through the build-system-hook.
  9. The feature-hook allows extensions to appear in an IDE’s extension management UI as features that can be enabled/disabled.
  10. The custom-hook and hook-handlers allows extensions to define their own extension points.

source:

Running the extension is to right-click the project and say Run Extension

The deployed extension will be seen from Tools menu and preferences

The sample project can be downloaded from here

For details on the tags in the extension.xml file, see the file JDEV_HOME/jdev/doc/extension/ide-extension-packaging.html

Each individual hook allows an extension to provide specific binding information to plug into different areas of an IDE. Here are the main areas where extensions plug-in:

  1. Menus and commands through the menu-hook,
  2. Document model through the document-hook,
  3. IDE events through the ide-listener-hook,
  4. Custom editors through the editor-hook,
  5. IDE preferences and project settings through the property-hook,
  6. Log pages through the log-hook
  7. New wizards through the wizard-hook, and
  8. The compiler through the build-system-hook.
  9. The feature-hook allows extensions to appear in an IDE’s extension management UI as features that can be enabled/disabled.
  10. The custom-hook and hook-handlers allows extensions to define their own extension points.

Unable to deploy EJB: ejb_ob_engine_wls.jar from ejb_ob_engine_wls.jar


If your soa server is up but your soa_infra is down then search for the following error in
$DOMAIN_HOME\servers\soa_server1\logs\soa_server1.log

weblogic.application.ModuleException: Exception preparing module: EJBModule(ejb_ob_engine_wls.jar)

Unable to deploy EJB: ejb_ob_engine_wls.jar from ejb_ob_engine_wls.jar:

There are 1 nested errors:

java.io.IOException: JDT compilation error!
 FacadeFinderBean_4vacyo_FacadeFinderBeanImpl.java: The method getMBeanAttribute(String, String) is undefined for the type FacadeFinderBean_4vacyo_Intf
 FacadeFinderBean_4vacyo_FacadeFinderBeanImpl.java: The method getNumberOfCompositeInstancesByPartitions(String[]) is undefined for the type FacadeFinderBean_4vacyo_Intf
 FacadeFinderBean_4vacyo_FacadeFinderBeanImpl.java: The method listComposites() is undefined for the type FacadeFinderBean_4vacyo_Intf
 FacadeFinderBean_4vacyo_FacadeFinderBeanImpl.java: The method invokeMBeanOperation(String, String, String[], Object[]) is undefined for the type FacadeFinderBean_4vacyo_Intf
 FacadeFinderBean_4vacyo_FacadeFinderBeanImpl.java: The method setMBeanAttribute(String, String, Object) is undefined for the type FacadeFinderBean_4vacyo_Intf
 FacadeFinderBean_4vacyo_FacadeFinderBeanImpl.java: The method getNumberOfFaultedCompositeInstancesByPartitions(String[]) is undefined for the type FacadeFinderBean_4vacyo_Intf
 at weblogic.ejb.container.ejbc.CompilerForJDT.compile(CompilerForJDT.java:57)
 at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:485)
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:452)
 at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:439)
 at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:779)
 at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:679)
 at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1237)
 at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:440)
.....
.....

Then install the SOA patchset installer (11.1.1.3) on top of your existing SOA suite 11.1.1.2