Bug 245284 - Use of Model Transaction in non plug-in eclipse applications
Summary: Use of Model Transaction in non plug-in eclipse applications
Status: RESOLVED WONTFIX
Alias: None
Product: EMF Services
Classification: Modeling
Component: Transaction (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement
Target Milestone: ---   Edit
Assignee: Boris Gruschko CLA
QA Contact:
URL:
Whiteboard: Broader Community
Keywords: plan
Depends on: 167972 201947
Blocks:
  Show dependency tree
 
Reported: 2008-08-26 13:31 EDT by Chessman K. F Correa CLA
Modified: 2021-02-27 07:14 EST (History)
3 users (show)

See Also:

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 Chessman K. F Correa CLA 2008-08-26 13:31:32 EDT 
I am trying to use the Transaction component but not as an eclipse plug-in. Therefore, there is no Plug-in id. Due to that, when I try to create a transactionalEditingDomain, a null point exception occurs. It would be very good and very useful if Model Transaction could be used in non plug-in software.
Comment 1 Christian Damus CLA 2008-08-26 13:48:18 EDT 
The transaction API was designed to serve Eclipse-based editors of EMF models.  I'll need help if this is to change.  It also depends on the Validation Framework component being free of Eclipse platform (bug 167972)
Comment 2 Christian Damus CLA 2008-11-24 09:52:56 EST 
Cleaning up after the milestones were all deranged.
Comment 3 Pierre-Charles David CLA 2021-02-27 07:14:54 EST 
Given the limited resources available to work on EMF Services, it is more realistic to admit that it will never get implmented.
Feel free to reopen (with a patch and/or a proposal to fund the work needed) if you feel strongly about this.