OK, so the issue I have is that I cannot create two separate REST Resources with nested URLs e.g.<div><br></div><div>class CustomerRestService(Resource):</div><div> """Handles REST operations for Customer /customer"""</div>
<div> pass</div><div><br></div><div><div>class CustomerAddressRestService(Resource):</div><div> """Handles REST operations for Customer Address /customer/<customerId>/address"""</div>
<div> pass</div></div><div><br></div><div>Instead I would need to have one common Resource that handles everything under '/customer',</div><div>including the customer entity and customer address entity in one (and any other entity whose root is '/customer').</div>
<div><br></div><div>That isn't a very good design...especially if you maybe have 50 different entities hooked up under '/customer' (like in our app).</div><div>It seems in order to enable having nice cohesive classes that provide a REST service for just one entity I would need to manually<br>
route the request from the root Resource into each of them myself.</div><div><br></div><div>That is what i was trying to avoid, but it looks like there is no other choice.</div><div><br></div><div>Jacek</div><div><br></div>
<div><br></div><div><br></div><div><br></div><div><br></div><div><br></div>