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.
While trying to fix issue 82450 there was incompatible change introduced. There is also inconsistency between EJB, Web and AppClient APIs on this level. It should be done in all projects in the same way and also synchronized in mevenide project types.
This is not going to be fixed in 5.5. Not really big issue, decreasing to P3.
not sure I understand the current state of fix for #82450. are you saying that the api is changed incopatibly and you are not planning to address that in 5.5 timeframe?
yet another incompatible change, this time in web apis http://jira.codehaus.org/browse/MEVENIDE-458. Anyone attempting to write a web framework provider can get hurt here.
*** Issue 88370 has been marked as a duplicate of this issue. ***
Andrei removed EjbJar.getMetadataUnit already, but I am not sure about WebModule.getJavaSources(). Andrei can you comment please (you are working on some cleanup?).
Nobody seems to need WebModule.getJavaSources(), and I would very much like to remove that method. Returning FileObject-s is probably not enough anyway, the method should return something like SourceGroup-s, but those are too much tied to the projects API. However, the reporter of MEVENIDE-458 seems to need it. So I'm not sure. Perhaps best would be to introduce a createJavaSource() method in WebAppMetadata (which can be obtained from getMetadataModel), returning a JavaSource on which the caller can call getClasspathInfo() to get a classpath to find resources on. Opinions anyone?
Is this issue still active? Or can we close it?
Not planned for 7.0
I am closing this issue as fixed, if there is still any unaddressed items, please reopen. thanks