I have a query which is generated out of a claim made by a peer in the shadow of ATG 10.1.2 CRS implementation.
The claim is that for the left navigation/faceted search/narrowing down implementation in CRS , Assembler APIs are being used to fetch the result instead of presentation API. I could not find a documentation or ref where I can test this. Cant check in my machine. I am no ATG god.
Is this true ? If so , are we looking ahead to the deprecation/extinction of the presentation APIs?
Can we do everything with Assember APIs only ?
Can some of the stuff that was done by the presentation API be done by Assembler API ? this can help me in one of my migration projects.
Mayank, that does not make sense. Internally NavigationCartridgeHandler and RefinementMenuHandler use the presentation API to get data from Endeca.
Presentation API allows you to get data out of Endeca where as the Assembler API is the controller framework for you frontend app. (think of it like it JDBC and spring). If you are writing a (custom) CartridgeHandler that has to get data from Endeca you will have to use presentation API.
Voila!! Thats kewl.
But has Oracle provided Assember APIs for everything we were doing using presentation API. For instance we have left faceted narrow down that I used to populate using presentation API. Now I found we can do this by creating a cartridge in ex mgr and retrive the result
I got some more confusion - what is Assembler API 2.1 and now we have Assembler and Assembler Dependencies . Are we not using Assembler APIs anymore?
Was this spring framework is part of Endeca Assembler API 2.x? Or it is just Endeca Assembler 3.x that comes with tools and framework?
There is one more scenario that I got recently where client told us to replace all presentation API with assembler API but they are using all the latest Endeca installations. How do you see this request?