My favorites | Sign in
Project Home Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 4: Patch: add @RelatedTo.elementClass attribute should be set based on target class when cardinality is many
1 person starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ----


 
Reported by ats...@gmail.com, Nov 29, 2011
What steps will reproduce the problem?
1. assuming there are types Pet and Vet
graph entity --class ~.domain.Pet
graph entity --class ~.domain.Vet
graph relationship --fieldName pets --from ~.domain.Vet --to ~.domain.Pet --direction OUTGOING --cardinality ONE_TO_MANY --type "PETS"
graph relationship --fieldName vet --from ~.domain.Pet --to ~.domain.Vet --direction INCOMING --cardinality MANY_TO_ONE --type "PETS"

What is the expected output?
public class Pet {
    @RelatedTo(type = "PETS", direction = Direction.INCOMING)
    private Vet vet;
}
public class Vet {
    @RelatedTo(type = "PETS", elementClass = Pet.class)
    private Set<Pet> pets;
}
What do you see instead?
Pet.vet field is generated as expected, but
RelatedTo annotation on field Vet.pets has no elementClass attribute
public class Vet {
    @RelatedTo(type = "PETS")
    private Set<Pet> pets;
}

What version of the product are you using? On what operating system?
Rev 365- current latest revision in repository 

Please provide any additional information below.
Pleas apply the patch from the attachment to resolve this issue
relatedToElementClass.patch.txt
878 bytes   View   Download
Nov 30, 2011
#1 Michael....@jexp.de
elementClass is not needed anymore since SDN 1.1, so it is optional. And should probably not be generated.

Powered by Google Project Hosting