Hi Alain, Thanks for reporting this.... could you raise a ticket, and ideally create a small example demonstrating the problem up on github?
In terms of a work-around, I presume you are using the @Aggregated annotation? If that's the case, then the easiest thing is probably to simply remove the FacetFactory from the programming model that picks up and processes this annotation. Doing this will mean that the entity is treated as a regular root entity. This won't make any difference if you are using the JDO object store (though in the future it might, and the [currently unreleased] NoSQL object store does support aggregated entities). The good news is that you can remove the facet factory just by editing the isis.properties file. I've documented how to do this on the website [1]. Let me know how you get on Dan [1] http://isis.apache.org/core/metamodel-finetuning-the-programming-model.html On 31 December 2012 01:52, 张峰昌 <[email protected]> wrote: > Hi,Dan:**** > > I have tried the isis 1.0.0,and there is a problem with wicket viewer. The > wicket viewer provide a view link for an aggregated entity,and the > subsequent call to the link will be treated as root oid,so the system will > throw exception for this operation.**** > > An other problem still exist when RootEntity has a collection member which > element is aggregated entity.(the wicket said:??? ENTITYMODEL OID:NULL for > eache element in the colleciton).**** > > ** ** > > It’s not a big problem,but when I want go ahead with my project I have to > change the aggregated entity into root entity,and then the domain model > will be no aggregated entities.**** > > ** ** > > Are there some advice for the problem above for now?**** > > ** ** > > ** ** > > Alain**** > > ** ** > > ** ** > > 张峰昌**** > > 电话：18930623939**** > > 欲知诸法实相，当习般若波罗蜜**** > > ** ** >
