War problems- Deployment descriptor is malformed, check agains the DTD (0/1)

I'm sorry for cross-posting this but I don't know which is the correct
newsgroup to post this.
I have posted this before but I haven't had a successful response that
has solved my problem so I'm reposting it again.
I'm trying to create an ear file for our ejbs and servlets. I create
my war file and ejb jar files and then create the ear file. When I
start weblogic the ejbs load fine but I get an error when loading my
war file. The error is Deployment descriptor is malformed, check
against the DTD. The weblogic.xml and web.xml files are the same
files that I place in the
/config/investia/applications/DefaultWebApp_javelin/WEB-INF.
Our current way of deploying our application is to create one jar file
that contains all our classes and add this to the system classpath and
and add the web.xml and weblogic.xml file in the WEB-INF directory.
We also specify the jar files in the config.xml file to point to this
jar.
One of the things that I also tried to do is just to grab the web.xml
and the weblogic.xml file from the petStore.war file that was in the
petStore.ear file located in the /config/petstore/applications
directory. I did not modify this file and just used this file as is
when I created my war file with my own classes. I just wanted to know
if I was going to get any DTD errors. Sure enough, I got DTD errors
when parsing this file. I was hoping this would load and I would get
some classpath not found error or something else because I didn't copy
any of the classes.
I have attachec my web.xml and weblogic.xml files that work fine when
not building the war file. I just can't seem to figure this out and
would appreciate all the help I can get. The web.xml file only has
one servlet active and everything below that is commented out.
Thanks,
Ruben

Hi,
The issue is not in the weblogic.xml file, the issue is on your classpath, JAVA_HOME variable, or on the starting script for your managed server that sets one variable wrong and the managed node is not able to find the proper JDK. My guess would be that it is the last one.
You may ignore the weblogic.xml warning (at least in WL 8.x) and correct that whenever you have some cycles left.
Regards,
LG

Similar Messages

  • War problems- Deployment descriptor is malformed, check agains the DTD (1/1)

              [weblogic.xml.template]
              [web.xml.template]
              

    Hi,
    The issue is not in the weblogic.xml file, the issue is on your classpath, JAVA_HOME variable, or on the starting script for your managed server that sets one variable wrong and the managed node is not able to find the proper JDK. My guess would be that it is the last one.
    You may ignore the weblogic.xml warning (at least in WL 8.x) and correct that whenever you have some cycles left.
    Regards,
    LG

  • Deployment Descriptor is malformed

              WLS 6.1, Win 2K Prof.
              I have deployed my JSP & EJBs in an EAR file. When I start the JSP I get the following
              errors in the WLS console, though it doesn't appear, at present to have an adverse
              effect. A pointer to what may be causing it would be welcome.
              <<<<< STARTS >>>>>
              <15-Nov-01 15:23:05 GMT> <Info> <HTTP> <Deployment descriptor is malformed, chec
              k against the DTD: org.xml.sax.SAXParseException: The content of element type
              "a
              ttribute" must match "(name,required?,rtexprvalue?)"..>
              <15-Nov-01 15:23:05 GMT> <Info> <HTTP> <Deployment descriptor is malformed, chec
              k against the DTD: org.xml.sax.SAXParseException: The content of element type
              "a
              ttribute" must match "(name,required?,rtexprvalue?)"..>
              <15-Nov-01 15:23:05 GMT> <Info> <HTTP> <Deployment descriptor is malformed, chec
              k against the DTD: org.xml.sax.SAXParseException: The content of element type
              "a
              ttribute" must match "(name,required?,rtexprvalue?)"..>
              <15-Nov-01 15:23:05 GMT> <Info> <HTTP> <Deployment descriptor is malformed, chec
              k against the DTD: org.xml.sax.SAXParseException: The content of element type
              "a
              ttribute" must match "(name,required?,rtexprvalue?)"..>
              <<<< ENDS >>>>>
              

    ram ram <> wrote:
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    Add tools.jar from your Java installation to the classpath.
    Bart
    Schelstraete Bart
    http://www.schelstraete.org
    http://www.mqseries.be

  • HT1338 I am having trouble installing updates on my mac this is the error code the pops upThe update could not be verified. It may have been corrupted or tampered with during downloading. The update will be downloaded and checked again the next time that

    can some one help me? I have been trying to update my MAC and it will not download because this message come up
    (The update could not be verified. It may have been corrupted or tampered with during downloading. The update will be downloaded and checked again the next time that Software Update runs.)

    For anyone that comes across this. I managed to fix the problem. It had something to do with the date on my computer. Mavericks installer apparently does a date check of some sort and that is where the error is coming from. Open terminal and check the system date. It may be wrong. Another poster in the forums told me how to to check the date and change it. Click here for the link to the explanation. Be careful because the date is in a weird format.

  • Can't download the latest iTunes. A window pops up... The update could not be verified. It may have been corrupted or tampered with during downloading. The update will be downloaded and checked again the next time that Software Update runs. No iTunes now.

    Can't download the latest iTunes. A window pops up... The update could not be verified. It may have been corrupted or tampered with during downloading. The update will be downloaded and checked again the next time that Software Update runs.
    Now, iTunes won't launch and can't be updated. Please help.
    If I have lost my music collection I will be switching platforms ASAP. It is insane that Apple has updates seemingly every day for their products.

    I was in your same situation with 14 downloads and 14 attempts. 
    You have to make sure that your Mac is booting into 64 bit mode.  You can make sure of this by going into System Preferences and scrolling down to 'Software' and making sure that you are booding with 64 bit Kexts. 
    If not, restart while holding the 6 and 4 keys down until you see the spinning gear wheel and try installng again. 
    BUT, what I also did was to go into Applications, click on the Lion installer, Get Info, and give yourself custom priviliges to Read And Write. 
    I did this simultaneously, and I don't know what function did it, but it worked for me, with no further downloads of the installer. 
    Good luck! 

  • The update could not be verified. It may have been corrupted during downloading. The update will be downloaded and checked again the next time that Software Update runs.

    How can I solve this? Every time I have the option to update an application I receive the same notification: "The update could not be verified. It may have been corrupted during downloading. The update will be downloaded and checked again the next time that Software Update runs"

    Can we eliminate one minor possibility: are you in the UK and using Virgin Media cable connection? I ask because the latest 'Superhub' firmware is corrupting large downloads for some people.

  • Latest update returns error " None of the selected updates could be installed. The update could not be expanded, and may have been corrupted during downloading. The update will be downloaded and checked again the next time that Software Update runs."

    Latest update returns error " None of the selected updates could be installed. The update could not be expanded, and may have been corrupted during downloading. The update will be downloaded and checked again the next time that Software Update runs."

    Which latest update? Details get answers. Rather than using SU, DL and install from http://support.apple.com/downloads/.

  • I purchased a app in the App Store but the app was under the free column but the app said $4.99 did I pay for the app? I also had 4 cents in my account but when I went to go and check again, the 4 cents was gone. So did I purchase the app?

    I seen in the App Store the app imovie for $4.99 but, it was in the free column. So I tried to see of ot would let me download it, and it did, but I also had 4 dents in my account. So did I purchase that app? When I went to go and see if the 4 cents was still there, it was gone. So I had to purchase the app. But It was in the free column of the App Store. I'm confused

    I was also on my ipad 4th generation on ios 7.0.4

  • Deployment descriptor "weblogic.xml" is malformed. in managed server

    Hi All,
              Appreciate if anyone can help.
              I have set up a cluster containing two nodes - one local and other
              remote machine on weblogic 8.1.4
              then i install my application this cluster setup its working fine.
              for my requirement i upgrade the the weblogic version from 8.1.4 to
              8.1.6 .
              i upgrade through the smart update from the bea site . i upgraded both
              the node.
              i started the admin server.it started with no issue.
              my problem comes when i start the my managed server on the cluster .it
              gives me this exception.
              <HTTP> <BEA-101296> <Unable to load the default compiler class
              "com.sun.tools.javac.Main". Using the default javac compiler to compile
              JSPs.>
              i checked the classpath it has the same jdk that i used for 8.1.4
              (jdk1.4.05 from sun.)
              should i used new jdk that comes with the upgrade package of 8.1.6 like
              (jdk1.4.11)
              my class path having the weblogic jar also.
              this is my class path.:
              E:\bea\weblogic81\server\lib\weblogic.jar and other my application
              jars.
              complete exception it is shown like :
              <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
              <Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
              Module: 'Nexaweb': Public ID references the old version of the Servlet
              DTD. You must change the public ID in web.xml file to "-//Sun
              Microsystems, Inc.//DTD Web Application 2.3//EN".>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
              <[Application:
              'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?br>Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
              Check against the DTD: org.xml.sax.SAXParseException: The content of
              element type "weblogic-web-app" must match
              "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?t*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?ontainer-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?ap?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
              (line 26, column 20).>
              Compiler class: 'com.sun.tools.javac.Main', not found
              java.lang.ClassNotFoundException: com.sun.tools.javac.Main
              at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
              at java.security.AccessController.doPrivileged(Native Method)
              at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
              at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
              at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
              at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:141)
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?6)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.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)
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
              <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
              will have better performance if it is enabled. To enable
              call-by-reference, set the enable-call-by-reference element to True in
              the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
              <Failed to initialize the application Xellerate due to error
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.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)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.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)
              weblogic.management.ApplicationException: prepare failed for
              xlBackOfficeBeans.jar
              Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
              EJBModule(xlBackOfficeBeans.jar,status=NEW)
              Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
              Compiler class: 'com.sun.tools.javac.Main', not found
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.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)
              java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
              found
              at
              weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
              at
              weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
              at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
              at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
              at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
              at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
              at
              weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
              at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
              at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.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)
              at
              weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1658)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
              at
              weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
              at
              weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
              at
              weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
              at
              weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
              at
              weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.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)
              ><Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
              <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
              to initialize due to failed deployments.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
              <The deployment framework was unable to resume accepting requests.>
              <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
              <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
              deployment framework was unable to resume accepting
              requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
              is unable to initialize due to failed deployments.>
              hope the scope of the questions is not too broad. Kindly let me know
              if you need more information.
              Thanks a lot.

    ram ram <> wrote:
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    Add tools.jar from your Java installation to the classpath.
    Bart
    Schelstraete Bart
    http://www.schelstraete.org
    http://www.mqseries.be

  • Deployment descriptor "weblogic.xml" is malformed.

    Hi All,
    Appreciate if anyone can help.
    I have set up a cluster containing two nodes - one local and other
    remote machine on weblogic 8.1.4
    then i install my application this cluster setup its working fine.
    for my requirement i upgrade the the weblogic version from 8.1.4 to
    8.1.6 .
    i upgrade through the smart update from the bea site . i upgraded both
    the node.
    i started the admin server.it started with no issue.
    my problem comes when i start the my managed server on the cluster .it
    gives me this exception.
    <HTTP> <BEA-101296> <Unable to load the default compiler class
    "com.sun.tools.javac.Main". Using the default javac compiler to compile
    JSPs.>
    i checked the classpath it has the same jdk that i used for 8.1.4
    (jdk1.4.05 from sun.)
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    complete exception it is shown like :
    <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
    <Application:
    'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
    Module: 'Nexaweb': Public ID references the old version of the Servlet
    DTD. You must change the public ID in web.xml file to "-//Sun
    Microsystems, Inc.//DTD Web Application 2.3//EN".>
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
    <[Application:
    'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?r',
    Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
    Check against the DTD: org.xml.sax.SAXParseException: The content of
    element type "weblogic-web-app" must match
    "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?gnment*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?er?,container-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?tch-map?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?oot?,wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
    (line 26, column 20).>
    Compiler class: 'com.sun.tools.javac.Main', not found
    java.lang.ClassNotFoundException: com.sun.tools.javac.Main
    at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:141)
    at
    weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:406)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
    at
    weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.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)
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
    <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
    will have better performance if it is enabled. To enable
    call-by-reference, set the enable-call-by-reference element to True in
    the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
    <Failed to initialize the application Xellerate due to error
    weblogic.management.ApplicationException: prepare failed for
    xlBackOfficeBeans.jar
    Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
    EJBModule(xlBackOfficeBeans.jar,status=NEW)
    Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
    Compiler class: 'com.sun.tools.javac.Main', not found
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
    at
    weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.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)
    java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
    found
    at
    weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:411)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
    at
    weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.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)
    weblogic.management.ApplicationException: prepare failed for
    xlBackOfficeBeans.jar
    Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
    EJBModule(xlBackOfficeBeans.jar,status=NEW)
    Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
    Compiler class: 'com.sun.tools.javac.Main', not found
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
    at
    weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.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)
    java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
    found
    at
    weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:411)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
    at
    weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.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)
    at
    weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1658)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
    at
    weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
    at
    weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
    at
    weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.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)
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
    <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
    to initialize due to failed deployments.>
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
    <The deployment framework was unable to resume accepting requests.>
    <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
    <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
    deployment framework was unable to resume accepting
    requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
    is unable to initialize due to failed deployments.>
    hope the scope of the questions is not too broad. Kindly let me know
    if you need more information.
    Thanks a lot.

    ram ram <> wrote:
    should i used new jdk that comes with the upgrade package of 8.1.6 like
    (jdk1.4.11)
    my class path having the weblogic jar also.
    this is my class path.:
    E:\bea\weblogic81\server\lib\weblogic.jar and other my application
    jars.
    Add tools.jar from your Java installation to the classpath.
    Bart
    Schelstraete Bart
    http://www.schelstraete.org
    http://www.mqseries.be

  • Problems deploying a war on iAS 6.0 sp3 on solaris.

    I have been trying to deploy a war file on iAS 6.0, but I just doesn't work. I wared the file up including a guid which I borrowed from an undeployed example. (because I had problems getting kgenguid to work.) Other examples deploy, but my war does not. Is there an example of a deployment of a module somewhere documented? The deployment copied the war file into the JAR directory, but the registry entries did not seem to happen. I attempted to enter in a bunch of registry entries manually to no avail. If anybody can give me a little insight in the requirements on how to deploy a war file on iAS 60 sp3 that would be greatly appreciated. I have been able to deploy my application on weblogic, websphere, jrun, jboss, etc. I don't think it's a problem with the application.

    I agree with the previous poster that you might want to try deploytool (so you avoid GUID conflicts) and reading the docs on deploying.
    You might also want to try:
    * Figuring out what is wrong with kguidgen. It's a very simple command line program. If it isn't working then you probably don't have a successful install. I'm guessing that your deployment problems might be related.
    * Checking out the samples. Lots of samples walk you through deployment. HelloWorld, for example, http://developer.iplanet.com/appserver/samples/helloworld/docs/index.html
    * Check kas.log

  • Problem deploying application - ERROR: No j2ee modules detected

    Hi
    I am new to jDeveloper, and I have created a stateless session EJB, and a JSF page with one ADF component on. When I try to deploy my application to Weblogic, I get this error:
    ERROR: No j2ee modules detected in EAR archive. Deployment aborted
    Any ideas what I can do to fix this?
    Thank you
    Søren

    Hi, I had this same problem. The whole purpose of a EAR is containing a J2EE app. It's divided on a Web Components Archive (WAR) and a JAR with the Enterprise App. I found this document useful and the app could be deployed successfully to an EAR. Remember to include all you extra libraries as another file Group of the "Libraries Type". Basically you owuld have to separatelly create the WAR deployment descriptor, the EJB JAR deployment descriptor and after that create the EAR based on one or two of them.
    [http://download.oracle.com/otndocs/tech/ias/portal/files/RG/OBE/deployToAppServer/lesson_Deployment.htm|http://download.oracle.com/otndocs/tech/ias/portal/files/RG/OBE/deployToAppServer/lesson_Deployment.htm ]
    This document is intended for Jdev10g and OracleAS 10, but the procedure is almost the same for both versions.

  • Error in J2ee .war file deployment using ASC

    Hi,
    When I deploy a .war file using Application Server Control web interface, after
    30 min or so, it gave me an error: "Processing has already completed". But when
    I checked, no application was deployed. Sometimes the same war file deployment
    finished successfully if I repeat the deployment process several times. The whole application is in a single .war, the war file size is about 52 MB. Looks like this is a
    deployment timeout issue when server is very busy. Any ideas?
    Thanks,
    Richard

    I have seen this before when the file names in the archive aren't case sensitive. I
    suspect you're using NT, so the direct access to the file system is case insensitive by
    default.
    Make sure that the META-INF directory in the archive is in upper case, and check the case
    requirements for the other files in the archive.
    Regards,
    Peter.
    rashmi wrote:
    Hello,
    I have created a chat application containing jsps and beans, and deployed it first
    in the exploded directory format. It works fine and I was able to run and test
    it. Since all the tests are done and the module is over,now i want to package
    it in war file and deploy it.Here comes the problem :- I have packaged the application
    in a war file using jar command and copied it under applications directory but
    when i restarted the server(wls 6.0 sp1) ,i found in console the application is
    deployed under applications node and not under web applications node-why? Agian
    unpacked the war file and deployed it in exploded directory format now the console
    shows it under web app node then why does not it deploy it as web application
    when deployed in war format. Any body faced the same situation,Plz help.
    rds rashmi

  • XML deployment descriptor generation

    How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
    By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
    Thanks.

    How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
    By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
    Thanks. Hi,
    there is no way (so far as I know) that an J2EE Application server (what oc4j is) makes the deployment descriptors, that's why they are called deployment descriptors, without them you can't deploy on any Application server.
    I personally use JDeveloper, but most current JAVA IDE's support generation of deployment descriptors.
    Basically my approach is to define the architecture within Rational Rose, which generates for me the stubs for the classes and for every ejb a deployment descriptor, later I copy all of them into one ejb-jar.xml and open the whole bunch with JDeveloper, it works fine with 903 preview, although there are some problems with the 902 version of JDeveloper.
    Which IDE are you using?
    --hery                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • JNDI environment properties for EJB in deployment descriptor

    Is it possible to deploy an EJB on weblogic 6.0 such that the EJBHome
    object is bound using JNDI to a different JNDI server such as ldap
    server instead of the weblogic server by specifying JNDI env.
    properties like PROVIDER_URL, INITIAL_CONTEXT_FACTORY in the
    deployment descriptor? That is use the weblogic built-in deployer but
    bind the JNDI names to a different JNDI server. For this, can the
    EJBHome objects be treated as just RMI (over IIOP) objects and bind
    them (stubs of the RMI objects) using the Sun's JNDI service provider.
    The goal is that thereafter the Home JNDI names can be looked up by
    RMI clients and the interface methods invoked.
    Thanks,
    ... arun

    Must I put the war and jar files in the same ear ?
    oh..ft...my boss is killing me ..
    package..repackage...package..repackage..and test ??
    Could anybody tell me how to refer a SLSB without put the webApp
    and the EjbApp together in an Ear file ??
    thanks very much!!!!

Maybe you are looking for

  • MIRO : Error message for a duplicate entry

    Hi, When we enter In MIRO an invoice with the same informations as another invoice that was already posted, the system display a Warning message like the following : Message no. F5117 Check whether document has already been entered with number 190000

  • ITunes Skipping like a CD

    I looked around in the community before posting this and no one has seemed to answer this or fix it. This started happening recently. Songs that never skipped before are acting like a scratched CD. It's not the songs, because they play fine in finder

  • CO46/MD4C - see 2 receipt elements (ShipNt & PchOrd) for one demand

    Scenario: Production Order for 10 ea for 'A' with a purchased material 'x'. The supplier confirms 5 ea of material 'x' have left the dock and I make a shipping notiication calculating expected delivery date and update MRP. I now have 2 receipt elemen

  • Some components make tomcat throw exceptions

    Hi, When i add for example 'table' or 'calendar' components on the page and run the app in tomcat it gives me exceptions. Anyone knows why it does not work? Thanks guys. P.S. I have copied jstl.jar and standard.jar to tomcat dir. Exception Details: o

  • Web services call datetime parameter format error...

    We fallow instruction below http://www.oracle.com/technology/products/jdev/viewlets/1013/bpelfromadf_viewlet_swf.html When we want to send date field to the bpel process fallowing error occurs. JBO-25009: $''2005-06-10T15:56:00'' value java.util.Date