Weld 1.1.0.Final available!

I work on GAE project, so I had to refuse weld because of long scanning time at cold start. Would you be able to describe how to point weld to one package only where beans are contained. Could it be faster than managed beans? How to configure mojarra not to scan beans? What is a best configuration to reduce application start time with weld and mojarra together?

Anyway, I think weld is great, thank you very much for your work.

Ara wrote on Jan 17, 2011 13:55:
I work on GAE project, so I had to refuse weld because of long scanning time at cold start. Would you be able to describe how to point weld to one package only where beans are contained.

That's the simplest example :-)

<beans xmlns="http://java.sun.com/xml/ns/javaee" 
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
        xmlns:weld="http://jboss.org/schema/weld/beans" 
        xsi:schemaLocation="
           http://java.sun.com/xml/ns/javaee http://jboss.org/schema/cdi/beans_1_0.xsd
           http://jboss.org/schema/weld/beans http://jboss.org/schema/weld/beans_1_1.xsd">
    
    <weld:scan>
        <weld:include name="the.one.package.to.scan.*" />
    </weld:scan>

</beans>

Could it be faster than managed beans?

I haven't measured this, but I suspect it should be around the same.

How to configure mojarra not to scan beans? What is a best configuration to reduce application start time with weld and mojarra together?

Maybe a Mojarra expert can help, but I agree with you, disable Mojarra scanning, and use the above snippet.

I would also like to suggest that you look at the possibility of using Always On instances in GAE. It costs a little money, but you are reserved 3 JVM instances for your application which are always running (i.e, no more waiting for container startup).

I know, but sometimes I use task queue API very extensive. In this case gae run more instances anyway, so it is better to have shorter start time to run tasks in more predictable order.

Awesome news, congratulations!

Maybe a Mojarra expert can help, but I agree with you, disable Mojarra scanning, and use the above snippet.

I investigated GAE start time problem little bit. Anybody can use this to save some start time that can be used for weld start.

1. Register all managed beans statically in faces-config.xml
2. Use metadata-complete=”true” attribute, so faces-config.xml boilerplate is:

<?xml version='1.0' encoding='UTF-8'?>
<faces-config 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/web-facesconfig_2_0.xsd"
              version="2.0"
              metadata-complete="true">
    
<!--Your stuff here-->
</faces-config>

Using this technique you force JSF not to scan classes for beans.
3. Force JSF not to check xml syntax. I hope your IDE do it instead. In web.xml check context parameter as here:

<context-param>
     <description>
         Set this flag to true if you want the JavaServer Faces
         Reference Implementation to validate the XML in your
         faces-config.xml resources against the DTD. Default
         value is false.
     </description>
     <param-name>com.sun.faces.validateXml</param-name>
     <param-value>false</param-value>
</context-param> 

Using these tricks I reduce GAE start time by two seconds. Not bad.

Is @ViewScoped included or I should use this instruction to port it by myself?

I continue investigation of GAE start time . Instead of usage of metadata-complete="true" you would be consider com.sun.faces.annotationScanPackages context param, that should be included to web.xml. Description could be found here . Start time is rather same.

Ara wrote on Jan 23, 2011 13:19:
Is @ViewScoped included or I should use this instruction to port it by myself?

You should port it yourself, or consider using Seam Faces.

Now, it is time to test weld 1.1.0 final on GAE.

1. Aded to pom.xml:

<repository>
    <id>jboss-my-rel</id>
    <url>https://repository.jboss.org/nexus/content/repositories/releases/</url>
</repository>
...
<dependency>
    <groupId>org.jboss.weld.servlet</groupId>
    <artifactId>weld-servlet</artifactId>
    <version>1.1.0.Final</version>
</dependency>

2. Created empty bean.xml
3. Aded to web.xml

<listener>
    <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>
</listener>

Result is error:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/G:/ideaworkspace/richgost/target/agost/WEB-INF/lib/slf4j-jdk14-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/G:/ideaworkspace/richgost/target/agost/WEB-INF/lib/weld-servlet-1.1.0.Final.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
24.01.2011 13:16:47 com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: failed com.google.apphosting.utils.jetty.DevAppEngineWebAppContext@1e232b5{/,G:\ideaworkspace\richgost\target\agost}: java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
24.01.2011 13:16:47 com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: failed JettyContainerService$ApiProxyHandler@16f144c: java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
24.01.2011 13:16:47 com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: Error starting handlers
java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V
        at org.slf4j.cal10n.LocLogger.info(LocLogger.java:122)
        at org.jboss.weld.bootstrap.WeldBootstrap.<clinit>(WeldBootstrap.java:207)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance_(Runtime.java:112)
        at com.google.appengine.tools.development.agent.runtime.Runtime.newInstance(Runtime.java:132)
        at org.jboss.weld.environment.servlet.util.Reflections.newInstance(Reflections.java:41)
        at org.jboss.weld.environment.servlet.Listener.<init>(Listener.java:68)

First question is what to do with slf4j-jdk14. It works perfect on gae with all log levels? Are that all errors?

I just removed slf4j-jdk from pom.xml. I’ve got new error.

24.01.2011 13:30:57 org.jboss.weld.environment.servlet.Listener contextInitialized
WARNING: @Resource injection not available in simple beans
24.01.2011 13:30:57 org.jboss.weld.bootstrap.WeldBootstrap startContainer
INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
24.01.2011 13:30:58 com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: failed com.google.apphosting.utils.jetty.DevAppEngineWebAppContext@3ac93e{/,G:\ideaworkspace\richgost\target\agost}: java.lang.NoClassDefFoundError: org/apache/catalina/core/ApplicationContextFacade
24.01.2011 13:30:58 com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: failed JettyContainerService$ApiProxyHandler@ecb67f: java.lang.NoClassDefFoundError: org/apache/catalina/core/ApplicationContextFacade
24.01.2011 13:30:58 com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: Error starting handlers
java.lang.NoClassDefFoundError: org/apache/catalina/core/ApplicationContextFacade
        at org.jboss.weld.environment.tomcat.WeldForwardingAnnotationProcessor.getStandardContext(WeldForwardingAnnotationProcessor.java:92)
        at org.jboss.weld.environment.tomcat.WeldForwardingAnnotationProcessor.replaceAnnotationProcessor(WeldForwardingAnnotationProcessor.java:69)
        at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:192)
        at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548)
        at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
        at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
        at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
        at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
        at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
        at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
        at org.mortbay.jetty.Server.doStart(Server.java:224)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
        at com.google.appengine.tools.development.JettyContainerService.startContainer(JettyContainerService.java:185)
        at com.google.appengine.tools.development.AbstractContainerService.startup(AbstractContainerService.java:149)
        at com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:219)
        at com.google.appengine.tools.development.DevAppServerMain$StartAction.apply(DevAppServerMain.java:164)
        at com.google.appengine.tools.util.Parser$ParseResult.applyArgs(Parser.java:48)
        at com.google.appengine.tools.development.DevAppServerMain.<init>(DevAppServerMain.java:113)
        at com.google.appengine.tools.development.DevAppServerMain.main(DevAppServerMain.java:89)
Caused by: java.lang.ClassNotFoundException: org.apache.catalina.core.ApplicationContextFacade
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at com.google.appengine.tools.development.IsolatedAppClassLoader.loadClass(IsolatedAppClassLoader.java:151)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        ... 21 more

The strange thing that with weld 1.0.1-Final weld works perfect! So, would you be able to provide some extra configuration? Or this is downgrade for GAE?

So, continue with weld 1.1.0 final on GAE. Logging problem could be solved by removing any slf4j dependencies. Weld brings slf4j api and correct apply it to GAE logger. You will have all logging levels. After, you should add

<dependency>
    <groupId>org.jboss.weld</groupId>
    <artifactId>weld-logger</artifactId>
    <version>1.0.0-CR2</version>
</dependency>

To you pom.xml. Now, you can just inject logger. Consider this to do it correctly. But the problem with second error still exists. I am very upset that is not able to try new abilities of weld on GAE.