1 2 Previous Next 22 Replies Latest reply on Feb 24, 2014 5:00 AM by Tomaž Cerar Go to original post
      • 15. Re: Deployment doesn't see the web.xml entries
        Ales Justin Master

        Thanks. This is what I have in ROOT.war/WEB-INF/logging.properties

        .level = INFO

         

        And app engine web has this:

        <system-properties>

            <property name="java.util.logging.config.file" value="WEB-INF/logging.properties"/>

          </system-properties>

         

        Hmm, yes, this should do it.

        Perhaps try to debug on why 500 response code.

         

        Where I know Marko just recently fixed some path mapping issues, so it could be related.

        • 16. Re: Deployment doesn't see the web.xml entries
          Ales Justin Master

          I can download the datanucleus-core 3.1.2 but I'm assuming I will also need to update datanucleus-jpa-1.1.5.jar and other jars. Is there a place where I can download what's officially supported and replace my existing jars? A reference war file of some sort?

          Yes, you need to update all related libs.

           

          See our tests:

          * https://github.com/capedwarf/capedwarf-blue/tree/master/testsuite/src/test/java/org/jboss/test/capedwarf/testsuite/jpa/test

          * https://github.com/capedwarf/capedwarf-blue/blob/master/testsuite/src/test/java/org/jboss/test/capedwarf/testsuite/jpa/test/TestUtils.java

          * https://github.com/capedwarf/capedwarf-blue/blob/master/pom.xml#L97

           

          It's trivial to do it via Maven, as all jars are in Maven Central.

          • 17. Re: Deployment doesn't see the web.xml entries
            Shai Almog Newbie

            Thanks!

            We've had so many issues with App Engine configurations we just don't want to risk the whole Maven migration process. I'd rather leave as much of the build as is so it will be the same as the app engine build.

            • 18. Re: Deployment doesn't see the web.xml entries
              Ales Justin Master

              Afaik, GAE SDK examples/demos, its HelloORM2 uses new DN libs.

              • 19. Re: Deployment doesn't see the web.xml entries
                Shai Almog Newbie

                This is seriously driving me crazy by now. I updated all the jars as far as I can see. But I'm getting 500 errors in the GWT code without anything being logged. I've tried changing the way I build an app engine app but I'm seriously at a loss on how to do this?

                I installed a new Eclipse version with the Google plugin and JBoss plugin but it won't let me deploy a hello world app engine app to Cape Dwarf. Is there no walk thru tutorial for someone using the standard Google App Engine plugin?

                • 20. Re: Deployment doesn't see the web.xml entries
                  Shai Almog Newbie

                  Just creating a hello world app engine project in the Eclipse plugin and copying the WAR into place results in the following exception. Not exactly sure what to make of this:

                  11:10:01,577 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."Test.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."Test.war".WeldStartService: Failed to start service

                      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]

                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]

                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]

                      at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]

                  Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type Set<Service> with qualifiers @Default

                    at injection point [BackedAnnotatedParameter] Parameter 1 of [BackedAnnotatedConstructor] @Inject com.google.gwt.thirdparty.guava.common.util.concurrent.ServiceManager(Set<Service>)

                    at com.google.gwt.thirdparty.guava.common.util.concurrent.ServiceManager.<init>(ServiceManager.java:0)

                   

                      at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:361)

                      at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:282)

                      at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:133)

                      at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:164)

                      at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:507)

                      at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)

                      at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)

                      at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)

                      at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)

                      at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_45]

                      ... 3 more

                   

                  11:10:01,585 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"Test.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"Test.war\".WeldStartService: Failed to start service

                      Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type Set<Service> with qualifiers @Default

                    at injection point [BackedAnnotatedParameter] Parameter 1 of [BackedAnnotatedConstructor] @Inject com.google.gwt.thirdparty.guava.common.util.concurrent.ServiceManager(Set<Service>)

                    at com.google.gwt.thirdparty.guava.common.util.concurrent.ServiceManager.<init>(ServiceManager.java:0)

                  "}}

                  • 21. Re: Deployment doesn't see the web.xml entries
                    Ales Justin Master

                    This is WildFly being very strict on JEE -- its CDI handling.

                    As it looks like GWT code / lib has some @Inject, which is treated as required by JEE7.

                     

                    You can add this jboss-all.xml to ignore this:

                    * Make site war run on WildFly by supressing implicit bean archives · 59567a0 · GoogleCloudPlatform/appengine-tck · GitHu…

                    1 2 Previous Next