[AWPR-9] Error in proxying the request through liferay portlet Created: 06/Sep/10  Updated: 07/Oct/11  Resolved: 07/Oct/11

Status: Closed
Project: Alfresco Web script Portlet rivet
Component/s: None
Affects Version/s: 1.5.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: ffournel Assignee: Al El-Nattar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1d
Time Spent: Not Specified
Original Estimate: 1d
Environment: Alfresco-tomcat bundle CE 3.3g + Liferay 6-tomcat bundle CE GA3 + STAR 1.3.0 + AWPR webScript example 1.6.0


 Description   
I manage to install all the stuff to make my portlet works. But only "awprmyspaces" portlet works, not the other "whatsnew" webscript portlet (I don't know why).
Concerning the first one, All links are corrupted because they take as web server the liferay's instance one (localhost:9090) instead of the alfresco instance one (localhost:8080).
Liferay and alfresco running in parallel on their own tomcat instance on my local post.
All the portlet preferences are well configured according to http://wiki.rivetlogic.com/display/AWPr/Example+Web+scripts. portlet.xml of awpr.war portlet is well configured also.
All reference to alfresco server are set to localhost:8080. So why when I click, it still take into account the liferay web context (localhost:9090) instead of the alfresco running instance (localhost:8080). Moreover, because of that (I think), all icons are not displayed.

Thanks for your answer.

 Comments   
Comment by ffournel [ 06/Sep/10 ]
Problem seems to be reported at AWPR-6. But How can I download or edit content then ?
Comment by Al El-Nattar [ 08/Sep/10 ]
Hi Francois,

Download should work. We are simply proxying the Alfresco download URL to be a portal URL so that the client (i.e. your browser) wouldn't need to be aware of the Alfresco ticket.

Could you please explain in more detail what error you're getting? It would help if you posted the download and icon URLs you're referring to as a comment to this issue.

Thanks.
Comment by Al El-Nattar [ 07/Oct/11 ]
I'm closing this issue because I think it no longer applies. Please reopen if this is still an issue.

Thank you.
Generated at Sat Feb 10 05:46:02 GMT 2024 using Jira 8.1.3#801003-sha1:6b6f07cffadda9a0d6efe24639daed8ce94dcdd6.