topic External Servlet for searchs [solved] in Alfresco Archive

External Servlet for searchs [solved]

anusk — Fri, 16 Jul 2010 11:07:00 GMT

Hola a todos!Hi all!I'm trying to do a servlet to access Alfresco through a specific URL. The idea is to redirect to the search results page.In the servlet I create an UIComponent of the type UISimpleSearch, an event and finally I add the searchContext to the event.Now the problem is that this only

Re: External Servlet for searchs [solved]

savic_prvoslav — Fri, 16 Jul 2010 14:40:02 GMT

Now the problem is that this only works if the user login in alfresco and then put the URL in the browser

this is normal alfresco does not allow to access if you are not logged in first.

so my advice is that you do next:
<servlet-name>externalAccess</servlet-name>
<servlet-class>org.alfresco.web.app.servlet.ExternalAccessServlet</servlet-class> check this inside web.xml this is servlet witch deals with /n/showDocDetails/${child.nodeRef} you get this and details dialog opens , nice. so why do not extend this servlet to post your search results.
if you are having problem with login part you can do :
loginbean.setusername("guets")
loginbean.login();

and if documents in guest homespace this would work.

Re: External Servlet for searchs [solved]

anusk — Mon, 19 Jul 2010 07:30:44 GMT

Hi savic!

Thanks for your post.
By the way, that is what I already did. I did an external servlet based in the one that provides alfresco. The login part I know is normal, I did another external servlet which leads you to an specific node in alfresco (and of course you have to login to access alfresco). The problem is when the user login, alfresco goes to company home space first!, then you refresh the browser and goes to the search results page. I don't know why alfresco goes first to company home space.
What I want is : you put the URL in the browser, alfresco login page appears, the user login, and alfresco shows you directly the page results.

Kind regards,
Ana

Re: External Servlet for searchs [solved]

anusk — Mon, 19 Jul 2010 08:52:02 GMT

I finally solved it.
The problem was the UIlocation was not initialized. After doing

 browseBean.updateUILocation(nodeRef);‍

it finally works!

Kind regards,
Ana