[ https://jira.jboss.org/jira/browse/JBIDE-3335?page=com.atlassian.jira.plu... ] Dirk Pitt commented on JBIDE-3335: ---------------------------------- As I mentioned in previous message, that completely kill the component reuse.... For new application I create the Seam project and use the newly created EjbModule for the new functionality... But then how can I use the my previously created components, please don't tell me to copy them under the source tree... Component reuse must be a concern for every project or not? -- 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-3335?page=com.atlassian.jira.plu... ] Dirk Pitt commented on JBIDE-3335: ---------------------------------- Well for example, if it is an another Seam EJBModule that is created in another Seam project, JBoss Tools content assist is not able findout that modules session beans and include them into the content assist. if I only include the jar to the WAR... That is the only reason I am using the JBoss Tools and Seam, to have the content assist in facelet and java pages, I don't want to search every time the code to find out what was the Name annotation in my previous project... And this functionality you mentioned 'state the war as its seam "parent', I can realise this via the wiazrd in EJB Module, I can do it manually by editing org.jboss.tools.seam.core.prefs but not via wizards... -- 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-3335?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-3335: -------------------------------------------- http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194317#... states he could set the parent project but haven't heard which version he actually used...he still had problems though so something is missing here. -- 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-3335?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-3335: -------------------------------------------- Why not just attach it to this bug ? or at least link them together. No reason to have 2 bugs open for the same thing. -- 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-3335?page=com.atlassian.jira.plu... ] Alexey Kazakov reassigned JBIDE-3335: ------------------------------------- Assignee: Alexey Kazakov (was: Denis Golovin) -- 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-3335?page=com.atlassian.jira.plu... ] Alexey Kazakov reassigned JBIDE-3335: ------------------------------------- Assignee: Viacheslav Kabanovich (was: Alexey Kazakov) -- 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-3335?page=com.atlassian.jira.plu... ] Alexey Kazakov commented on JBIDE-3335: --------------------------------------- Sorry, it was my fault. I forgot to set java ee dependency on new EJB Module for parent seam war project. So the only unresolved issue for proper work with multi EJB modules is #3. I will create new issue in jira for it. -- 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-3335?page=com.atlassian.jira.plu... ] Mehmet Salgar commented on JBIDE-3335: -------------------------------------- Is this fix allready in the Jboss Nightly? If it is what correct way of proceeding with the solution.. First to create the ejb projects and include them as references to the EAR project then on the WAR project to install the Seam Facet and Seam Settings... Can you please tell me the order of activities? -- 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-3335?page=com.atlassian.jira.plu... ] Alexey Kazakov commented on JBIDE-3335: --------------------------------------- Now when user is add Seam Facet to an EJB prroject we look for all referencing projects. If we can find any Seam War project which are referenced to the project directly or if the project and Seam War projects are modules of the same EAR then we use found WAR as Seam parent project. For example: 1. Create Seam Web Project (EAR deployment type). So we have: - seamtest-ear (EAR project) - seamtest-ejb (EJB module of seamtest-ear. Seam project) - seamtest (WAR module of seamtest-ear. Seam project.) 2. We want to add some new EJB module to seamtest-ear. And make it Seam project. - Create EJB project. (for exampe "newejbmodule") Make it a module of seamtest-ear. - Project Settings -> Project Facets -> Add Seam facet (EAR deployment type is set by default for this project) 3. During adding Seam Facet we figured out that newejbmodule project is a module of seamtest-ear. And seamtest-ear contains one Seam War module - seamtest. We set this seamtest as parent seam war project for newejbmodule. 4. newejbmodule Properties -> j2EE module dependencies -> Select libs from EAR to be included to class path. 5. seamtest Properties -> J2EE module dependencies -> Select newejbmodule jar to be included to class path. So if a project already has some references (via parent EAR) to any Seam War project then we use this found seam war as a parent for the new Seam module. So user should first create War Seam project then add it to EAR. Then create EJB project and add it to the same EAR. After that our seam facet will be able to find parent Seam project. If you want to create new Seam War project for existend EJB Seam projects then you have to Remove/Re-add Seam Facets to old EJB Seam project to use new War as parent Seam War project for old Seam EJBs. I see one improvement for Seam facet install delegate. If user try to add seam facet in New EJB Project Wizard instead of adding seam facet to an existed project we don't use "Add project to an EAR" field for searching War Seam project. User have to create project (and add it to an EAR) first and add Seam Facet after that. I will create an issue to fix it. -- 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