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.
The file type 'Java ME Client to Web Application' in the J2ME project, requires whole Java EE be installed. Consider make this filetype to available in the J2ME project if and only if Java EE is installed/active, otherwise hide it.
Thank you for filing the issue. Here, in JavaME department, we do not understand how can JavaME installation depend on JavaEE. From bug #203649 we see that jsr172 (WebServices/XML) is involved somehow, but it still gives us no clue. Our customers wants minimal NetBeans installation and this dependency is rather painful for us.
Note that there are two file templates, which requires JavaEE: Java ME Client to Web Application Java ME Web Service Client
Impl. for the present on branch meee_221836 in the repository - http://hg.netbeans.org/releases/
Created attachment 128523 [details] a proposed patch The patch adds a new module into enterprise cluster - web.mobilitybridge, it's module which owns just a layer, no dependencies on other module and web.kit depends on that. Petr, David, please look on it. I'm going to integrate it tomorrow if no objections.
Looks good to me, assuming there are no user-visible UI elements in case the Java ME functionality is not installed or enabled.
This will work but it does not look like a right solution IMO. Module web.mobilitybridge should not be part of EE cluster but should be in ME cluster and should be a type of module which gets loaded automatically when EE functionality is presented. Looking at NetBeans Module documentation the mobilitybridge module is "eager" module which gets enabled when web.kit and me.kit are both enabled.
(In reply to comment #6) > This will work but it does not look like a right solution IMO. Module > web.mobilitybridge should not be part of EE cluster but should be in ME cluster > and should be a type of module which gets loaded automatically when EE > functionality is presented. Looking at NetBeans Module documentation the > mobilitybridge module is "eager" module which gets enabled when web.kit and > me.kit are both enabled. Okay, we chose another solution which doesn't require any changes on J2EE side. http://hg.netbeans.org/core-main/rev/b3998d0360ed
Just to provide more details about what is the behavior now after the fix. Now the 'Java ME Client to Web Application' and 'Java ME Web Service Client' file types are made available in J2ME Project only if EE is installed and enabled at the same time. Otherwise they are hidden. This is not only the most correct solution technically, it also makes sense for the following usability reason - if we enabled the aforementioned file types in J2ME Project without having installed and enabled EE, the user would actually end up in dead end in the instantiating dialogs, because both of the file types require existing Web or EE projects to which they can refer.
Integrated into 'main-golden', will be available in build *201212080001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/b3998d0360ed User: Jiri Rechtacek <jrechtacek@netbeans.org> Log: #221836: Eliminate dependency on JavaEE
Integrated into 'main-golden', will be available in build *201212090001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/78d73d447d62 User: Jiri Rechtacek <jrechtacek@netbeans.org> Log: again #221836: Eliminate dependency on JavaEE