Null log inside EntityQuery while testing with TestNG

[vanyatka]

Hi,

How can one setup getLog() working with TestNG? I've got the problem that getLog() doesn't return the actual logger, and that breaks testing with NPE.

Here is the component I'd like to test:

@Name("regionList")
public class RegionList extends EntityQuery<Region>
{
    public RegionList()
    {
        setEjbql("select region from Region region");
    }

    @Override
    public List<Region> getResultList() {
        List<Region> regionList = super.getResultList();

        //## Here it breaks in testNG ##
        getLog().warn("Size is #0", regionList.size()); 

        return regionList;
    }

The test class for the component:

public class RegionListTest extends SeamTest {

    @Test
    public void testGetRegions() throws Exception {
        new ComponentTest() {
            protected void testComponents() throws Exception {
                RegionList regionList = new RegionList();
                List<Region> resultList = regionList.getResultList();
                for (Region region : resultList) {
                    System.out.println("region = " + region.getFullName());
                }
            }
        }.run();
    }
}

Any advice is appreciated,
Ivan

[cash1981]

Just use the seam logger in your RegionList and it should work fine.


@Logger
Log log;

and instead if getLog(), just have log.warn("");
And then testng logging should also be displayed.

If it is not displayed, then check your log levels. Maybe it is set to error.

[vanyatka]

Just use the seam logger in your RegionList and it should work fine.

   @Logger
   Log log;

Thanks for advice, Shervin

However, the component extends EntityQuery, which already has a log object (and getLog() works fine on the server). It makes little sense injecting another one to a subclass. Besides, it is a nuisance having to add it to each EntityQuery component.

I was hoping for some testNG configuration setup that would eliminate the problem.

[paulmkeogh]

It doesnt work for me either !

Any suggestions anyone - can't believe its not possible to test a component with @Logger ?