Hi Maxim, no sorry. I had the same issue before.
Is there a @where clause possible in the annotation? Did you see my comment about this issue: http://code.google.com/p/openmeetings/issues/detail?id=1454 If nothing helps we might try re-organizing the dataship relations: instead of mapping the table organization_users as extra Java Object we add a new table: organization_properties => where we store the isModerator flag for the user And the organization_users becomes a pure mapping table. In a many-to-many relation this mapping table would have no own Java Object, it would be just konwn internally by openJPA and would only contain two columns: user_id organization_id in the User-Object you would then have directly an attribute: List<Organizations> Maybe we should try that one? Sebastian 2011/8/25 Maxim Solodovnik <[email protected]> > Hello Sebastian, > > Could you please help me with following issue: > > currently we have Organisation_Users mapping in Users class defined as > follows: > @OneToMany(fetch = FetchType.EAGER) > @JoinColumn(name = "user_id", insertable = true, updatable = true) > private List<Organisation_Users> organisation_users; > > BUT > deleteUserFromOrganisation method does not actually deletes > the Organisation_Users object. It is set deleted flag to "true". > Maybe you know the way how Organisation_Users list for user can be filtered > by *deleted=false *? > > Thanks in advance > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner http://www.webbase-design.de http://openmeetings.googlecode.com http://www.wagner-sebastian.com [email protected] -- You received this message because you are subscribed to the Google Groups "OpenMeetings developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/openmeetings-dev?hl=en.
