Hi Martin,
Thanks for your comments!
In order to get further insight about the context, my answers are inline
below:
M: In what sense are these related (i.e. what does it mean for one to be a
child of the other)?
S: Here s4 and s5 are the restful web service / application, which provides
an interface to our database application which stores data about the
computing resources provided by each university, lets say s4 for university1
and s5 for university2. However, they are the children of a similar kind of
web service (a level higher) where all the data of the resources are being
aggregated, which we call the region/state level web service, called s3.
Similarly s3 is connected to the s2 which is a country level web service
which aggregates all the data of their children (states) into the country
level repository.
We also have requirement for a continent level web service which aggregates
all the resource information (the datastore) from their respective children,
thus making a "federation" of jersey web services.
M: Do s4 and s5 need resources of its parents to work properly?
S: I think s4 and s5 has to know where their parent is so that the owned
resource information can be published.
Best regards,
Sam
--
View this message in context: http://jersey.576304.n2.nabble.com/Restful-service-hierarchy-tp6510175p6512918.html
Sent from the Jersey mailing list archive at Nabble.com.