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.

Bug 232131 - Newly created WS on Tomcat doesn't work
Summary: Newly created WS on Tomcat doesn't work
Status: RESOLVED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: REST (show other bugs)
Version: 7.4
Hardware: PC Windows 7
: P2 normal (vote)
Assignee: Milan Kuchtiak
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2013-07-02 10:28 UTC by Stepan Zebra
Modified: 2013-07-02 15:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stepan Zebra 2013-07-02 10:28:33 UTC 
Product Version: NetBeans IDE Dev (Build 201307012300)
Java: 1.7.0_25; Java HotSpot(TM) 64-Bit Server VM 23.25-b01
Runtime: Java(TM) SE Runtime Environment 1.7.0_25-b13
System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)

related to issue 229898

When generating RESTful Web Service in Web application running on Tomcat with option "Use Jersey specific features", the generated result doesn't run. Problem seems to be invalid web.xml.

To reproduce, you can follow the first four paragraphs of
http://wiki.netbeans.org/TS_72_JavaEE_Sanity
only select Tomcat instead of Glassfish and additionally tick the "Use Jersey specific features" option during the WS generation (second paragraph of the TS).
Comment 1 Milan Kuchtiak 2013-07-02 10:47:01 UTC 
Caused by upgrading Jersey 1.x to Jersey 2.0. 
web.xml entries added by Netbeans are not valid (against Jersey 2.0)
Comment 2 Milan Kuchtiak 2013-07-02 15:31:16 UTC 
Fixed for Tomcat7 (JavaEE 6) project types. 
The Jersey config panel is hidden in (first) Rest Service wizard for non Jersey Java EE6 web project types.

See:
hg.netbeans.org/web-main/rev/90e13f698438

There are still some issue with web services in Java EE5 projects on Tomcat 6 (Java EE 5).

See the bug 231640.