JRebel’s integration features with other frameworks are implemented as isolated plugins. Most of the plugins are enabled by default (see notifications of disabled plugins in the JRebel banner on JVM startup). Integration plugins can be turned on/off by adding the JVM parameter -Drebel.[plugin_id]=false (/ true). For example, to disable the EclipseLink plugin, add JVM argument -Drebel.eclipselink_plugin=false. If you are using the configuration wizard, you can enable/disable the plugins through the wizard.
Disabling a plugin only disables the extra features listed in the table below for that given plugin. Otherwise, the framework will still function and JRebel’s core features (class reloading) will still be available. Disabling a plugin might be useful when some certain plugin causes problems in your environment or is otherwise buggy. All that kind of incidents should be reported to firstname.lastname@example.org so we can improve our integration and make our product better suit your needs : )
Tested with versions
Expected to work with versions
allows ADF page definition files to be reloaded.
Oracle Fusion Middleware 184.108.40.206.0
Patches ADF implementation of JSF lifecycle allowing Mojarra plugin to do the rest.
adf-richclient version 33061
adf-richclient version 41532
Enables the load-time-weaving of AspectJ aspects. Can alter class loading/initialization order during startup.
The plugin reinitializes ATG Nucleuses when the Nucleuse elements Java class file has changed.
It also re-reads the values from the properties file in the reloading process. So that when Nucleuses have new conntections then they will be initialized and if they have new properties values then those will also be there.
ATG 10.1 and ATG 2007.4
ATG 10.1 and ATG 2007.4
Reloads the menu definition from menu.xml.
Tracks changes in the configuration of Apache CXF REST/WS application
2.1.2, 2.4.3, 2.5.2
2.1.2+, 2.4.x, 2.5.x
Reloads an EntityManagerFactory when any of the mapping files or annotated entity classes changes. When an entity class is reloaded the corresponding cache entries are flushed.
Turns on facelet development mode for automatic reloading of facelets.
Also provides reloading of facelet tag libraries.
Reloads BeanWrapper. Remedies the flaws of FreeMarker’s own JRebel integration.
Refreshes Groovy class metadata and call site cache on class change. After reload, call site cache may be misaligned for obsolete methods on stack.
Wires changed dependencies in Guice singletons.
1.0, 2.0, 3.0
Enables to reload client-side classes in hosted (development) mode. Server-side classes should be reloaded without the plugin.
Enables configuration reloading (rebuilding of Hibernate’s SessionFactory) when updates are detected to underlying configuration resources (either XML mapping files or model classes with JPA annotations).
Enables automatic schema updating if hibernate.hbm2ddl.auto=update or schemaUpdate=true on org.springframework.orm.hibernate3.LocalSessionFactoryBean.
Limitations: The SessionFactory rebuilding works when it is being built through classes HibernatePersistence, HibernateService, org.jboss.hibernate.jmx.Hibernate or org.springframework.orm.hibernate3.LocalSessionFactoryBean. All classes that create SessionFactory instances have to be handled separately. If user creates SessionFactory in his own code, the integration won’t capture that.
Enables adding/editing/removing Bean Validation constraint annotations on bean classes and parent constraint annotation types (i.e., supports composite constraints)
Monitors Spring bean definitions in xml-files, reloads them when changed.
Monitors packages that could contain Spring beans defined by annotations. If new beans (or changes to old ones) are seen, reloads them.
Makes Spring re-do the bean auto-wiring and singleton bean configuration.
Disables caches for properties that are replaced replaced for property placeholders in Spring’s XML configuration files. When underlying properties files have changed, new values will be inserted on next reloading of these Spring beans.
(The integration doesn’t of course support features that Spring 2.0 itself didn’t yet support).
Reloads Spring Data-generated repository implementations if repository interface changes.
Handles adding and modifying Spring Data-managed persistent entities (@Document, @NodeEntity).
If repositories are configured using Spring configuration, then Spring core plugin should be enabled, otherwise repository reloading won’t work.
Spring Data Commons 1.2.1, 1.3.2, 1.4.0 RC1
Spring Data Commons 1.x
Reload URL mappings (defined by @RequestPath annotations) when Spring beans have changed. (Before processing a request, Spring MVC plugin tells Spring core plugin to check/reload the beans. If any bean was reloaded, Spring core plugin sends notification to Spring MVC plugin, which then triggers URL mappings rebuilding.
Also supports reloading other annotations: @ExceptionHandler, @ModelAttribute, @RequestParam.
The plugin ID intentionally collides with the one of Spring core plugin. Spring MVC integration depends on Spring core integration and cannot be enabled independently.
Handles adding/editing of annotation-based security checks.
Handles adding/modifying/removing of <http> blocks in xml configuration files.
Just turns on the development mode by default. No other customizations at all.
Reloads endpoint mappings when classes have changed (annotation-driven conf) or new endpoint is added in via xml (xml conf)
Republishes wsdl after xsd is changed (when using dynamicWsdlDefinition)
Fixes Stripes’s annotations metadata caching to work with reloading. Classes that have fields with @Validate annotations will be removed from caches and re-processed by Stripes after being reloaded by JRebel.
Fixes UrlBinding caching for ActionBeans. UrlBindings configured with the @UrlBinding annotations are reloaded by overriding the behaviour of the NameBasedActionResolver.
Supports stripes-guice and stripes-guicer plug-ins for instantiating Guice ActionBeans. (available since JRebel 4.0 M2)
Includes 3rd party contributions from Andreas Knifh.
Reloads full Struts configuration (by forcing Struts to re-create it’s ActionServlet when updates to underlying configuration XML-files are detected. (XML configuration files are remembered when Struts is initializing itself.)
“Reloads” Struts’s message resources by emptying the message caches when there are any updates to message resources. (Message resource files are remembered when Struts is initializing itself.)
Keeps track of XML configuration file updates and triggers the Struts2 configuration reloading when there are any (duplicates Struts2’s own buggy file monitoring mechanism — see other comments).
Keeps track of annotated action-classes. If the set of action-classes has changed or there are changes to any of the action-classes, trigger configuration reloading.
Enables adding new listener methods to Tapestry’s Page classes.
3rd party contribution.
(embedded in Struts1)
Enabled reloading of Tiles definitions from XML configuration files. Implements it by recreating DefinitionsFactory instance when the underlying XML configuration resources have changed.
JRebel works out of the box with Vaadin framework. Read more here.
Velocity has a method cache for its known beans that prevents changes to those beans (new getter methods) to become accessible from associated Velocity templates. The plugin remedies this by triggering a cache rebuild each time a bean accessed by velocity has been reloaded by JRebel. The implementation is fine-grained: cache will be emptied only for the bean that was reloaded.
probably also others
Refreshes Weld class metadata and wires changed dependencies on class change.
Automatically turns on Wicket’s HTML template reloading.
Tells Spring to try refreshing its context when Spring bean lookup operations fail.
Listens for class reload events. When received, cleans Wicket’s class metadata caches for the reloaded classes that cache the @SpringBean annotations, forcing Wicket to reload the metadata and enabling annotations to take effect.