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 192634 - Can't create remote EJB interface in same EJB project using New Session Bean wizard
Summary: Can't create remote EJB interface in same EJB project using New Session Bean ...
Status: RESOLVED INVALID
Alias: None
Product: javaee
Classification: Unclassified
Component: EJB (show other bugs)
Version: 7.0
Hardware: PC Linux
: P1 normal (vote)
Assignee: David Konecny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-29 12:26 UTC by eugene-71
Modified: 2011-04-06 06:54 UTC (History)
2 users (show)

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 eugene-71 2010-11-29 12:26:09 UTC 
When "Remote" option in "New Session Bean wizard" is checked, current project not present in combobox.

Error message displayed: "There is no suitable project available into which Remote interface could be stored. An open Ant based Java Class Library project is required."

In NetBeans 6.9.1 current project name present in combobox.
Comment 1 eugene-71 2010-11-29 12:27:50 UTC 
This bug affects NetBeans 7 beta.
Comment 2 catweasle 2010-12-12 14:11:57 UTC 
I would expect the current project to be ALWAYS IMPLICITLY present. 
The remote interface defines what THIS project what is exposed externally, no?
I guess this menu would allow you to add this interface additionally to another project, but I can not really tell as the HELP does not contain this feature yet (just has the remote option from NB 6).
Also: the error message does not wrap in the window, which could be problematic for ling errors.
Comment 3 catweasle 2010-12-12 15:09:02 UTC 
Hm, I see, this is meant to indicate, in case of a composite project, which of the composing projects projects exposes this interface.
I can confirm that this is a regression from 6.9.1 where this works (though not explained in the help there either).
Comment 4 Petr Jiricka 2011-01-04 15:54:19 UTC 
This change is intentional, see also issue 186332 for more background. The best practice is to use a separate "client jar", which is added to the classpath of the EJB module or (in case of EE 6) the Web module. The client jar should contain the remote interfaces plus any classes these interfaces depend on, and should be put on the classpath of the client application. The reason for using the client jar rather than putting the interfaces directly in the EE module is essentially to comply with the packaging requirements of the Java EE spec. So I think this report should be closed as invalid.

I agree this should be better explained in the documentation, cc'ing Ken as the doc writer.
Comment 5 David Konecny 2011-01-04 20:33:47 UTC 
Explained by Petr.
Comment 6 m44miri 2011-04-06 06:54:33 UTC 
In the Netbeans 7.0 RC1 at the Create time (ejb) see this error:
here is no suitable project available into which Remote interface could be stored. An open Ant based Java Class Library project is required.