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 136408 - Cannot enable TX support from the Edit web service Attributes dialog in an EJB project
Summary: Cannot enable TX support from the Edit web service Attributes dialog in an EJ...
Status: RESOLVED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: WSIT (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-03 18:39 UTC by pvarghese
Modified: 2008-06-20 17:26 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot of the wsit dialog (19.57 KB, image/gif)
2008-06-03 18:41 UTC, pvarghese
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pvarghese 2008-06-03 18:39:10 UTC
Cannot enable TX support from the Edit web service Attributes dialog in an EJB project

1. Create an EJB module project and configure it to be exposed as a web-service. 
2. Right click on the project class in the "Web Services" folder under the EJB project and select "Edit web service
Attributes" option.
3. In the dialog box, trying to set a value for the "Transaction" attribute for any of the web-service operations fails
as the dialog to select the options is disabled. 

Attached a screen shot of the dialog with the disabled Transaction attribute dropdown.
Comment 1 pvarghese 2008-06-03 18:41:29 UTC
Created attachment 62331 [details]
screenshot of the wsit dialog
Comment 2 Martin Grebac 2008-06-18 16:11:06 UTC
This is as designed - for controlling TX setup in EJB project you can use the regular JavaEE Tx annotations.
Comment 3 Murali Pottlapelli 2008-06-19 16:29:30 UTC
This is definitely an usability issue.

User using NB/open-esb tools can build WS in web application, EJB application or Composite application (CASA).

To add quality of services transaction, security, MTOM, Reliable Message Delivery etc. to web services, user selects
action "Edit Web Service Attributes" from context menu on WS/ SOAP EP, it brings up "Quality of Services"/"WS Policy
Attachment" (inconsistent names for window, CASA uses later name, why it is not "Quality of Services"?)

Consistent behavior is required from all the thee paths.

Stating that for EJB WS user needs to use JavaEE Tx annotations, is this not introducing inconsistent behavior?

Can a user configure all the QOS features available on "WSIT" window from JavaEE annotation? If not,  is this  not
another configuration?

When a "Quality" is grayed out, are we conveying this feature is not available vs can not be configured from here?  What
is the grayed out QOS feature means? Is this consistent with NB gui standards?
Comment 4 Martin Grebac 2008-06-20 17:26:18 UTC
Based on discussion, Tx were enabled.