Trying to deploy a provider in Tomcat - Missing: oracle/bali/share...

I managed to get past some other missing JAR's, but since Oracle doesn't have any good documentation for deploying a portlet /provider in anything but OC4J, i'm stuck.
Anyone know where I can find:
oracle/bali/share/util/UnhandledException?
There is just wayyy too many files / folders in a 9iAS install .. and there is no docs on what goes where. (Thanks guys)..
Please help!
Even better would be a document that details the procedure of creating a provider in ANY j2ee container. (Not just OC4J)..
Thanks,
-Sean

Very elegant response. I do appreciate the information. It is kinda amusing to think OC4J is the only "certified" app server. One of the touted benefits of portal is that it is "100% Pure J2EE Compliant..." :0) *(insert good laugh)* Seems like Oracle would be inclined to make this information more obvious (about the provider requirements), since there are soooo many app servers out there that could host portlets. I can't see how providing 'alternative, unsupported configuration docs' could hurt.
Either way, it's no skin off my back, just a little wasted time. I will check out this 'pdksoftware.zip' and see what it gives me. I have a feeling it's the same JAR's I managed to wrangle off the PDK and server, but it's nice to know for recreating a dev environment. (And the demo I'm doing tomorrow)
Honestly, my Netbeans / Tomcat portlet development environment is very splendid! I must say, that making a change in my 'Renderer' class and having the changes appear immediately in our development portal is a very VERY good thing. (we're talkin 5 second turnaround here) The only change that requires any kind of 'reloading' is when I change my provider.xml. Just need to 'reload' the provider, and all is good again.
A year ago, there was a serious bug in JDev / OC4J in which the auto class reload feature simply did not work. I had this confirmed with a TAR. Hence the abandonment of JDev. Needless to say, I've been a very open-standards kinda person. May as well mention, JDev was too slow and painful to use for the kind of development I like. Maybe it's better now. Who knows.
As my team and I slowly shuffle the moving parts of Portal, you will surely see more of my posts. Thanks again for the help!
Cheers!
-Sean

Similar Messages

Error when trying to deploy ADF application in Java Cloud Service - SaaS Extension

Hello guys,
I'm trying to deploy a simple ADF application in "Oracle Java Cloud Service - SaaS Extension" and i'm still having the error below
The job turns to Failed at "Deploy Application" step:
Did someone already got this error ?
Thanks at advance
Sid
2014-12-10 11:06:20 PST: Starting action "Deploy Application"
2014-12-10 11:06:20 PST: Deploy Application started
2014-12-10 11:06:28 PST: weblogic.application.ModuleException: weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1531)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:488)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:44)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:573)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:327)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
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: java.security.AccessControlException: access denied ("java.net.NetPermission" "specifyStreamHandler")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:372)
at java.security.AccessController.checkPermission(AccessController.java:559)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at java.net.URL.checkSpecifyHandler(URL.java:649)
at java.net.URL.<init>(URL.java:373)
at weblogic.application.io.MergedDescriptorFinder.getSource(MergedDescriptorFinder.java:46)
at weblogic.application.io.DescriptorFinder.getSource(DescriptorFinder.java:44)
at weblogic.utils.classloaders.MultiClassFinder.getSource(MultiClassFinder.java:67)
at weblogic.application.utils.CompositeWebAppFinder.getSource(CompositeWebAppFinder.java:71)
at weblogic.servlet.internal.War$ResourceFinder.getSource(War.java:1213)
at weblogic.servlet.internal.War$ResourceFinder.getSource(War.java:1203)
at weblogic.servlet.internal.War.getResourceAsSource(War.java:512)
at weblogic.servlet.internal.WebAppServletContext.getResourceAsSource(WebAppServletContext.java:3436)
at weblogic.servlet.internal.WebAppServletContext.getResourceAsSource(WebAppServletContext.java:3427)
at weblogic.servlet.internal.WebAppServletContext.getResourceAsStream(WebAppServletContext.java:872)
at com.sun.faces.config.ConfigureListener$WebXmlProcessor.scanForFacesServlet(ConfigureListener.java:805)
at com.sun.faces.config.ConfigureListener$WebXmlProcessor.<init>(ConfigureListener.java:768)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:178)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1871)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3173)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1529)
2014-12-10 11:06:28 PST: WL action state: failed
2014-12-10 11:06:28 PST: Action FAILED with WL action state: failed
2014-12-10 11:06:28 PST: Check the server log of your Java cloud service for more info about the failure.
2014-12-10 11:06:28 PST: Application deployment failed.
2014-12-10 11:06:28 PST: "Deploy Application" complete: status FAILED

The Application does nothing, it's just a simple page (the button does nothing too) the aim is to deploy a jsf page with ADF forms.
The deployment log is on the first message.
I'm using Jdeveloper and i note the Jdev inserts some servlets into the web.xml file ! is it possible that the probleme is related to this ? (below the web.xml file)
Sid
<?xml version = '1.0' encoding = 'windows-1252'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
 version="2.5">
<servlet>
 <servlet-name>Faces Servlet</servlet-name>
 <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
 <load-on-startup>1</load-on-startup>
</servlet>
<servlet>
 <servlet-name>resources</servlet-name>
 <servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
</servlet>
<servlet>
 <servlet-name>BIGRAPHSERVLET</servlet-name>
 <servlet-class>oracle.adf.view.faces.bi.webapp.GraphServlet</servlet-class>
</servlet>
<servlet>
 <servlet-name>BIGAUGESERVLET</servlet-name>
 <servlet-class>oracle.adf.view.faces.bi.webapp.GaugeServlet</servlet-class>
</servlet>
<servlet>
 <servlet-name>MapProxyServlet</servlet-name>
 <servlet-class>oracle.adf.view.faces.bi.webapp.MapProxyServlet</servlet-class>
</servlet>
<servlet-mapping>
 <servlet-name>Faces Servlet</servlet-name>
 <url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
 <servlet-name>resources</servlet-name>
 <url-pattern>/adf/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
 <servlet-name>resources</servlet-name>
 <url-pattern>/afr/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
 <servlet-name>BIGRAPHSERVLET</servlet-name>
 <url-pattern>/servlet/GraphServlet/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
 <servlet-name>BIGAUGESERVLET</servlet-name>
 <url-pattern>/servlet/GaugeServlet/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
 <servlet-name>MapProxyServlet</servlet-name>
 <url-pattern>/servlet/mapproxy/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
 <servlet-name>resources</servlet-name>
 <url-pattern>/bi/*</url-pattern>
</servlet-mapping>
<filter>
 <filter-name>trinidad</filter-name>
 <filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-class>
</filter>
<filter>
 <filter-name>ServletADFFilter</filter-name>
 <filter-class>oracle.adf.share.http.ServletADFFilter</filter-class>
</filter>
<filter-mapping>
 <filter-name>trinidad</filter-name>
 <servlet-name>Faces Servlet</servlet-name>
 <dispatcher>FORWARD</dispatcher>
 <dispatcher>REQUEST</dispatcher>
 <dispatcher>ERROR</dispatcher>
</filter-mapping>
<filter-mapping>
 <filter-name>ServletADFFilter</filter-name>
 <servlet-name>Faces Servlet</servlet-name>
 <dispatcher>FORWARD</dispatcher>
 <dispatcher>REQUEST</dispatcher>
</filter-mapping>
<context-param>
 <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
 <param-value>client</param-value>
</context-param>
<context-param>
 <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
 <param-value>false</param-value>
</context-param>
<context-param>
 <description>If this parameter is true, there will be an automatic check of the modification date of your JSPs, and saved state will be discarded when JSP's change. It will also automatically check if your skinning css files have changed without you having to restart the server. This makes development easier, but adds overhead. For this reason this parameter should be set to false when your application is deployed.</description>
 <param-name>org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION</param-name>
 <param-value>false</param-value>
</context-param>
<context-param>
 <description>Whether the 'Generated by...' comment at the bottom of ADF Faces HTML pages should contain version number information.</description>
 <param-name>oracle.adf.view.rich.versionString.HIDDEN</param-name>
 <param-value>true</param-value>
</context-param>
<context-param>
 <description>Security precaution to prevent clickjacking: bust frames if the ancestor window domain(protocol, host, and port) and the frame domain are different. Another options for this parameter are always and never.</description>
 <param-name>org.apache.myfaces.trinidad.security.FRAME_BUSTING</param-name>
 <param-value>differentOrigin</param-value>
</context-param>
<context-param>
 <param-name>javax.faces.VALIDATE_EMPTY_FIELDS</param-name>
 <param-value>true</param-value>
</context-param>
<context-param>
 <param-name>oracle.adf.view.rich.geometry.DEFAULT_DIMENSIONS</param-name>
 <param-value>auto</param-value>
</context-param>
<context-param>
 <param-name>oracle.adf.view.rich.SYNCROWS</param-name>
 <param-value>enable</param-value>
</context-param>
<context-param>
 <param-name>javax.faces.FACELETS_SKIP_COMMENTS</param-name>
 <param-value>true</param-value>
</context-param>
<context-param>
 <param-name>javax.faces.FACELETS_DECORATORS</param-name>
 <param-value>oracle.adfinternal.view.faces.facelets.rich.AdfTagDecorator</param-value>
</context-param>
<context-param>
 <param-name>javax.faces.FACELETS_RESOURCE_RESOLVER</param-name>
 <param-value>oracle.adfinternal.view.faces.facelets.rich.AdfFaceletsResourceResolver</param-value>
</context-param>
<context-param>
 <param-name>javax.faces.FACELETS_VIEW_MAPPINGS</param-name>
 <param-value>*.jsf;*.xhtml</param-value>
</context-param>
<mime-mapping>
 <extension>swf</extension>
 <mime-type>application/x-shockwave-flash</mime-type>
</mime-mapping>
<mime-mapping>
 <extension>amf</extension>
 <mime-type>application/x-amf</mime-type>
</mime-mapping>
<listener>
 <listener-class>oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack</listener-class>
</listener>
<login-config />
</web-app>

How to deploy EAR file in Tomcat?

Is we can deploy ear file in tomcat?
Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
But samethink I have tried EAR file. But it is not working.
Is we can deploy EAR file or not?
If not plz give reason.

Hi
Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
The Tomcat Servlet/JSP Container
The Apache Tomcat 5.5 Servlet/JSP Container
 Apache Logo
Links
* Docs Home
Contents
* Contents
* Introduction
* Installation
* Deployment
* Source Code
* Processes
* Example App
Application Developer's Guide
Deployment
 Printer Friendly Version
print-friendly
version
Background
Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
Standard Directory Layout
To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web application (that is, the files that Tomcat actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory:
* *.html, *.jsp, etc. - The HTML and JSP pages, along with other files that must be visible to the client browser (such as JavaScript, stylesheet files, and images) for your application. In larger applications you may choose to divide these files into a subdirectory hierarchy, but for smaller apps, it is generally much simpler to maintain only a single directory for these files.
* /WEB-INF/web.xml - The Web Application Deployment Descriptor for your application. This is an XML file describing the servlets and other components that make up your application, along with any initialization parameters and container-managed security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection.
* /WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under /WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named /WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
* /WEB-INF/lib/ - This directory contains JAR files that contain Java class files (and associated resources) required for your application, such as third party class libraries or JDBC drivers.
When you install an application into Tomcat (or any other 2.2/2.3-compatible server), the classes in the WEB-INF/classes/ directory, as well as all classes in JAR files found in the WEB-INF/lib/ directory, are made visible to other classes within your particular web application. Thus, if you include all of the required library classes in one of these places (be sure to check licenses for redistribution rights for any third party libraries you utilize), you will simplify the installation of your web application -- no adjustment to the system class path (or installation of global library files in your server) will be necessary.
Much of this information was extracted from Chapter 9 of the Servlet API Specification, version 2.3, which you should consult for more details.
Shared Library Files
Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
* $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
* $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
* The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
* An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
Web Application Deployment Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
Tomcat Context Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
Deployment With Tomcat 5
In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
* Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
* Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
* Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
* Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
* Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
Copyright © 1999-2006, Apache Software Foundation

Jar not loaded Error when deploying weblogic.jar in tomcat

Hi experts,
This time i have one more problem,
i have deployed my application in tomcat such that when tomcat starts my java program also gets started, for my java program i had to use a weblogic library which is in "web-inf / lib / weblogic.jar" . but when i start tomcat i get error like
INFO: validateJarFile (C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\MyApp\WEB-INF\lib\weblogic.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Dec 4, 2006 8:27:18 PM org.apache.catalina.core.StandardPipeline registerValve
INFO: Can't register valve org.apache.catalina.core.StandardContextValve@1362012
org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@1bc82e7 for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category) (Caused by org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@1bc82e7
for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category))
 at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
what could be the problem in loading weblogic.jar
my platform configuations are
TOMCAT 5.5
OS - windows 2000

 have u done the servlet naminga and mapping in the web.xml file??
 Kumar Allamraju <[email protected]> wrote:
 ><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 ><html>
 >Have you registered the servlet in web.xml?
 >--
 > Kumar
 >Deepak Balakrishna wrote:
 ><blockquote TYPE=CITE>Hi.
 >I am having trouble deploying a servlet to WLS 6.1
 >a) The name of the servlet is HaServlet and it's duly noted in web.xml
 > b) I created a directory
 > config/examples/applications/cluster-servlet/WEB-INF
 > c) Added web.xml under WEB-INF/. web.xml was created using the weblogic
 > DDInit CLI
 > d) Added the servlet classfile (HaServlet.class) under
 > WEB-INF/classes/samples/cluster/servlet/.
 > e) Tried to access it by http://host:port/cluster-servlet/HaServlet
 >I get
 > Error 404--Not Found
 >What am I missing? I also tried restarting the app server to no avail.
 >Thx,
 > - deepak</blockquote>
 ></html>
 >

Getting bad host error when trying to deploy simple web sample application

hi,
Can someone tell me why I'm getting this error when trying to deploy the simple web application from samples
This is what it said:
deploy_common:
[echo] Deploying ../assemble/war/webapps-simple.war.
[exec] java.net.MalformedURLException: Bad host: station_1
thanks

Hi,
Another update on this issue.
To remove the error that we were getting (java.lang.LinkageError: Class javax/xml/transform/Source violates loader constraints), we tried some searching around and found out that the way to fix it is to provide correct versions of xalan.jar, xml-apis.jar and xercesImpl.jar. We downloaded the required version from the apache site and added it to our WEB-INF/lib folder in the WAR file.
Now, we are getting this error:
XPathFactory#newInstance() failed to create an XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom with the XPathFactoryConfigurationException: javax.xml.xpath.XPathFactoryConfigurationException: No XPathFctory implementation found for the object model: http://java.sun.com/jaxp/xpath/dom
What else we might be missing in our libs or do we need to check some other configurations?
Any help on this would be much appreciated.
Thanks,
Gaurav

Bad Magic Number error trying to deploy WAR file from Netweaver Studio

We hae an application that runs fine as a WAR in both Tomcat and Weblogic and we are trying to deploy it on Netweaver. I tried both to use the External deployment archives and the Workspace Deployable Archives. In both cases, the deployment fails with error:
Bad magic number, found 0x80CCF1C3, expected 0xCAFEBABE.
I know the server is working because I can deploy a very simple test application with no errors. The server is a new installation of 7.1.
Any help on how to get past this error or how to troubleshoot further is appreciated.

Looks like it's complaining about a missing shared library. Check weblogic.xml for library-ref elements and make sure the domain you are deploying to has those libraries deployed.

Errors while trying to deploy email portlet

Hi,
I am using Oracle JDeveloper 10.1.3. I am trying to register a portlet. The provider validation was unsuccessful. When trying to run it I get the following error messages:
XML processing error: unable to create object of type edu.umt.portal.custom.CustomRenderCSS due to the following exception: oracle.classloader.util.AnnotatedClassNotFoundException: Missing class: edu.umt.portal.custom.CustomRenderCSS Dependent class: oracle.portal.utils.xml.v2.DefaultNodeHandler Loader: current-workspace-app.web.ceaiWebmailWeb:0.0.0 Code-Source: /C:/jdev/jdev/mywork/ceaiWebmail/ceaiWebmailWeb/public_html/WEB-INF/lib/ptlshare.jar Configuration: WEB-INF/lib/ directory in C:\jdev\jdev\mywork\ceaiWebmail\ceaiWebmailWeb\public_html\WEB-INF\lib This load was initiated at current-workspace-app.web.ceaiWebmailWeb:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system.
can you help me in figuring out what is the problem.
Thanks
Abhishek

Hi Democritos,
Often this kind of error appears when you are trying to deploy to the PDA target something that the PDA does not support.
I would start from this two document.
Why Do I Receive An Unknown Error When Building a LabVIEW VI For PDA?
How Can I Tell What Features for Controls and Indicators are Supported in the LabVIEW PDA Module?
Another source of the same cryptic error message can be an improper installation of all the module needed to build PDA application, the first document suggested above point in this direction too.
I would check the PDA module manual and verify the proper installation order.
LabVIEW 8.0 PDA Module Help
I hope you can dig out a solution from these documents.
Write if you need further help
FiloP
It doesn't matter how beautiful your theory is, it doesn't matter how smart you are. If it doesn't agree with experiment, it's wrong.
Richard P. Feynman

To Deploy a Servlet using Tomcat

I am trying to deploy an example servlet in tomcat.
my example servlet code is
import javax.servlet.http.*;
import javax.servlet.*;
import java.io.*;
public class HitServlet extends HttpServlet {
private int mCount;
public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
String message = "Hits: " + ++mCount;
response.setContentType("text/plain");
response.setContentLength(message.length());
PrintWriter out = response.getWriter();
out.println(message); } }
i 've placed my servlet in the directory
webapps/midp/WEB-INF/classes/HitServlet.java
i've successfully compiled the code. Then started the tomcat server & thro' IE tried to open the url to http://localhost:8080/midp/hits.
but i 'm receiving the error the servlet bob is missing. i've placed the web.xml & server.xml in the folders specified in the tutorial. in server.xml i've added the code
<Context path="/midp" docBase="midp" debug="0" reloadable="true" privileged="true"/>
web.xml
<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> <web-app> <servlet> <servlet-name>bob</servlet-name> <servlet-class>HitServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>bob</servlet-name> <url-pattern>/hits</url-pattern> </servlet-mapping> </web-app>
If u can guide me to deploy the servlet it'll be very helpfull.
With Best Regards
Ramkumar

one idea that I have is the CATALINA_HOME and CATALINA_BASE.
We use CATALINA_BASE to install our stuff in another directory than that of the tomcat installation.
in the tomcat-engine.log you should se sth similar to:
2003-06-18 09:19:04 StandardHost[localhost]: Installing web application at context path /hits from URL file:<xxx/webapps/midp>
2003-06-18 09:19:04 WebappLoader[/gtfn]: Deploying class repositories to work directory $CATALINA_BASE/work/Apache/localhost/gtfn
...

How to deploy mapviewer.ear at tomcat

Hi,
I have read the thread "how to deploy mapviewer at tomcat" and I understand which jar files I have to add to tomcat to have meet the requirements of oracle, but I am still confused how to deploy mapviewer.ear file at tomcat. Can somebody tell me how to do it step by step or give me some useful links about this topic?
Your generous help will be appreciated!
Peifang

Hi Andrejus,
In our department, we have oracle application server licence. I am trying to do as you told me, but I still have a question. I extracted mapviewer.ear file which includes a file named web.war. Is it right that I copy this war file directly into /webapps of TOMCAT or do I have to change something in this war file? In this procedure when can I provide the licence of oracle application server?
Thank you and Best Regards!
Peifang

Hi Experts, when i am trying to deploy the application error is coming

Hi Experts,
when i am trying to deploy the webdynpro java pplication error is coming.but before up to 2 days every thing is working fine.
from two days onwards i cant run any webdynpro applications even which are sap provided applications also.and also can not come properly http://hostname:portno/sld page. i can not moving to more to do anything.
every browser saying javavoid(0); and java applet can not be run like.
only the opera browser shoeing the error toatlly . here i paste the error . please give reply why i can not doing any thing more. But my server and every thing is showing up and good.
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
This page was created by SAP NetWeaver. All rights reserved.
Web Dynpro client:
Nokia Series 80 Client
Web Dynpro client capabilities:
User agent: Opera/9.80 (Windows NT 5.2; U; en) Presto/2.2.15 Version/10.00, client type: op6, client type profile: op6, ActiveX: disabled, Cookies: enabled, Frames: enabled, Java applets: disabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Accessibility mode: false
Web Dynpro runtime:
Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-05:15:08:24[UTC], changelist=413534, host=pwdfm101), build date: Thu Aug 13 23:44:29 GMT+05:30 2009
Web Dynpro code generators of DC sap.com/tcsldwd~main:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcsldwd~landscape:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcwddispwda: No information available!
Web Dynpro code generators of DC sap.com/tcsldwd~businesssystem:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcsldwd~technicalsystem:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcwdcorecomp: No information available!
Web Dynpro code generators of DC sap.com/tcsldwd~softwarecatalog:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcsldwd~namereservation:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
J2EE Engine:
7.00 patchlevel
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_12-b03, vendor: Sun Microsystems Inc.
O

HI surya,
Restart the SDM and try again...
regards,
viswa

Deploying Web application in Tomcat

Hi,
I am trying to deploy a web application "Simulator" in Tomcat. I am getting an error HTTP Status 404.
1> Here is my web.xml file........
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<servlet>
<servlet-name>IOServlet</servlet-name>
<servlet-class>com.iflex.fcc.xmlgateway.IOServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>com.iflex.fcc.xmlgateway.IOServlet</servlet-name>
<url-pattern>/servlet/com.iflex.fcc.xmlgateway.IOServlet</url-pattern>
</servlet-mapping>
</web-app>
2> The folder structure which I created is............
D:\tomcat\tomcat-jwsdp-1.4\webapps\Simulator\WEB-INF\classes\
(followed by my package structure) com\iflex\fcc\xmlgateway\IOServlet
3> The Url which I use to access this servlet is,
http://localhost:8888/Simulator/servlet/com.iflex.fcc.xmlgateway.IOservlet
Pls. Help me.

Change this line in ur web.xml
<servlet-name>com.iflex.fcc.xmlgateway.IOServlet</servlet-name>
to
<servlet-name>IOServlet</servlet-name>
By the way, kya iflex recruit kar rahi hai ??
-L.

Error while trying to deploy a cube

I am getting an error message while trying to deploy a cube. OWB Client version is 10.2.0.1.31 and the repository version is 10.2.0.1.0
Below is the piece of code that generates the error:
BEGIN
CWM2_OLAP_CUBE.ADD_DIMENSION_TO_CUBE('EXPENSE_WH', 'REL_EXPENSE', 'EXPENSE_WH', 'REL_CATEGORY');
END;
Error report:
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.CWM2_OLAP_UTILITY", line 1660
ORA-01403: no data found
ORA-06512: at "OLAPSYS.CWM2_OLAP_CUBE", line 33
ORA-06512: at "OLAPSYS.CWM2_OLAP_CUBE", line 55
ORA-06512: at "OLAPSYS.CWM2_OLAP_CUBE", line 386
ORA-06512: at line 2
I would appreciate any help.

Is the dependent dimension deployed to the catalog? Generally the no data found error indicates some dependent object is missing; either an implementing table or a dependent dimension.
Cheers
David

MDS dialog when trying to deploy

Hi,
I'm trying to permanently deploy my JDeveloper 11.1.1.2.0 application (which has MDS enabled, as per http://biemond.blogspot.com/2009/07/customize-and-personalize-your-jsf.html), to the IntegratedWebLogicServer. After creating the new deployment profile, when I try to run it I get a new 'MDS' dialog appearing and I don't know what values to use.
The dialog contains the fields Repository Name, Repository Type, Partition Name and Path/JNDI Info. Here's a screenshot:
http://i934.photobucket.com/albums/ad187/japher/mds_fields.png
The Repository Name combo box is empty.
If I just right-click on a jspx and choose Run or Debug, the app runs without problems. However, when I try to run the deployment profile to deploy permanently, this dialog appears (and I cannot continue). Am I missing something with my MDS configuration? Can anyone advise on what values need to go in here?
Cheers!

If I leave this dialog blank and continue to deploy, I get the following error why trying to load a page:
Error 500--Internal Server Error
oracle.adf.share.ADFShareException: MDSConfigurationException encountered in parseADFConfiguration
     at oracle.adf.share.config.ADFMDSConfig.parseADFConfiguration(ADFMDSConfig.java:178)
     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:597)
     at oracle.adf.share.config.ADFConfigImpl.getResultFromComponent(ADFConfigImpl.java:442)
     at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.java:507)
     at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.java:490)
     at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.java:546)
     at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.java:541)
     at oracle.adf.share.config.ADFContextMDSConfigHelperImpl.getMDSInstance(ADFContextMDSConfigHelperImpl.java:274)
     at oracle.adf.share.ADFContext.getMDSInstanceAsObject(ADFContext.java:1203)
     at oracle.adf.share.http.ServletADFContext.initialize(ServletADFContext.java:434)
     at oracle.adf.share.http.ServletADFContext.initThreadContext(ServletADFContext.java:351)
     at oracle.adf.model.servlet.HttpBindingRequestHandler.initADFContext(HttpBindingRequestHandler.java:55)
     at oracle.adf.model.BindingRequestHandler.beginRequest(BindingRequestHandler.java:107)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:189)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "MAR_TargetRepos" is invalid.
MDS-00058: Invalid Metadata Path: Metadata Path cannot be null.
     at oracle.mds.config.PConfig.loadFromBean(PConfig.java:695)
     at oracle.mds.config.PConfig.(PConfig.java:504)
     at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:692)
     at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:749)
     at oracle.mds.config.MDSConfig.(MDSConfig.java:407)
     at oracle.mds.core.MDSInstance.getMDSConfigFromDocument(MDSInstance.java:2007)
     at oracle.mds.core.MDSInstance.createMDSInstanceWithCustomizedConfig(MDSInstance.java:1169)
     at oracle.mds.core.MDSInstance.getOrCreateInstance(MDSInstance.java:569)
     at oracle.adf.share.config.ADFMDSConfig.parseADFConfiguration(ADFMDSConfig.java:137)
     ... 38 more
Caused by: oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "MAR_TargetRepos" is invalid.
MDS-00058: Invalid Metadata Path: Metadata Path cannot be null.
     at oracle.mds.config.PConfig.loadFromBean(PConfig.java:689)
     ... 46 more

Trying to deploy IE10 via WSUS... doesn't seem to work

I am trying to deploy IE 10 to my windows 7 machines using WSUS. I have imported the update from the catalog and approved it for install in my workstations group.
I still have a hybrid environment of XP and Windows 7 - but of the 112 Windows 7 machines we've got, my goal is to get all of them to IE 10. My WSUS says I'm at 96% installed / not applicable, but that number doesn't accurately represent what I am
seeing.
In addition, I sat at a couple of my Windows 7 w/ IE 8 or 9 on it, and tried to force check and install (wuauclt /detectnow) and it never seems to find the IE 10 install.
I am quite certain that I am doing something wrong as I am nowhere near a WSUS expert, so I need help
Thanks in advance,
sb

Hi,
Please make sure that these systems have ALL of the required prerequisites as discussed in
KB2818833.
Hope this helps.
Regards, Yan Li
This will help for sure as I've made a lot of tests and if you don't have all KB from the link you gave, IE10 will not apply on computers.
For me it was only related to the following one :
2670838 A platform update is available for Windows 7 SP1 and Windows Server 2008 R2 SP1
This update provides improved features and performance in Windows 7 SP1 and Windows Server 2008 R2 SP1. It includes updates to the following DirectX components: Direct2D, DirectWrite, Direct3D, Windows Imaging Component (WIC), and Windows Advanced Rasterization
Platform (WARP). Additionally, it includes updates to the Windows Animation Manager (WAM), the XPS Document API, and the MPEG-2 Video Decoder. After you install this update, you may have to restart your computer.
x86 package
x64 package
TiGrOu.

EJBCompiler Exception when trying to deploy application in a cluster

Hi,
 I have setup a cluster environment with 2 Managed Servers. While I tried to deploy the application using the Admin console, I got the following exception on both managed servers. I have tried suggestions from different websites:
 1. adding JDK to $PATH in WebLogic startup script and the system PATH.
 http://forum.java.sun.com/thread.jspa?threadID=465456&messageID=2605081
 2. Increasing memory for javac
 http://forum.java.sun.com/thread.jspa?threadID=492907&messageID=2605123
 My application was compiled with JDK 1.4
 But still no luck.
 What am I missing here?
 Thanks.
 Teresa
 [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application opencase on edcCluster.:
 Exception:weblogic.management.ApplicationException: prepare failed for opencase-ejb.jar
 Module: opencase-ejb.jar Error: Exception preparing module: EJBModule(opencase-ejb.jar,status=NEW)
 Unable to deploy EJB: opencase-ejb.jar from opencase-ejb.jar:
 Compiler failed executable.exec
 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:493)
 at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:784)
 at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:700)
 at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1339)
 at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
 at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
 at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
 at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2513)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2463)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
 java.io.IOException: Compiler failed executable.exec
 at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:469)
 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:493)
 at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:784)
 at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:700)
 at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1339)
 at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
 at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
 at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
 at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
 at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2513)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2463)
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

I solved recently a similar problem. The problem arised because the
 developer had compiled the ejb.jar with JDK 5.0, and then he was trying to
 deploy it to WLS 8.1, which supports only JDK 1.4 compiled classes when
 EJBCompiling.
 <T Y> wrote in message news:[email protected]...
 > Hi,
 > I have setup a cluster environment with 2 Managed Servers. While I tried
 > to deploy the application using the Admin console, I got the following
 > exception on both managed servers. I have tried suggestions from different
 > websites:
 > 1. adding JDK to $PATH in WebLogic startup script and the system PATH.
 > http://forum.java.sun.com/thread.jspa?threadID=465456&messageID=2605081
 >
 > 2. Increasing memory for javac
 > http://forum.java.sun.com/thread.jspa?threadID=492907&messageID=2605123
 >
 > My application was compiled with JDK 1.4
 >
 > But still no luck.
 > What am I missing here?
 >
 > Thanks.
 >
 > Teresa
 >
 >
 > [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
 > application opencase on edcCluster.:
 > Exception:weblogic.management.ApplicationException: prepare failed for
 > opencase-ejb.jar
 > Module: opencase-ejb.jar Error: Exception preparing module:
 > EJBModule(opencase-ejb.jar,status=NEW)
 > Unable to deploy EJB: opencase-ejb.jar from opencase-ejb.jar:
 > Compiler failed executable.exec
 > 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:493)
 > at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:784)
 > at
 > weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:700)
 > at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1339)
 > at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
 > at
 > weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
 > at
 > weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
 > at
 > weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
 > at
 > weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2513)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2463)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
 > at
 > weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
 > java.io.IOException: Compiler failed executable.exec
 > at
 > weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:469)
 > 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:493)
 > at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:784)
 > at
 > weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:700)
 > at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1339)
 > at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
 > at
 > weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
 > at
 > weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
 > at
 > weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
 > at
 > weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2513)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2463)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
 > at
 > weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
 > at
 > weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Trying to deploy a provider in Tomcat - Missing: oracle/bali/share...

Similar Messages

Maybe you are looking for