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.
Summary: | Need event notification to track model transaction state | ||
---|---|---|---|
Product: | xml | Reporter: | Alexey Yarmolenko <alexeyyarmolenko> |
Component: | XAM | Assignee: | Svata Dedic <sdedic> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | slunegov |
Priority: | P3 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | 160903 | ||
Bug Blocks: | 132316 |
Description
Alexey Yarmolenko
2008-04-29 12:11:32 UTC
I need more concrete use-cases to understand what is needed here. Can you not extend xam to do this at the BPEL side? Sam, we'd like this one to be implemented in 7.0. XAM is an abstract model and you write domain specific models on top of it. You could override the start and end transaction on your side and provide what is needed. There are at least three known domain models (axi, schema, wsdl) based on XAM and all of them have a rich UI set that gets updated on various events. So far we have not seen any performance issue as a result of this. Have you done proper homework as to why you've performance issues in the first place? Sam, yes we did. Reopen the issue. Needs some discussion. Can you attach the analysis of performance issue? Also I said that your domain model could overwrite start and end transaction and fire events. Have you tried that? There are many difficulties with improving XAM model because it has a public status. So only small changes can be done. The XAM already provide a kind of notification about transactions' ending. I mean an abstract method AbstractModel.transactionCompleted(). But it isn't convenient for using because a model's owner has to implement its own notification mechanism (XXXEvent class, XXXListener class, addXXXListener(), removeXXXListener(), ...). It is impossible to reuse PropertyChangeEvent, which is already used by XAM, for example, for notification about model's status changes. It is impossible to do out of the AbstractModel class because of access restrictions. My suggestion is to send a new PropertyChangeEvent directly from the AbstractModel class. The only changes to XAM API is adding the new TRANSACTION_COMPLETE_PROPERTY string constant. Initially it was suggested to notify about entering and leaving transaction. But it looks like only leaving is required. Moreover the end of transaction can be successful or not (endTransaciton() or rollbackTransaction()). The client's side code is interested only in getting notification about successful end of transaction. So it is suggested to introduce only one new event. It is better in order to minimize XAM API changes. Nikita, what is the progress with this issue ? No demand, no response, no progress in past 6 years. |