Home » Eclipse Projects » DTP » Ecore - oda driver : Is there an offical release ?
| | | | | | |
| Re: EMF Ecore - oda driver [message #698628 is a reply to message #689973] |
Tue, 19 July 2011 20:31   |
Eclipse User |
|
|
|
Originally posted by: John E. Conlon
Just upgraded to Indigo, and wish to replace the old incubator driver
with the new Ecore ODA driver.
Saw the presentation slides, but can't find where to update or download.
What project is it in and what update repo can I get the driver and
it's UI from?
thanks,
John
On 06/28/2011 11:47 AM, Ed Merks wrote:
> Linda,
>
> I know the folks who funded its development are using it and are happy
> with it but given it's been poorly documented and poorly advertised,
> there's been no other feedback and hence no requests for enhancements.
> It is fully functional so I don't think a lot more needs to be done...
>
>
> On 27/06/2011 4:44 PM, Linda Chan wrote:
>> Thanks Ed.
>>
>> Any insight re: feedback on the emf.oda.ecore driver thus far? And are
>> there further work/enhancements planned for the driver?
>>
>> Linda
|
|
|
| Re: EMF Ecore - oda driver [message #698629 is a reply to message #698628] |
Tue, 19 July 2011 20:46 |
| Eclipse User |
|
|
|
Originally posted by: John E. Conlon
While I found it, in the update site, does it have any web presence
within a Modeling project?
It's in the Eclipse Modeling Project Update Site -
http://www.eclipse.org/modeling/updates/
On 07/19/2011 03:31 PM, John E. Conlon wrote:
> Just upgraded to Indigo, and wish to replace the old incubator driver
> with the new Ecore ODA driver.
>
> Saw the presentation slides, but can't find where to update or download.
> What project is it in and what update repo can I get the driver and it's
> UI from?
>
>
> thanks,
>
> John
>
> On 06/28/2011 11:47 AM, Ed Merks wrote:
>> Linda,
>>
>> I know the folks who funded its development are using it and are happy
>> with it but given it's been poorly documented and poorly advertised,
>> there's been no other feedback and hence no requests for enhancements.
>> It is fully functional so I don't think a lot more needs to be done...
>>
>>
>> On 27/06/2011 4:44 PM, Linda Chan wrote:
>>> Thanks Ed.
>>>
>>> Any insight re: feedback on the emf.oda.ecore driver thus far? And are
>>> there further work/enhancements planned for the driver?
>>>
>>> Linda
>
|
|
| |
| Re: EMF Ecore - oda driver [message #702748 is a reply to message #702418] |
Tue, 26 July 2011 18:45 |
| Eclipse User |
|
|
|
Originally posted by: John E. Conlon
Hi Alex,
Yes I have encountered this bug and have viewed it in the debugger. Is
there a bugzilla opened on this?
thanks for the warning,
John
On 07/26/2011 05:44 AM, Alex Tugarev wrote:
> The EMF ODA driver has no category. So uncheck "Group items by category"
> on the "Install new Software" page.
> Be forewarned: There is still a bug in connection with OCL dependencies.
> The field delegateDomain used in
> org.eclipse.ocl.ecore.delegate.AbstractOCLDelegateFactory.getDelegateDomain(EPackage)
> is null, though an OCLDelegateDomain object is expected.
> This bug prevents you finishing the New Data Set Wizard. So the ODA
> driver is not useable, unless you patch the method mentioned above
> yourself.
>
>
|
|
|
| Re: EMF Ecore - oda driver [message #702758 is a reply to message #702748] |
Tue, 26 July 2011 18:55 |
 Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Guys,<br>
<br>
I was asking Kenn Hussey and Ed Willink about this. Kenn commented
that it must be a regression because it used to be fine and wondered
if it could be fixed in a maintenance release. Ed mentioned that:<br>
<blockquote>I'm sure it's fixable, but all tests pass, so there must
be some use case we don't understand.<br>
<br>
I've no idea what a New Data Set wizard is, so it would help if
someone who does identifies a failing<br>
stack trace and ensures that some unit test animates it.<br>
</blockquote>
So please do open an OCL bugzilla with a test case (preferably with
minimal dependencies) that manifests the problem.<br>
<br>
<br>
On 26/07/2011 11:45 AM, John E. Conlon wrote:
<blockquote cite="mid:j0n1cr$pn9$1@news.eclipse.org" type="cite">Hi
Alex,
<br>
<br>
Yes I have encountered this bug and have viewed it in the
debugger. Is there a bugzilla opened on this?
<br>
<br>
thanks for the warning,
<br>
John
<br>
<br>
<br>
On 07/26/2011 05:44 AM, Alex Tugarev wrote:
<br>
<blockquote type="cite">The EMF ODA driver has no category. So
uncheck "Group items by category"
<br>
on the "Install new Software" page.
<br>
Be forewarned: There is still a bug in connection with OCL
dependencies.
<br>
The field delegateDomain used in
<br>
org.eclipse.ocl.ecore.delegate.AbstractOCLDelegateFactory.getDelegateDomain(EPackage)
<br>
is null, though an OCLDelegateDomain object is expected.
<br>
This bug prevents you finishing the New Data Set Wizard. So the
ODA
<br>
driver is not useable, unless you patch the method mentioned
above
<br>
yourself.
<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
</body>
</html>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: EMF Ecore - oda driver [message #702862 is a reply to message #702758] |
Tue, 26 July 2011 22:27 |
| Eclipse User |
|
|
|
Originally posted by: John E. Conlon
Hi Ed,
See inline comments...
On 07/26/2011 01:55 PM, Ed Merks wrote:
> Guys,
>
> I was asking Kenn Hussey and Ed Willink about this. Kenn commented that
> it must be a regression because it used to be fine and wondered if it
> could be fixed in a maintenance release. Ed mentioned that:
>
> I'm sure it's fixable, but all tests pass, so there must be some use
> case we don't understand.
>
> I've no idea what a New Data Set wizard is, so it would help if
> someone who does identifies a failing
> stack trace and ensures that some unit test animates it.
>
If the following looks ok, I will open a bugzilla...
-------------------------------------------------------
This problem occurs when the user tries to create a BIRT Report using
the new EMF ECore ODA Driver.
1. First the user would create a BIRT ODA DataSource using the new 'EMF
ECore Data Source' Pointing it to a model instance in the workspace.
This seems to work ok - at least testing the connection says so.
2. Next a BIRT report requires DataSets to hold a subset of the data
extracted from the datasource, so creating a DataSet from the EMF ECore
Data Source is a requirement. This is implemented by the
EcoreDataSetWizardPage in the org.eclipse.emf.oda.ecore.ui plugin.
After defining the context, the query and the type the wizard page
validates each.
The PROBLEM (AFAIK) occurs when an ePackage returns a null from:
EAnnotation eAnnotation = ePackage.getEAnnotation(EcorePackage.eNS_URI);
inside the DelegateEPackageAdapter (see debug stack trace below)
As it works it's way back up the stack this will eventually throw a NPE,
which will be caught but not be correctly converted to a message so the
user will have no indication that an error occurred, accept that the
EcoreDataSetWizardPage will never validate the data and no finish key
will be enabled.
------------------------------
Thread [main] (Suspended (breakpoint at line 99 in
DelegateEPackageAdapter))
DelegateEPackageAdapter.getDelegateDomains() line: 99
DelegateEPackageAdapter.getDelegateDomain(String) line: 89
OCLQueryDelegateFactory$Global(AbstractOCLDelegateFactory).getDelegateDomain(EPackage) line: 53
OCLQueryDelegateFactory$Global(OCLQueryDelegateFactory).createQueryDelegate(EClassifier, Map<String,EClassifier>, String) line: 61
OCLQueryDelegateFactory$Global.createQueryDelegate(EClassifier,
Map<String,EClassifier>, String) line: 82
EcoreDataSetWizardPage.validateData() line: 1015
EcoreDataSetWizardPage.promptForResultTypeSelection() line: 591
EcoreDataSetWizardPage$11.widgetSelected(SelectionEvent) line: 622
TypedListener.handleEvent(Event) line: 240
EventTable.sendEvent(Event) line: 84
Button(Widget).sendEvent(Event) line: 1258
Display.runDeferredEvents() line: 3588
Display.readAndDispatch() line: 3209
WizardDialog(Window).runEventLoop(Shell) line: 825
WizardDialog(Window).open() line: 801
NewDataSetAction.createNewDataSet() line: 193
NewDataSetAction.run() line: 181
NewDataSetAction(Action).runWithEvent(Event) line: 498
ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584
ActionContributionItem.access$2(ActionContributionItem, Event, boolean)
line: 501
ActionContributionItem$5.handleEvent(Event) line: 411
EventTable.sendEvent(Event) line: 84
MenuItem(Widget).sendEvent(Event) line: 1258
Display.runDeferredEvents() line: 3588
Display.readAndDispatch() line: 3209
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2696
Workbench.runUI() line: 2660
Workbench.access$4(Workbench) line: 2494
Workbench$7.run() line: 674
Realm.runWithDefault(Realm, Runnable) line: 332
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 667
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
IDEApplication.start(IApplicationContext) line: 123
EclipseAppHandle.run(Object) line: 196
EclipseAppLauncher.runApplication(Object) line: 110
EclipseAppLauncher.start(Object) line: 79
EclipseStarter.run(Object) line: 344
EclipseStarter.run(String[], Runnable) line: 179
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not
available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 57
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
Method.invoke(Object, Object...) line: 616
Main.invokeFramework(String[], URL[]) line: 622
Main.basicRun(String[]) line: 577
Main.run(String[]) line: 1410
Main.main(String[]) line: 1386
> So please do open an OCL bugzilla with a test case (preferably with
> minimal dependencies) that manifests the problem.
>
>
> On 26/07/2011 11:45 AM, John E. Conlon wrote:
>> Hi Alex,
>>
>> Yes I have encountered this bug and have viewed it in the debugger.
>> Is there a bugzilla opened on this?
>>
>> thanks for the warning,
>> John
>>
>>
>> On 07/26/2011 05:44 AM, Alex Tugarev wrote:
>>> The EMF ODA driver has no category. So uncheck "Group items by category"
>>> on the "Install new Software" page.
>>> Be forewarned: There is still a bug in connection with OCL dependencies.
>>> The field delegateDomain used in
>>> org.eclipse.ocl.ecore.delegate.AbstractOCLDelegateFactory.getDelegateDomain(EPackage)
>>>
>>> is null, though an OCLDelegateDomain object is expected.
>>> This bug prevents you finishing the New Data Set Wizard. So the ODA
>>> driver is not useable, unless you patch the method mentioned above
>>> yourself.
>>>
>>>
>>
|
|
|
| Re: EMF Ecore - oda driver [message #702918 is a reply to message #702862] |
Wed, 27 July 2011 00:00 |
Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
John,
It sounds okay to me. It's certainly a good way to start the
conversation, which can then continue in the bugzilla itself.
On 26/07/2011 3:27 PM, John E. Conlon wrote:
> Hi Ed,
>
> See inline comments...
>
>
> On 07/26/2011 01:55 PM, Ed Merks wrote:
>> Guys,
>>
>> I was asking Kenn Hussey and Ed Willink about this. Kenn commented that
>> it must be a regression because it used to be fine and wondered if it
>> could be fixed in a maintenance release. Ed mentioned that:
>>
>> I'm sure it's fixable, but all tests pass, so there must be some use
>> case we don't understand.
>
> >
> > I've no idea what a New Data Set wizard is, so it would help if
> > someone who does identifies a failing
> > stack trace and ensures that some unit test animates it.
> >
>
>
> If the following looks ok, I will open a bugzilla...
> -------------------------------------------------------
>
> This problem occurs when the user tries to create a BIRT Report using
> the new EMF ECore ODA Driver.
>
> 1. First the user would create a BIRT ODA DataSource using the new
> 'EMF ECore Data Source' Pointing it to a model instance in the
> workspace.
> This seems to work ok - at least testing the connection says so.
>
> 2. Next a BIRT report requires DataSets to hold a subset of the data
> extracted from the datasource, so creating a DataSet from the EMF
> ECore Data Source is a requirement. This is implemented by the
> EcoreDataSetWizardPage in the org.eclipse.emf.oda.ecore.ui plugin.
>
> After defining the context, the query and the type the wizard page
> validates each.
>
> The PROBLEM (AFAIK) occurs when an ePackage returns a null from:
>
> EAnnotation eAnnotation = ePackage.getEAnnotation(EcorePackage.eNS_URI);
> inside the DelegateEPackageAdapter (see debug stack trace below)
>
> As it works it's way back up the stack this will eventually throw a
> NPE, which will be caught but not be correctly converted to a message
> so the user will have no indication that an error occurred, accept
> that the EcoreDataSetWizardPage will never validate the data and no
> finish key will be enabled.
>
>
> ------------------------------
> Thread [main] (Suspended (breakpoint at line 99 in
> DelegateEPackageAdapter))
> DelegateEPackageAdapter.getDelegateDomains() line: 99
> DelegateEPackageAdapter.getDelegateDomain(String) line: 89
> OCLQueryDelegateFactory$Global(AbstractOCLDelegateFactory).getDelegateDomain(EPackage)
> line: 53
> OCLQueryDelegateFactory$Global(OCLQueryDelegateFactory).createQueryDelegate(EClassifier,
> Map<String,EClassifier>, String) line: 61
> OCLQueryDelegateFactory$Global.createQueryDelegate(EClassifier,
> Map<String,EClassifier>, String) line: 82
> EcoreDataSetWizardPage.validateData() line: 1015
> EcoreDataSetWizardPage.promptForResultTypeSelection() line: 591
> EcoreDataSetWizardPage$11.widgetSelected(SelectionEvent) line: 622
> TypedListener.handleEvent(Event) line: 240
> EventTable.sendEvent(Event) line: 84
> Button(Widget).sendEvent(Event) line: 1258
> Display.runDeferredEvents() line: 3588
> Display.readAndDispatch() line: 3209
> WizardDialog(Window).runEventLoop(Shell) line: 825
> WizardDialog(Window).open() line: 801
> NewDataSetAction.createNewDataSet() line: 193
> NewDataSetAction.run() line: 181
> NewDataSetAction(Action).runWithEvent(Event) line: 498
> ActionContributionItem.handleWidgetSelection(Event, boolean) line:
> 584
> ActionContributionItem.access$2(ActionContributionItem, Event,
> boolean) line: 501
> ActionContributionItem$5.handleEvent(Event) line: 411
> EventTable.sendEvent(Event) line: 84
> MenuItem(Widget).sendEvent(Event) line: 1258
> Display.runDeferredEvents() line: 3588
> Display.readAndDispatch() line: 3209
> Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2696
> Workbench.runUI() line: 2660
> Workbench.access$4(Workbench) line: 2494
> Workbench$7.run() line: 674
> Realm.runWithDefault(Realm, Runnable) line: 332
> Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 667
> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
> IDEApplication.start(IApplicationContext) line: 123
> EclipseAppHandle.run(Object) line: 196
> EclipseAppLauncher.runApplication(Object) line: 110
> EclipseAppLauncher.start(Object) line: 79
> EclipseStarter.run(Object) line: 344
> EclipseStarter.run(String[], Runnable) line: 179
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line:
> not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 57
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 616
> Main.invokeFramework(String[], URL[]) line: 622
> Main.basicRun(String[]) line: 577
> Main.run(String[]) line: 1410
> Main.main(String[]) line: 1386
>
>
>
>
>
>
>
>> So please do open an OCL bugzilla with a test case (preferably with
>> minimal dependencies) that manifests the problem.
>>
>>
>> On 26/07/2011 11:45 AM, John E. Conlon wrote:
>>> Hi Alex,
>>>
>>> Yes I have encountered this bug and have viewed it in the debugger.
>>> Is there a bugzilla opened on this?
>>>
>>> thanks for the warning,
>>> John
>>>
>>>
>>> On 07/26/2011 05:44 AM, Alex Tugarev wrote:
>>>> The EMF ODA driver has no category. So uncheck "Group items by
>>>> category"
>>>> on the "Install new Software" page.
>>>> Be forewarned: There is still a bug in connection with OCL
>>>> dependencies.
>>>> The field delegateDomain used in
>>>> org.eclipse.ocl.ecore.delegate.AbstractOCLDelegateFactory.getDelegateDomain(EPackage)
>>>>
>>>>
>>>> is null, though an OCLDelegateDomain object is expected.
>>>> This bug prevents you finishing the New Data Set Wizard. So the ODA
>>>> driver is not useable, unless you patch the method mentioned above
>>>> yourself.
>>>>
>>>>
>>>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: EMF Ecore - oda driver [message #703475 is a reply to message #702918] |
Wed, 27 July 2011 15:52 |
| Eclipse User |
|
|
|
Originally posted by: John E. Conlon
Filed Bugzilla 353227
https://bugs.eclipse.org/bugs/show_bug.cgi?id=353227
On 07/26/2011 07:00 PM, Ed Merks wrote:
> John,
>
> It sounds okay to me. It's certainly a good way to start the
> conversation, which can then continue in the bugzilla itself.
>
>
> On 26/07/2011 3:27 PM, John E. Conlon wrote:
>> Hi Ed,
>>
>> See inline comments...
>>
>>
>> On 07/26/2011 01:55 PM, Ed Merks wrote:
>>> Guys,
>>>
>>> I was asking Kenn Hussey and Ed Willink about this. Kenn commented that
>>> it must be a regression because it used to be fine and wondered if it
>>> could be fixed in a maintenance release. Ed mentioned that:
>>>
>>> I'm sure it's fixable, but all tests pass, so there must be some use
>>> case we don't understand.
>>
>> >
>> > I've no idea what a New Data Set wizard is, so it would help if
>> > someone who does identifies a failing
>> > stack trace and ensures that some unit test animates it.
>> >
>>
>>
>> If the following looks ok, I will open a bugzilla...
>> -------------------------------------------------------
>>
>> This problem occurs when the user tries to create a BIRT Report using
>> the new EMF ECore ODA Driver.
>>
>> 1. First the user would create a BIRT ODA DataSource using the new
>> 'EMF ECore Data Source' Pointing it to a model instance in the workspace.
>> This seems to work ok - at least testing the connection says so.
>>
>> 2. Next a BIRT report requires DataSets to hold a subset of the data
>> extracted from the datasource, so creating a DataSet from the EMF
>> ECore Data Source is a requirement. This is implemented by the
>> EcoreDataSetWizardPage in the org.eclipse.emf.oda.ecore.ui plugin.
>>
>> After defining the context, the query and the type the wizard page
>> validates each.
>>
>> The PROBLEM (AFAIK) occurs when an ePackage returns a null from:
>>
>> EAnnotation eAnnotation = ePackage.getEAnnotation(EcorePackage.eNS_URI);
>> inside the DelegateEPackageAdapter (see debug stack trace below)
>>
>> As it works it's way back up the stack this will eventually throw a
>> NPE, which will be caught but not be correctly converted to a message
>> so the user will have no indication that an error occurred, accept
>> that the EcoreDataSetWizardPage will never validate the data and no
>> finish key will be enabled.
>>
>>
>> ------------------------------
>> Thread [main] (Suspended (breakpoint at line 99 in
>> DelegateEPackageAdapter))
>> DelegateEPackageAdapter.getDelegateDomains() line: 99
>> DelegateEPackageAdapter.getDelegateDomain(String) line: 89
>> OCLQueryDelegateFactory$Global(AbstractOCLDelegateFactory).getDelegateDomain(EPackage)
>> line: 53
>> OCLQueryDelegateFactory$Global(OCLQueryDelegateFactory).createQueryDelegate(EClassifier,
>> Map<String,EClassifier>, String) line: 61
>> OCLQueryDelegateFactory$Global.createQueryDelegate(EClassifier,
>> Map<String,EClassifier>, String) line: 82
>> EcoreDataSetWizardPage.validateData() line: 1015
>> EcoreDataSetWizardPage.promptForResultTypeSelection() line: 591
>> EcoreDataSetWizardPage$11.widgetSelected(SelectionEvent) line: 622
>> TypedListener.handleEvent(Event) line: 240
>> EventTable.sendEvent(Event) line: 84
>> Button(Widget).sendEvent(Event) line: 1258
>> Display.runDeferredEvents() line: 3588
>> Display.readAndDispatch() line: 3209
>> WizardDialog(Window).runEventLoop(Shell) line: 825
>> WizardDialog(Window).open() line: 801
>> NewDataSetAction.createNewDataSet() line: 193
>> NewDataSetAction.run() line: 181
>> NewDataSetAction(Action).runWithEvent(Event) line: 498
>> ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584
>> ActionContributionItem.access$2(ActionContributionItem, Event,
>> boolean) line: 501
>> ActionContributionItem$5.handleEvent(Event) line: 411
>> EventTable.sendEvent(Event) line: 84
>> MenuItem(Widget).sendEvent(Event) line: 1258
>> Display.runDeferredEvents() line: 3588
>> Display.readAndDispatch() line: 3209
>> Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2696
>> Workbench.runUI() line: 2660
>> Workbench.access$4(Workbench) line: 2494
>> Workbench$7.run() line: 674
>> Realm.runWithDefault(Realm, Runnable) line: 332
>> Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 667
>> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
>> IDEApplication.start(IApplicationContext) line: 123
>> EclipseAppHandle.run(Object) line: 196
>> EclipseAppLauncher.runApplication(Object) line: 110
>> EclipseAppLauncher.start(Object) line: 79
>> EclipseStarter.run(Object) line: 344
>> EclipseStarter.run(String[], Runnable) line: 179
>> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not
>> available [native method]
>> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 57
>> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
>> Method.invoke(Object, Object...) line: 616
>> Main.invokeFramework(String[], URL[]) line: 622
>> Main.basicRun(String[]) line: 577
>> Main.run(String[]) line: 1410
>> Main.main(String[]) line: 1386
>>
>>
>>
>>
>>
>>
>>
>>> So please do open an OCL bugzilla with a test case (preferably with
>>> minimal dependencies) that manifests the problem.
>>>
>>>
>>> On 26/07/2011 11:45 AM, John E. Conlon wrote:
>>>> Hi Alex,
>>>>
>>>> Yes I have encountered this bug and have viewed it in the debugger.
>>>> Is there a bugzilla opened on this?
>>>>
>>>> thanks for the warning,
>>>> John
>>>>
>>>>
>>>> On 07/26/2011 05:44 AM, Alex Tugarev wrote:
>>>>> The EMF ODA driver has no category. So uncheck "Group items by
>>>>> category"
>>>>> on the "Install new Software" page.
>>>>> Be forewarned: There is still a bug in connection with OCL
>>>>> dependencies.
>>>>> The field delegateDomain used in
>>>>> org.eclipse.ocl.ecore.delegate.AbstractOCLDelegateFactory.getDelegateDomain(EPackage)
>>>>>
>>>>>
>>>>> is null, though an OCLDelegateDomain object is expected.
>>>>> This bug prevents you finishing the New Data Set Wizard. So the ODA
>>>>> driver is not useable, unless you patch the method mentioned above
>>>>> yourself.
>>>>>
>>>>>
>>>>
>>
|
|
|
Goto Forum:
Current Time: Fri Apr 19 20:55:49 GMT 2024
Powered by FUDForum. Page generated in 0.04836 seconds |
] 
Search
Help
Register
Login
Home
