Deploying WAR file using IAS Test Drive edition...

Hi:
Is it okay to deploy a build using a WAR file instead of an EAR file? Is
there any documentation for deploying WAR files? All the available docs and
examples start with EAR files.
Thanks,
George

Hi,
A war file is okay if you are using servlets & JSP, WAR means Web Archive.
So you can very well go ahead with a war file, incase you are thinking of EJB's
then a .ear file will help you.
Regards
Raj
George Sang wrote:
Hi:
Is it okay to deploy a build using a WAR file instead of an EAR file? Is
there any documentation for deploying WAR files? All the available docs and
examples start with EAR files.
Thanks,
George

Similar Messages

  • Error while deploying war file using JRUN JMC

    Hi,
    I am getting "Deployment service failed to deploy war file" Error
    while trying to deploy a war file using JRUN Mgmt console.
    If anyone has any idea about it, please help.
    Thanks
    Jit

    Check the logs. There might be a detailed exception in it. My guess is that it might have something to do with the deployment descriptors.
    If you could post the deployment descriptors and the exception stack trace, it would be easier to figure out.

  • Ias console and deploy war file

    Hi All,
    I need to deploy a war file into EBS R12. I thought of enable the ias console and deploy. I followed the steps
    1. Change $INST_TOP/ora/10.1.3/Apache/Apache/conf/trusted.conf file and change
    [Location ~ “/ascontrol”]
    Order deny,allow
    Deny from all
    Allow from localhost
    [Location]
    to
    [Location ~ “/ascontrol”]
    Order deny,allow
    Allow from all
    [Location]
    2. Restart Apache
    adapcctl.sh stop
    adapcctl.sh start
    3. Access it via
    http://server:port/ascontrol
    After doing the above steps, am able to open ias console. But when i go to tab oc4j-instances and click on any instance oafm or forms or oacore, its saying an error Error Mesg: Unable to login to the OC4J "default_group" on  Application Server "oacore" the OC4J is not running . I checked opmnctl status, all components are running. Please let me know any suggestion on this.
    Also is there any way to deploy war file from back end. I got one utility like admin_client.jar. but when i try to validate using the following command
    java -jar admin_client.jar deployer:oc4j:<host>:6003 oc4jadmin welcome123 -validateURI .. giving error as below
    Failed at "Could not get DeploymentManager".
    This is typically the result of an invalid deployer URI format being supplied, the target server not being in a started state or incorrect authentication details being supplied.
    More information is available by enabling logging -- please see the Oracle Containers for J2EE Configuration and Administration Guide for details.
    Valid connection_uris are:
    1. To target all OC4J instances that belongs to an OC4J group in an Oracle Application Server Cluster:
    deployer:cluster:[ormis:]opmn://opmnHost[:opmnPort]/oc4jGroupName
    2. To target a specific OC4J instance within a cluster:
    deployer:oc4j:[ormis:]opmn://opmnHost[:opmnPort]/oc4jInstanceName
    deployer:oc4j:[ormis:]opmn://opmnHost[:opmnPort]/asInstanceName/oc4jInstanceName
    3. To target a standalone OC4J server:
    deployer:oc4j:oc4jHost:rmiPort
    deployer:oc4j:ormis:oc4jHost:ormisPort
    opmnPort is the OPMN request port specified in opmn.xml.
    If omitted, defaults to 6003.
    Thanks,
    Manikandan

    Hi;
    Please check below thread than recheck your steps
    Re: Deploy .war file in Ebs 11i-11.5.10.2
    Regard
    Helios

  • Deploying WAR file into OC4J 9.0.3 (IAS)

    Hello,
    I try to deploy my WAR file using following command:
    dcmctl redeployApplication -v -d -f myWAR.war -a myApp -rc /test/myApp -co test
    When the deployment is finished I check default-web-site.xml for the "test" component and I a new line there:
    &lt;web-app application="myApp" name="myApp" root="/test/myApp"/&gt;
    But in the documentation I found that the "name" attribute of the "web-app" tag should contain the name of the WAR file. It is a problem because when I try to deploy another WAR file using the same application name it overwrites "&lt;web-app&gt;" tag. In principal, can I deploy several WAR files using the same application name?
    Thanks in advance,
    Iouri.

    Please look at the following thread in this forum that describes the steps : Re: Query takes large time to execute
    regards
    Debu panda
    Oracle

  • Deployment of .war file using JMX in jboss 4.0.5 GA

    Hi,
    Can anyone help me out in the steps of deployment of .war file using JMX in JBOSS 4.0.5 server.I went through the documentation in jboss.org but couldn't find a suitable one though there were many.Any links/url that you know about the deployment process will also be helpful to me.
    Thanks

    You're probably using an older version of JavaMail where there was a bug in the example
    DummySSLSocketFactory. Download the latest version and the example is correct.
    Also, if you're using DummySSLSocketFactory just to control which servers you trust,
    JavaMail 1.4.3 has some properties that will make this easier for you and avoid the need
    for DummySSLSocketFactory. In particular, see the mail.imaps.ssl.trust property.

  • Unable to Deploy WAR file  (Unknown assembly root-tag attribute: version)

    Hello,
    I created a simple web application with eclipse + tomcat plugin + struts2 (JPA Spring Hibernate ) and created the WAR file using the tomcat plugin compiler. When I deploy the war file into Tomcat 6 the file is deployed properly and i can view the website properly. But when I try to deploy the the WAR file from Oracle 9i Application Server I get the following error.
    Failed to deploy web application "mytest". Nested exception Root Cause: Error loading web-app 'mytest' at C:\ora9ias\j2ee\MySystem\applications\mytest\mytest: Unknown assembly root-tag attribute: version; nested exception is: java.lang.InstantiationException: Error loading web-app 'SFPD' at C:\ora9ias\j2ee\MySystem\applications\mytest\mytest: Unknown assembly root-tag attribute: version.
    My Current web.xml is this.
    <?xml version="1.0" ?>
    <web-app id="WebApp_9" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
         http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <display-name>My Test Project System</display-name>
    <filter>
    <filter-name>struts2</filter-name>
    <filter-class>org.apache.struts2.dispatcher.FilterDispatcher</filter-class>
    </filter>
    <filter-mapping>
    <filter-name>struts2</filter-name>
    <url-pattern>/*</url-pattern>
    </filter-mapping>
    <welcome-file-list>
    <welcome-file>index.html</welcome-file>
    </welcome-file-list>
    <listener>
    <listener-class>
    org.springframework.web.context.ContextLoaderListener
    </listener-class>
    </listener>
    </web-app>
    thanks in advance,

    Thanks for the reply sasesha,
    I've changed my web.xml to
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <!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>     
         <display-name>My Test Project System</display-name>
         <filter>
              <filter-name>struts2</filter-name>
              <filter-class>org.apache.struts2.dispatcher.FilterDispatcher</filter-class>
         </filter>
         <filter-mapping>
              <filter-name>struts2</filter-name>
              <url-pattern>/*</url-pattern>
         </filter-mapping>
         <listener>
              <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
         </listener>
         <welcome-file-list>
              <welcome-file>index.html</welcome-file>
         </welcome-file-list>
    </web-app>
    During the initial upload the previous error doesn't show anymore, however, I'm getting this new error and currently I'm a bit at a loss since i included the spring.jar library file in my war file. I tried the new war file in Tomcat and the war file deploys fine. Am I missing a configuration or setup ?
    Failed to deploy web application "mytest". Nested exception Root Cause: Class not found: org.springframework.beans.factory.BeanDefinitionStoreException; nested exception is: java.lang.ClassNotFoundException: org.springframework.beans.factory.BeanDefinitionStoreException. Class not found: org.springframework.beans.factory.BeanDefinitionStoreException; nested exception is: java.lang.ClassNotFoundException: org.springframework.beans.factory.BeanDefinitionStoreException
    Thanks again,
    sethsera

  • Deploying war files to weblogic 10.3.4

    I have a weblogic domain 10.3.4 and a war file (smap.war). I can deploy this war file using weblogic console (10.3.4).
    However, I cannot using ant (wldeploy 11.1.1.4) to deploy this war file. It shows error as follow.
    This war file and weblogic domain is in the same machine.
    ------------------error---------------------------
    [wldeploy] Task 27 failed: [Deployer:149026]deploy application smap.war on AdminServer.
    [wldeploy] Target state: deploy failed on Server AdminServer
    [wldeploy] weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
    [wldeploy] problem: cvc-complex-type.2.4a: Expected element 'servlet-name@http://java.sun.com/xml/ns/javaee' instead of 'description@http://www.w3.org/2001/XMLSchema-instance' here in element servlet@http://java.sun.com/xml/ns/javaee:<null>
    [wldeploy] problem: cvc-complex-type.2.4a: Expected element 'servlet-name@http://java.sun.com/xml/ns/javaee' instead of 'display-name@http://www.w3.org/2001/XMLSchema-instance' here in element servlet@http://java.sun.com/xml/ns/javaee:<null>
    [wldeploy]      at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:245)
    [wldeploy]      at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231)
    ---------------------------build.xml------------------------
    <?xml version="1.0" encoding="UTF-8" ?>
    <!--Ant buildfile generated by Oracle JDeveloper-->
    <!--Generated Mar 11, 2011 3:52:31 PM-->
    <project default="init">
    <target name="init">
    <tstamp/>
    </target>
    <property name="wls.username" value="weblogic" />
    <property name="wls.password" value="welcome1" />
    <property name="wls.hostname" value="localhost" />
    <property name="wls.port" value="7001" />
    <property name="admin.server.name" value="AdminServer" />
    <property name="deploy.target" value="AdminServer" />
    <!-- Here you can specify Either ClusterName, IndividualServerName Like "ManagedOne" or comma Seperated List of Managed/AdminServer -->
    <property name="deploy.name" value="smap.war" />
    <property name="deploy.source" value="E:\SVN_Root\smap_Build" />
    <taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy">
    <classpath>
    <pathelement location="D:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar"/>
    </classpath>
    </taskdef>
    <target name="szmap" depends="init" >
    <war destfile="${deploy.source}\smap.war"
    webxml="${deploy.source}\smap\WebContent\WEB-INF\web.xml" >
    <fileset dir="${deploy.source}\smap\WebContent"/>
    <classes dir="${deploy.source}\smap\build\classes"/>
    </war>
    </target>
    <target name="deployX" depends="init">
    <echo message="27 deploy.source=${deploy.source}"/>
    <echo message="28 deploy.name=${deploy.name}"/>
    <wldeploy action="deploy"
    name="${deploy.name}"
    source="${deploy.source}\${deploy.name}"
    user="${wls.username}"
    nostage="true"
    password="${wls.password}"
    verbose="true"
    adminurl="t3://${wls.hostname}:${wls.port}" targets="${deploy.target}"
    debug="true"
    />
    </target>
    <!-- Redeploying Applications -->
    <target name="redeploy">
    <wldeploy action="redeploy"
    name="${deploy.name}"
    user="${wls.username}"
    nostage="true"
    password="${wls.password}"
    verbose="true"
    adminurl="t3://${wls.hostname}:${wls.port}" targets="${deploy.target}" />
    </target>
    <!-- Uneploying Applications -->
    <target name="undeployX">
    <wldeploy action="undeploy"
    name="szmap"
    failonerror="false"
    user="${wls.username}"
    password="${wls.password}"
    verbose="true"
    adminurl="t3://${wls.hostname}:${wls.port}" targets="${deploy.target}" />
    </target>
    <target name="all" depends="init, deployX"/>
    </project>

    In szmap.war\WEB-INF\lib, I can find spring-beans-2.0.8.jar, spring-context-2.0.8.jar, spring-core-2.0.8.jar, spring-web-2.0.8.jar.
    I change weblogic.xml as follows. Then, I get new errors.
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd"
    xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app">
    <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
    <library-ref>
    <library-name>spring-beans-2.0.8.jar</library-name>
    </library-ref>
    <library-ref>
    <library-name>spring-context-2.0.8.jar</library-name>
    </library-ref>
    <library-ref>
    <library-name>spring-core-2.0.8.jar</library-name>
    </library-ref>
    <library-ref>
    <library-name>spring-web-2.0.8.jar</library-name>
    </library-ref>
    <library-ref>
    <library-name>cxf-2.2.5.jar</library-name>
    </library-ref>
    <library-ref>
    <library-name>wsdl4j-1.6.2.jar</library-name>
    </library-ref>
    </weblogic-web-app>
    ----------------------------error-------------------------------------
    Buildfile: E:\CI_Build\szmap\ANT\ANTszmap\ANT_szmap\build_szmap.xml
    init:
    deployX:
    [echo] 27 deploy.source=E:\SVN_Root\szmap_Build
    [echo] 28 deploy.name=szmap.war
    [wldeploy] weblogic.Deployer -debug -nostage -verbose -noexit -name szmap.war -source E:\SVN_Root\szmap_Build\szmap.war -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -password ******** -deploy
    [wldeploy] weblogic.Deployer invoked with options: -debug -nostage -verbose -noexit -name szmap.war -source E:\SVN_Root\szmap_Build\szmap.war -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -deploy
    [wldeploy] [WebLogicDeploymentManagerImpl.<init>():115] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():158] : Connecting to admin server at localhost:7001, as user weblogic
    [wldeploy] [ServerConnectionImpl.getEnvironment():286] : setting environment
    [wldeploy] [ServerConnectionImpl.getEnvironment():289] : getting context using t3://localhost:7001
    [wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.domainruntime
    [wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.runtime
    [wldeploy] [DomainManager.resetDomain():36] : Getting new domain
    [wldeploy] [DomainManager.resetDomain():39] : Using pending domain: true
    [wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@4406cef4
    [wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@4406cef4
    [wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@8429c19
    [wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@8429c19
    [wldeploy] [ServerConnectionImpl.initialize():169] : Connected to WLS domain: sunzmap_domain
    [wldeploy] [ServerConnectionImpl.init():159] : Initializing ServerConnection : [email protected]3969
    [wldeploy] [BasicOperation.dumpTmids():713] : Incoming tmids:
    [wldeploy] [BasicOperation.dumpTmids():715] : {Target=AdminServer, WebLogicTargetType=server, Name=szmap.war}, targeted=true
    [wldeploy] [BasicOperation.deriveAppName():141] : appname established as: szmap.war
    [wldeploy] <2011-3-15 下午03时48分03秒 CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, szmap.war [archive: E:\SVN_Root\szmap_Build\szmap.war], to AdminServer .>
    [wldeploy] [BasicOperation.dumpTmids():713] : Incoming tmids:
    [wldeploy] [BasicOperation.dumpTmids():715] : {Target=AdminServer, WebLogicTargetType=server, Name=szmap.war}, targeted=true
    [wldeploy] [BasicOperation.loadGeneralOptions():628] : Delete Files:false
    [wldeploy] Timeout :3600000
    [wldeploy] Targets:
    [wldeploy] AdminServer
    [wldeploy] ModuleTargets={}
    [wldeploy] SubModuleTargets={}
    [wldeploy] }
    [wldeploy] Files:
    [wldeploy] null
    [wldeploy] Deployment Plan: null
    [wldeploy] App root: C:\Users\ADMINI~1\AppData\Local\Temp\2\Administrator\.\config\deployments\szmap.war
    [wldeploy] App config: C:\Users\ADMINI~1\AppData\Local\Temp\2\Administrator\.\config\deployments\szmap.war\plan
    [wldeploy] Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=nostage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=szmap.war,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false}
    [wldeploy]
    [wldeploy] [BasicOperation.execute():445] : Initiating deploy operation for app, szmap.war, on targets:
    [wldeploy] [BasicOperation.execute():447] : AdminServer
    [wldeploy] Task 33 initiated: [Deployer:149026]deploy application szmap.war on AdminServer.
    [wldeploy] dumping Exception stack
    [wldeploy] Task 33 failed: [Deployer:149026]deploy application szmap.war on AdminServer.
    [wldeploy] Target state: deploy failed on Server AdminServer
    [wldeploy] java.lang.NoSuchMethodException: oracle.j2ee.ws.wsdl.extensions.soap.SOAPBindingImpl.getElementType()
    [wldeploy]      at java.lang.Class.getDeclaredMethod(Class.java:1937)
    [wldeploy]      at org.apache.cxf.tools.common.ExtensionInvocationHandler.invoke(ExtensionInvocationHandler.java:41)
    [wldeploy]      at $Proxy325.getElementType(Unknown Source)
    [wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.hasUsingAddressing(JaxWsEndpointImpl.java:201)
    [wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.extractWsdlExtensibilities(JaxWsEndpointImpl.java:184)
    [wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.<init>(JaxWsEndpointImpl.java:174)
    [wldeploy]      at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.createEndpoint(JaxWsServiceFactoryBean.java:206)
    [wldeploy]      at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:165)
    [wldeploy]      at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:105)
    [wldeploy]      at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:167)
    [wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:346)
    [wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:259)
    [wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:209)
    [wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:404)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1414)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1375)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
    [wldeploy]      at java.security.AccessController.doPrivileged(Native Method)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
    [wldeploy]      at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
    [wldeploy]      at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
    [wldeploy]      at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
    [wldeploy]      at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
    [wldeploy]      at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
    [wldeploy]      at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
    [wldeploy]      at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
    [wldeploy]      at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    [wldeploy]      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    [wldeploy]      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    [wldeploy]      at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    [wldeploy]      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    [wldeploy]      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    [wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    [wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    [wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    [wldeploy]      at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    [wldeploy]      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    [wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    [wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    [wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    [wldeploy]      at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    [wldeploy]      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    [wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    [wldeploy]      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    [wldeploy]      at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
    [wldeploy]      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    [wldeploy]      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    [wldeploy]      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    [wldeploy]      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    [wldeploy]      at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    [wldeploy]
    [wldeploy]
    [wldeploy] Target Assignments:
    [wldeploy] + szmap.war AdminServer
    [wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Task 33 failed: [Deployer:149026]deploy application szmap.war on AdminServer.
    [wldeploy] Target state: deploy failed on Server AdminServer
    [wldeploy] java.lang.NoSuchMethodException: oracle.j2ee.ws.wsdl.extensions.soap.SOAPBindingImpl.getElementType()
    [wldeploy]      at java.lang.Class.getDeclaredMethod(Class.java:1937)
    [wldeploy]      at org.apache.cxf.tools.common.ExtensionInvocationHandler.invoke(ExtensionInvocationHandler.java:41)
    [wldeploy]      at $Proxy325.getElementType(Unknown Source)
    [wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.hasUsingAddressing(JaxWsEndpointImpl.java:201)
    [wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.extractWsdlExtensibilities(JaxWsEndpointImpl.java:184)
    [wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.<init>(JaxWsEndpointImpl.java:174)
    [wldeploy]      at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.createEndpoint(JaxWsServiceFactoryBean.java:206)
    [wldeploy]      at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:165)
    [wldeploy]      at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:105)
    [wldeploy]      at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:167)
    [wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:346)
    [wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:259)
    [wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:209)
    [wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:404)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1414)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1375)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
    [wldeploy]      at java.security.AccessController.doPrivileged(Native Method)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
    [wldeploy]      at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
    [wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
    [wldeploy]      at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
    [wldeploy]      at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
    [wldeploy]      at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
    [wldeploy]      at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
    [wldeploy]      at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
    [wldeploy]      at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
    [wldeploy]      at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    [wldeploy]      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    [wldeploy]      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    [wldeploy]      at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
    [wldeploy]      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
    [wldeploy]      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
    [wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    [wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    [wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    [wldeploy]      at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    [wldeploy]      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    [wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    [wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    [wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    [wldeploy]      at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    [wldeploy]      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
    [wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    [wldeploy]      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
    [wldeploy]      at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
    [wldeploy]      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    [wldeploy]      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
    [wldeploy]      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    [wldeploy]      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    [wldeploy]      at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    [wldeploy]
    [wldeploy]
    [wldeploy]
    [wldeploy]      at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:542)
    [wldeploy]      at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
    [wldeploy]      at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
    [wldeploy]      at weblogic.utils.compiler.Tool.run(Tool.java:158)
    [wldeploy]      at weblogic.utils.compiler.Tool.run(Tool.java:115)
    [wldeploy]      at weblogic.Deployer.run(Deployer.java:70)
    [wldeploy]      at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
    [wldeploy]      at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
    [wldeploy]      at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
    [wldeploy]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
    [wldeploy]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    [wldeploy]      at org.apache.tools.ant.Task.perform(Task.java:348)
    [wldeploy]      at org.apache.tools.ant.Target.execute(Target.java:357)
    [wldeploy]      at org.apache.tools.ant.Target.performTasks(Target.java:385)
    [wldeploy]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
    [wldeploy]      at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [wldeploy]      at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    [wldeploy]      at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
    [wldeploy]      at org.apache.tools.ant.Main.runBuild(Main.java:758)
    [wldeploy]      at org.apache.tools.ant.Main.startAnt(Main.java:217)
    [wldeploy]      at org.apache.tools.ant.Main.start(Main.java:179)
    [wldeploy]      at org.apache.tools.ant.Main.main(Main.java:268)
    [wldeploy] [ServerConnectionImpl.close():332] : Closing DM connection
    [wldeploy] [ServerConnectionImpl.close():352] : Unregistered all listeners
    [wldeploy] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection
    [wldeploy] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
    [wldeploy] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection
    BUILD FAILED
    weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 33 failed: [Deployer:149026]deploy application szmap.war on AdminServer.
    Target state: deploy failed on Server AdminServer
    java.lang.NoSuchMethodException: oracle.j2ee.ws.wsdl.extensions.soap.SOAPBindingImpl.getElementType()
         at java.lang.Class.getDeclaredMethod(Class.java:1937)
         at org.apache.cxf.tools.common.ExtensionInvocationHandler.invoke(ExtensionInvocationHandler.java:41)
         at $Proxy325.getElementType(Unknown Source)
         at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.hasUsingAddressing(JaxWsEndpointImpl.java:201)
         at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.extractWsdlExtensibilities(JaxWsEndpointImpl.java:184)
         at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.<init>(JaxWsEndpointImpl.java:174)
         at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.createEndpoint(JaxWsServiceFactoryBean.java:206)
         at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:165)
         at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:105)
         at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:167)
         at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:346)
         at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:259)
         at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:209)
         at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:404)
         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 org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1414)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1375)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
         at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
         at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
         at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
         at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
         at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
         at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
         at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
         at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
         at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
         at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
         at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
         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.Ev

  • Error 160078 when deploying WAR file after EAR file

    I am tetsing an application which does automatic deployment to WebLogic 8.1 running on Windows XP using ejbgen tool through Ant.
    The following deployment sequence produces an error. I deploy an EAR file with EJB JAR and WAR file inside. It deploys correctly. I then undeploy the EAR file. This also works. Next I deploy a WAR file using the same deployment name as for the EAR file (the 'name' parameter of weblogic.Deployer command). This deployment fails. If I restart WebLogic server, the same deployment of the WAR file succeeds.
    Any idea what goes wrong?
    Thank you.
    Michael
    Here is the command used for deployment (as reported by Ant):
    [java] 'weblogic.Deployer'
    [java] '-debug'
    [java] '-verbose'
    [java] '-noexit'
    [java] '-remote'
    [java] '-upload'
    [java] '-name'
    [java] 'discoverytestproject'
    [java] '-source'
    [java] 'C:/Projects/Jetson/Toolbox/Tests/Projects/DiscoveryTestProject/build/staging/discoverytestproject-ws.war'
    [java] '-targets'
    [java] 'myserver'
    [java] '-adminurl'
    [java] 't3://10.10.0.123:7001'
    [java] '-user'
    [java] 'system'
    [java] '-password'
    [java] 'password'
    [java] '-deploy'
    This is the error message:
    <Oct 13, 2006 3:04:21 PM EDT> <Warning> <J2EE> <BEA-160018> <ComponentMBean: Nam
    e = discoverytestproject-ws, Type = WebAppComponentConfig - Targeted on this ser
    ver but, no corresponding module found in application descriptor. The component
    mbean is being Ignored.>
    <Oct 13, 2006 3:04:21 PM EDT> <Error> <J2EE> <BEA-160078> <None of the modules o
    f application 'discoverytestproject' in 'META-INF/application.xml' are configure
    d in the 'Application' entry in 'config.xml' to be targetted to 'myserver'.>
    <Oct 13, 2006 3:04:21 PM EDT> <Warning> <Deployer> <BEA-149004> <Failures were d
    etected while initiating Deploy task for application discoverytestproject.>
    <Oct 13, 2006 3:04:21 PM EDT> <Error> <Deployer> <BEA-149201> <Failed to complet
    e the deployment task with ID 6 for the application discoverytestproject.
    weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: [J2EE:160078]None of the mod
    ules of application 'discoverytestproject' in 'META-INF/application.xml' are con
    figured in the 'Application' entry in 'config.xml' to be targetted to 'myserver'
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createCon
    tainer(SlaveDeployer.java:2556)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(S
    laveDeployer.java:2474)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
    veDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDepl
    oyer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
    loyer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
    dler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    --------------- nested within: ------------------
    weblogic.management.ManagementException: - with nested exception:
    [weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: [J2EE:160078]None of the mod
    ules of application 'discoverytestproject' in 'META-INF/application.xml' are con
    figured in the 'Application' entry in 'config.xml' to be targetted to 'myserver'
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(S
    laveDeployer.java:2491)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
    veDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDepl
    oyer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
    loyer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
    dler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >

    I am tetsing an application which does automatic deployment to WebLogic 8.1 running on Windows XP using ejbgen tool through Ant.
    The following deployment sequence produces an error. I deploy an EAR file with EJB JAR and WAR file inside. It deploys correctly. I then undeploy the EAR file. This also works. Next I deploy a WAR file using the same deployment name as for the EAR file (the 'name' parameter of weblogic.Deployer command). This deployment fails. If I restart WebLogic server, the same deployment of the WAR file succeeds.
    Any idea what goes wrong?
    Thank you.
    Michael
    Here is the command used for deployment (as reported by Ant):
    [java] 'weblogic.Deployer'
    [java] '-debug'
    [java] '-verbose'
    [java] '-noexit'
    [java] '-remote'
    [java] '-upload'
    [java] '-name'
    [java] 'discoverytestproject'
    [java] '-source'
    [java] 'C:/Projects/Jetson/Toolbox/Tests/Projects/DiscoveryTestProject/build/staging/discoverytestproject-ws.war'
    [java] '-targets'
    [java] 'myserver'
    [java] '-adminurl'
    [java] 't3://10.10.0.123:7001'
    [java] '-user'
    [java] 'system'
    [java] '-password'
    [java] 'password'
    [java] '-deploy'
    This is the error message:
    <Oct 13, 2006 3:04:21 PM EDT> <Warning> <J2EE> <BEA-160018> <ComponentMBean: Nam
    e = discoverytestproject-ws, Type = WebAppComponentConfig - Targeted on this ser
    ver but, no corresponding module found in application descriptor. The component
    mbean is being Ignored.>
    <Oct 13, 2006 3:04:21 PM EDT> <Error> <J2EE> <BEA-160078> <None of the modules o
    f application 'discoverytestproject' in 'META-INF/application.xml' are configure
    d in the 'Application' entry in 'config.xml' to be targetted to 'myserver'.>
    <Oct 13, 2006 3:04:21 PM EDT> <Warning> <Deployer> <BEA-149004> <Failures were d
    etected while initiating Deploy task for application discoverytestproject.>
    <Oct 13, 2006 3:04:21 PM EDT> <Error> <Deployer> <BEA-149201> <Failed to complet
    e the deployment task with ID 6 for the application discoverytestproject.
    weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: [J2EE:160078]None of the mod
    ules of application 'discoverytestproject' in 'META-INF/application.xml' are con
    figured in the 'Application' entry in 'config.xml' to be targetted to 'myserver'
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createCon
    tainer(SlaveDeployer.java:2556)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(S
    laveDeployer.java:2474)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
    veDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDepl
    oyer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
    loyer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
    dler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    --------------- nested within: ------------------
    weblogic.management.ManagementException: - with nested exception:
    [weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: [J2EE:160078]None of the mod
    ules of application 'discoverytestproject' in 'META-INF/application.xml' are con
    figured in the 'Application' entry in 'config.xml' to be targetted to 'myserver'
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(S
    laveDeployer.java:2491)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
    veDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDepl
    oyer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
    loyer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
    dler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >

  • Images and js files within a deployed war file are generating 404 errors.

    Greetings,
    I have an odd situation in that image files and js files that are part of a deployed war file are generating 404 (not found) errors when accessed via https but ARE found when accessed via http.
    Unfortunately we are required to use https.
    I have verified via jar -tf that the files are indeed part of the war file. So, it is not that they are missing as is evident when accessed via http. (they appear as expected)
    A work around is to create the sub directories under the document root, on the ohs, and populate the sub directories with the images and js files that were used as part of the war file build. While this works, it doesn't explain why they would generate a 404 error when referenced from within the war via https.
    The war file works correctly on our 10g installation.
    I also have a very simple deployed war file and it too seems to have an issue finding direcotries/files that are part of the war file when referenced via https but not http.
    We are using Oracle 11g OHS and using the WLS Admin Console to do the deploying. We also are using the OSSO for the performing the required authentication.
    I have an SR in with oracle and have been working with them but I thought I would post here too.
    Suggestions?
    Thanks in advance.
    Edited by: emmett on Jan 5, 2011 2:47 PM

    Don't crosspost. Continue here: http://forum.java.sun.com/thread.jspa?threadID=5251627

  • Deploying war file on iplanet application server 6.5

    Hi ,
    We are trying to deploy WebObjects application on Iplanet Application server server 6.5.
    Steps we tried for deployment :
    1) War file generated by WebObjects.
    2) Started IPlanet Application server.
    3) Opened the War file in the deployment tool.
    4) Verified that the WAR file to be deployed using the verify option in the deployment tool(Verified successfully)
    5) We tried to save the archive, then it throws an error saying "
    "Invalid entry compressed size (expected 52 bytes but got 51 bytes)".
    We ignored this message and proceeded further by clicking on OK.
    6) Deployed the WAR file using the deploy option
    7) In the deploy message box, it diplays that the application was deployed successfully.
    Then we tried to access the application by trying the following url : " http://localhost/NASApp/<CONTEXT NAME>/WebObjects/<APPLICATION NAME>"
    (eg : http://localhost/NASApp/SampleApplication/WebObjects/SampleApplication.woa>)
    We are getting the error saying that " GXError". We are not sure whether the the above mentioned url is the correct way to access the application !
    What we think the problem in deployment is
    i) because of error while saving the WAR file (Invalid entry compressed size (expected 52 bytes but got 51 bytes)
    ii) URL not appropriate
    Other observations :
    We tried to deploy to deploy sample application on Iplanet Application server. All these sample applications are deployed properly without the above mentioned error message. All these application are accessed by typing following url : " http:localhost/NASApp/<CONTEXT NAME>/<APPLICATION NAME>". IN all the sample application, url contains "NASApp" . We are not sure what this stand for and maps to. What we assumed is that it maps to the the iplanet app document root i.e "installedroot/ias6/ias/App"
    The exception throw while saving the WAR file is " com.iplanet.ias.tools.buzz.util.ArchiveHandlerException"
    Has any body who has tried this can help us?
    Thanks,
    Raju and Venkatesh

    Hi,
    First of all the application you are trying is from a WebObjects application server. I don't know how they package the modules and what is the format/file structure. I just went to their site, though they say that the WebObjects applications can be deploy on any J2EE Application server but still how they package and how they write the xml descriptors is not known.
    Looking at your exception it seem that first it is something to do the war/jar archive file compression thing (as the deployment tool is not able to read the complete file) then comes the deployment descriptors.
    I tried to get a few sample application from their site but I couldn't fine any, it will be great help if you can provide a WebObjects sample app to me (mail it to [email protected]).
    Regarding the NASApp string in URL, it has nothing to do with document root of iAS and also installedroot/ias6/ias/APPS dir is not the document root of iPlanet app server, this is the place where it save/explodes all the archives (ear).
    See iPlanet App server don't have any HTTP daemon to listen to the HTTP requests, so it needs a web server with a plugin (web connector) to forward the HTTP requests meant for iAS, and this NASApp string in the URL is the key to that.
    All the URLs are first send to the iAS plugin (as configured in web server's obj.conf file) and plugin look for this NASApp string (configurable), if it is there in the URL then it converts the HTTP request and send it to iAS over a proprietary protocol (KCP), otherwise it gives the request as it is to web server to process it.
    The NASApp string is a iAS registry parameter which you can change any time. And generally the context root part of the URL is the war file name (by default). So the typical URL for any web application (MyWeb.war) will be:
    http://<host>:<port>/NASApp/MyWeb/<Servlet_name>.
    I don't know why that extension "*.woa" is there. So if you send me a sample war file, I will be able to try it out.
    Please feel free to ask further questions.
    Sanjeev,
    Developer Support, Sun ONE Application Server-India.

  • [b]problem with deploy .war file

    Hi
    I am trying to deploy a war file. I have Oracle 9iAS (release 2) in Sun Solaris server.
    I am using the enterprise manager gui to try to deploy a .war file as follows.
    My .war file has the structure: folder META-INF, folder WEB-INF, and other folders. THe folder
    WEB-INF has the file web.xml and the folder classes.
    I connect to enterprise manager at port 1810 and go to the OC4J home page and under
    deployed applications, I choose under applications "Deploy WAR file". It takes me to the next page
    where I enter the war file (pippo.war)
    Application Name: pippo
    Map to URL: /pippo
    THe only choice I have then is to click the Deploy button. I then get the response
    "Failed to deploy web application "pippo". Jar file: /var/tmp/jar29056.tmp is missing its standard xml descriptor located at WEB-INF/web.xml"
    In that path there is not that file, there are 2 folders, one with the file .war and one with the file .ear
    I have no idea what this error message means.
    The documentation for deploying servlets in 9ias using enterprise manager makes no mention of this.
    Thanks,
    Marcella

    Marcella,
    Are you using Oracle9iAS 9.0.3 ?
    Does this happen with any war file ?
    Are you able to deploy a ear file without problems ?
    Can you please test if you can deploy your war in a
    OC4J standalone environment ? steps from the general faq available at http://otn.oracle.com/tech/java/oc4j
    How can I deploy a WAR file to OC4J standalone ?
    The command line deployment tool (admin.jar) requires an EAR file as it's deployment archive. To deploy a WAR file using this, you must package the WAR file within a EAR file.
    You can manually deploy a WAR file to OC4J However following are the steps involved in deploying a WAR file in OC4J.
    1. Copy the file to D:\oc4j\j2ee\home\applications where d:\oc4j is the location OC4J is installed in.
    copy mywar.war D:\oc4j\j2ee\home\applications
    2. Open the application.xml file in D:\oc4j\j2ee\home\config directory
    and add the following after the <web-module id="defaultWebApp" path="../default-web-app" />
    line:
    <web-module id="mywar" path="../applications/mywar.war" />
    3. Open the default-web-site.xml file in D:\oc4j\j2ee\home\config directory and add the following after the <default-web-app application="default" name="defaultWebApp" /> line:
    <web-app application="default" name="mywar" root="/mywar" />
    In Oracle9iAS Release 2; deployment of applications is done either using EM or via the DCM commands.
    thanks,
    -Prasad

  • How to deploy WAR file in tomcat.?

    Can anybody please provide step by step information of deploying war file to Jakarta tomcat without IDE.
    I am working on Windows XP with jakarta tomcat 4.1.30.
    Thanks in advance.
    Regards,
    Aman Aggarwal

    See if tomcat runs as a service in your operating system. If you can locate it, you can set the start type to automatic. A very crud way is to run the tomcat startup file from autoexe.bat.
    I don't know how to do this in Linux. Here is a link for tomcat 6. Maybe it is the same in tomcat 4
    [http://tomcat.apache.org/tomcat-6.0-doc/setup.html]
    Edited by: nirvan on Dec 29, 2008 9:15 AM

  • How to deploy war file in wesphere5.1

    hi
    i am new to websphere 5.1. i am trying to deploy war file in websphere admin it giving an error that ear file is corrupt. same file is working with weblogicc..
    so please tell me step by step .
    if is there any other site where can i get the step step process..
    thanks
    anagh

    first step: read documentation
    second step: apply gathered knowledge
    a few pointers, if i am not mistaken your problem is that a weblogic ear uses weblogic specific application.xml, you might wanna focus on that

  • Customizing AM Images & Facing Problem in Update & Deploy War files

    Hey Guys!
    This is Yash Bansal from Gurgaon, India. i am new to access manager. i am now customizing it and facing problem in customizing.
    I have customized images which is present in directory path:
    opt/SUNWam/web-src/services/images/
    and updated services.war file which is present in directory path:
    opt/SUNWam/war/
    with command
    jar -uvf services.war /opt/SUNWam/web-src/services/images/login-backimage.jpg
    then deployed configuration from the web server 7.0 admin console.
    after that when i open the url
    http://<hostname>/amserver/console
    then Page Not Found error comes in the browser.
    Just wanted to ask you guys am i doing the steps right. please help if someone know how to update and deploy war file on Sun Web server 7.0.
    Thanks & Regards,
    Yash Bansal

    Hi!
    Deploying the configuration does not (re)deploy the application. Webserver stores a copy of the deployed application and all configurations in the admin instance. When you change anything in the webserver console it is first written there and only applied to the productive instance when you deploy configuration.
    When you add images, jsps or something else to /opt/SUNWam/... and want it redeployed you have to use amconfig command. in /opt/SUNWam/bin there is a file called amsamplesilent. You have to fill the values in this file and then use
    ./amconfig -s amsamplesilent
    I believe for a redeploy you have to set DEPLOY_LEVEL to 21, not sure here, check documentation.
    I personally usually do not redeploy for images and such, I simply copy them directly the deployed location.
    Why http://.../amserver/console does not work anymore, I have no idea. But at least after a redeploy it should be there again.
    hth Chris

  • Deploying WAR file gets error

    Hi,
    I am new to weblogic and am trying to deploy jsps and servlets. This is my directory structure:
    MiniEjbs --> src, build, myapp dirs
    src ---->CalculateHOme,Calculate,CalculateBean. java files
    build----> src ----> ejb's class files
    ----> META-INF-----> *.xml (for ejb)
    --->MiniEjb.jar,Miniwebapps.war
    myapp--->WEB-INF--->*.xml(web)
    --->class---> accessServlet.class
    ---> calc_num.jsp
    when I deploy the war file using console I get an error
    J2EE:160043]Missing deployment descriptor "WEB-INF/web.xml"at "C:\bea\user_projects\domains\AnilRukkuDomain\AnilRukku\upload\Miniwebapp.war"
    I created a new domain AnilRukkuDomain,but all my ejbs and client apps are in C:\MiniEjbs dir.Is this a problem for my deployment? After I deploy would my context root be myapp or do I set that explicitly? My ejbs are deployed without any problem.Will my application run if I create seperate modules and deploy individually?Is it mandatory for me to create an application?
    Kindly help me out with this. I appreciate your help.
    Thanks,
    Rukmini

    Hello,
    Could you check weblogic.xml?
    Specifically the element jsp-descriptors.
    For example:
    One can receive the same error if weblogic.xml had specified workingDir to a non-existent directory i.e d:\foo.
    The problem was that the weblogic.xml specified a non-existent directory for "workingDir" parameter for jsp-descriptor. Check once weblogic.xml especially <jsp-descriptor>.
    <jsp-descriptor>
    <jsp-param>
    <param-name>compileCommand</param-name>
    <param-value>javac</param-value>
    </jsp-param>
    <jsp-param>
    <param-name>workingDir</param-name>
    <param-value>d:\foo</param-value>
    </jsp-param>
    <jsp-param>
    <param-name>keepgenerated</param-name>
    <param-value>true</param-value>
    </jsp-param>
    Try to comment any elements in weblogic.xml that is either not used or redundant.
    There is one CR also filed for prabably similar issue. You can get more informaiton about CR200819 from bea support.
    Regards,
    Kuldeep Singh.

Maybe you are looking for