Hi <span style>Jérémie,</span><div><font color="#222222" face="arial, sans-serif"><br></font></div><div><font color="#222222" face="arial, sans-serif">Thanks for putting an initial portal plugin together.  It was something on my list for the months ahead, but you beat me to it! ;-)</font></div>
<div><font color="#222222" face="arial, sans-serif"><br></font></div><div><font color="#222222" face="arial, sans-serif">I&#39;ve responded in line to your questions.</font></div><div><font color="#222222" face="arial, sans-serif"><br>
</font></div><div><font color="#222222" face="arial, sans-serif">Regards</font></div><div><font color="#222222" face="arial, sans-serif">Ken<br></font><br><div class="gmail_quote">On Sun, Apr 1, 2012 at 3:00 PM, Jérémie <span dir="ltr">&lt;<a href="mailto:jer@printstacktrace.org">jer@printstacktrace.org</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Forge Team!<div><br></div><div>I would like to create a plugin to manage javaee portlets.</div><div>A first commit is available here <a href="http://goo.gl/OKgsG" target="_blank">http://goo.gl/OKgsG</a> . </div>
<div><br>
</div><div>Before going further and create a Forge Jira ticket  I would appreciate your opinion.</div><div> - Do you think core/javaee-api and core /javaee-impl  is a right place or I need to create an other project?</div>
</blockquote><div><br></div><div>I think this is the correct place, though Lincoln would have the final say on that ;-)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div> - The JBoss Shrinkwrap project doesn&#39;t currently include the portlet.xml description. I think it&#39;s interesting to do that. (I can create an other Jira ticket)</div></blockquote><div><br></div><div>By all means go ahead and create the jira and do the work.  It would be quite straight forward to complete.  I myself did the JSF ones last week, and was planning on getting to portal descriptors over the coming weeks.  It&#39;s just a case of adding the necessary xsd files, making sure the generation process worked, and writing some tests to verify it.  If you have any questions about it drop by #jbosstesting on irc and speak with Andrew (ALR) who leads the project.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div> - The quickstart option  would be interesting to push the generated code in a GateIn instance (not implemented yet).</div>
</blockquote><div><br></div><div>You could certainly do a deploy of the portlet to GateIn, or any other portal, but I think it makes sense for that to be a separate concern from creating a portlet and it&#39;s descriptors.  That is how a lot of the other plugins work, and also because the deployment would be specific to GateIn, and it would be messy to have a plugin that deals with descriptor generation and deploying to different portal containers.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> - Command names and options are correct?</div><div>Thanks for your comments.</div><div><br></div><div>For now here&#39;s what you can do: </div><div> $ portlet setup</div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> $ portlet add --named helloportlet --title &quot;My forge portlet&quot; --short-title ForgePortlet --keywords &quot;demo,forge,portlet&quot;</div></blockquote><div><br></div><div>Might make it clearer for command to be called &quot;new-portlet&quot; instead of &quot;add&quot;</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> $ portlet add-param --portlet helloportlet --name javax.portlet.faces.defaultViewId.view --value &quot;/home.xhtml&quot;</div><div> $ portlet add-param --portlet helloportlet --name javax.portlet.faces.defaultViewId.edit --value &quot;/edit.xhtml&quot;</div>

<div> $ portlet add-param --portlet helloportlet --name javax.portlet.faces.defaultViewId.help --value &quot;/help.xhtml&quot;</div></blockquote><div><br></div><div>Could be nice to have the &quot;new-portlet&quot; command automatically create these parameters with the default values you specify above, as without them a portlet won&#39;t deploy successfully.  Just as you have with the default portlet modes that are defined.</div>
<div> </div><div>It would also be nice to have aliased add-param versions for specifically adding a view, edit and help viewId.  It&#39;s pretty onerous to force someone to remember the exact syntax of javax.portlet.faces.defaultViewId.* every time they want to add or modify what viewId each of those portlet modes points at.</div>
<div><br></div><div>So you could have something like:</div><div>$ portlet set-view-id --portlet helloportlet --view &quot;/home.html&quot;</div><div><div>$ portlet set-edit-id --portlet helloportlet --view &quot;/edit.html&quot;</div>
</div><div><div>$ portlet set-help-id --portlet helloportlet --view &quot;/help.html&quot;</div></div><div><br></div><div>and then internally it actually calls add-param with the addition of the appropriate param name.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div><div>And the result is :
</div><div>src/main/webapp/WEB-INF/portlet.xml</div><div>-----------------------------------------------------</div><div><div><div>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&gt;</div>

<div>&lt;portlet-app xmlns=&quot;<a href="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" target="_blank">http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd</a>&quot; xmlns:xsi=&quot;<a href="http://www.w3.org/2001/XMLSchema-instance" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a>&quot; version=&quot;2.0&quot; xsi:schemaLocation=&quot;<a href="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" target="_blank">http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd</a>&quot;&gt;</div>

<div>  &lt;portlet&gt;</div><div>    &lt;portlet-name&gt;helloportlet&lt;/portlet-name&gt;</div><div>    &lt;portlet-class&gt;javax.portlet.faces.GenericFacesPortlet&lt;/portlet-class&gt;</div><div>    &lt;supports&gt;</div>

<div>      &lt;mime-type&gt;text/html&lt;/mime-type&gt;</div><div>      &lt;portlet-mode&gt;EDIT&lt;/portlet-mode&gt;</div><div>      &lt;portlet-mode&gt;HELP&lt;/portlet-mode&gt;</div><div>      &lt;portlet-mode&gt;VIEW&lt;/portlet-mode&gt;</div>

<div>    &lt;/supports&gt;</div><div>    &lt;portlet-info&gt;</div><div>      &lt;title&gt;My forge portlet&lt;/title&gt;</div><div>      &lt;short-title&gt;ForgePortlet&lt;/short-title&gt;</div><div>      &lt;keywords&gt;demo,forge,portlet&lt;/keywords&gt;</div>

<div>    &lt;/portlet-info&gt;</div><div>    &lt;init-param&gt;</div><div>      &lt;name&gt;javax.portlet.faces.defaultViewId.view&lt;/name&gt;</div><div>      &lt;value&gt;/home.xhtml&lt;/value&gt;</div><div>    &lt;/init-param&gt;</div>

<div>    &lt;init-param&gt;</div><div>      &lt;name&gt;javax.portlet.faces.defaultViewId.edit&lt;/name&gt;</div><div>      &lt;value&gt;/edit.xhtml&lt;/value&gt;</div><div>    &lt;/init-param&gt;</div><div>    &lt;init-param&gt;</div>

<div>      &lt;name&gt;javax.portlet.faces.defaultViewId.help&lt;/name&gt;</div><div>      &lt;value&gt;/help.xhtml&lt;/value&gt;</div><div>    &lt;/init-param&gt;</div><div>  &lt;/portlet&gt;</div><div>&lt;/portlet-app&gt;</div>

</div><div><br></div></div><div><br></div><div>Regads,</div><div>Jérémie.</div>
<br>_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br></blockquote></div><br></div>