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 250474 - Can't deploy REST web project example on Glassfish
Summary: Can't deploy REST web project example on Glassfish
Status: RESOLVED DUPLICATE of bug 233481
Alias: None
Product: webservices
Classification: Unclassified
Component: REST (show other bugs)
Version: 8.0.2
Hardware: PC Windows 8 x64
: P1 normal (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-17 19:56 UTC by david.chaves
Modified: 2015-02-20 15:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
complete project of the failed deployment and server log (45.83 KB, application/x-zip-compressed)
2015-02-17 19:56 UTC, david.chaves 		Details
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 david.chaves 2015-02-17 19:56:03 UTC 
Created attachment 152037 [details]
complete project of the failed deployment and server log

I'm using the following configuration:
-Windows 8.1 Pro x64
-Netbeans 8.0.2 up to date
-JDK 1.8
-Glassfish 4.1

Doing the following steps

1. Create table in local MySQL database.
2. Create new Java Web Project in Netbeans.
3. Create "Entity Classes from database" using the integrated MySQL JDBC driver (successfully created)
4. Create "REST web services from Entities" (successfully created)
5. Deploy Project for testing --- FAIL

And this error appears in the log (complete server log of the failed deployment it's inside the attached file):

"java.lang.RuntimeException: Invalid resource : gothere__pm"

I attach the server Log of the last failed deployment. I been trying to test it on different configurations using all the possible combinations:

-JDK 1.7
-Glassfish 4.0
-Netbeans 8.0.1

Also tested in a Mac OSX with clean installation without result. It's been two weeks that my team are trying to find some workaround which had force us to use Eclipse temporally.
Comment 1 Antonin Nebuzelsky 2015-02-20 15:41:59 UTC 

*** This bug has been marked as a duplicate of bug 233481 ***