Did that immediately after applying the new code. Didn't help. Strange though that you haven't encountered it and that the CI build isn't broken. Will investigate further.
Cheers, Jeroen On Mon, Nov 25, 2013 at 9:17 PM, Dan Haywood <d...@haywood-associates.co.uk> wrote: > Jeroen, > I've just a change to Estatio's isis.properties file so that > RegisterEntities is called first. Could you check if this fixes the issue? > Cheers > Dan > > > On 25 November 2013 18:54, Jeroen van der Wal (JIRA) <j...@apache.org>wrote: > >> >> [ >> https://issues.apache.org/jira/browse/ISIS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831762#comment-13831762] >> >> Jeroen van der Wal commented on ISIS-597: >> ----------------------------------------- >> >> In my case this updates causes estatio to fail upon initalization when >> running the fixture. This is the last output I get in the console: >> >> 19:45:43,958 [Schema ] Creating column >> "levellingPercentage" for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column >> "nextIndexValue" for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column >> "settledValue" for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column >> "baseIndexStartDate" for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column "indexId" >> for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column >> "indexedValue" for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column "baseValue" >> for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column >> "effectiveDate" for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column >> "indexationPercentage" for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column >> "baseIndexValue" for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column >> "nextIndexStartDate" for table "LeaseTerm" >> 19:45:43,958 [Schema ] Creating column >> "rebaseFactor" for table "LeaseTerm" >> 19:45:43,958 [Schema ] ALTER TABLE "LeaseTerm" ADD >> COLUMN "levellingPercentage" DECIMAL(19,1) NULL >> >> The levellingPercentage field is defined on the subclass of LeaseTerm. >> >> >> > Services still not injected when entering @PostConstruct methods on a >> Service >> > >> ----------------------------------------------------------------------------- >> > >> > Key: ISIS-597 >> > URL: https://issues.apache.org/jira/browse/ISIS-597 >> > Project: Isis >> > Issue Type: Improvement >> > Components: Core, Objectstore: JDO >> > Affects Versions: objectstore-jdo-1.3.0, core-1.3.0 >> > Reporter: Oscar Bou >> > Assignee: Dan Haywood >> > Fix For: objectstore-jdo-1.4.0, core-1.4.0 >> > >> > >> > Methods annotated with @PostConstruct are invoked before their objects >> being injected. >> > Steps to reproduce: >> > As per [1], create a method on a service annotated with @PostConstruct, >> like this one: >> > @PostConstruct >> > public void init(final Map<?, ?> props) { >> > server.setGlobal("eventOccurrences", this.eventOccurrences); >> > >> > } >> > .... >> > // {{ injected: EventOccurrences >> > private EventOccurrences eventOccurrences; >> > public final void injectEventOccurrences(final EventOccurrences >> eventOccurrences) { >> > this.eventOccurrences = eventOccurrences; >> > } >> > // }} >> > The problem is that when the execution arrives to: >> > server.setGlobal("eventOccurrences", this.eventOccurrences); >> > this.eventOccurrences is still null... So it has not yet been injected >> (or instantiated). >> > [1] http://isis.apache.org/core/services/initializing-services.html >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.1#6144) >>
