Why is the path to the dsl request object limited to four levels?

Question

I am currently using the maven apt plugin to create EntityPath base classes.

      <plugin>
            <groupId>com.mysema.maven</groupId>
            <artifactId>maven-apt-plugin</artifactId>
            <version>1.0.4</version>
            <executions>
                <execution>
                    <goals>
                        <goal>process</goal>
                    </goals>
                    <phase>generate-sources</phase>
                    <configuration>
                        <outputDirectory>target/generated-sources/java</outputDirectory>
                        <processor>com.mysema.query.apt.jpa.JPAAnnotationProcessor</processor>
                    </configuration>
                </execution>
            </executions>
            <dependencies>
                <dependency>
                    <groupId>com.mysema.querydsl</groupId>
                    <artifactId>querydsl-apt</artifactId>
                    <version>${querydsl.version}</version>
                </dependency>
                <dependency>
                    <groupId>com.mysema.querydsl</groupId>
                    <artifactId>querydsl-jpa</artifactId>
                    <classifier>apt</classifier>
                    <version>${querydsl.version}</version>
                </dependency>
            </dependencies>
        </plugin>

this generates the desired Q classes, and it is useful in constructing predicates for queries. However, I noticed that I always get an exception with a null pointer whenever I go beyond four levels, i.e.:

QFoo.foo.x.y.z

where Z is of type QZ; generated by EntityPath.

Is this a limitation of QueryDSL?

Answer 1

, Querydsl. , . , http://www.querydsl.com/static/querydsl/3.5.0/reference/html/ch03s03.html#d0e2181