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 116700 - [60cat] EntityManager.persist() does not throw exception
Summary: [60cat] EntityManager.persist() does not throw exception
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-25 15:55 UTC by vanob
Modified: 2007-09-26 15:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
3 Projects. Enterprise, EJB and Web (30.53 KB, application/x-tar)
2007-09-25 15:58 UTC, vanob
Details

Note You need to log in before you can comment on or make changes to this bug.
Description vanob 2007-09-25 15:55:09 UTC
[ BUILD # : 200709250000 ]
[ JDK VERSION : 1.6.0_02 ]

1. Install NetBeans with glassfish
2. Unpack the content of the attached file to some folder.
3. Open Enterprise Application Project from that folder.
4. Debug the project
5. From the browser enter Product1 in the textfield and press add.
6. Set breakpoint in the file test.ProductManagerBean on the line 27 at the first line of the method createProduct
7. In the browser press Add again.
As you can see em.persist does not throw exception but glassfish output tab lists the stacktrace.

I don't know if it's a bug in glassfish or in glassfish plugin but some exception should definitely be thrown from the method so I can catch it. I tested this scenario with Hibernate Entity Manager but got the same situation.
Comment 1 vanob 2007-09-25 15:58:54 UTC
Created attachment 49478 [details]
3 Projects. Enterprise, EJB and Web
Comment 2 Vince Kraemer 2007-09-26 15:13:56 UTC
The plugin takes care of getting the bits to the server...  You should probably open a bug at
https://glassfish.dev.java.net/servlets/ProjectIssues.

I am marking this issue Invalid, since it is outside of the IDE and the plugin...  I am not saying that what you
reported isn't a bug... I am saying this is a bug that this team cannot apply code changes to resolve.