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 55264 - Error verifying ejb app
Summary: Error verifying ejb app
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: _ ludo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-21 01:14 UTC by markreynolds
Modified: 2005-09-29 17:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Sample Project (180.33 KB, application/octet-stream)
2005-02-21 11:01 UTC, markreynolds
Details

Note You need to log in before you can comment on or make changes to this bug.
Description markreynolds 2005-02-21 01:14:28 UTC
When I run a verify on an ejb app I created with
Netbeans 4.1 I receive the following message.
+++++++
JDO72351: This error (All key fields of the bean
corresponding to the generated class
pkg.DepartmentBean978639062_JDOState must be
present in the key class
pkg.DepartmentBean978639062_JDOState$Oid.
Add the following key fields to the generated key
class: generatedPKField) should not occur.  Please
contact support and file a bug.
+++++++

I running on Windows XP SP2, PostgreSql, Sun App
Server 8.1

Please advise

Mark
Comment 1 _ ludo 2005-02-21 01:29:20 UTC
it would be great if you could attached the zip file for this project.
Comment 2 markreynolds 2005-02-21 11:01:42 UTC
Created attachment 20431 [details]
Sample Project
Comment 3 Petr Jiricka 2005-02-21 13:43:20 UTC
Also, which build of NB 4.1 are you using, please?
Comment 4 markreynolds 2005-02-21 14:47:13 UTC
I'm running Netbeans 4.1 EA 2 Build 200501180000.
Comment 5 _ ludo 2005-03-17 23:09:52 UTC
Could you  check for primary key information - if it is properly captured for
the postgress db.  This can probably be done with a jdbc program or by looking
at the dbschema file in the IDE. 
Or best, if you could attach the dbschema file, we would go faster.
Thanks,
Comment 6 _ ludo 2005-03-18 19:32:36 UTC
waiting for more info.
Comment 7 gustavoorsi 2005-06-28 18:38:19 UTC
Hi, i have an Enterprise Application which is made up of two modules: An ejb 
Module and a web Moudle.
In my ejb module i have severals Entity beans and some Stateless session beans 
acting like a facede. 
My problem comes when i call an ejb located in the ejb module from a servlet 
of my web module. 
Ok, this is what i do, 
first i make the entity bean and then a session facede, 
second i make the servlet and then press right click on the servlet a 
select "Enterprise resouserses -> Call enterprise bean" and chose my session 
facede bean.
So on its everything ok (or i supouse) but when i try to verify my web module 
(right click on my web module -> Verifiy Project) i have this problem:

Status: Error
Test Description: Could not verify successfully
Result: java.lang.RuntimeException: Error: Unresolved <ejb-link>: e-
commerce_EJB.jar#SignOnBean




Details:
java.lang.RuntimeException: Error: Unresolved <ejb-link>: e-
commerce_EJB.jar#SignOnBean

	at com.sun.enterprise.deployment.util.EjbBundleValidator.accept
(EjbBundleValidator.java:158)

	at com.sun.enterprise.deployment.WebBundleDescriptor.visit
(WebBundleDescriptor.java:1106)

	at com.sun.enterprise.deployment.Application.visit
(Application.java:1346)

	at com.sun.enterprise.deployment.Application.visit
(Application.java:1316)

	at com.sun.enterprise.tools.verifier.VerificationHandler.verifyArchive
(VerificationHandler.java:72)

	at com.sun.enterprise.tools.verifier.Verifier.verify(Verifier.java:75)

	at com.sun.enterprise.tools.verifier.Verifier.main(Verifier.java:53)


Comment 8 Vince Kraemer 2005-09-21 20:49:29 UTC
gustavoorsi needs to run the verifier on the EAR project, not the webapp.
Comment 9 _ ludo 2005-09-29 17:37:31 UTC
So this is a user error: the verifier is emitting the correct message when
verifyin htis standalone web app.
When you verify the entire J2EE project, then the verifier is happy.
It means that as a standalone web app, this web app is not j2ee compatible
(cannot resolved <ejb-link>) without extra ejb module , and this is the correct
status.