This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Run valid enterprise application(with session bean in ejb and servers set) - no index.jsp page is displayed in browser,there's error page instead ("http://localhost:8080/com.mycompany_mavenproject1-ear_ear_1.0-SNAPSHOT") If I manually change URL to "http://localhost:8080/mavenproject1-web/", index.jsp is correctly displayed.
Changing the default owner to issues@javaee.
I can not reproduce - in fact, for me the browser is not opened at all. Do you have exact steps to reproduce?
Here is what I found out. When I deploy a Maven EAR project, for some reason the TargetModuleID returned by GlassFish does not contain any children (corresponding to the web module included in the EAR). Because of this, method org.netbeans.modules.j2ee.deployment.impl.projects.DeploymentTargetImpl#findWebUrl returns null. For Ant-based EAR projects, the returned TargetModuleID contains the correct children, as well as for Maven-based EAR projects targeting WebLogic. Passing to Vince.
PetrJ: which gf are you deploying to?
I am trying with v3 final.
Vince, any update on this issue? Is it really a problem on GF side? Or does something else needs to happen on Maven EAR projest side? Thx.
*** Bug 188944 has been marked as a duplicate of this bug. ***
I should be doing something else but this issue was real pain for me and seeing that Vince in on holiday for next week or two I decided to fix it - 5a173d79a765
Thanks, though it looks like the current fix is a heuristic which may or may not work, right? E.g. if the artefact name is com.thisgreatcompanyiworkfor.app1_1.0-dev, will it do the right thing?
(In reply to comment #9) > Thanks, though it looks like the current fix is a heuristic which may or may > not work, right? E.g. if the artefact name is > com.thisgreatcompanyiworkfor.app1_1.0-dev, will it do the right thing? It will work but in this case it will be slower because unrelated application will be returned by the query. The algorithm does initial query and then compare results against full module name so everything will work correctly (or at least that's how I understood - Vince can confirm). So for com.thisgreatcompanyiworkfor.app1_1.0-dev the query would be *.thisgreatcompanyiworkfor.* which could return for example * com.thisgreatcompanyiworkfor.app1_1.0-dev * com.thisgreatcompanyiworkfor.foo.1 * com.thisgreatcompanyiworkfor.bar.2 but later they would be ignored because another test for full module name is done.