What is the "o" directory?What is the "o" directory?https://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1043356372024-03-29T10:57:16Z2024-03-29T10:57:16ZRE: What is the "o" directory?Yvonne Allenhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1043797442018-02-22T16:32:51Z2018-02-22T16:32:51Z<div class="quote-title">Olaf Kock:</div><blockquote><div class="quote-title">Yvonne Allen:</div><blockquote>Does that apply only to Liferay 7+? because I we are still on Liferay 6.2.</blockquote><br /><br />Indeed. The main reason for it to be required from version 7 on is that plugins are no longer deployed as webapplications. Webapplications can easily serve their own resources, while OSGi bundles can't, if we don't make this method available to them.</blockquote><br /><br />Thank you very much for your quick replies.Yvonne Allen2018-02-22T16:32:51ZRE: What is the "o" directory?Olaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1043522752018-02-22T07:30:28Z2018-02-22T07:30:28Z<div class="quote-title">Yvonne Allen:</div><blockquote>Does that apply only to Liferay 7+? because I we are still on Liferay 6.2.</blockquote><br /><br />Indeed. The main reason for it to be required from version 7 on is that plugins are no longer deployed as webapplications. Webapplications can easily serve their own resources, while OSGi bundles can't, if we don't make this method available to them.Olaf Kock2018-02-22T07:30:28ZRE: What is the "o" directory?Yvonne Allenhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1043463222018-02-22T01:25:51Z2018-02-22T01:25:51ZDoes that apply only to Liferay 7+? because I we are still on Liferay 6.2.Yvonne Allen2018-02-22T01:25:51ZRE: What is the "o" directory?Olaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1043388622018-02-21T22:35:31Z2018-02-21T22:35:31Z<div class="quote-title">Yvonne Allen:</div><blockquote>In many tutorials I look at, I am seeing developers refer to a "/o/" directory. What does this directory refer to in Liferay? </blockquote><br /><br />It's the prefix for any request dynamically handled by the OSGi runtime (that can't go through portlet URLs - e.g. no resource-, action- or render-URLs (that might include a page reference). The <a href="https://github.com/liferay/liferay-blade-samples/tree/master/liferay-workspace/extensions/servlet">blade servlet sample</a> is another place where it is quite obvious - it's just not a portletOlaf Kock2018-02-21T22:35:31ZWhat is the "o" directory?Yvonne Allenhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1043356362018-02-21T20:27:23Z2018-02-21T20:27:23ZIn many tutorials I look at, I am seeing developers refer to a "/o/" directory. What does this directory refer to in Liferay? I saw <br />David H Nebinger refer to it here in this <a href="https://web.liferay.com/community/forums/-/message_boards/message/104027439">forum post</a><br /><br />And it was also refered to here in this gist <a href="https://gist.github.com/mjbradford89/e0d2175e1742173530966827184f5a21">Angular 2 in Liferay 7</a><br />@Component({<br /> selector: 'location-conte