Eclipse Community Forums: DTP » [ODA Ecore] URLs to identify models

Help

Home

Home » Eclipse Projects » DTP » [ODA Ecore] URLs to identify models

Show: Today's Messages :: Show Polls :: Message Navigator

[ODA Ecore] URLs to identify models [message #48396]

Thu, 07 August 2008 20:51

Eclipse User

Originally posted by: jconlon.apache.org

I have a use case where I would like to report on Ecore model instances
that reside on remote webservers.

When creating ODA Ecore DataSources, I see that models can be browsed
for (located) in the workspace and the file system ...

but could URLs be used to identify Ecore models that are located on web
servers (etc.) as well?

If not, is this a constraint based on EMF/Ecore limitations or the
present implementation of ODA Ecore?

cheers,
John

Report message to a moderator

Re: [ODA Ecore] URLs to identify models [message #48452 is a reply to message #48396]

Thu, 07 August 2008 21:20

Ed Merks

Messages: 33140
Registered: July 2009

Senior Member

John,

EMF itself definitely supports arbitrary URLs right at the core. Our
Load Resource dialog allows an arbitrary URI to be entered? Of course
there are only browse buttons for workspace and file system, but you can
enter a URL (such as an http-based one) directly in the entry field.
Maybe that the dialog you're already seeing?

John E. Conlon wrote:
> I have a use case where I would like to report on Ecore model
> instances that reside on remote webservers.
>
> When creating ODA Ecore DataSources, I see that models can be browsed
> for (located) in the workspace and the file system ...
>
> but could URLs be used to identify Ecore models that are located on
> web servers (etc.) as well?
>
> If not, is this a constraint based on EMF/Ecore limitations or the
> present implementation of ODA Ecore?
>
> cheers,
> John

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: [ODA Ecore] URLs to identify models [message #48480 is a reply to message #48452]

Fri, 08 August 2008 02:19

Eclipse User

Originally posted by: jconlon.apache.org

Hi Ed,

The Dialog only gives a check box with two choices:
1. Use model from workspace
2. Use model form filesystem

and a text field with a browse button.

On the off chance the ODA Ecore DataSource wizard would maybe accept a
http url, I tried pasting in a URL for a model instance that is on a
http server, but got the exception:

org.eclipse.datatools.connectivity.oda.OdaException ;
java.lang.NullPointerException
at
org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper.open(OdaConnectionWrapper.java:215)
at
org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper. <init>(OdaConnectionWrapper.java:59)
at
org.eclipse.datatools.connectivity.oda.profile.OdaConnection Factory.createConnection(OdaConnectionFactory.java:26)
at
org.eclipse.datatools.connectivity.internal.ConnectionFactor yProvider.createConnection(ConnectionFactoryProvider.java:83 )
at
org.eclipse.datatools.connectivity.internal.ConnectionProfil e.createConnection(ConnectionProfile.java:355)
at
org.eclipse.datatools.connectivity.ui.PingJob.createTestConn ection(PingJob.java:76)
at
org.eclipse.datatools.connectivity.oda.design.internal.ui.Da taSourceWizardPageCore$1.run(DataSourceWizardPageCore.java:2 31)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:70)
at
org.eclipse.datatools.connectivity.ui.wizards.ConnectionProf ileDetailsPage.testConnection(ConnectionProfileDetailsPage.j ava:194)
at
org.eclipse.datatools.connectivity.ui.wizards.ConnectionProf ileDetailsPage$2.widgetSelected(ConnectionProfileDetailsPage .java:131)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3401)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3033)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825 )
at org.eclipse.jface.window.Window.open(Window.java:801)
at
org.eclipse.birt.report.designer.ui.actions.NewDataSourceAct ion.run(NewDataSourceAction.java:126)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:583)
at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:500)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3401)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3033)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: java.lang.NullPointerException
at java.io.File.<init>(File.java:222)
at org.eclipse.emf.common.util.URI.createFileURI(URI.java:832)
at
org.eclipse.datatools.enablement.oda.ecore.impl.Connection.d ataSourceUriFromProperties(Connection.java:83)
at
org.eclipse.datatools.enablement.oda.ecore.impl.Connection.g etModel(Connection.java:63)
at
org.eclipse.datatools.enablement.oda.ecore.impl.Connection.o pen(Connection.java:52)
at
org.eclipse.datatools.connectivity.oda.consumer.helper.OdaCo nnection.open(OdaConnection.java:235)
at
org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper.open(OdaConnectionWrapper.java:209)
... 45 more

BTW - Welcome back from your voyage,

John
Ed Merks wrote:
> John,
>
> EMF itself definitely supports arbitrary URLs right at the core. Our
> Load Resource dialog allows an arbitrary URI to be entered? Of course
> there are only browse buttons for workspace and file system, but you can
> enter a URL (such as an http-based one) directly in the entry field.
> Maybe that the dialog you're already seeing?
>
>
> John E. Conlon wrote:
>> I have a use case where I would like to report on Ecore model
>> instances that reside on remote webservers.
>>
>> When creating ODA Ecore DataSources, I see that models can be browsed
>> for (located) in the workspace and the file system ...
>>
>> but could URLs be used to identify Ecore models that are located on
>> web servers (etc.) as well?
>>
>> If not, is this a constraint based on EMF/Ecore limitations or the
>> present implementation of ODA Ecore?
>>
>> cheers,
>> John

Report message to a moderator

Re: [ODA Ecore] URLs to identify models [message #48510 is a reply to message #48480]

Fri, 08 August 2008 05:39

Tim Myer

Messages: 81
Registered: July 2009

Member

Hi John,
I definitely appreciate these use cases you are submitting and your
active interest in the project. This was certainly something we clearly
overlooked and we will add it to the backlog.
Thanks again.
-----Tim-----

John E. Conlon wrote:
> Hi Ed,
>
> The Dialog only gives a check box with two choices:
> 1. Use model from workspace
> 2. Use model form filesystem
>
> and a text field with a browse button.
>
> On the off chance the ODA Ecore DataSource wizard would maybe accept a
> http url, I tried pasting in a URL for a model instance that is on a
> http server, but got the exception:
>
> org.eclipse.datatools.connectivity.oda.OdaException ;
> java.lang.NullPointerException
> at
> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper.open(OdaConnectionWrapper.java:215)
>
> at
> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper. <init>(OdaConnectionWrapper.java:59)
>
> at
> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Factory.createConnection(OdaConnectionFactory.java:26)
>
> at
> org.eclipse.datatools.connectivity.internal.ConnectionFactor yProvider.createConnection(ConnectionFactoryProvider.java:83 )
>
> at
> org.eclipse.datatools.connectivity.internal.ConnectionProfil e.createConnection(ConnectionProfile.java:355)
>
> at
> org.eclipse.datatools.connectivity.ui.PingJob.createTestConn ection(PingJob.java:76)
>
> at
> org.eclipse.datatools.connectivity.oda.design.internal.ui.Da taSourceWizardPageCore$1.run(DataSourceWizardPageCore.java:2 31)
>
> at
> org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:70)
> at
> org.eclipse.datatools.connectivity.ui.wizards.ConnectionProf ileDetailsPage.testConnection(ConnectionProfileDetailsPage.j ava:194)
>
> at
> org.eclipse.datatools.connectivity.ui.wizards.ConnectionProf ileDetailsPage$2.widgetSelected(ConnectionProfileDetailsPage .java:131)
>
> at
> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:228)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3401)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3033)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825 )
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at
> org.eclipse.birt.report.designer.ui.actions.NewDataSourceAct ion.run(NewDataSourceAction.java:126)
>
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
> at
> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:583)
>
> at
> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:500)
>
> at
> org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:411)
>
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3401)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3033)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
>
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at
> org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
>
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> Caused by: java.lang.NullPointerException
> at java.io.File.<init>(File.java:222)
> at org.eclipse.emf.common.util.URI.createFileURI(URI.java:832)
> at
> org.eclipse.datatools.enablement.oda.ecore.impl.Connection.d ataSourceUriFromProperties(Connection.java:83)
>
> at
> org.eclipse.datatools.enablement.oda.ecore.impl.Connection.g etModel(Connection.java:63)
>
> at
> org.eclipse.datatools.enablement.oda.ecore.impl.Connection.o pen(Connection.java:52)
>
> at
> org.eclipse.datatools.connectivity.oda.consumer.helper.OdaCo nnection.open(OdaConnection.java:235)
>
> at
> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper.open(OdaConnectionWrapper.java:209)
>
> ... 45 more
>
>
>
> BTW - Welcome back from your voyage,
>
> John
> Ed Merks wrote:
>> John,
>>
>> EMF itself definitely supports arbitrary URLs right at the core. Our
>> Load Resource dialog allows an arbitrary URI to be entered? Of course
>> there are only browse buttons for workspace and file system, but you
>> can enter a URL (such as an http-based one) directly in the entry
>> field. Maybe that the dialog you're already seeing?
>>
>>
>> John E. Conlon wrote:
>>> I have a use case where I would like to report on Ecore model
>>> instances that reside on remote webservers.
>>>
>>> When creating ODA Ecore DataSources, I see that models can be browsed
>>> for (located) in the workspace and the file system ...
>>>
>>> but could URLs be used to identify Ecore models that are located on
>>> web servers (etc.) as well?
>>>
>>> If not, is this a constraint based on EMF/Ecore limitations or the
>>> present implementation of ODA Ecore?
>>>
>>> cheers,
>>> John

Report message to a moderator

Re: [ODA Ecore] URLs to identify models [message #48599 is a reply to message #48510]

Fri, 08 August 2008 20:45

Eclipse User

Originally posted by: jconlon.apache.org

Hi Tim,

Glad to help in anyway I can.

I am very enthusiastic about the work you and Jeff Ramsdale have done
with ODA Ecore to date, as it adds the whole range of BIRT functionality
to the already powerful capabilities of EMF.

thanks again all your work,
John

Tim Myer wrote:
> Hi John,
> I definitely appreciate these use cases you are submitting and your
> active interest in the project. This was certainly something we clearly
> overlooked and we will add it to the backlog.
> Thanks again.
> -----Tim-----
>
> John E. Conlon wrote:
>> Hi Ed,
>>
>> The Dialog only gives a check box with two choices:
>> 1. Use model from workspace
>> 2. Use model form filesystem
>>
>> and a text field with a browse button.
>>
>> On the off chance the ODA Ecore DataSource wizard would maybe accept a
>> http url, I tried pasting in a URL for a model instance that is on a
>> http server, but got the exception:
>>
>> org.eclipse.datatools.connectivity.oda.OdaException ;
>> java.lang.NullPointerException
>> at
>> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper.open(OdaConnectionWrapper.java:215)
>>
>> at
>> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper. <init>(OdaConnectionWrapper.java:59)
>>
>> at
>> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Factory.createConnection(OdaConnectionFactory.java:26)
>>
>> at
>> org.eclipse.datatools.connectivity.internal.ConnectionFactor yProvider.createConnection(ConnectionFactoryProvider.java:83 )
>>
>> at
>> org.eclipse.datatools.connectivity.internal.ConnectionProfil e.createConnection(ConnectionProfile.java:355)
>>
>> at
>> org.eclipse.datatools.connectivity.ui.PingJob.createTestConn ection(PingJob.java:76)
>>
>> at
>> org.eclipse.datatools.connectivity.oda.design.internal.ui.Da taSourceWizardPageCore$1.run(DataSourceWizardPageCore.java:2 31)
>>
>> at
>> org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:70)
>> at
>> org.eclipse.datatools.connectivity.ui.wizards.ConnectionProf ileDetailsPage.testConnection(ConnectionProfileDetailsPage.j ava:194)
>>
>> at
>> org.eclipse.datatools.connectivity.ui.wizards.ConnectionProf ileDetailsPage$2.widgetSelected(ConnectionProfileDetailsPage .java:131)
>>
>> at
>> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:228)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
>> at
>> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3401)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3033)
>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825 )
>> at org.eclipse.jface.window.Window.open(Window.java:801)
>> at
>> org.eclipse.birt.report.designer.ui.actions.NewDataSourceAct ion.run(NewDataSourceAction.java:126)
>>
>> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
>> at
>> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:583)
>>
>> at
>> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:500)
>>
>> at
>> org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:411)
>>
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
>> at
>> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3401)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3033)
>> at
>> org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
>> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
>> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
>> at
>> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
>>
>> at
>> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
>>
>> at
>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
>> at
>> org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
>>
>> at
>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>>
>> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>>
>> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>>
>> at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
>>
>> at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
>> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
>> Caused by: java.lang.NullPointerException
>> at java.io.File.<init>(File.java:222)
>> at org.eclipse.emf.common.util.URI.createFileURI(URI.java:832)
>> at
>> org.eclipse.datatools.enablement.oda.ecore.impl.Connection.d ataSourceUriFromProperties(Connection.java:83)
>>
>> at
>> org.eclipse.datatools.enablement.oda.ecore.impl.Connection.g etModel(Connection.java:63)
>>
>> at
>> org.eclipse.datatools.enablement.oda.ecore.impl.Connection.o pen(Connection.java:52)
>>
>> at
>> org.eclipse.datatools.connectivity.oda.consumer.helper.OdaCo nnection.open(OdaConnection.java:235)
>>
>> at
>> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper.open(OdaConnectionWrapper.java:209)
>>
>> ... 45 more
>>
>>
>>
>> BTW - Welcome back from your voyage,
>>
>> John
>> Ed Merks wrote:
>>> John,
>>>
>>> EMF itself definitely supports arbitrary URLs right at the core. Our
>>> Load Resource dialog allows an arbitrary URI to be entered? Of
>>> course there are only browse buttons for workspace and file system,
>>> but you can enter a URL (such as an http-based one) directly in the
>>> entry field. Maybe that the dialog you're already seeing?
>>>
>>>
>>> John E. Conlon wrote:
>>>> I have a use case where I would like to report on Ecore model
>>>> instances that reside on remote webservers.
>>>>
>>>> When creating ODA Ecore DataSources, I see that models can be
>>>> browsed for (located) in the workspace and the file system ...
>>>>
>>>> but could URLs be used to identify Ecore models that are located on
>>>> web servers (etc.) as well?
>>>>
>>>> If not, is this a constraint based on EMF/Ecore limitations or the
>>>> present implementation of ODA Ecore?
>>>>
>>>> cheers,
>>>> John

Report message to a moderator

Re: [ODA Ecore] URLs to identify models [message #49213 is a reply to message #48599]

Fri, 22 August 2008 14:35

Tim Myer

Messages: 81
Registered: July 2009

Member

Hi John,
There is now an option on the dialog that allows entry of an arbitrary
URI. Filesystem and Workspace locations still allow browsing.
Arbitrary URIs must be entered by hand.
Let us know if this is what you had in mind. Thanks!
------Tim-------

John E. Conlon wrote:
> Hi Tim,
>
> Glad to help in anyway I can.
>
> I am very enthusiastic about the work you and Jeff Ramsdale have done
> with ODA Ecore to date, as it adds the whole range of BIRT functionality
> to the already powerful capabilities of EMF.
>
> thanks again all your work,
> John
>
> Tim Myer wrote:
>> Hi John,
>> I definitely appreciate these use cases you are submitting and your
>> active interest in the project. This was certainly something we
>> clearly overlooked and we will add it to the backlog.
>> Thanks again.
>> -----Tim-----
>>
>> John E. Conlon wrote:
>>> Hi Ed,
>>>
>>> The Dialog only gives a check box with two choices:
>>> 1. Use model from workspace
>>> 2. Use model form filesystem
>>>
>>> and a text field with a browse button.
>>>
>>> On the off chance the ODA Ecore DataSource wizard would maybe accept
>>> a http url, I tried pasting in a URL for a model instance that is on
>>> a http server, but got the exception:
>>>
>>> org.eclipse.datatools.connectivity.oda.OdaException ;
>>> java.lang.NullPointerException
>>> at
>>> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper.open(OdaConnectionWrapper.java:215)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper. <init>(OdaConnectionWrapper.java:59)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Factory.createConnection(OdaConnectionFactory.java:26)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.internal.ConnectionFactor yProvider.createConnection(ConnectionFactoryProvider.java:83 )
>>>
>>> at
>>> org.eclipse.datatools.connectivity.internal.ConnectionProfil e.createConnection(ConnectionProfile.java:355)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.ui.PingJob.createTestConn ection(PingJob.java:76)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.oda.design.internal.ui.Da taSourceWizardPageCore$1.run(DataSourceWizardPageCore.java:2 31)
>>>
>>> at
>>> org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:70)
>>> at
>>> org.eclipse.datatools.connectivity.ui.wizards.ConnectionProf ileDetailsPage.testConnection(ConnectionProfileDetailsPage.j ava:194)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.ui.wizards.ConnectionProf ileDetailsPage$2.widgetSelected(ConnectionProfileDetailsPage .java:131)
>>>
>>> at
>>> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:228)
>>>
>>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
>>> at
>>> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3401)
>>> at
>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3033)
>>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825 )
>>> at org.eclipse.jface.window.Window.open(Window.java:801)
>>> at
>>> org.eclipse.birt.report.designer.ui.actions.NewDataSourceAct ion.run(NewDataSourceAction.java:126)
>>>
>>> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
>>> at
>>> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:583)
>>>
>>> at
>>> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:500)
>>>
>>> at
>>> org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:411)
>>>
>>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
>>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
>>> at
>>> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3401)
>>> at
>>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3033)
>>> at
>>> org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
>>> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
>>> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
>>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
>>> at
>>> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
>>>
>>> at
>>> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
>>>
>>> at
>>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
>>> at
>>> org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
>>>
>>> at
>>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>>>
>>> at
>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>>>
>>> at
>>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>>>
>>> at
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
>>>
>>> at
>>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
>>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
>>> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
>>> Caused by: java.lang.NullPointerException
>>> at java.io.File.<init>(File.java:222)
>>> at org.eclipse.emf.common.util.URI.createFileURI(URI.java:832)
>>> at
>>> org.eclipse.datatools.enablement.oda.ecore.impl.Connection.d ataSourceUriFromProperties(Connection.java:83)
>>>
>>> at
>>> org.eclipse.datatools.enablement.oda.ecore.impl.Connection.g etModel(Connection.java:63)
>>>
>>> at
>>> org.eclipse.datatools.enablement.oda.ecore.impl.Connection.o pen(Connection.java:52)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.oda.consumer.helper.OdaCo nnection.open(OdaConnection.java:235)
>>>
>>> at
>>> org.eclipse.datatools.connectivity.oda.profile.OdaConnection Wrapper.open(OdaConnectionWrapper.java:209)
>>>
>>> ... 45 more
>>>
>>>
>>>
>>> BTW - Welcome back from your voyage,
>>>
>>> John
>>> Ed Merks wrote:
>>>> John,
>>>>
>>>> EMF itself definitely supports arbitrary URLs right at the core.
>>>> Our Load Resource dialog allows an arbitrary URI to be entered? Of
>>>> course there are only browse buttons for workspace and file system,
>>>> but you can enter a URL (such as an http-based one) directly in the
>>>> entry field. Maybe that the dialog you're already seeing?
>>>>
>>>>
>>>> John E. Conlon wrote:
>>>>> I have a use case where I would like to report on Ecore model
>>>>> instances that reside on remote webservers.
>>>>>
>>>>> When creating ODA Ecore DataSources, I see that models can be
>>>>> browsed for (located) in the workspace and the file system ...
>>>>>
>>>>> but could URLs be used to identify Ecore models that are located on
>>>>> web servers (etc.) as well?
>>>>>
>>>>> If not, is this a constraint based on EMF/Ecore limitations or the
>>>>> present implementation of ODA Ecore?
>>>>>
>>>>> cheers,
>>>>> John

Report message to a moderator