Re: [forge-dev] Questions about a new javaee portlet plugin

Hi Jérémie, Thanks for putting an initial portal plugin together. It was something on my list for the months ahead, but you beat me to it! ;-) I've responded in line to your questions. Regards Ken On Sun, Apr 1, 2012 at 3:00 PM, Jérémie <jer(a)printstacktrace.org&gt; wrote: I think this is the correct place, though Lincoln would have the final say on that ;-) 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. 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. $ portlet add --named helloportlet --title "My forge portlet" Might make it clearer for command to be called "new-portlet" instead of "add" 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. 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. So you could have something like: $ portlet set-view-id --portlet helloportlet --view "/home.html" $ portlet set-edit-id --portlet helloportlet --view "/edit.html" $ portlet set-help-id --portlet helloportlet --view "/help.html" and then internally it actually calls add-param with the addition of the appropriate param name.