…rams when an exception is logged by the application"
…ix to node names"
…message tag. specifically, if the default value was an empty string it wasn't being respected.
…ing the jetty plugin"
…pplication context so that any configuration made by plugins/apps apply to our proxy creator." Installing the APC in this way makes it not be used when generating transactional proxies, which means that Groovy classes don't automatically get proxied by class. Unfortunately, installing it in a way that does allow it to be used when generating transactional proxies runs up against the Spring bug SPR-7808 (which prevents usage of custom APC with 'aop' or 'tx' namespaces). This exercise has revealed that any user or plugin code that looks up the APC via it's well defined name during application bootstrap will not receive our custom instance. When Spring is doing this internally it will create an instance based on the default implementation. Once the Spring bug is fixed, the solution for us will be to replace line 72 of this patch we are reverting to: getSpringConfig().getUnrefreshedApplicationContext().beanFactory.registerBeanDefinition(AopConfigUtils.AUTO_PROXY_CREATOR_BEAN_NAME, proxyCreatorDefinition)
…on context so that any configuration made by plugins/apps apply to our proxy creator.
…solver(ServletContext) to satisfy some failing tests. the real issue here may be some tests that need improving, pending investigation.
…n the jspViewResolver bean instead of the first ViewResolver bean found in the application context.
…ll to deprecated bindMultipartFiles with call to bindMultipart
… just whitespace either side of a delimited word or phrase. In other words, this: This _works_: now generates italics for the word 'works' whereas it did no before.
…tCase to simply unit testing code that renders validation errors as XML or JSON.
…gin to rig up the appropriate marshallers. This test would have been failing before GRAILS-6791 was fixed except for the fact that the test was registring a marshaller that the plugin should have been registering.
…s out to be a problem in ConvertersGrailsPlugin where the XML ObjectMarshallerRegisterer and JSON ObjectMarshallerRegisterer converter were being added to the application context with the same bean name so the last one in won.
… when the valueMessagePrefix wasn't provided. This is now working. Also updated the tests which weren't covering this scenario properly.