[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4320) ESB Projects does not respect WTP module dependency rules

[ https://jira.jboss.org/jira/browse/JBIDE-4320?page=com.atlassian.jira.plu... ] Denny Xu commented on JBIDE-4320: --------------------------------- Just looked through the patch, there are some problem in it: 1. we cannot use PersistentProperty of project to persist any property, this would prevent sharing projects between different workspaces. 2. we cannot change the resource mappings to below: <wb-resource deploy-path="/" source-path="/esbcontent"/> <wb-resource deploy-path="/" source-path="/build/classes"/> the folder "/build/classes" is java project output folder and the name and the path are changeable, so if the user change the project default output folder, how do you handle it, just test this case, the patch doesn't work. I don't think the old resource mapping has any problem, it's just like how WTP Web projects use resource mappings, the reason why WTP does so is because of handling the case that the default java project output folder is changed after the project was created. the issue is that the ESB module factory doesn't act like WTP J2EE module, I just refactored the ESB module factory base on a WTP module delegate: J2EEFlexProjDeployable, so currently, the ESB module factory follows the standard way of using Virtual component. anyway, the new ESB module delegate also extends from JBTProjectModuleDelegate and doesn't overwrite any method except the "members()". so the new ESB module factory can work with old ESB project and also support any resource mappings that you expect. -- 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