[seam-dev] Status check!

[Dan Allen]

I've done #1.

In order to pass any test successfully on GlassFish atm, you need to use the
seam-solder combined JAR. That's necessary until I complete #2.

Here's a list of the test failures to give you an idea of where we are:

Tests in error:
  testDefaultBean(org.jboss.seam.solder.test.defaultbean.DefaultBeanTest)
  testDefaultProducerMethod(org.jboss.seam.solder.test.defaultbean.DefaultBeanTest)
  testDefaultProducerUsesCorrectDelegate(org.jboss.seam.solder.test.defaultbean.DefaultBeanTest)
  testDefaultProducerFields(org.jboss.seam.solder.test.defaultbean.DefaultBeanTest)
  testDefaultBeanObserverMethods(org.jboss.seam.solder.test.defaultbean.DefaultBeanTest)
  testGeneric(org.jboss.seam.solder.test.bean.generic.method.GenericBeanTest)
  testGeneric(org.jboss.seam.solder.test.bean.generic.method.ProducersOnGenericBeanTest)
  testProducerSuperclass(org.jboss.seam.solder.test.bean.generic.method.ProducersOnGenericBeanTest)
  testGeneric(org.jboss.seam.solder.test.bean.generic.method.GenericProductTest)
  testDisposerCalled(org.jboss.seam.solder.test.bean.generic.method.GenericProductTest)
  testGeneric(org.jboss.seam.solder.test.bean.generic.method.QualifierOnlyGenericBeanTest)
  testGeneric(org.jboss.seam.solder.test.bean.generic.field.GenericBeanTest)
  testScope(org.jboss.seam.solder.test.bean.generic.field.GenericBeanTest)
  testGenericUnwrap(org.jboss.seam.solder.test.bean.generic.field.GenericBeanUnwrapTest)
  testGeneric(org.jboss.seam.solder.test.bean.generic.field.ObserversOnGenericBeanTest)
  testGeneric(org.jboss.seam.solder.test.bean.generic.field.ProducersOnGenericBeanTest)
  testGeneric(org.jboss.seam.solder.test.bean.generic.field.GenericProductTest)
  testElResolver(org.jboss.seam.solder.test.el.ElTest)
  testCustomElResolver(org.jboss.seam.solder.test.el.ElTest)
  testUnwrapsInjectionPoint(org.jboss.seam.solder.test.unwraps.UnwrapsTest)
  testUnwraps(org.jboss.seam.solder.test.unwraps.UnwrapsTest)
  org.jboss.seam.solder.test.serviceHandler.ServiceHandlerTest
  org.jboss.seam.solder.test.serviceHandler.ServiceHandlerTest
  org.jboss.seam.solder.test.bean.generic.alternative.GenericBeanAlternativeTest
  org.jboss.seam.solder.test.bean.generic.alternative.GenericBeanAlternativeTest

Tests run: 94, Failures: 0, Errors: 25, Skipped: 0

If you want to start testing, you need to change Deployments.java as follows
until #2 is done.

public class Deployments
{
   private static final String LOCAL_MAVEN_REPO =
         System.getProperty("maven.repo.local") != null ?
System.getProperty("maven.repo.local") :
               (System.getProperty("user.home") + File.separatorChar +
               ".m2" + File.separatorChar + "repository");

   public static WebArchive baseDeployment()
   {
      return ShrinkWrap.create(WebArchive.class, "test.war")
         .addLibraries(
               new File(LOCAL_MAVEN_REPO + File.separator +
"org.jboss.seam.solder".replace(".", File.separator) +
                     File.separator + "seam-solder" + File.separator +
"3.0.0-SNAPSHOT" + File.separator + "seam-solder-3.0.0-SNAPSHOT.jar"),
               MavenArtifactResolver.resolve("org.jboss.logging",
"jboss-logging"))
         .addWebResource(EmptyAsset.INSTANCE, "beans.xml");
   }
}

-Dan

On Fri, Jan 21, 2011 at 16:32, Dan Allen <dan.j.allen at gmail.com> wrote:

> On Fri, Jan 21, 2011 at 15:50, Shane Bryzak <sbryzak at redhat.com> wrote:
>
>>  Realistically you probably have a couple more days before we sort out the
>> Solder issues with Glassfish, I need to catch up with Dan first and find out
>> what the current status is.  If you could get the API changes done before
>> then, then great, otherwise we'll have to make them between betas.
>>
>
> As you are aware, we have to sort out the Solder issues on GlassFish. We
> want to solve this problem in the most efficient manner as possible, which
> we believe is by using Arquillian to get the Solder test suite to run on
> GlassFish (allowing us to work inside the IDE and debugger). We will target
> GlassFish 3.1-b37 or better. Once it passes, that will be our indication it
> works (plus some subsequent manual testing just to be sure).
>
> However, the remote GlassFish adapter for Arquillian based on JSR-88 was
> extremely fragile and when we leaned on it, it fell apart. So Jason Porter
> came through in a major way and implemented a new remote GlassFish adapter
> for Arquilian based on the admin REST API in GlassFish 3.1. I verified last
> night that it works and I pushed out a snapshot.
>
> What this means is that we can now comfortably debug the Arquillian tests,
> likely getting us there a heck of a lot faster. Here are the steps that need
> to be performed:
>
> 1. Add the arquillian-glassfish-remote-3.1:1.0.0-SNAPSHOT profile to the
> Solder pom.xml
> 2. Move all sources from api/ into impl/ (we will more gradually move
> sources to the api/ module once tests are passing on GlassFish)
> 3. Work through the failing tests and figure out which ones are failing and
> get them fixed
> 4. Merge Ken's logging changes (I think biting this bullet is important for
> the first Beta1)
> (anything I may be missing)
>
> I'll do #1 shortly and hopefully #2 before the end of the day (or I'll
> delegate it). #3 is work for the weekend or early next week. #4 should be
> quick once we solve the GlassFish issue.
>
> -Dan
>
> --
> Dan Allen
> Principal Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen
>



-- 
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110121/b0bdca1b/attachment.html