Community
Participate
Working Groups
Steps to follow: 1.- Create a EAR with the default modules 2.- Open the Deployment Assembly of the EJB (Connector, WebProject, AppClient) 3.- Modify the Deploy Path field of the /ejbModule (/connectorModule, /WebContent, /appClientModule ) 4.- Click OK 5.- An exception is thrown 6.- Try to open the Deployment Assembly Page and a error dialog is shown (see image included) 7.- When the Deployment Assembly is displayed the Manifest Entries tab looks empty The changes included in this patch are: - Adding a 'Revert' and 'Apply' button the the Deployment Assembly window (both tabs). - Adding the verify() method to the modify() method, so that changing the deploy path causes validation to reset. - Adding checks to make sure the Manifest file exists before updating or reading it. - Disabling buttons in the Manifest Entries tab if the Manifest file exists. - The WorkbenchComponentImpl currently has caching issues with its defaultSourceRoot. This value is not being reset when resource mappings are removed.
Created attachment 173052 [details] patch for 3.2.1
Requesting PMC approval because of a new string, "Revert".
approved
approving (for next weeks build, not 7/1, as doesn't appear blocking). I've added "PII" to keywords, as I think that is our convention to help Babel or or other translators find changes that might need a new translation. (Well, they'll see the changes with their tools ... but, marking can help size before using the tools, or see the explanation of why needed, etc.).
doh, I just realized you had [NLS] in title ... so, never mind my comment about pii keyword ... I'm not sure what the best approach is ... but sounds like you already knew to flag it, so one way or the other is fine by me.
checked into head for wtp 3.2.1