Community
Participate
Working Groups
When a J2EE module exists within a project, it has a name and id that's fairly simple, e.g. "PublishTestWeb". When the same module is exported out and reimported as a binary module within the EAR, its name and id change to "lib/PublishTestEAR/EarContent/PublishTestWeb.jar". While this seems like a simple difference, it causes two problems: 1) Users will see ugly names like "lib/PublishTestEAR/EarContent/PublishTestWeb.jar" in the add/remove module wizard and Servers view. 2) If a user has a module deployed to the server, and then switches to or from binary mode, the app will be missing on the server. They will need to remove the old application and add the new one back to be able to run it. I've tracked this back to J2EEDeployableFactory.createModuleDelegates(), but I don't know enough about it to understand the difference between binary and regular modules.
Jason assigning this to you
Just found out that getContextRoot() also returns this full lib/xyz string instead of the correct context root. People are unlikely to do Run on Server for binary web modules, but this would cause an invalid URL in the browser.
mass update to remove target for all those targeted to 1.5.3 that were "normal" severity and "priority 3" (on the surface those dont' seem serious enough to fix in a maintenance release). If I have made an error pleasae reset target and set priority appropriately.
Closing old bugs.
