Deploy Petstore in Exploded Directory(Weblogic 7.0)

I can deploy and run the Petstore in .ear format under Weblogic 7.0. How do I
run it in the Exploded format? Do I need to remove all the .ear, .jar, .war entries/tags
in my config.xml and application.xml files.
I did un-jar all the petstor.ear file and all the .jar files inside the petstore.ear(except
the jar files in the WEB-INF/lib/ directory). I did delete all the .ear, .jar
& .war files(except the jar files in the WEB-INF/lib/ directory), before I put
the exploded petstore/ directory under the ...server/config/examples/applications
directory.
Do I need to put an empty REDEPLOY file in the WEB-INF directory? Anything else
that I'm missing?
Please help! I'm stucked here.
I've attached a jar file, which includes my xml files and log files:
1. ...samples/server/config/examples/config.xml
2. ...samples/server/config/examples/applications/petstore/META-INF/application.xml
3. ...samples/server/config/examples/applications/petstore/WEB-INF/web.xml
4. ...samples/server/config/examples/applications/petstore/WEB-INF/weblogic.xml
5. 3 log files: wl-domain.log, wxamplesServer.log & access.log
[petstore_xml_log_files.jar]

Similar Messages

Deploy web application with exploded directory format

I am quite new with Oracle9iAS Containers for J2EE. Currently, my project is not using EJB, only JSP and Servlets. I want to deploy the war file with exploded directory format. I don't want to use the default web application directory j2ee/home/default-web-app. The "Using Oracle9iAS Containers for J2EE" get start documentation only explained how to deploy J2ee application. What about the web application without EJB jar file? Anybody knows how to do that. Please let me know.
Thanks in advance.

Though you don't have ejbs, you can still use the ear file format. This would be most convenient way of deploying.
Use of a tool like Ant is recommended if you are not using JDeveloper.
Also, you can findinfo on deploying using a exploded directory
http://otn.oracle.com/docs/tech/java/oc4j/htdocs/getstart.htm#1027810
But recommed having ear file as it is convenient. If you want to see an example of use of Ant and deploying using ear file
check out one of the recently posted how-tos E.g. http://otn.oracle.com/tech/java/oc4j/htdocs/how-to-servlet-events.html

Can't deploy a SINGLE bean in weblogic 6.1 SP2 w/o application reload

Anyone know how to update a single bean in an application without
redeploying the entire application?
We have a project containing 101 beans (session and entity) and 372
jsps which we are deploying on weblogic 6.1, SP2 as a single
application. The project is deployed in an exploded directory format
as follows:
trader/
META-INF/application.xml
lib/
third-party.jar
third-party.jar (etc.)
SessionBean.jar
EntityBean.jar (etc.)
trader/
WEB-INF/web.xml
META-INF/MANIFEST.MF (contains Class-Path: entry to lib dir)
jsp/html/gif's reside below this point.
Each bean jar has a META-INF/MANIFEST.MF to resolve third-party
library dependencies through the use of the Class-Path entry.
When we we try to update a single bean's implementation, the
entire application reloads, which can take between 10 - 30 minutes.
We have tried using the weblogic.deploy tool as well as undeploying
and redeploying the bean from the console. In both cases, the
entire application reloads.
When we use weblogic.deploy, we've tried the following:
weblogic.deploy
-url T3://localhost:7001
update weblogicpwd trader ~/trader/build/SessionBean.jar
and
weblogic.deploy
-url T3://localhost:7001
-component SessionBean:srvr1
update weblogicpwd trader ~/trader/build/SessionBean.jar

Anyone know how to update a single bean in an application without
redeploying the entire application?
We have a project containing 101 beans (session and entity) and 372
jsps which we are deploying on weblogic 6.1, SP2 as a single
application. The project is deployed in an exploded directory format
as follows:
trader/
META-INF/application.xml
lib/
third-party.jar
third-party.jar (etc.)
SessionBean.jar
EntityBean.jar (etc.)
trader/
WEB-INF/web.xml
META-INF/MANIFEST.MF (contains Class-Path: entry to lib dir)
jsp/html/gif's reside below this point.
Each bean jar has a META-INF/MANIFEST.MF to resolve third-party
library dependencies through the use of the Class-Path entry.
When we we try to update a single bean's implementation, the
entire application reloads, which can take between 10 - 30 minutes.
We have tried using the weblogic.deploy tool as well as undeploying
and redeploying the bean from the console. In both cases, the
entire application reloads.
When we use weblogic.deploy, we've tried the following:
weblogic.deploy
-url T3://localhost:7001
update weblogicpwd trader ~/trader/build/SessionBean.jar
and
weblogic.deploy
-url T3://localhost:7001
-component SessionBean:srvr1
update weblogicpwd trader ~/trader/build/SessionBean.jar

Exploded deployment doesn't work in Weblogic 8.1

Hi
I have a very weird problem. I am trying to deploy my apllication in Weblogic
8.1 in exploded format.Well problem is when i deploy it ,on server startup Weblogic
doesn't deploy it automatically way its mentioned in the release.txt and also
way it used to do in WLC 6.1.Also when i deploy it using the console i cannot
get the updated version of my jsp. I have double cked set STARTMODE= false so
its in development mode.I also noticed the various forms of deployment in WLC
8.1 nostage,stage...-
Is there anything i am forgetting.
Thanks
Maulik

Can you show me the server log, the contents of your applications
directory, and your config.xml?
If not, you probably should just open a case with [email protected]
-- Rob
MAULIK SHAH wrote:
Yes Rob exactly the same was as its mentioned in WLS.
Rob Woollen <[email protected]> wrote:
how are you deploying it? via the applications directory?
-- Rob
MAULIK SHAH wrote:
Hi
I have a very weird problem. I am trying to deploy my apllication inWeblogic
8.1 in exploded format.Well problem is when i deploy it ,on serverstartup Weblogic
doesn't deploy it automatically way its mentioned in the release.txtand also
way it used to do in WLC 6.1.Also when i deploy it using the consolei cannot
get the updated version of my jsp. I have double cked set STARTMODE=false so
its in development mode.I also noticed the various forms of deploymentin WLC
8.1 nostage,stage...-
Is there anything i am forgetting.
Thanks
Maulik

Any tool to help deploy with Exploded Directory Format

I read through the "Oracle9iAS Containers for J2EE" Getting Started document and saw the section on "Deploying with Exploded Directory Format". I would like to take the Petstore1.1.2 code and put it in exploded directory format so that OC4J can easily pick up changes to servlets and EJBs. But the codebase for Petstore is complicated enough that I would like to have a tool (possibly ant) that can automate the process of going from either the source directory or even ear file to the "exploded directory format".
Are there any tools available to help automate this process??

Never mind. This stuff is a lot simpler than I initially thought. There is no need for a tool because it is easy enough to do by hand.
Sorry for bothering everyone

Deploying the exploded directory

I am trying to find out if there are any known bugs for deploying the
exploded directory.

Yes. See my recent post in the ejb section called "Classpath Help?"
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
Tangosol: How Weblogic applications are customized
"Mukesh Kumar" <[email protected]> wrote in message
news:3b4e0e25$[email protected]..
I am trying to find out if there are any known bugs for deploying the
exploded directory.

Re: Exploded directory format in an EAR

          I am now trying to deploy the ear file in v6.1 sp2. Has anyone managed to deploy
          an ear where util / third party classes are stored in a lib directory of the ear
          and referenced in EJB-jar manifest.mf files using the classpath header?
          ie as documented in bea weblogic server bible on page 614/615
          EntApp/
          accountEJB.jar
          accountManager.war
          /lib/
          xerces.jar
          xalan.jar
          log4j.jar
          /META-INF/
          application.xml
          "erik" <[email protected]> wrote:
          >
          >This is hearsay but I was recommended to use v 6.1 SP 2.
          >/erik
          >
          >"Ivan" <[email protected]> wrote:
          >>
          >>I have a problem wrapping up an exploded directory format application
          >>into an ear
          >>file running weblogic 6.0sp2 on winnt 4. One of the things I would like
          >>to do
          >>is load a config file from a helper class without specifying a path.
          >>
          >>
          >>EAR APP statementapp.ear contains: META-INF/MANIFEST.MF statement.jar
          >>statementwebapp.war
          >>META-INF/application.xml lib/log4j.jar (and other third party jar files
          >>crimson.jar,
          >>jaxp.jar etc.)
          >>
          >>The third party jar files have been manually unjar'ed and re-jar'ed
          >without
          >>compression
          >>(after reading that a suggestion to someone else).
          >>
          >>WEB APP statementwebapp.war contains: all my jsp's at root level WEB-INF/classes/uk/.../servlets
          >>- servlets WEB-INF/classes/uk/.../util - helper classes WEB-INF/tlds
          >>- tag library
          >>descriptors WEB-INF/web.xml & weblogic.xml - deployment descriptors
          >
          >>
          >>Some of the helper classes make use of configuration files (for example
          >>I have
          >>a Logger class that uses Log4j). Here is how I would like to access
          >the
          >>config
          >>file
          >>
          >>... private static final String config = "config.properties" ; PropertyConfigurator.configure(
          >>config ) ; ...
          >>
          >>I have tried putting the config.properties file in the WEB-INF/classes
          >>directory
          >>and in the WEB-INF directory, however they don't seem to be found by
          >>the class
          >>loader.
          >>
          >>EJB statement.jar contains an ejb with the following: uk...business.statement...
          >>- Statement ejb classes with ejbc generated stub and skeleton classes
          >>uk...util
          >>- Several Helper classes
          >>
          >>One such helper is Logger for which the Log4j jar file is needed. I
          >deploy
          >>the
          >>statement.jar file in the ear (as listed above). Weblogic throws an
          >error
          >>message
          >>saying cannot deploy statement (NoClassDefFound...): java.lang.NoClassDefFoundError:
          >>org/apache/log4j/Category ie it cannot find the log4j package which
          >is
          >>referenced
          >>in the Class-Path header of the manifest.mf file and located in the
          >ear
          >>file under
          >>the lib directory.
          >>
          >>The manifest.mf file contains a line with the following: Class-Path:
          >>lib/log4j.jar
          >>lib/crimson.jar lib/jaxp.jar which I have read should allow the enterprise
          >>classloader
          >>to pick up the log4j.jar and xml parsing classes (ref. weblogic server
          >>bible chap
          >>18) without needing to be referenced in the weblogic start up class
          >path.
          >>
          >>
          >>Can manifest class-path references be used like this in weblogic 6.0?
          >>Where should
          >>I put the application properties files in the war and jar files?
          >>
          >>Clarification much appreciated. Ivan.
          >>
          >>PS: I had this application working in exploded directory format with
          >>the jar files
          >>in the system classpath and the properties file locations hardcoded
          >in
          >>the class
          >>files. (not ideal for a clustered production environment!)
          >>
          >


          This is hearsay again.
          These people did as you did no compression etc. they were able to put the application's
          utility classes in a lib but not the third party jars. They suspected that the
          ear where to big to deploy so they put all thirdparty jars in the system classpath
          and then the internal utility classes were loaded by using CLASSPATH in the manifest
          file.
          I gave up because I could deploy everything except servlets and I went back to
          exploded deployment. That bloody EAR thing took to much time.
          If you succeed in everything including warfiles with JSPs and servlets (those
          I was talking about only had EJBs)
          let me know.
          I also had a peculiar problem with EARs that a cascading stylesheet was not found
          in the ear but it worked in an exploded it worked fine
          Otherwise I must recommend Orion, which I had up and running in a matter of days
          when ported from WLS 5.1.
          Good luck.
          "Ivan" <[email protected]> wrote:
          >
          >I am now trying to deploy the ear file in v6.1 sp2. Has anyone managed
          >to deploy
          >an ear where util / third party classes are stored in a lib directory
          >of the ear
          >and referenced in EJB-jar manifest.mf files using the classpath header?
          >
          >ie as documented in bea weblogic server bible on page 614/615
          >EntApp/
          > accountEJB.jar
          > accountManager.war
          > /lib/
          > xerces.jar
          > xalan.jar
          > log4j.jar
          > /META-INF/
          > application.xml
          >
          >"erik" <[email protected]> wrote:
          >>
          >>This is hearsay but I was recommended to use v 6.1 SP 2.
          >>/erik
          >>
          >>"Ivan" <[email protected]> wrote:
          >>>
          >>>I have a problem wrapping up an exploded directory format application
          >>>into an ear
          >>>file running weblogic 6.0sp2 on winnt 4. One of the things I would
          >like
          >>>to do
          >>>is load a config file from a helper class without specifying a path.
          >>>
          >>>
          >>>EAR APP statementapp.ear contains: META-INF/MANIFEST.MF statement.jar
          >>>statementwebapp.war
          >>>META-INF/application.xml lib/log4j.jar (and other third party jar files
          >>>crimson.jar,
          >>>jaxp.jar etc.)
          >>>
          >>>The third party jar files have been manually unjar'ed and re-jar'ed
          >>without
          >>>compression
          >>>(after reading that a suggestion to someone else).
          >>>
          >>>WEB APP statementwebapp.war contains: all my jsp's at root level WEB-INF/classes/uk/.../servlets
          >>>- servlets WEB-INF/classes/uk/.../util - helper classes WEB-INF/tlds
          >>>- tag library
          >>>descriptors WEB-INF/web.xml & weblogic.xml - deployment descriptors
          >>
          >>>
          >>>Some of the helper classes make use of configuration files (for example
          >>>I have
          >>>a Logger class that uses Log4j). Here is how I would like to access
          >>the
          >>>config
          >>>file
          >>>
          >>>... private static final String config = "config.properties" ; PropertyConfigurator.configure(
          >>>config ) ; ...
          >>>
          >>>I have tried putting the config.properties file in the WEB-INF/classes
          >>>directory
          >>>and in the WEB-INF directory, however they don't seem to be found by
          >>>the class
          >>>loader.
          >>>
          >>>EJB statement.jar contains an ejb with the following: uk...business.statement...
          >>>- Statement ejb classes with ejbc generated stub and skeleton classes
          >>>uk...util
          >>>- Several Helper classes
          >>>
          >>>One such helper is Logger for which the Log4j jar file is needed. I
          >>deploy
          >>>the
          >>>statement.jar file in the ear (as listed above). Weblogic throws an
          >>error
          >>>message
          >>>saying cannot deploy statement (NoClassDefFound...): java.lang.NoClassDefFoundError:
          >>>org/apache/log4j/Category ie it cannot find the log4j package which
          >>is
          >>>referenced
          >>>in the Class-Path header of the manifest.mf file and located in the
          >>ear
          >>>file under
          >>>the lib directory.
          >>>
          >>>The manifest.mf file contains a line with the following: Class-Path:
          >>>lib/log4j.jar
          >>>lib/crimson.jar lib/jaxp.jar which I have read should allow the enterprise
          >>>classloader
          >>>to pick up the log4j.jar and xml parsing classes (ref. weblogic server
          >>>bible chap
          >>>18) without needing to be referenced in the weblogic start up class
          >>path.
          >>>
          >>>
          >>>Can manifest class-path references be used like this in weblogic 6.0?
          >>>Where should
          >>>I put the application properties files in the war and jar files?
          >>>
          >>>Clarification much appreciated. Ivan.
          >>>
          >>>PS: I had this application working in exploded directory format with
          >>>the jar files
          >>>in the system classpath and the properties file locations hardcoded
          >>in
          >>>the class
          >>>files. (not ideal for a clustered production environment!)
          >>>
          >>
          >

Exploded directory format in an EAR

          I have a problem wrapping up an exploded directory format application into an ear
          file running weblogic 6.0sp2 on winnt 4. One of the things I would like to do
          is load a config file from a helper class without specifying a path.
          EAR APP statementapp.ear contains: META-INF/MANIFEST.MF statement.jar statementwebapp.war
          META-INF/application.xml lib/log4j.jar (and other third party jar files crimson.jar,
          jaxp.jar etc.)
          The third party jar files have been manually unjar'ed and re-jar'ed without compression
          (after reading that a suggestion to someone else).
          WEB APP statementwebapp.war contains: all my jsp's at root level WEB-INF/classes/uk/.../servlets
          - servlets WEB-INF/classes/uk/.../util - helper classes WEB-INF/tlds - tag library
          descriptors WEB-INF/web.xml & weblogic.xml - deployment descriptors
          Some of the helper classes make use of configuration files (for example I have
          a Logger class that uses Log4j). Here is how I would like to access the config
          file
          .. private static final String config = "config.properties" ; PropertyConfigurator.configure(
          config ) ; ...
          I have tried putting the config.properties file in the WEB-INF/classes directory
          and in the WEB-INF directory, however they don't seem to be found by the class
          loader.
          EJB statement.jar contains an ejb with the following: uk...business.statement...
          - Statement ejb classes with ejbc generated stub and skeleton classes uk...util
          - Several Helper classes
          One such helper is Logger for which the Log4j jar file is needed. I deploy the
          statement.jar file in the ear (as listed above). Weblogic throws an error message
          saying cannot deploy statement (NoClassDefFound...): java.lang.NoClassDefFoundError:
          org/apache/log4j/Category ie it cannot find the log4j package which is referenced
          in the Class-Path header of the manifest.mf file and located in the ear file under
          the lib directory.
          The manifest.mf file contains a line with the following: Class-Path: lib/log4j.jar
          lib/crimson.jar lib/jaxp.jar which I have read should allow the enterprise classloader
          to pick up the log4j.jar and xml parsing classes (ref. weblogic server bible chap
          18) without needing to be referenced in the weblogic start up class path.
          Can manifest class-path references be used like this in weblogic 6.0? Where should
          I put the application properties files in the war and jar files?
          Clarification much appreciated. Ivan.
          PS: I had this application working in exploded directory format with the jar files
          in the system classpath and the properties file locations hardcoded in the class
          files. (not ideal for a clustered production environment!)


          This is hearsay but I was recommended to use v 6.1 SP 2.
          /erik
          "Ivan" <[email protected]> wrote:
          >
          >I have a problem wrapping up an exploded directory format application
          >into an ear
          >file running weblogic 6.0sp2 on winnt 4. One of the things I would like
          >to do
          >is load a config file from a helper class without specifying a path.
          >
          >
          >EAR APP statementapp.ear contains: META-INF/MANIFEST.MF statement.jar
          >statementwebapp.war
          >META-INF/application.xml lib/log4j.jar (and other third party jar files
          >crimson.jar,
          >jaxp.jar etc.)
          >
          >The third party jar files have been manually unjar'ed and re-jar'ed without
          >compression
          >(after reading that a suggestion to someone else).
          >
          >WEB APP statementwebapp.war contains: all my jsp's at root level WEB-INF/classes/uk/.../servlets
          >- servlets WEB-INF/classes/uk/.../util - helper classes WEB-INF/tlds
          >- tag library
          >descriptors WEB-INF/web.xml & weblogic.xml - deployment descriptors
          >
          >Some of the helper classes make use of configuration files (for example
          >I have
          >a Logger class that uses Log4j). Here is how I would like to access the
          >config
          >file
          >
          >... private static final String config = "config.properties" ; PropertyConfigurator.configure(
          >config ) ; ...
          >
          >I have tried putting the config.properties file in the WEB-INF/classes
          >directory
          >and in the WEB-INF directory, however they don't seem to be found by
          >the class
          >loader.
          >
          >EJB statement.jar contains an ejb with the following: uk...business.statement...
          >- Statement ejb classes with ejbc generated stub and skeleton classes
          >uk...util
          >- Several Helper classes
          >
          >One such helper is Logger for which the Log4j jar file is needed. I deploy
          >the
          >statement.jar file in the ear (as listed above). Weblogic throws an error
          >message
          >saying cannot deploy statement (NoClassDefFound...): java.lang.NoClassDefFoundError:
          >org/apache/log4j/Category ie it cannot find the log4j package which is
          >referenced
          >in the Class-Path header of the manifest.mf file and located in the ear
          >file under
          >the lib directory.
          >
          >The manifest.mf file contains a line with the following: Class-Path:
          >lib/log4j.jar
          >lib/crimson.jar lib/jaxp.jar which I have read should allow the enterprise
          >classloader
          >to pick up the log4j.jar and xml parsing classes (ref. weblogic server
          >bible chap
          >18) without needing to be referenced in the weblogic start up class path.
          >
          >
          >Can manifest class-path references be used like this in weblogic 6.0?
          >Where should
          >I put the application properties files in the war and jar files?
          >
          >Clarification much appreciated. Ivan.
          >
          >PS: I had this application working in exploded directory format with
          >the jar files
          >in the system classpath and the properties file locations hardcoded in
          >the class
          >files. (not ideal for a clustered production environment!)
          >

Java.util.zip.ZipException: Is a directory- weblogic exception comming

I am getting following exception while deploying the web application in weblogic Enviornment, on Sun solaris 5.8, please help:
<Jul 11, 2008 5:39:07 PM EDT> <Error> <J2EE> <BEA-160131> <Error deploying fotrd: with deployment error Could not load fotrd and nested error weblogic.management.DeploymentException: [HTTP:101062][ServletContext(id=175067,name=,context-path=/)] Error reading Web application "/export/enterprise-docs/fo2oli/citioliprodfix/po2trd/deploy/po2trd.ear/fotrd.war".
java.util.zip.ZipException: Is a directory
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.><init>(ZipFile.java:111)
at java.util.jar.JarFile.<init>(JarFile.java:127)
at java.util.jar.JarFile.<init>(JarFile.java:65)
at weblogic.servlet.internal.WebAppServletContext.getDescriptorLoader(WebAppServletContext.java:1443)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:492)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:621)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:121)
at weblogic.j2ee.Application.addComponent(Application.java:322)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:162)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:202)
at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:516)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
at weblogic.management.configuration.WebServerMBean_Stub.addWebDeployment(WebServerMBean_Stub.java:2596)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:289)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:755)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:734)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:516)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:990)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:948)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:948)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:475)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7731)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1321)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:339)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)

Could it be that you are trying to install from an exploded version of your war files? It looks like WebLogic thinks it's a war file but it seems to be a directory... You might try to rename those directories to anything that's not .war and .ear.

Exploded directory: wl6.0 sp2: how to define in config.xml?

hi,
          how do i define a web server with exploded directory format. i dont want to
          use webcomponent because it creates a war and the jsp changes are not
          reflected. war is fine for production, but during development i dont want to
          restart the server to see the jsp changes.
          is there a way to create a web server component with an exploded directory
          format in config.xml. i want to map the current jsp directory to the web
          server.
          in short: i want to see the jsp changes immediately without restarting the
          server everytime.
          thanks.


          "Muthu Ram" <[email protected]> wrote:
          >hi,
          >
          >how do i define a web server with exploded directory format. i dont want
          >to
          >use webcomponent because it creates a war and the jsp changes are not
          >reflected. war is fine for production, but during development i dont
          >want to
          >restart the server to see the jsp changes.
          >
          >is there a way to create a web server component with an exploded directory
          >format in config.xml. i want to map the current jsp directory to the
          >web
          >server.
          >
          >in short: i want to see the jsp changes immediately without restarting
          >the
          >server everytime.
          >
          >thanks.
          >
          >
          apparently if you create an empty file called REDEPLOY (no exstension) in your
          meta-inf directory then either touch it if on unix or change it and save it (i
          add then delete a spce in it) in win32. apparently wls looks at this file and
          if its been changed it reloads the rest off the webapp and hey presto dynamic
          deployment. the alternative is to goto the console goto your app uncheck the deployed
          box click apply then check the deployed box and click apply (this should redeploy
          it). Note jsps don't seem to redeploy well if you have keepgenerate set to true
          in the weblogic.xml.

Does a war file explode in Weblogic ?

I deployed a war file in weblogic, and I am not able to find one that is exploded, I worked with Tomcat previously and when I deploy a war file, I can see the exploded war file in the same directory..please give links, reference...if you can...I will read up.
thanks
Pradeep

Why do you need to see the exploded war file? If you wanted to deploy an exploded war file, then deploy an exploded war file (by copying the dirtree to the "applications" directory).

Problem in deploying an ear file in weblogic 8.1 SP5

Hi,
When I tried deploying my ear file in Weblogic 8.1 SP5, I am getting the following error:
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for counter-ejb.jar
Module: counter-ejb.jar Error: Exception preparing module: EJBModule(counter-ejb.jar,status=NEW)
Unable to deploy EJB: com_liferay_counter_service_ejb_CounterServiceEJB from counter-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'mail/MailSession' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
at weblogic.ejb20.deployer.EnvironmentBuilder.addConnectorRef(EnvironmentBuilder.java:294)
at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(EnvironmentBuilder.java:232)
at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:384)
at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1181)
at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:952)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1437)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3149)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1590)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1234)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1077)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2530)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2480)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2484)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
The config.xml is
<?xml version="1.0" encoding="UTF-8"?>
<Domain ConfigurationVersion="8.1.5.0" Name="mydomain">
<Server ListenAddress="" ListenPort="7001" Name="myserver"
NativeIOEnabled="true" ReliableDeliveryPolicy="RMDefaultPolicy" ServerVersion="8.1.5.0">
<SSL Enabled="false" HostnameVerificationIgnored="false"
IdentityAndTrustLocations="KeyStores" Name="myserver"/>
</Server>
<JMSFileStore Directory="rmfilestore" Name="FileStore"/>
<WSReliableDeliveryPolicy DefaultRetryCount="10"
DefaultTimeToLive="60000" Name="RMDefaultPolicy" Store="FileStore"/>
<JDBCConnectionPool
DriverName="com.microsoft.jdbc.sqlserver.SQLServerDriver"
Name="LiferayPool" PasswordEncrypted="{3DES}MO3m0i6yVqM="
Properties="user=lportal;url=jdbc:microsoft:sqlserver://localhost:1433;selectMethod=cursor;userName=lportal;dataSourceName=SQL2000JDBC;databaseName=lportal;serverName=localhost"
Targets="myserver" TestConnectionsOnReserve="true"
TestTableName="SQL SELECT * from sysobjects" URL="jdbc:microsoft:sqlserver://localhost:1433"/>
<JDBCTxDataSource JNDIName="jdbc/LiferayPool" Name="LiferayPool"
PoolName="LiferayPool" Targets="myserver"/>
<Security Name="mydomain"
PasswordPolicy="wl_default_password_policy"
Realm="wl_default_realm" RealmSetup="true"/>
<EmbeddedLDAP
CredentialEncrypted="{3DES}VKU1Z+Rt+9H2BdJ/IWLykO3UHDGbDN2w3so0iy8xk1o=" Name="mydomain"/>
<SecurityConfiguration
CredentialEncrypted="{3DES}HVQXen+OHn1WVUhPVXQ5Etq0wZGW3TnCcMyK65ekuw56D9CS2M/ODdh/PomFZBYLRYlkhysTEvGDijpcBUYz6FzUcyq5JYry"
Name="mydomain" RealmBootStrapVersion="1"/>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<FileRealm Name="wl_default_file_realm"/>
<PasswordPolicy Name="wl_default_password_policy"/>
<JMSServer Name="WSStoreForwardInternalJMSServermyserver"
Store="FileStore" Targets="myserver">
<JMSQueue CreationTime="1155021233552"
JNDIName="jms.internal.queue.WSStoreForwardQueue"
JNDINameReplicated="false" Name="WSInternaljms.internal.queue.WSStoreForwardQueuemyserver"/>
<JMSQueue CreationTime="1155021233723"
JNDIName="jms.internal.queue.WSDupsEliminationHistoryQueue"
JNDINameReplicated="false" Name="WSInternaljms.internal.queue.WSDupsEliminationHistoryQueuemyserver"/>
</JMSServer>
<MailSession JNDIName="mail/MailSession" Name="mail/MailSession"
Properties="mail.pop3.host=localhost;mail.imap.host=localhost;mail.transport.protocol=smtp;mail.smtp.host=localhost;mail.store.protocol=imap" Targets="myserver"/>
</Domain>
The ejb-jar.xml is :
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
     <enterprise-beans>
          <session>
               <display-name>CounterServiceEJB</display-name>
               <ejb-name>com_liferay_counter_service_ejb_CounterServiceEJB</ejb-name>
               <home>com.liferay.counter.service.ejb.CounterServiceHome</home>
               <remote>com.liferay.counter.service.ejb.CounterServiceEJB</remote>
               <ejb-class>com.liferay.counter.service.ejb.CounterServiceEJBImpl</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Bean</transaction-type>
               <resource-ref>
                    <res-ref-name>jdbc/LiferayPool</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <resource-ref>
                    <res-ref-name>mail/MailSession</res-ref-name>
                    <res-type>javax.mail.Session</res-type>
                    <res-auth>Container</res-auth>
               </resource-ref>
          </session>
     </enterprise-beans>
     <assembly-descriptor>
          <method-permission>
               <unchecked />
               <method>
                    <ejb-name>com_liferay_counter_service_ejb_CounterServiceEJB</ejb-name>
                    <method-name>*</method-name>
               </method>
          </method-permission>
     </assembly-descriptor>
</ejb-jar>
The weblogic-ejb-jar.xml is:
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN" "http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
     <weblogic-enterprise-bean>
          <ejb-name>com_liferay_counter_service_ejb_CounterServiceEJB</ejb-name>
          <reference-descriptor>
          <resource-description>
          <res-ref-name>mail/MailSession</res-ref-name>
          <jndi-name>MailSession</jndi-name>
          </resource-description>
          </reference-descriptor>
          <jndi-name>com_liferay_counter_service_ejb_CounterServiceEJB</jndi-name>
     </weblogic-enterprise-bean>
</weblogic-ejb-jar>
Please Help!
Thanks in Advance.
- Karthikeyan

Hi,
I am still getting the error even after changing the JNDI name.
The modified weblogic-ejb-jar.xml is:
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN" "http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>com_liferay_counter_service_ejb_CounterServiceEJB</ejb-name>
<reference-descriptor>
<resource-description>
<res-ref-name>mail/MailSession</res-ref-name>
<jndi-name>mail/MailSession</jndi-name>
</resource-description>
</reference-descriptor>
<jndi-name>com_liferay_counter_service_ejb_CounterServiceEJB</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Thanks..
- Karthikeyan

Error deploying Struts 1.1 on weblogic 6.1 sp2

Hello,
I am trying to deploy the struts-documentation.war that comes with struts 1.1
on weblogic 6.1 sp2.
I already have xerces.jar , xalan.jar and crimson.jar in WEB-INF/lib. I have also
tired giving the files in the weblogic classpath.
It does not deploy the application and it gives the following error:
####<Jul 13, 2004 2:26:44 PM IST> <Debug> <HTTP> <phinwo-w00206>
<myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
<system> <> <101158> <Exception thrown while loading struts-documentation:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1>
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1525)
at
weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
at
weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
at
weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:177)
at
weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3405)
at
weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
at
weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
at
weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
at
weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at
weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy29.addWebDeployment(Unknown Source)
at
weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:984)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:971)
at
weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:956)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:648)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.addTarget(Unknown Source)
at
weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:867)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:966)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:886)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:802)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:733)
at
weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy5.update(Unknown Source)
at
weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:149)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Jul 13, 2004 2:26:44 PM IST> <Error> <J2EE> <phinwo-w00206>
<myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
<system> <> <160001> <Error deploying application struts-documentation:
Could not load struts-documentation>
####<Jul 13, 2004 2:26:44 PM IST> <Error> <Management> <phinwo-w00206>
<myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
<system> <> <141042> <Error deploying application
.\config\mydomain\applications\struts-documentation.war:
java.lang.reflect.UndeclaredThrowableException>
Any help in this regard will be highly appreciated.

I'm also running Weblogic 6.1 SP2 and getting a very similar error during startup when trying to deploy JSTL (Apache's version 1.0.6 from here http://jakarta.apache.org/taglibs/) in an exploded application that starts up fine if I remove the JSTL jars from WEB-INF/lib.
The exact stack trace in my case is this:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1525)
at weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:234)
at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3407)
at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy31.addWebDeployment(Unknown Source)
at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy30.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy41.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)

Hi i when i am trying to deploy an EJB module on weblogic server i get the

Hi all,
when i am trying to deploy an EJB module on weblogic server i get the the following exception on the server.
Exception:weblogic.management.ApplicationException: prepare failed for test Module: test Error: Exception preparing module: EJBModule(test,status=NEW) Unable to deploy EJB: D:\bea\weblogic81b\server\bin\myserver\upload\test.jar from test.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: Class bytes found but defineClass()failed for: 'HelloBean' at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:525) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.(MBeanDeploymentInfoImpl.java:230) at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1256) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:449) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2792) at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1478) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1136) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:975) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2571) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2523) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2453) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:820) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:536) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:494) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
[Deployer:149033]preparing application test on myserver
[Deployer:149033]failed application test on myserver
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application test on myserver.: Exception:weblogic.management.ApplicationException: prepare failed for test Module: test Error: Exception preparing module: EJBModule(test,status=NEW) Unable to deploy EJB: D:\bea\weblogic81b\server\bin\myserver\upload\test.jar from test.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: Class bytes found but defineClass()failed for: 'HelloBean' at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:525) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.(MBeanDeploymentInfoImpl.java:230) at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1256) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:449) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2792) at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1478) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1136) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:975) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2571) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2523) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2453) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:820) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:536) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:494) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread

Hi, i am also facing the same problem.......
my ejb-jar.xml is
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar >
<description><![CDATA[No Description.]]></description>
<display-name>Generated by XDoclet</display-name>
<enterprise-beans>



<entity >
<description><![CDATA[Description for Account]]></description>
<display-name>Name for Account</display-name>
<ejb-name>Account</ejb-name>
<home>com.app.j2ee.bmp.interfaces.AccountHome</home>
<remote>com.app.j2ee.bmp.interfaces.Account</remote>
<local-home>com.app.j2ee.bmp.interfaces.AccountLocalHome</local-home>
<local>com.app.j2ee.bmp.interfaces.AccountLocal</local>
<ejb-class>com.app.j2ee.bmp.ejb.AccountBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>com.app.j2ee.bmp.interfaces.AccountPK</prim-key-class>
<reentrant>False</reentrant>
          <resource-ref>
          <res-ref-name>jdbc/ejbPool</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
</entity>
</enterprise-beans>



<assembly-descriptor >










<container-transaction>
          <method>
          <ejb-name>Account</ejb-name>
          <method-intf>Local</method-intf>
          <method-name>*</method-name>
          </method>
          <method>
          <ejb-name>Account</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
     </container-transaction>
</assembly-descriptor>
</ejb-jar>

Deploying CMP Entity Beans in Weblogic

How to generate/convert the Orion xml file to Weblogic_RDBMS ?
Thx

petstore 1.3 will be available for the upcoming beta of weblogic 7.0...
Andrew Sliwkowski(BEA)
[email protected]
"Nitin Sawant" <[email protected]> wrote in message
news:3c04f6cd$[email protected]..
>
Appreciate if you can share your plans on releasing a petstore 1.3 patchfor weblogic.
>
>
i am having problems deploying CMP Entity Beans in petstore 1.3 where theprimary
key class is defined as java.lang.Object in the ejb-jar.xml descriptor(<prim-key-class>java.lang.Object</prim-key-class>).
Does weblogic 6.1 with 1.3 features enabled support the above feature.
Thanks,

Deploy Petstore in Exploded Directory(Weblogic 7.0)

Similar Messages

Maybe you are looking for