[ http://jira.jboss.com/jira/browse/JBIDE-2233?page=comments#action_12413186 ] Max Rydahl Andersen commented on JBIDE-2233: -------------------------------------------- would it be enough to just have it as an eclipse facet which will add in this file and jars for a Dynamic Web Project? (e.g. like Dali/JPA works?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2233?page=all ] Snjezana Peco reassigned JBIDE-2233: ------------------------------------ Assignee: Snjezana Peco -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2233?page=all ] Max Rydahl Andersen updated JBIDE-2233: --------------------------------------- Fix Version/s: 3.0.alpha -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2233?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-2233: -------------------------------------- I have created the org.jboss.tools.portlet.feature feature, the org.jboss.tools.portlet.core and org.jboss.tools.portlet.ui plugins and committed them to the trunk/portlet. Attached is a document describing this feature as well as some proposals relating to JBoss Portlet. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2233?page=com.atlassian.jira.plu... ] Snjezana Peco updated JBIDE-2233: --------------------------------- Attachment: (was: JBossPortlet.zip) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2233?page=com.atlassian.jira.plu... ] Thomas Heute commented on JBIDE-2233: ------------------------------------- Snjezana, i tried to install the plugin, but i'm not very good at Eclipse stuff :) What i did: - Installed Eclipse Europe Winter - Copied: http://anonsvn.jboss.org/repos/jbosstools/trunk/portlet/ inside my eclipse installation I create a new: "Dynamic Web Project" and a new Target runtime based on JBoss AS 4.2. I don't see a dropdown for "Dynamic Web Module version" and don't see the portlet facets neither. Do you know what i might be missing ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2233?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-2233: -------------------------------------- Thomas, I would like you to say something... :) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2233?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-2233: -------------------------------------- Thomas, You have to use Eclipse Ganymede, not Eclipse Europe. The following is the link to download Webtools with all its prerequisites (Eclipse 3.4, EMF, XSD, GEF, DTP) http://download.eclipse.org/webtools/downloads/drops/R3.0/R-3.0-200806161... After installing Webtools, you need to do the following: - install JBoss Tools nightly build: http://download.jboss.org/jbosstools/builds/nightly/200807220811-nightly/... , - check out the portlet plugin from http://anonsvn.jboss.org/repos/jbosstools/trunk/portlet/ , - launch a new Eclipse configuration Be sure the portlet plugins to be included (check the Plugins tab of the Run Configuration dialog). This will start a new Eclipse application that will contain the Dynamic Web Project wizard (including the Portlet facet), New Portlet wizard... Another way is to install Eclipse 3.4, Webtools, JBoss Tools as described above and to add the portlet feature using the attached update site. The Portlet feature will be included in some of the next builds. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2233?page=com.atlassian.jira.plu... ] Thomas Heute commented on JBIDE-2233: ------------------------------------- Thanks ! This is really cool, and a very good start. Few comments: - 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. - 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 - For the method stubs, it's a bit buguy: doDispatch appears twice (i understand that it's because it's defined by Generic Portlet and Portlet, but we should filter) When you uncheck "inherited abstract class" then click on doHelp for example, it becomes grey (unselectable) - The last step "Create Portlet" should be made optional, because you can do it through the administration portlet. 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. Also is there a particular reason to include portal-common.jar ? If not i suggest that we remove it. Again, thanks a lot ! -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2233?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-2233: -------------------------------------- Thomas, I think I have done everything you suggested. Now I think I understand what you mean by this sentence: "The last step "Create Portlet" should be made optional, because you can do it through the administration portlet.". The attached screenshots show the last page of the wizard. If the user unchecks the "Create Portlet Instance" checkbox, JBoss Tools won't create the deployment elements in the default-object.xml and portlet-instances.xml files. The portlet definition in the portlet.xml file will always be created. The changes are committed to SVN. Do I need to create a new update site for you? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2233?page=com.atlassian.jira.plu... ] Thomas Heute commented on JBIDE-2233: ------------------------------------- I checked the latest, this is great ! About the modes, you can forget it. In theory you can add modes specific to a portal. But those are very barely used. Adding that in the GUI would probably confuse most of the users. I think we can close that task. The other task was about Seam portlet. Before doing that task, it would be better to have plain JSF support, because that's what we will support in production and also because it's a step forward the Seam support. Configuration gets tricky The task is here: https://jira.jboss.org/jira/browse/JBIDE-2574 -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-2233?page=com.atlassian.jira.plu... ] Snjezana Peco updated JBIDE-2233: --------------------------------- Fix Version/s: 3.0.0.alpha (was: 3.0.0.beta1) Labels: (was: new_and_noteworthy) -- 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