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>     &quot;&quot;&quot;Handles REST operations for Customer /customer&quot;&quot;&quot;</div>
<div>     pass</div><div><br></div><div><div>class CustomerAddressRestService(Resource):</div><div>     &quot;&quot;&quot;Handles REST operations for Customer Address /customer/&lt;customerId&gt;/address&quot;&quot;&quot;</div>
<div>     pass</div></div><div><br></div><div>Instead I would need to have one common Resource that handles everything under &#39;/customer&#39;,</div><div>including the customer entity and customer address entity in one (and any other entity whose root is &#39;/customer&#39;).</div>
<div><br></div><div>That isn&#39;t a very good design...especially if you maybe have 50 different entities hooked up  under &#39;/customer&#39; (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>