On 10 October 2014 08:18, Erik de Hair <e...@pocos.nl> wrote:
> Besides cleaning my local mvn repo I might have changed the logging
> properties indeed.
>
>
OK. The ticket I raised has been fixed, will be in 1.7.0 release.
> On 10/09/2014 12:57 PM, Dan Haywood wrote:
>
>> Just coming back to you on this... the only thing that looks different is
>> your use of the QXxx type-safe query classes. I doubt that is the issue,
>> but it's the only thing that I can see.
>>
>> What happens if you run a JDOQL-style query?
>>
> I tried different types of queries, also JDOQL-style. Always the same
> error... (the only thing that differs than, is the way the query compiles)
>
> Could there be any dependencies missing
perhaps, though doesn't really look like a dependency issue.
> or is there any need to add dependencies for testing purposes?
>
>
Not that I'm aware of.
All I can suggest is to rewind to a known good point: eg take the simple
app (from the simple app archetype), and then copy your code on top of
that, taking care with any configuration files.
And/or, we could do a TeamViewer session for 20 minutes if you want to see
if we can figure it out; contact me off-list to arrange.
Thx
Dan
>
>> On 8 October 2014 15:11, Dan Haywood <d...@haywood-associates.co.uk>
>> wrote:
>>
>> OK, well, from I've figured out the issue for your original problem (and
>>> it is a defect in Isis...)
>>>
>>> ... specifically *if logging is set to DEBUG*, then there's a call to
>>> pojo.hashCode() on the request-scoped service (Bulk.InteractionContext),
>>> and that's what's tripping up.
>>>
>>> I'll fix that for 1.7.0.
>>>
>>> Not sure about your JDBC issue though, let me stare at it for a while.
>>>
>>> Dan
>>>
>>>
>>> On 8 October 2014 14:49, Erik de Hair <e...@pocos.nl> wrote:
>>>
>>> It's against 1.6.0.
>>>>
>>>> I tried to get you an example that produces the same error by stripping
>>>> all 'company code' from my code but this gives me some other errors... I
>>>> believe I can't give you the right example :-(
>>>>
>>>> ________________________________________
>>>> From: Dan Haywood [d...@haywood-associates.co.uk]
>>>> Sent: Wednesday, October 08, 2014 2:22 PM
>>>> To: users
>>>> Subject: Re: integration tests fail: problem with registration of
>>>> services
>>>>
>>>> is this against 1.7.0-snapshot or 1.6.0?
>>>>
>>>> and (even better) can you provide an example demonstrating the issue on
>>>> github?
>>>>
>>>> On 8 October 2014 13:17, Erik de Hair <e...@pocos.nl> wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> When running integration tests I get the following stacktrace:
>>>>>
>>>>> Caused by: java.lang.IllegalStateException: No service found for
>>>>> thread;
>>>>> make sure ((RequestScopedService)service).__isis_startRequest() is
>>>>>
>>>> called
>>>>
>>>>> first
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.services.ServiceInstantiator$
>>>> 2.invoke(ServiceInstantiator.java:117)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.applib.annotation.Bulk$InteractionContext_$$_jvst36f_
>>>> 0.hashCode(Bulk$InteractionContext_$$_jvst36f_0.java)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.persistence.adaptermanager.
>>>> PojoAdapterHashMap.add(PojoAdapterHashMap.java:121)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.persistence.adaptermanager.
>>>> AdapterManagerDefault.mapAndInjectServices(AdapterManagerDefault.java:
>>>> 717)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.persistence.adaptermanager.
>>>> AdapterManagerDefault.adapterFor(AdapterManagerDefault.java:174)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.system.persistence.PersistenceSession.
>>>> createServiceAdapters(PersistenceSession.java:221)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.system.persistence.PersistenceSession.
>>>> initServices(PersistenceSession.java:209)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.system.persistence.
>>>> PersistenceSession.open(PersistenceSession.java:199)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.system.session.IsisSessionDefault.open(
>>>> IsisSessionDefault.java:110)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.system.context.IsisContextStatic.
>>>> openSessionInstance(IsisContextStatic.java:71)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.system.context.IsisContext.
>>>> openSession(IsisContext.java:279)
>>>>
>>>>> at
>>>>>
>>>>> org.apache.isis.core.runtime.system.IsisSystemFixturesHookAbstract
>>>> .initializeServices(IsisSystemFixturesHookAbstract.java:177)
>>>>
>>>>> I'm using the todo app ToDoSystemInitializer with the following
>>>>> registration of services:
>>>>>
>>>>> // services annotated with @DomainService
>>>>> withServices(new Contacts(), new Companies(),
>>>>> new Permissions(), new Roles(),
>>>>> new NestedSetManagerService(),
>>>>> new QueryResultsCache());
>>>>>
>>>>> withServicesIn("org.apache.isis.core.wrapper"
>>>>> ,"org.apache.isis.applib"
>>>>> ,"org.apache.isis.core.
>>>>> metamodel.services"
>>>>> ,"org.apache.isis.core.runtime.services"
>>>>>
>>>>> ,"org.apache.isis.objectstore.jdo.datanucleus.service.support" //
>>>>> IsisJdoSupportImpl
>>>>>
>>>>> ,"org.apache.isis.objectstore.jdo.datanucleus.service.eventbus" //
>>>>> EventBusServiceJdo
>>>>> );
>>>>>
>>>>> When I omit the withServicesIn-call my tests start but I get an other
>>>>> error later on.
>>>>>
>>>>> I used the todoapp as the basis for my tests but had to replace/remove
>>>>>
>>>> the
>>>>
>>>>> dom-part with my own dom. The todoapp tests run OK.
>>>>>
>>>>> Any idea?
>>>>> Erik
>>>>>
>>>>>
>>>
>
