If created, the calls return true. If they already existed and need not be created, false is returned.
The pojo subsystem apparently tries to deploy beans it finds in any jboss-beans.xml file it finds on the classpath. The netty jar has one, of course, but it references a bean that's already installed in the AS, because it depends on netty, too. A side benefit of removing the pojo subsystem is the disappearance of this annoying log message: "Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xml features (potential exceptions)." It remains to be seen whether Immutant users will rely on this now-missing feature. I kinda doubt it. :)
This fix has the happy side effect of allowing the dev ns to be used in clojure 1.3. It also includes some test re-org in core.
…solved by polyglot.
This works, unless you want to change :singleton. I'll take a look at that next.
We had this to prevent duplicate cookies (one for JSESSIONID, one for ring-session, both with the same value), but it turns out ring needs the ring-session value to properly clear sessions, even when we are using ServletSession. My last change here had the handler stuffing a ring-session cookie back in place, which is brittle and foolish. So, we're ditching this handler altogether.
Also making the JobScheduler fallback to the default JobFactory for jobs not originally scheduled with it, e.g. when scheduled via quartzite or some other quartz api.
Still need to upgrade polyglot to quartz 2.1.5 to make quartzite happy.