|
|
|
[
Permlink
| « Hide
]
Mike Aizatsky - 29 Jan 07 18:55
You should make them dependent of each other
LOL, no way. They're packaged into the same EAR and don't have anything else in common. Making them dependent just to resolve links doesn't make any sense. Also, last time I checked, cyclic webapp-dependencies were not allowed.
Dmitry, Mike, the proposed solution really doesn't work: IDEA does not allow cyclic dependencies between Web modules which would be necessary to support the described case.
The linking between the webapps really is something IDEA could (and should) know from the fact that the modules are supposed to be packaged into the same application module. Please re-open or explicitly state that you don't intend to implement this. If you don't consider implementing this, at least turn off the highlighting for paths that go below the root of the web-application. I do not want to see this yellow highlighting that I can not reasonably turn off in these cases for paths which I know that they are perfectly valid.
Please provide the corresponding fragment from your application.xml
<application> ... <module id="reporting-gui.iml"> <web> <web-uri>reporting.war</web-uri> <context-root>ecs/reporting</context-root> </web> </module> <module id="ecs-monitoring.iml"> <web> <web-uri>monitoring.war</web-uri> <context-root>ecs/monitoring</context-root> </web> </module> </application> index.jsp from module ecs-monitoring: Links: <a href="../reporting">eCS-Reporting</a> | ... Also the completion after ../ shows filesystem-based suggestions, which is incorrect for the deployed application: |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||