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'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"><<a href="mailto:jer@printstacktrace.org">jer@printstacktrace.org</a>></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't currently include the portlet.xml description. I think it'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'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'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'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 "My forge portlet" --short-title ForgePortlet --keywords "demo,forge,portlet"</div></blockquote><div><br></div><div>Might make it clearer for command to be called "new-portlet" instead of "add"</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 "/home.xhtml"</div><div> $ portlet add-param --portlet helloportlet --name javax.portlet.faces.defaultViewId.edit --value "/edit.xhtml"</div>
<div> $ portlet add-param --portlet helloportlet --name javax.portlet.faces.defaultViewId.help --value "/help.xhtml"</div></blockquote><div><br></div><div>Could be nice to have the "new-portlet" command automatically create these parameters with the default values you specify above, as without them a portlet won'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'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 "/home.html"</div><div><div>$ portlet set-edit-id --portlet helloportlet --view "/edit.html"</div>
</div><div><div>$ portlet set-help-id --portlet helloportlet --view "/help.html"</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><?xml version="1.0" encoding="UTF-8" standalone="no"?></div>
<div><portlet-app xmlns="<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>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a>" version="2.0" xsi:schemaLocation="<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>"></div>
<div> <portlet></div><div> <portlet-name>helloportlet</portlet-name></div><div> <portlet-class>javax.portlet.faces.GenericFacesPortlet</portlet-class></div><div> <supports></div>
<div> <mime-type>text/html</mime-type></div><div> <portlet-mode>EDIT</portlet-mode></div><div> <portlet-mode>HELP</portlet-mode></div><div> <portlet-mode>VIEW</portlet-mode></div>
<div> </supports></div><div> <portlet-info></div><div> <title>My forge portlet</title></div><div> <short-title>ForgePortlet</short-title></div><div> <keywords>demo,forge,portlet</keywords></div>
<div> </portlet-info></div><div> <init-param></div><div> <name>javax.portlet.faces.defaultViewId.view</name></div><div> <value>/home.xhtml</value></div><div> </init-param></div>
<div> <init-param></div><div> <name>javax.portlet.faces.defaultViewId.edit</name></div><div> <value>/edit.xhtml</value></div><div> </init-param></div><div> <init-param></div>
<div> <name>javax.portlet.faces.defaultViewId.help</name></div><div> <value>/help.xhtml</value></div><div> </init-param></div><div> </portlet></div><div></portlet-app></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>