Deploying exploded archives?

Hi,
          I am doing J2EE/Struts/EJB Development on Weblogic 8.1.
          Have an EAR file with WAR file and bunch of EJB JARs inside that EAR.
          I need to do a lot of changes and additions to the GUI,
          which is mostly JSPs inside that WAR.
          Probably the easiest way to do it would be by editing
          JSPs deployed on Weblogic directly, however I can't do it,
          because it explodes EAR, but not WAR file inside the EAR.
          Is there a way of exploding WAR there [via console or Ant]?
          Or can I make changes to JSPs in my build folders and somehow auto-deploy them on running Weblogic ? I've heard of wldeploy, but not sure how to use it for that.
          [use Eclipse IDE]
          Please help !
          Thank you,
          Oleg.

This should work with exploded archives where an exploded ear contains one or more exploded j2ee modules. If the webapps are exploded then any change made to JSPs is automatically re-compiled the next time you refresh the browser.
          exploded_ear/exploded_war/foo.jsp
          /WEB-INF/web.xml
          So in summary, using an exploded war should do the trick.
          -- Nagesh

Similar Messages

Wls 8.1 sp5 - cannot deploy exploded archive anymore

Hi all,
I used to deploy exploded archive in development mode with wls 8.1 sp4. When browsing the file system, the console used to show a radio button to the left of folders which contained an exploded war.
Since I replace 8.1 sp4 with 8.1 sp5, this radio button does not appear anymore along folders that contain exploded war.
Is this a known issue ? Anyone reproduced the same behaviour ?
Thanks for letting me know of any workaround as this feature is really handy ...
Kind regards,
Regis

Dear Prasanth,
You're right; so what I did next was to rename my .jspx to .jsp, and this time round I hit this exception while accessing the index.jsp page, any idea what other stuffs I did to do?
Thanks for your help!
javax.servlet.jsp.JspException: Cannot find FacesContext
at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:405)
at com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java:105)

Problem in Deployment as Exploded archive

Hi All,
I am really saturated working on above. currently My application deploy as single .ear file. I need to deploy my application as exploded archive. for the same I have changed my deployment scripts which explode my ear file and .jar file inside .ear file in the applications dir of my domain. I also install weblogic as service. so then when I start the weblogic, it has got exception while deploying EJBmodule.
<Error> <Deployer> < BEA-149205> <failed to initialize the application myapplication due to err { module name : EJBS.jar,Error:exception preparing module:EJBModule
If someone has step-by-step process of deploying ear application as exploded in production please send it to me. I will be very thankful.
Apart from that I have few queries.
1. How workshop compile and build application. I know in normal case it uses wlwbuild but I would like in detail from where it gets information about what to build and how.
2. when workshop build the application, where all classes are stored on server (in devlopment mode)

Did you find my experiments with the Oracle AS at http://blogs.sun.com/marcoscorner? Look at the navigation bar to fina all the pieces;-)
Maybe that gives you some hints.
Thanks,
-- Marco

JSF 1.2 app is deployed only in exploded archive mode if JSF 2.0 facet used

Hi.
I'm developing JSF 1.2 + facelets application. The only way to configure eclipse WTP editors to properly handle xhtml pages is to install JSF 2.0 facet (there was facelets plugin before, but it was superseded by JSF 2.0 facet if I'm not mistaken). When application is deployed on WL, OEPE show message that JSF 2.0 applications can be deployed only in exploded archive mode.
Is there any way to make OEPE to believe that this application is based on JSF 1.2 (as really is)?
Regards,
Vadim.

Hi, Ian.
You are stating that it's a JSF 2.0 app by selecting that facet - the tooling relies on your facet selection to determine what features are available.Thought as much. Determining which JSF implementation will be active at deployment time looks like very complicated task and facet version is a reliable source of such kind info. Sadly :)
What "eclipse WTP editors" are you trying to configure?"HTML editor". Without JSF 2.0 facet it doesn't handle JSF taglibs' namespaces and EL expressions content assist/navigation.
The other option is to install JBoss Tools richfaces support, but for various reasons I'd like not to.
After using exploded deployment for a week now I see that it is not that slow as I initially thought (at least for a small project): JSP/XHTML changes picked up, class methods reloaded. Manual republishing is still not as fast as in case of the splitsource deployment, but it don't call it often.
Thanks.
Edited by: user3269289 on Apr 8, 2011 2:34 AM

How the diference " publish as a virtual application vs an exploded archive" ?

how the diference " publish as a virtual application vs an exploded archive" ?

Hi,
The following documentation describes the difference between virtual vs exploded archive deployment.
http://docs.oracle.com/cd/E13222_01/wls/docs103/deployment/deployunits.html
FYI: In OEPE, you can select the deployment option on Server Properties window. Here are the steps to switch between Virtual/Exploded archive deployment:
> In Server view, right click on server configuration | select "Properties"
> Expand WebLogic | and select "Publishing" to modify the mode
-Ram

Deploying Enterprise Archive into weblogic 10.3.4.0 application server

Hi All,
I am trying to deploy enterprise archive into web-logic application server. This ear contains two modules. web service module and web application module.
This application was previously running on Apache tomcat server and now i am migrating to web-logic application server.
I am getting following error when deploying to the web-logic application server. Below exception.
For web service and web application, I am using Hibernate and Spring frameworks. Following are the dependencies of web service
[INFO] ------------------------------------------------------------------------
[INFO] Building WebServiceModule Maven Webapp 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ MavenWebAppModule ---
[INFO] com.packt.maven:MavenWebAppModule:war:1.0-SNAPSHOT
[INFO] +- com.packt.maven:BusinessLogicModule:jar:1.0-SNAPSHOT:compile
[INFO] | +- com.packet.maven:DataPersistanceModule:jar:1.0-SNAPSHOT:compile
[INFO] | \- com.packt.maven:DataModelModule:jar:1.0-SNAPSHOT:compile
[INFO] +- com.packt.maven:WebServiceClientModule:jar:1.0-SNAPSHOT:compile
[INFO] +- org.apache.struts:struts2-core:jar:2.1.8:compile
[INFO] | +- com.opensymphony:xwork-core:jar:2.1.6:compile
[INFO] | | \- org.springframework:spring-test:jar:2.5.6:compile
[INFO] | +- org.freemarker:freemarker:jar:2.3.15:compile
[INFO] | +- ognl:ognl:jar:2.7.3:compile
[INFO] | +- commons-fileupload:commons-fileupload:jar:1.2.1:compile
[INFO] | \- commons-io:commons-io:jar:1.3.2:compile
[INFO] +- org.apache.struts:struts2-spring-plugin:jar:2.1.8:compile
[INFO] | +- org.springframework:spring-beans:jar:2.5.6:compile
[INFO] | +- org.springframework:spring-core:jar:2.5.6:compile
[INFO] | \- org.springframework:spring-context:jar:2.5.6:compile
[INFO] | \- aopalliance:aopalliance:jar:1.0:compile
[INFO] +- xml-apis:xml-apis:jar:1.0.b2:provided (scope not updated to compile)
[INFO] +- javassist:javassist:jar:3.12.1.GA:compile
[INFO] +- com.oracle:ojdbc6:jar:11.2.0:compile
[INFO] +- org.springframework:spring:jar:2.5.6:compile
[INFO] +- org.springframework:spring-web:jar:2.5.6:compile
[INFO] +- org.hibernate:hibernate:jar:3.2.7.ga:compile
[INFO] | +- net.sf.ehcache:ehcache:jar:1.2.3:compile
[INFO] | +- javax.transaction:jta:jar:1.0.1B:compile
[INFO] | \- asm:asm-attrs:jar:1.5.3:compile
[INFO] +- dom4j:dom4j:jar:1.6.1:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] +- commons-collections:commons-collections:jar:3.2.1:compile
[INFO] +- cglib:cglib:jar:2.2:compile
[INFO] +- antlr:antlr:jar:2.7.7:compile
[INFO] +- asm:asm:jar:3.3:compile
[INFO] +- javax.xml.soap:saaj-api:jar:1.3.3:compile
[INFO] | \- javax.activation:activation:jar:1.1:compile
[INFO] +- com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.4:compile
[INFO] | \- org.jvnet:mimepull:jar:1.4:compile
[INFO] \- junit:junit:jar:3.8.1:test (scope not updated to compile)
[INFO]
Following are the dependencies of maven web app module
[INFO] ------------------------------------------------------------------------
[INFO] Building MavenWebAppModule Maven Webapp 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ WebServiceModule ---
[INFO] com.packt.maven:WebServiceModule:war:1.0-SNAPSHOT
[INFO] +- org.springframework:spring:jar:2.5.6:compile
[INFO] +- org.springframework:spring-web:jar:2.5.6:compile
[INFO] | +- org.springframework:spring-beans:jar:2.5.6:compile
[INFO] | +- org.springframework:spring-context:jar:2.5.6:compile
[INFO] | | \- aopalliance:aopalliance:jar:1.0:compile
[INFO] | \- org.springframework:spring-core:jar:2.5.6:compile
[INFO] +- xml-apis:xml-apis:jar:1.0.b2:provided (scope not updated to compile)
[INFO] +- javax:javaee-api:jar:6.0:provided
[INFO] +- junit:junit:jar:3.8.1:test (scope not updated to compile)
[INFO] +- com.oracle:ojdbc6:jar:11.2.0:compile
[INFO] +- org.hibernate:hibernate:jar:3.2.7.ga:compile
[INFO] | +- net.sf.ehcache:ehcache:jar:1.2.3:compile
[INFO] | +- javax.transaction:jta:jar:1.0.1B:compile
[INFO] | \- asm:asm-attrs:jar:1.5.3:compile
[INFO] +- dom4j:dom4j:jar:1.6.1:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] +- commons-collections:commons-collections:jar:3.2.1:compile
[INFO] +- cglib:cglib:jar:2.2:compile
[INFO] +- antlr:antlr:jar:2.7.7:compile
[INFO] +- com.sun.xml.ws:jaxws-rt:jar:2.2.3:compile
[INFO] | +- javax.xml.ws:jaxws-api:jar:2.2.3:compile
[INFO] | | +- javax.xml.bind:jaxb-api:jar:2.2.2:compile
[INFO] | | \- org.glassfish:javax.annotation:jar:3.1-b35:compile
[INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile
[INFO] | +- com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.8:compile
[INFO] | +- com.sun.xml.stream.buffer:streambuffer:jar:1.2:compile
[INFO] | +- org.codehaus.woodstox:wstx-asl:jar:3.2.1:compile
[INFO] | | \- stax:stax-api:jar:1.0.1:compile
[INFO] | +- org.jvnet.staxex:stax-ex:jar:1.4:compile
[INFO] | | \- javax.xml.stream:stax-api:jar:1.0-2:compile
[INFO] | +- com.sun.org.apache.xml.internal:resolver:jar:20050927:compile
[INFO] | +- org.jvnet:mimepull:jar:1.5:compile
[INFO] | +- com.sun.xml.ws:policy:jar:2.2.2:compile
[INFO] | | +- com.sun.xml.txw2:txw2:jar:20090102:compile
[INFO] | | \- com.sun.istack:istack-commons-runtime:jar:2.2.1:compile
[INFO] | +- org.glassfish.gmbal:gmbal-api-only:jar:3.1.0-b001:compile
[INFO] | | \- org.glassfish.external:management-api:jar:3.0.0-b012:compile
[INFO] | \- org.glassfish.ha:ha-api:jar:3.1.8:compile
[INFO] +- asm:asm:jar:3.3:compile
[INFO] \- org.jvnet.jax-ws-commons.spring:jaxws-spring:jar:1.8:compile
[INFO] +- javax.servlet:servlet-api:jar:2.5:compile
[INFO] +- org.apache.xbean:xbean-spring:jar:2.7:compile
[INFO] +- javax.jws:jsr181-api:jar:1.0-MR1:compile
[INFO] +- javax.xml.soap:saaj-api:jar:1.3:compile
[INFO] +- com.sun.xml.stream:sjsxp:jar:1.0:compile
[INFO] +- javax.annotation:jsr250-api:jar:1.0:compile
[INFO] \- javax.activation:activation:jar:1.1:compile
[INFO]
In my weblogic application configuration i have provided following configuration to load java from my applications first. Could anybody help me on this issue. Thanks in advance for anyhelp
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application
     xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.0/weblogic-application.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd">
     
     <wls:application-param>
          <wls:param-name>webapp.encoding.default</wls:param-name>
          <wls:param-value>UTF-8</wls:param-value>
     </wls:application-param>
     <wls:prefer-application-packages>
          <wls:package-name>antlr.*</wls:package-name>
     </wls:prefer-application-packages>
</wls:weblogic-application>
Exception.......
SEVERE: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.sun.xml.ws.transport.http.servlet.SpringBinding#0' defined in ServletContext resourcepring/config/SpringBeans.xml]: Cannot create inner bean '(inner bean)' of type [org.jvnet.jax_ws_commons.spring.SpringService] while setting bean property 'service'; nested exceramework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)': FactoryBean threw exception on object creation; nested exception is java.lang.Linkageaint violation: when resolving field "DATETIME" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the referring class, javax/xml/datatype/Datahe class loader (instance of <bootloader>) for the field's resolved type, javax/xml/namespace/QName, have different Class objects for that type
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:230)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1245)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1010)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472)
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.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
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:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
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:323)
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:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)': FactoryBean threw exception on object creation; nested exceptiogeError: loader constraint violation: when resolving field "DATETIME" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the referring class, jtatypeConstants, and the class loader (instance of <bootloader>) for the field's resolved type, javax/xml/namespace/QName, have different Class objects for that type
Edited by: user8643895 on Apr 14, 2013 3:42 AM

This forum is about iAS. For weblogic go to: WebLogic Server - General

How to deploy exploded war file(from JBoss-Eclipse IDE) to Sun Server 9

anyone plz tell how to deploy exploded war file (from JBoss-Eclipse IDE) to sun application server 9.i deployed noramllay at tht time404 hrown.plzz tell urgent
regards,
S Sunder

Hi!
How did You deploy WAR file? Did You try to do this with Application Server Admin Console?
Thanks,
Roman.

Deploy exploded WAR file

Hello!
I need to deploy a war file extracted into a custom folder. Is it possible in WEB AS to point the deployment to a particular folder of our choice instead of deploying the WAR/EAR file?
Thanks
/Ray

Hi Ray,
applications on Web AS are deployed in the database, and the corresponding binaries are synchronized to the file system from the DB. Hence, you cannot point the deployment to a custom directory.
Anyway, why do you need that? Usually, exploded deployment is needed for development environment for the sake of quick update of the changed files? Is that your requirement also? If so, you could try using the Single File Update function of the Web AS Deploy service to update single files in your application. For details, see Deploying exploded EAR in WAS 6.40 thread.
Hope that helps a bit.

WLS 10.3.5 : upload a Deployment Plan Archive

hi
Please consider the WebLogic Server 10.3.5 console "Summary of Deployments" page, where an "Install" button takes you to the first page of the "Install Application Assistant" which says "... If you cannot find your deployment files, upload your file(s) ..."
with a link to the page where you can select and upload a "Deployment Archive" and a "Deployment Plan Archive",
a shown in the screenshot at http://www.consideringred.com/files/oracle/img/2011/WLS1035-DeploymentPlanArchive.png
For this "Deployment Plan Archive" the page has a description that says
"A deployment plan is a configuration which can supplement the descriptors included in the deployment archive. A deployment will work without a deployment plan, but you can also upload a deployment plan archive now. This deployment plan archive will be a directory of configuration information packaged as a .jar file. See related links for additional information about deployment plans. "
So, there seems to be a difference between a deployment plan file (plan.xml) and a deployment plan archive (JAR file).
- (q1) Where can I find documentation on what such deployment plan archive (JAR file) should look like?
many thanks
Jan Vervecken

fyi
In the context of service request 3-4667732128 I got this feedback:
"Deployment Plan Archive" Option that we have in WebLogic Console at Deployment Service is new feature added from 11G and currently not under full fledged implementation, so that's the reason its not documented in any of the Oracle Documentation.regards
Jan

Deploying .WAR archive gives classNotFound:FacesServlet error

Hi all,
I am using ANT scripts to build a .war archive of an ADF project, I am then using the .war archive to manually deploy to a weblogic server.
However, when I do this, I get the following error message:
[09 October 2012 09:30:27 o'clock BST] Initiating deploy operation ...
[09 October 2012 09:30:27 o'clock BST] Validating deployment plan...
[09 October 2012 09:30:28 o'clock BST] Deployment plan validated.
[09 October 2012 09:30:28 o'clock BST] Archive: C:\MIDDLE~2\USER_P~1\domains\SOASUI~1\sysman\upload\deploy\otn\archive\otn.war
[09 October 2012 09:30:28 o'clock BST] Deployment plan: C:\MIDDLE~2\USER_P~1\domains\SOASUI~1\sysman\upload\deploy\otn\config\plan.xml
[09 October 2012 09:30:29 o'clock BST] [Deployer:149193]Operation 'deploy' on application 'otn' has failed on 'AdminServer'
[09 October 2012 09:30:29 o'clock BST] java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet
[09 October 2012 09:30:29 o'clock BST] javax.faces.webapp.FacesServlet
[09 October 2012 09:30:29 o'clock BST] Deploy operation failed.
Can anyone offer a solution to this problem?
Thanks
Onkar

The problem was that the weblogic.xml specified a non-existent directory for "workingDir" parameter for 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>
          </jsp-descriptor>
          please check your jsp-descriptor attribute.
          - Navaneeth

Deployment using exploded archive

Hello, I have just one question:
Is it possible to deploy a large application with 1 archive file ( .ear ) which contains many modules (but modules are not packaged, just some directories with the same name than the module packaged).
Example:
test.ear/web.war
web.war is a directory, the same file structure than a web module packaged ...
Is it possible to do that ? WebLogic will accept that .ear ???
Edited by loopx at 03/30/2007 12:58 AM

To complicate matters I'm also mixing in M2Eclipse & M2EclipseWTP, however I don't think that is part of the issue here.Your assumption is wrong. OEPE does not support M2Eclipse and trying to mix the two will not yield good results.
- Konstantin

Exploded / Archive J2ee Applications

What is the difference between Exploded and Archived J2ee Applications? How to deploy each of the applications?

What is the difference between Exploded and Archived J2ee Applications? How to deploy each of the applications?

ZipException while deploying exploded .ear

WLS 8.1 SP1.
My .ear contains 2 ejb.jar's, 1 web.war, and some library jar's. It is deployed
without any problem. Now trying to deploy as exploded directory, I got
<Jul 30, 2003 12:15:14 PM EDT> <Error> <J2EE> <BEA-160131> <Error deploying abc_web:
with deployment error Could not load abc_web and nested error weblogic.management.DeploymentException:
[HTTP:101062][ServletContext(id=3831981,name=,context-path=/)] Error reading Web
application "c:\bea\user_projects\ABC\deploy\abc_app.ear\abc_web.war".
java.util.zip.ZipException: Access is denied
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:112)
at java.util.jar.JarFile.<init>(JarFile.java:117)
at java.util.jar.JarFile.<init>(JarFile.java:55)
Any suggestions? Thanks.
Eric Ma

Are you saying that you are successfully using a directory name of
<something>.war in WL 8.1xx? I continue to get the error you mentioned. I
suspect that it is a bug in WL. You will notice that the stack trace goes
through java.util.ZipFile. This makes me think that WL is supposing that the
archive is jar'ed instead of exploded.
"Eric Ma" <[email protected]> wrote in message
news:[email protected]..
>
sangita:
Thanks a lot! I deleted the .wlnotdelete directory and restarted theserver and
now it works!
Eric Ma
"sangita" <[email protected]> wrote:
did you deleted all references to the old .ear file ???
i hope you might have deleted/undeployed the .ear file before deploying
as in
exploded form ?
"Eric Ma" <[email protected]> wrote:
WLS 8.1 SP1.
My .ear contains 2 ejb.jar's, 1 web.war, and some library jar's. It
is deployed
without any problem. Now trying to deploy as exploded directory, Igot
<Jul 30, 2003 12:15:14 PM EDT> <Error> <J2EE> <BEA-160131> <Error
deploying
abc_web:
with deployment error Could not load abc_web and nested errorweblogic.management.DeploymentException:
[HTTP:101062][ServletContext(id=3831981,name=,context-path=/)] Error
reading Web
application "c:\bea\user_projects\ABC\deploy\abc_app.ear\abc_web.war".
java.util.zip.ZipException: Access is denied
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:112)
at java.util.jar.JarFile.<init>(JarFile.java:117)
at java.util.jar.JarFile.<init>(JarFile.java:55)
Any suggestions? Thanks.
Eric Ma

Deploying exploded war to a managed server

We've just started using exploded war files for development, but we're
having trouble deploying these applications on server's other than the
managing/console. We keep getting this error:
Error deploying application zq: error retrieving component [
Caching Stub]Proxy for blue:Name=zq,Location=webserv,Type=We
bAppComponentConfig,ApplicationConfig=zq
Can someone shed some light on what this cryptic message means?
Thanks,
Eric

Interesting, never seen this before.
can you give some details - which server, complete trace etc....
mihir
Eric F wrote:
We've just started using exploded war files for development, but we're
having trouble deploying these applications on server's other than the
managing/console. We keep getting this error:
Error deploying application zq: error retrieving component [
Caching Stub]Proxy for blue:Name=zq,Location=webserv,Type=We
bAppComponentConfig,ApplicationConfig=zq
Can someone shed some light on what this cryptic message means?
Thanks,
Eric

Deploying exploded ear file

Hi,
I have exploded an ear file, and I am trying to deploy it in weblogic 7.0.
This ear has several jars and war files.
However, when I deploy it
(Access is denied) at java.io.FileInputStream.open(Native Method) -- while trying
to open the war file.
I have followed the same steps as mentioned in the bea docs , by exploding all
the individual wars, jars, inside the ear ..
Any help is appreciated..
Thanks in advance.

I believe manifest class-paths should work fine for exploded EARs as
well. Don't you want 'common' rather than '../common' in your
class-path entry?
-- Rob
Eric Ma wrote:
Rob:
Yes, I was talking about the MANIFEST.MF Class-Path entries. My exploded ear
looks like (under mydomain/applications)
app
--META-INF
----application.xml
--ejb
----com
------abc.class
----META-INF
------MANIFEST.MF
------ejb-jar.xml
--common
----com
------xyz.class
--web
----jsp
----WEB-INF
------web.xml
------lib
--------struts.jar
The MANIFEST.MF file has
Class-Path: ../common/
I read at http://e-docs.bea.com/wls/docs61/ejb/EJB_deployover.html#1074087 that
Class-Path is only supported in the .ear format. Is it true?
Rob Woollen <[email protected]> wrote:
Are you talking about manifest class-path entries? If so, can you show
me what your exploded EAR looks like? (ie its layout and your
class-path entries.)

Deploying exploded archives?

Similar Messages

Maybe you are looking for