<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>liferay 7 Ext Module cannot add new portlet?</title>
  <link rel="self" href="https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=120547035" />
  <subtitle>liferay 7 Ext Module cannot add new portlet?</subtitle>
  <id>https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=120547035</id>
  <updated>2026-05-02T20:20:48Z</updated>
  <dc:date>2026-05-02T20:20:48Z</dc:date>
  <entry>
    <title>RE: RE: liferay 7 Ext Module cannot add new portlet?</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120546572" />
    <author>
      <name>Olaf Kock</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120546572</id>
    <updated>2021-01-14T15:50:33Z</updated>
    <published>2021-01-14T15:50:33Z</published>
    <summary type="html">&lt;p&gt;&amp;quot;and modify src codes to implement some functions&amp;quot;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;I'm wondering what you're implementing. Since everything is on OSGi
  now, there's often no more need to modify source in order to achieve a
  certain behavior.&lt;/p&gt;
&lt;p&gt;You might want to rephrase your question and let us know about your
  actual plan: What's the feature you're trying to implement this way?&lt;/p&gt;
&lt;p&gt;Solving &lt;a href="https://xyproblem.info/"&gt;X-Y-problems&lt;/a&gt; can be
  hard (and this sounds like one), even though the underlying problem
  might be easy.&lt;/p&gt;</summary>
    <dc:creator>Olaf Kock</dc:creator>
    <dc:date>2021-01-14T15:50:33Z</dc:date>
  </entry>
  <entry>
    <title>RE: RE: liferay 7 Ext Module cannot add new portlet?</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120548415" />
    <author>
      <name>sunny huang</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120548415</id>
    <updated>2021-01-14T14:02:38Z</updated>
    <published>2021-01-14T14:02:38Z</published>
    <summary type="html">&lt;p&gt;Yes , You are right. thank you for reply. At first, i want to rebuild
  document library web module and modify src codes to implement some funtions.&lt;/p&gt;
&lt;p&gt;But there are same errors like that.&lt;/p&gt;
&lt;p&gt;
  &lt;a
    href="https://liferay.dev/ask#/questions/development/liferay-npm-bundler-build-error"&gt;liferay-npm-bundler
    build error&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;So I tried to use EXT. It work well but cannot create new portlet I
  need. Just like you said, It 's not a good idea to implement my need.
  But I can't find a solution to the error in the thread above. Are
  there any good suggestions？&lt;/p&gt;</summary>
    <dc:creator>sunny huang</dc:creator>
    <dc:date>2021-01-14T14:02:38Z</dc:date>
  </entry>
  <entry>
    <title>RE: liferay 7 Ext Module cannot add new portlet?</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120545271" />
    <author>
      <name>Olaf Kock</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120545271</id>
    <updated>2021-01-12T08:34:55Z</updated>
    <published>2021-01-12T08:34:55Z</published>
    <summary type="html">&lt;p&gt;You should minimize the use of ext at all cost. If you &lt;em&gt;need&lt;/em&gt;
  to change some implementation: Most likely you just found the wrong
  solution for the underlying problem. In the few cases where you
  actually need to change the implementation (through ext): Go ahead,
  but minimize the size of the ext. Then add whatever you need on top,
  in regular modules.&lt;/p&gt;
&lt;p&gt;Your future self will thank you when they'll have to upgrade that
  code to the next version.&lt;/p&gt;
&lt;p&gt;And if you don't have to upgrade the code yourself: Assume those who
  will need to do it know where you live.&lt;/p&gt;
&lt;p&gt;Seriously: Ext can easily introduce a maintenance burden, which
  should be minimized at all cost. It's Liferay's business to change
  their implementation. If you interfere with that, you'll have to do
  the three-way-merges on every individual upgrade - worst case even on
  minor upgrades or, in case of DXP, from Fixpack to Fixpack. Don't go
  there if you don't absolutely have to.&lt;/p&gt;</summary>
    <dc:creator>Olaf Kock</dc:creator>
    <dc:date>2021-01-12T08:34:55Z</dc:date>
  </entry>
  <entry>
    <title>liferay 7 Ext Module cannot add new portlet?</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120547034" />
    <author>
      <name>sunny huang</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=120547034</id>
    <updated>2021-01-12T01:44:05Z</updated>
    <published>2021-01-12T01:44:05Z</published>
    <summary type="html">&lt;p&gt;HI,&lt;/p&gt;
&lt;p&gt;Is the development of new portlets not supported by ext module?&lt;/p&gt;
&lt;p&gt;The portlet created in the ext module cannot be displayed normally.
  Not found in the app.&lt;/p&gt;</summary>
    <dc:creator>sunny huang</dc:creator>
    <dc:date>2021-01-12T01:44:05Z</dc:date>
  </entry>
</feed>
