JRebel 6.5.1
NetBeans8.1 (but Glassfish4.1, because for some strange reason my large web app takes about 10 times longer to deploy on Glassfish4.1.1 or Payara4.1).
In a relatively standard (but somewhat old) very large NetBeans web app, deployed over /build/web.
I am NOT using compile-on-save deliberately, I am using explicit compile (because I am using ObjectDB as JPA provider, and I have not managed to get its enhancement to work yet with NetBeans compile-on-save, see below.)
I am getting copious output (1000s of lines) in the Glassfish log on making changes to and reloading an abstract class and an extending concrete @ViewScoped managed bean class. The first few lines of the copious output (adapted) are like:
Warning: Naming binding already exists for java:module/env/com.example.ejb.ExampleBean/ctx in namespace {java:module/env/com.example.ejb.DocumentFacade=com.sun.enterprise.naming.impl.JavaURLContext@5669b9c9, java:module/env/com.example.web.ElementManager/ejbFacade=com.sun.enterprise.container.common.impl.ComponentEnvManagerImpl$EjbReferenceProxy@4f45d31d, java:module/env/com.example.ejb.DemoCommon/exampleRequest=com.sun.enterprise.container.common.impl.ComponentEnvManagerImpl$EjbReferenceProxy@13fea916, ...
I will provide both Glassfish output and jrebel.log (info level at first) via support@zeroturnaround.com.
PS: I am using ObjectDB as JPA provider and have some other compatibility problems, but I don’t think they are related to this particular problem with simple JSF managed beans as reported here.
-
This topic was modified 1 day, 15 hours ago by
webel.
