Indeed these are good news, I'm going to try with even more Seam3 modules on gf3.1_b43.
I've managed to upgrade logging to slf4j-api-1.6.1 and newest logback 0.9.28 - but that required using (as additional maven dependency) newest
org.jboss.logging:jboss-logging:3.0.0.Beta5 which also needs to be fixed for api change between slf4j 1.5.x and 1.6.1,
basically:
in Slf4jLocationAwareLogger.java:
//call to logger.log needs one more arg (null) to be comatible with slf4j 1.6.1
//logger.log(null, loggerClassName, translate(level), text, thrown);
//fixed:
logger.log(null, loggerClassName, translate(level), text, null, thrown);
but upgrading to jboss-logging:3.0.0.Beta5 and fixing the compatibiliy issue will not suffice -
seam-solder provides it's own repack of jboss-logging:3.0.0.Beta4 - but it's stripped across api and impl jar - for me best was to remove all occurrences of jboss-logging sources them from seam-solder (api, impl) and recompile them. After that If I recall - some sources of several seam-modules (seam-servlet) needs to be fixed - mainly missing imports after removing jboss-logging from seam-solder and some minor fixes to make seam modules code compatible with org.jboss.logging:jboss-logging:3.0.0.Beta5.
One more thing is required during build of upgraded seam modules - which use type-safe jboss-logging loggers: @MessageLogger/@LogMessage and @MessageBundle/@Message - you have to introduce additional maven dep:
<!-- JBoss Logging annotation processor for generating type-safe loggers, 1.0.0.Beta1 used by Seam3 -->
<dependency>
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging-tools</artifactId>
<version>1.0.0.Beta4</version>
<scope>provided</scope>
<optional>true</optional>
</dependency>
to generate concrete classes for interfaces annotated with above mentioned annotations.
Indeed these are good news, I'm going to try with even more Seam3 modules on gf3.1_b43.