Troubles with Grails + Maven integration testing
Locked
 
|
Administrator
|
|
|
|
|
|
|
|
Hi Ian,
I still can't make GATE and Grails like each other. Can you take a look at the applicationContext.xml and resources.xml which are attached? The relevant part of the Maven log is also attached. I can't figure out what could possibly try to initialize GATE twice. Thanks in advance, Stefan > On 20.4.2012 г. 20:54 ч., Stefan wrote: >> Thanks for the clarifications Ian! >> >> I was puzzled because the app was working properly when deployed to a >> webapp container, but just didn't seem into place when running the >> integration tests in the Maven build. >> >> By the way I've already tried putting <gate:init> and friends into >> the resources.xml only but then it wouldn't run - something was >> trying to set gate.home and the other properties twice, which >> resulted in IllegalStateExceptions. But maybe I'm doing something wrong. >> >> Thanks anyway, >> Stefan >> >> On 20.4.2012 г. 20:16 ч., Ian Roberts wrote: >>> On 20/04/2012 17:55, Stefan wrote: >>>> Why is that? As I've used Spring before Grails there are some cases >>>> when >>>> you have an applicationContext which holds the "application >>>> context" and >>>> you also have a DispatcherServlet context, where you do the URL >>>> mapping >>>> and define the necessary beans. So I think it is natural to have the >>>> most common or let's say fundamental resources defined in the >>>> applicationContext and just override/extend it via resources.xml. >>>> And as >>>> the documentation says "/You can easily register new (or override >>>> existing) beans by configuring them in >>>> |grails-app/conf/spring/resources.groovy|/", there should be some >>>> beans >>>> defined by me in the applicationContext, right? That's what I mean >>>> by my >>>> own applicationContext.xml. >>> The root application context (WEB-INF/applicationContext.xml) in Grails >>> is very minimal, it defines the GrailsApplication and one or two other >>> supporting objects but everything else goes into the >>> GrailsApplication's >>> "mainContext" - not only things you define in resources.xml/groovy but >>> also the beans defined by Grails core and plugins, such as services, >>> controllers, domain classes etc. This context is certainly supposed to >>> be created for integration tests, that's what distinguishes them from >>> unit tests... >>> >>>> I'm trying to use GATE embedded into my Grails app, you can see >>>> http://gate.ac.uk/sale/tao/splitch7.html#x11-1750007.15 if you're >>>> interested. >>>> We've used it in many Spring applications, but it just seems that the >>>> applicationContext isn't loaded at all in the integration-test >>>> phase and >>>> the resources.xml cannot reference beans defined in the >>>> applicationContext. >>> You can put the<gate:init> and friends into resources.xml (or the >>> equivalent DSL into resources.groovy or a plugin), it doesn't have >>> to go >>> into the parent applicationContext.xml. This is how Mímir works and >>> it's how I've done it in several other (non-open-source) Grails apps. >>> >>> [Full disclosure - I'm one of the GATE core developers, and the one who >>> wrote its Spring support in the first place] >>> >>> Ian >>> >> >> > > -- Stefan Enev<[hidden email]> Software Engineer Ontotext AD --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email  applicationContext.xml (2K) Download Attachment resources.xml (2K) Download Attachment mvn.txt (4K) Download Attachment |
Loading...
| Powered by Nabble | Edit this page |