It's expected in 7.3, but may be item need to be removed instead of disabled.
7.3 will contain jpql editor for ant j2se only.
as web project is run in a container(and persistence.xml contain corresponding properties) even if it will be possible to enable it on nb side for web projects, it will require special handling and may be realized in future releases.

ok, would be nice to have this for Maven J2SE for 7.3

http://hg.netbeans.org/web-main/rev/8313e1a22c82 enabled for maven j2se
if it's good to remove instead of disable for web, it may be better to track as separate issue now

Integrated into 'main-golden', will be available in build *201209130001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/8313e1a22c82
User: Sergey B. Petrov <sj-nb@netbeans.org>
Log: #217587 enable jpql editor in maven j2se

Hi Sergey, so are you saying that for web projects the difficulty is that we need to launch the container? We already have some support for the embeddable container for testing, could we reuse that? Cc'ing David who implemented the embeddable container support.

At least special handling is required and feature fall out of 7.3 scope because of limited time. embedded container may not solve everithing as thee should be datasource configured the same way as in target container. I have some ideas to substitute datasource properties with connection properties, add provider property, and run as resource_local but can't say if it's easy or not and ifthere are any issues, it's just ideas about realization

Sergey, could you tell me please why this cannot be enabled for Web Projects? I would think that all you need is a data source similarly like in "Entity from DB" wizard. Or am I missing something? Thanks.

web application can be run on server only, jpql execution is similar to main class execution but user do not have to right own code and need to build once instead of rebuild after each jpql change.
persistence do nothing with user's application yet but in case of web some actions similar to 'entity from db' will be required but I expect it will not be enough.

one more item is classpath. for j2se it's expected to have everithing inside but for ee it's expected to have a lot of libraries on server side and it may be more worst issue for realization compare to issue with datasource->jdbc url converting.

Thanks for the explanation. I understand it now. Yes, the embeddable container should help in this case. If I remember it correctly each server which is supporting the embeddable container returns a new type of classpath which can be used to run for example unit tests in the embeddable container. "j2ee.platform.embeddableejb.classpath" classpath property. You should be able to just run your code in this classpath *in theory*.

jpql editor may be switched on for web, it's under investigation and preliminary results seems promising