[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2233) Ability to create a new "Portlet" project

[Snjezana Peco (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12422258#action_12422258 ] 

Snjezana Peco commented on JBIDE-2233:
--------------------------------------

Thomas,

> There is too much restrictions on the Web Module version and portlet version (for example you can do a portlet 1.0 with a web-app 2.5. The thing is that if you use JBoss Portal 2.6 you will need to have a portlet 1.0 spec file.

I suppose that you have used Portlet Project 1.0 preset that appears when selecting Web Module version 2.3.
I will fix that issue. In the meantime, if you want to do a portlet 1.0 with a web module 2.4/2.5, you can choose Web Module version 2.4/2.5 then add portlet facet 1.0 (or 2.0) using the "Modify..." button.

> Portlet modes are not necessarily limited to View Edit and Mode, but for the first iteration that's fine since there is no real cases using other modes 

Are there a fixed number of modes or do I need to use an editable combo?

> doDispatch appears twice (i understand that it's because it's defined by Generic Portlet and Portlet, but we should filter)

I added it by mistake. Will fix it now.

> When you uncheck "inherited abstract class" then click on doHelp for example, it becomes grey (unselectable) 

That behavior is inherited from Webtools. I will check.

>  The last step "Create Portlet" should be made optional, because you can do it through the administration portlet. 

I am not sure if I understand this. The Create Portlet wizard is a separate wizard that a user can (but doesn't have to) call.

> For the -object.xml files, there is one file created per portlet. A common scenario is to put them all in the same file usually called default-object.xml. But that's not a big deal, both works fine. 

I will do it as you suggested.

> Also is there a particular reason to include portal-common.jar ? If not i suggest that we remove it. 

There is no any particular reason for that. I have seen the portal-common and portlet-api libs in the Helloworld portlet. If the portlet can be compiled without it, I will remove it. In my opinion, this isn't so important because these libraries aren't deployed.

Thank you for your suggestions.

> Ability to create a new "Portlet" project
> -----------------------------------------
>
>                 Key: JBIDE-2233
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2233
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: Portal
>            Reporter: Thomas Heute
>            Assignee: Snjezana Peco
>             Fix For: 3.0.0.beta1
>
>         Attachments: JBossPortlet.zip, org.jboss.tools.portlet.updatesite.zip
>
>
> A portlet application is a standard application with an additional file:
> WEB-INF/portlet.xml
> Two versions of the portlet specification exist at the moment, we can simply focus on the second one.
> The schema for the first version of the portlet specification is available at:
> http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd
> The new version should be available at the following address anytime soon:
> http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira