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.
based on yesterday's discussion I found out that the issue was really due to my impatience. I pressed [Ctrl][Shift]-I (fix imports) too quickly, after adding the @Path annotation, so that a wrong import clause were added by netbeans and REST plugin was not given a chance to update project config to include jersey libraries. The solution in such case is to remove the wrong import and wait till the REST plugin catches up. My personal opinion is that such kind of functionality (adding libraries to a project) should be fully under user's control. I.e. I would prefer to have a checkbox available for REST plugin, so that people can explicitely say if they want REST support or not.
It is now. If not, then it is a bug...
v.
I just talked with Paul this morning at J1. The way we automatically add ServletAdaptor is no longer recommended way to use latest Jersey release. In addition, developer should be able to specify their own implementation. So basically, we need explicit UI for turning on/off Jersey REST support, possibly with ability to specify the actually class name instead of the default ServletAdaptor. I am reopen this as bug, and will add Paul to comment in details on the various use-cases.
I agree that implicitly modifying the web.xml can cause much confusion. It needs to be an explicit solution especially since developers may want to modify the servlet pattern. Perhaps if NB detects such annotations and there is no appropriate servlet configured then NB could as the user if they would like to include one.
From: Daniel Silva <ddso.01@gmail.com> Date: May 21, 2008 7:19:04 AM PDT To: nbusers@netbeans.org Subject: [nbusers] RESTful Reply-To: nbusers@netbeans.org Hello, Netbeans keeps adding RESTful support for my web applications without my conscious asking. What setting should I put to stop this? It's really annoying. -- Abraços, Daniel Silva
With the fix to http://www.netbeans.org/issues/show_bug.cgi?id=134750, this issue is no longer a p1. I am downgrading this to a p2.
Changing this into an enhancement.