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 244428 - Message Driven Bean dropdown empty when no mappedName in MBean
Summary: Message Driven Bean dropdown empty when no mappedName in MBean
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: EJB (show other bugs)
Version: 8.0
Hardware: All All
: P2 normal (vote)
Assignee: Martin Fousek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-11 23:43 UTC by awgtek
Modified: 2014-07-09 02:47 UTC (History)
0 users

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 awgtek 2014-05-11 23:43:34 UTC 
Steps:

- Ensure no projects exist in Projects tab
- New Project, Java EE, Enterprise Application
- Using wizard, add New Message-Driven Bean to ejb project; set Server Destination from drop-down (e.g. "jms/dest").
- Create Servlet in war project
- In processRequest method do Alt-Insert, Send JMS Message...
- Select Message Driven Bean -- note nothing in drop-down (but see below)

Speculation on cause:

I had to add mappedName element to the MessageDriven annotation to get it to show. Evidently mappedName addition was removed from the "New Message-Driven Bean" wizard results, replaced by destinationLookup in activationConfig. So the "Send JMS Message" insert code popup should find beans based on the destinationLookup perhaps? Also noticed duplicates occurring in the dropdown when adding more MDBs without the mappedName.
Comment 1 Martin Fousek 2014-07-07 13:33:45 UTC 
(In reply to awgtek from comment #0)
> I had to add mappedName element to the MessageDriven annotation to get it to
> show. Evidently mappedName addition was removed from the "New Message-Driven
> Bean" wizard results, replaced by destinationLookup in activationConfig. So
> the "Send JMS Message" insert code popup should find beans based on the
> destinationLookup perhaps? Also noticed duplicates occurring in the dropdown
> when adding more MDBs without the mappedName.

You are right, it doesn't work due to redesign to destanationLookup in case of MDBs 2.0+. I have it almost resolved, just few details to tune...
Comment 2 Martin Fousek 2014-07-08 09:03:24 UTC 
There were few unimplemented parts but it should work now. Feel free to check it once it will be available in dev builds (automatic message should appear here).

Fixed in web-main #3905b1ebebbc.
Comment 3 Quality Engineering 2014-07-09 02:47:14 UTC 
Integrated into 'main-silver', will be available in build *201407090001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/3905b1ebebbc
User: Martin Fousek <marfous@netbeans.org>
Log: #244428 - Message Driven Bean dropdown empty when no mappedName in MBean