seems to work fine You're right that you cannot combine these two. Instagram's API has a limited number of endpoints and their functionality is often narrow. To achieve what you're looking for you'll need to call the endpoint you're calling and filter them yourself (or call the tag endpoint and filter by user). This may prove to be prohibitive if the overlap is small and you're unwilling to make a large number of calls to the API.
Does that help In a WCF service hosted in IIS, I'm trying to set up multiple endpoints. One for SOAP and one for SOAP12. Per the MSDN documentation, I've edited Web.config like: , The problem was the service name:
Instagram user likes endpoint only returning public photos
this one helps. JAXBElement is here because you have custom type. If you point nillable=true you get the same. As you already understood you need to do your request and response simple elements, so JAXBElement wrapper won't be needed. ANd it's good practice to put real data model in one xsd and its wrappers like request and response element in another. In that case you can change the representation of your data model with different wrappers without changing data model itself.
No adapter for endpoint; Is your endpoint annotated with @Endpoint, or does it implement a supported interface like Mess