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 183916 - [69cat] Cannot run App Client project
Summary: [69cat] Cannot run App Client project
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: App Client (show other bugs)
Version: 6.x
Hardware: PC Mac OS X
: P2 normal (vote)
Assignee: Tomas Mysik
URL:
Keywords:
: 184763 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-04-12 14:15 UTC by Martin Schovanek
Modified: 2010-04-27 06:43 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Sample project (63.45 KB, application/octet-stream)
2010-04-13 06:56 UTC, Martin Schovanek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schovanek 2010-04-12 14:15:26 UTC
#201004120251, jdk1.6, Java EE 6, GF v3

to reproduce:
-------------
1) have a EAR project with a Session bean and App Client
2) run the project

ERROR: the build script cycling, see the output:
pre-init:
init-private:
init-userdir:
init-user:
init-project:
do-init:
post-init:
init-check:
init:
deps-jar:
deps-j2ee-archive:
EnterpriseApplication27-app-client.init:
EnterpriseApplication27-ejb.init:
EnterpriseApplication27-app-client.init:
EnterpriseApplication27-ejb.init:
EnterpriseApplication27-app-client.init:
....
Comment 1 David Konecny 2010-04-12 23:00:15 UTC
Regardless of what I try I cannot reproduce. Please attach your project and reopen. Thx.
Comment 2 Martin Schovanek 2010-04-13 06:56:59 UTC
Created attachment 97136 [details]
Sample project
Comment 3 David Konecny 2010-04-13 18:51:51 UTC
The problem is in your project setup: AppClient project has EJB project on its classpath and EJB project has AppClient project on its classpath. I can see how that happened: when you were creating Remote Interface for your EJB you selected in wizard to create EJB's remote interface in AppClient project. That does not make much sense - you want to place remote interface into a project (most likely Java class library) which then can be used by both EJB module (to implement the EJB) and AppClient module (to lookup EJB in runtime; and compile against in development time).

The UI for remote interface destination should be improved and not list projects which would create cyclic dependency.

As user error I do not think this is P1 anymore (and beta stopper). Up to QA to decide and change though. Thanks.
Comment 4 Martin Schovanek 2010-04-14 13:05:16 UTC
Changing the priority to P2.
Comment 5 David Konecny 2010-04-20 20:13:16 UTC
This should be simple to fix. Could you have a look Tomas please.
Comment 6 Tomas Mysik 2010-04-23 07:46:14 UTC
I would probably display all the project (as it is now) but would not allow to continue with error saying "Cyclic project dependency would be created.". This is IMHO better because user knows what would be wrong, otherwise it's not possible to find out why the project is not listed in the combo box (or, at least for me it would be impossible :).

Any objections?
Comment 7 Vince Kraemer 2010-04-26 18:05:27 UTC
it looks like bug 184763 is a dup of this issue.
Comment 8 Petr Jiricka 2010-04-26 19:48:10 UTC
*** Bug 184763 has been marked as a duplicate of this bug. ***
Comment 9 Quality Engineering 2010-04-27 04:25:23 UTC
Integrated into 'main-golden', will be available in build *201004270201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/
User: 
Log:
Comment 10 Tomas Mysik 2010-04-27 06:43:07 UTC
Fixed, please verify. Thanks.
http://hg.netbeans.org/web-main/rev/5cb7b53212ad