8 Replies Latest reply on Mar 17, 2010 5:45 AM by ropalka

    Unable to process deployment descriptor for context and @Web

    chubinator

      Hello,

      I've created some JbossWS web services using the top-down approach and wsconsume. I'm deploying a Stateless EJB implementation of one of my services to JBoss 5.1.0.

      It all deploys fine, but I get this warning:

      WARNING [config] Unable to process deployment descriptor for context '/myapp'


      My EJB looks like this:

      @Stateless
      @WebService
      @WebContext( contextRoot="/myapp" )
      public class MyServiceBean implements com.company.webservices.myapp.v1.MyServicePortType {


      My deployment package is a .ear file with the following contents:

      META-INF/application.xml
      myservices.jar
      myapp.jar


      The contents of the application.xml is:

      <?xml version="1.0" encoding="UTF-8"?>
      <application xmlns="http://java.sun.com/xml/ns/javaee"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
       version="5">
       <display-name>myapp-1.0</display-name>
       <module>
       <ejb>myapp.jar</ejb>
       </module>
       <module>
       <java>myservices.jar</java>
       </module>
      </application>


      I spent a lot of time searching around the internet and the forums, and the best I can figure is that JBoss wants me to configure the context some place. The two examples I found reference some context.xml file that can be either in the WEB-INF folder of the war or configured as part of the JBoss server (outside my ear).

      I was not able to locate a DTD for this context.xml file and I'd really like to include it in my .ear. I'll generate a war if necessary, but want to be sure I understand what JBoss expects to see.

      Any help is greatly appreciated,
      Mark

        • 1. Re: Unable to process deployment descriptor for context and
          chubinator

          Ok, feeling little stupid. Apparently I didn't spend enough time searching--I think I kept including JBoss in my search which led me down rabbit holes.

          Searching on context.xml makes it clear that this little beast has been around for some time:

          http://wiki.metawerx.net/wiki/Context.xml

          So I'll figure out where I have to put it in my war-less deployment. :)

          • 2. Re: Unable to process deployment descriptor for context and
            chubinator

            Spoke too soon:

            The problem I'm running into is that I can deploy a context.xml in a war, but I can't include a war in my ear with the same context as my web services. JBoss reports that the context is already installed.

            So, how do I configure the context for my web services and include it in my ear/jar? In the end, I can fallback to configuring it outside my ear, but I'd rather not.

            Thanks

            • 3. Re: Unable to process deployment descriptor for context and
              henrik242

              Hi Mark, did you ever figure this one out?

              • 4. Re: Unable to process deployment descriptor for context and
                chubinator
                I have not.  Right now, we just ignore the warning and things seem to work.  But would rather have a proper solution.
                • 5. Re: Unable to process deployment descriptor for context and
                  henrik242

                  The patch (aka "ugly hack") in https://jira.jboss.org/jira/browse/JBAS-7130 removes the warning.

                   

                  It doesn't help me, though, because my webservices immediately get undeployed anyway:

                   

                  2010-03-11 14:48:45,665 INFO  [org.jboss.wsf.framework.management.DefaultEndpointRegistry] (main) register: jboss.ws:context=Mypackage,endpoint=MyPackageWSBean
                  2010-03-11 14:48:46,840 INFO  [org.jboss.wsf.stack.jbws.WSDLFilePublisher] (main) WSDL published to: file:/usr/local/jboss-5.1.0.GA/server/all/data/wsdl/my-ear.ear/mypackage-ejb-1.0.0-SNAPSHOT.jar/MyPackageWSBean21031.wsdl
                  2010-03-11 14:48:46,851 INFO  [org.jboss.wsf.framework.management.DefaultEndpointRegistry] (main) register: jboss.ws:context=Rule,endpoint=RuleWSBean
                  2010-03-11 14:48:47,706 INFO  [org.jboss.wsf.stack.jbws.WSDLFilePublisher] (main) WSDL published to: file:/usr/local/jboss-5.1.0.GA/server/wimp/data/wsdl/my-ear.ear/ruleengine-ejb-1.0.0-SNAPSHOT.jar/RuleWSBean21036.wsdl
                  2010-03-11 14:48:49,207 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/My
                  2010-03-11 14:48:49,743 WARN  [org.jboss.web.jsf.integration.config.JBossJSFConfigureListener] (main) HACK! HACK! HACK! JBAS-7130
                  2010-03-11 14:48:49,763 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/Rule
                  2010-03-11 14:48:50,440 WARN  [org.jboss.web.jsf.integration.config.JBossJSFConfigureListener] (main) HACK! HACK! HACK! JBAS-7130
                  2010-03-11 14:48:50,770 INFO  [org.jboss.cache.jmx.PlatformMBeanServerRegistration] (main) JBossCache MBeans were successfully registered to the platform mbean server.
                  2010-03-11 14:48:50,770 INFO  [org.jboss.cache.factories.ComponentRegistry] (main) JBoss Cache version: JBossCache 'Cascabel' 3.1.0.GA
                  2010-03-11 14:48:50,874 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) undeploy, ctxPath=/Rule
                  2010-03-11 14:48:50,889 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) undeploy, ctxPath=/My
                  2010-03-11 14:48:51,219 INFO  [org.jboss.wsf.framework.management.DefaultEndpointRegistry] (main) remove: jboss.ws:context=Rule,endpoint=RuleWSBean
                  2010-03-11 14:48:51,218 INFO  [org.jboss.wsf.framework.management.DefaultEndpointRegistry] (main) remove: jboss.ws:context=System,endpoint=MyPackageWSBean
                   
                  
                  • 6. Re: Unable to process deployment descriptor for context and
                    henrik242
                    Update: My webservices undeployed because of a completely unrelated error  (this one: https://jira.jboss.org/jira/browse/JBWS-2535).  The patch in JBAS-7130   seems to work as intended.
                    • 7. Re: Unable to process deployment descriptor for context and
                      chubinator

                      Henrik,

                       

                      Thanks for posting back, very much appreciated!

                      • 8. Re: Unable to process deployment descriptor for context and
                        ropalka
                        EJBs and POJOs cannot use the same web context