Hot answers tagged

12

You're 2 years late to the party then. The Tridion Content Delivery Service (REST, ODATA) has been available since Tridion 2011 GA, and there are already quite a few sites being built exactly as you want to. Given Tridion's generic Content Model on the delivery tier, still expect to see "Content" as one of your data elements. As long as your templates in ...


9

Yes, there is. In the cd_link_conf.xml of the (Session-enabled) Content Service there is a OverrideDiscoveryService attribute. If you set that to true, the Content Service will switch back to old-style link resolving using the mappings defined in cd_link_conf.xml and if you don't define any mappings in there, you will get relative URLs. Unfortunately, the ...


5

This is how I implement this type of functionality, feel free to disagree with me: Request comes in for page /somepath/index Query to OData to get /Pages()?$filter=Url eq '%2Fsomepath%2Findex' Potentially use a $expand(PageContent) on that URL so that it brings the presentation content as well Load the PageContent, it's been escaped because Tridion cannot ...


4

DXA 1.2 is for sure tightly coupled to the SDLTridion2013sp1 provider and we haven't looked at supporting the REST provider or what that would entail. So I really can't say anymore than that, I don't know right now if it should/could work. Our current focus is the 1.3 release which adds SDL Web 8 support and for that we will introduce a SDLWeb8 provider for ...


3

In addition to Rick's correct answer... You can indeed use the OverrideDiscoveryService to get relative URLs. The default cd_link_conf.xml in the content, session and preview micro services contains the following comment which I found confusing. OverrideDiscoveryService - specifies whether OData discovery endpoint configuration should be overridden ...


3

You will have to change the Sdl.Web.Tridion project source code which will mean you will be breaking out of the DXA releases. I simply removed the SDLTridion2013sp1 reference from the Sdl.Web.Tridion project, added a reference to DD4T.Providers.Rest through nuget in that same project, then updated the DD4TFactoryCache.cs file to use DD4T.Providers.Rest ...


3

Given it seems that the question is Can we plugin a new or updated query model for the web content services? the short answer is no. As per the documentation - the ODATA implementation is a partial implementation of the OData protocol so it doesn't actually provide for the full flavour of ODATA in the existing version even. I think Nick encapsulates ...


2

Yes, there is a way to extend the Odata. Please check the referenced article: Odata Extension Please note, extension is possible to odata however after every upgrade you might have to revisit this extension so that it continues to work.


2

The RESTful API role should be installed on the machine(s) where you want to use the API, so where your Web Application resides (referred to as Presentation Server in SDL Web docs). Note that this is a thin client which does not do license checks; these are done in the CIS microservices. It is not wrong to install your Web App and the RESTful API role on ...


1

You could put a .Net WebService like WebApi 2 or ServiceStack in front of a Core Service app to get the Component XML. Also, note that the native CoreService xml methods do not expose the Component Metadata. As far as looking up items by name, OOTB Tridion has the internal Solr search engine - but I'd probably look @ persisting the Component Name, URI, and ...


Only top voted, non community-wiki answers of a minimum length are eligible