Home » Modeling » Modeling (top-level project) » Why does the URI scheme disallow ':' ?
| |
Re: Why does the URI scheme disallow ':' ? [message #381140 is a reply to message #381138] |
Wed, 18 July 2007 21:14 |
Bryan Hunt Messages: 366 Registered: July 2009 |
Senior Member |
|
|
Sorry Ed, I thought eclipse.modeling was the "new" emf newsgroup.
A full jdbc uri looks like:
jdbc:db2://host:port/db_name
or
jdbc:mysql://host:port/db_name
As a side note, I'm currently using a URI that looks like:
jdbc_db2://host:port/db_name?table=TABLE_NAME,key=PRIMARY_KE Y_COLUNM
and my custom URI converter changes the '_' to a ':' and strips off the
query before opening the jdbc connection.
Bryan
On 2007-07-18 15:31:46 -0500, Ed Merks <merks@ca.ibm.com> said:
> Bryan,
>
> This sounds like an EMF specific question best asked on the EMF
> newsgroup, which I've added to the "to" list of the reply, although I'm
> sure I've seen you ask questions before. :-)
> EMF's URI implementation is simply enforcing the URI RFC's rules.
> Something like jdbc:db2 definitely isn't a scheme, it's a
> non-hierarchical URI with scheme jdbc and opaque part db2. So it's a
> valid URI, but the scheme is only the jdbc. What does a full such URI
> look like?
>
>
> Bryan Hunt wrote:
>> Why does the URI scheme disallow the ':' character? By making this
>> restriction, you cannot create a uri with the scheme jdbc:db2 which is
>> perfectly valid in jdbc.
>>
>> Bryan
|
|
|
Re: Why does the URI scheme disallow ':' ? [message #381142 is a reply to message #381140] |
Wed, 18 July 2007 21:27 |
Ed Merks Messages: 33140 Registered: July 2009 |
Senior Member |
|
|
Bryan,
Some people think EMF == Modeling, but that's not the case! (I'm sure
Rich will chuckle now.) I've resisted closing the old newsgroup and
creating a new one because I'd lose the whole history of tens of
thousands of questions and answers (except for archives that no one
would think to search). Maybe eventually we'll have time to figure out
how to copy and rename a newsgroup...
Unfortunately, this ends up being a non-hierarchical URI. The RFC is
quite clear on the need for a "/" after the ":" to make a URI
hierarchical, so it's unfortunate that so many URI-based designs were
based on a poor understanding of the RFC... :-( Even Eclipse's
platform scheme, though avoiding this flaw, would have been more
consistent if it had been of the form platform://resource/... making it
clear that the "resource" is the authority, and what follows is a path
within that authority. Oh well, water under the bridge...
Bryan Hunt wrote:
> Sorry Ed, I thought eclipse.modeling was the "new" emf newsgroup.
>
> A full jdbc uri looks like:
>
> jdbc:db2://host:port/db_name
>
> or
>
> jdbc:mysql://host:port/db_name
>
> As a side note, I'm currently using a URI that looks like:
>
> jdbc_db2://host:port/db_name?table=TABLE_NAME,key=PRIMARY_KE Y_COLUNM
>
> and my custom URI converter changes the '_' to a ':' and strips off
> the query before opening the jdbc connection.
>
> Bryan
>
> On 2007-07-18 15:31:46 -0500, Ed Merks <merks@ca.ibm.com> said:
>
>> Bryan,
>>
>> This sounds like an EMF specific question best asked on the EMF
>> newsgroup, which I've added to the "to" list of the reply, although
>> I'm sure I've seen you ask questions before. :-)
>> EMF's URI implementation is simply enforcing the URI RFC's rules.
>> Something like jdbc:db2 definitely isn't a scheme, it's a
>> non-hierarchical URI with scheme jdbc and opaque part db2. So it's a
>> valid URI, but the scheme is only the jdbc. What does a full such
>> URI look like?
>>
>>
>> Bryan Hunt wrote:
>>> Why does the URI scheme disallow the ':' character? By making this
>>> restriction, you cannot create a uri with the scheme jdbc:db2 which
>>> is perfectly valid in jdbc.
>>>
>>> Bryan
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Re: Why does the URI scheme disallow ':' ? [message #381143 is a reply to message #381142] |
Wed, 18 July 2007 22:32 |
Bryan Hunt Messages: 366 Registered: July 2009 |
Senior Member |
|
|
Yes, I realize now that I'm trying to fit a square peg in a round hole.
Even my "trick" of using jdbc_db2 doesn't work when you use
java.net.URI. I've refined my trick and now I'm using the form:
jdbc://db2@host:port/db_name?query
so that I don't have to do the parsing myself. From there, it's
relatively easy to convert the hierarichal URI into the
non-hierarchical URI that JDBC needs.
Bryan
On 2007-07-18 16:27:53 -0500, Ed Merks <merks@ca.ibm.com> said:
> Bryan,
>
> Some people think EMF == Modeling, but that's not the case! (I'm sure
> Rich will chuckle now.) I've resisted closing the old newsgroup and
> creating a new one because I'd lose the whole history of tens of
> thousands of questions and answers (except for archives that no one
> would think to search). Maybe eventually we'll have time to figure out
> how to copy and rename a newsgroup...
>
> Unfortunately, this ends up being a non-hierarchical URI. The RFC is
> quite clear on the need for a "/" after the ":" to make a URI
> hierarchical, so it's unfortunate that so many URI-based designs were
> based on a poor understanding of the RFC... :-( Even Eclipse's
> platform scheme, though avoiding this flaw, would have been more
> consistent if it had been of the form platform://resource/... making it
> clear that the "resource" is the authority, and what follows is a path
> within that authority. Oh well, water under the bridge...
>
>
> Bryan Hunt wrote:
>> Sorry Ed, I thought eclipse.modeling was the "new" emf newsgroup.
>>
>> A full jdbc uri looks like:
>>
>> jdbc:db2://host:port/db_name
>>
>> or
>>
>> jdbc:mysql://host:port/db_name
>>
>> As a side note, I'm currently using a URI that looks like:
>>
>> jdbc_db2://host:port/db_name?table=TABLE_NAME,key=PRIMARY_KE Y_COLUNM
>>
>> and my custom URI converter changes the '_' to a ':' and strips off the
>> query before opening the jdbc connection.
>>
>> Bryan
>>
>> On 2007-07-18 15:31:46 -0500, Ed Merks <merks@ca.ibm.com> said:
>>
>>> Bryan,
>>>
>>> This sounds like an EMF specific question best asked on the EMF
>>> newsgroup, which I've added to the "to" list of the reply, although I'm
>>> sure I've seen you ask questions before. :-)
>>> EMF's URI implementation is simply enforcing the URI RFC's rules.
>>> Something like jdbc:db2 definitely isn't a scheme, it's a
>>> non-hierarchical URI with scheme jdbc and opaque part db2. So it's a
>>> valid URI, but the scheme is only the jdbc. What does a full such URI
>>> look like?
>>>
>>>
>>> Bryan Hunt wrote:
>>>> Why does the URI scheme disallow the ':' character? By making this
>>>> restriction, you cannot create a uri with the scheme jdbc:db2 which is
>>>> perfectly valid in jdbc.
>>>>
>>>> Bryan
|
|
|
Re: Why does the URI scheme disallow ':' ? [message #381145 is a reply to message #381142] |
Thu, 19 July 2007 09:17 |
Richard Gronback Messages: 605 Registered: July 2009 |
Senior Member |
|
|
:) yup.
On 7/18/07 11:27 PM, in article f7m0ku$iq2$1@build.eclipse.org, "Ed Merks"
<merks@ca.ibm.com> wrote:
> Bryan,
>
> Some people think EMF == Modeling, but that's not the case! (I'm sure
> Rich will chuckle now.) I've resisted closing the old newsgroup and
> creating a new one because I'd lose the whole history of tens of
> thousands of questions and answers (except for archives that no one
> would think to search). Maybe eventually we'll have time to figure out
> how to copy and rename a newsgroup...
>
> Unfortunately, this ends up being a non-hierarchical URI. The RFC is
> quite clear on the need for a "/" after the ":" to make a URI
> hierarchical, so it's unfortunate that so many URI-based designs were
> based on a poor understanding of the RFC... :-( Even Eclipse's
> platform scheme, though avoiding this flaw, would have been more
> consistent if it had been of the form platform://resource/... making it
> clear that the "resource" is the authority, and what follows is a path
> within that authority. Oh well, water under the bridge...
>
>
> Bryan Hunt wrote:
>> Sorry Ed, I thought eclipse.modeling was the "new" emf newsgroup.
>>
>> A full jdbc uri looks like:
>>
>> jdbc:db2://host:port/db_name
>>
>> or
>>
>> jdbc:mysql://host:port/db_name
>>
>> As a side note, I'm currently using a URI that looks like:
>>
>> jdbc_db2://host:port/db_name?table=TABLE_NAME,key=PRIMARY_KE Y_COLUNM
>>
>> and my custom URI converter changes the '_' to a ':' and strips off
>> the query before opening the jdbc connection.
>>
>> Bryan
>>
>> On 2007-07-18 15:31:46 -0500, Ed Merks <merks@ca.ibm.com> said:
>>
>>> Bryan,
>>>
>>> This sounds like an EMF specific question best asked on the EMF
>>> newsgroup, which I've added to the "to" list of the reply, although
>>> I'm sure I've seen you ask questions before. :-)
>>> EMF's URI implementation is simply enforcing the URI RFC's rules.
>>> Something like jdbc:db2 definitely isn't a scheme, it's a
>>> non-hierarchical URI with scheme jdbc and opaque part db2. So it's a
>>> valid URI, but the scheme is only the jdbc. What does a full such
>>> URI look like?
>>>
>>>
>>> Bryan Hunt wrote:
>>>> Why does the URI scheme disallow the ':' character? By making this
>>>> restriction, you cannot create a uri with the scheme jdbc:db2 which
>>>> is perfectly valid in jdbc.
>>>>
>>>> Bryan
>>
>>
|
|
|
Re: Why does the URI scheme disallow ':' ? [message #596890 is a reply to message #381137] |
Wed, 18 July 2007 20:31 |
Ed Merks Messages: 33140 Registered: July 2009 |
Senior Member |
|
|
Bryan,
This sounds like an EMF specific question best asked on the EMF
newsgroup, which I've added to the "to" list of the reply, although I'm
sure I've seen you ask questions before. :-)
EMF's URI implementation is simply enforcing the URI RFC's rules.
Something like jdbc:db2 definitely isn't a scheme, it's a
non-hierarchical URI with scheme jdbc and opaque part db2. So it's a
valid URI, but the scheme is only the jdbc. What does a full such URI
look like?
Bryan Hunt wrote:
> Why does the URI scheme disallow the ':' character? By making this
> restriction, you cannot create a uri with the scheme jdbc:db2 which is
> perfectly valid in jdbc.
>
> Bryan
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Re: Why does the URI scheme disallow ':' ? [message #596905 is a reply to message #381138] |
Wed, 18 July 2007 21:14 |
Bryan Hunt Messages: 366 Registered: July 2009 |
Senior Member |
|
|
Sorry Ed, I thought eclipse.modeling was the "new" emf newsgroup.
A full jdbc uri looks like:
jdbc:db2://host:port/db_name
or
jdbc:mysql://host:port/db_name
As a side note, I'm currently using a URI that looks like:
jdbc_db2://host:port/db_name?table=TABLE_NAME,key=PRIMARY_KE Y_COLUNM
and my custom URI converter changes the '_' to a ':' and strips off the
query before opening the jdbc connection.
Bryan
On 2007-07-18 15:31:46 -0500, Ed Merks <merks@ca.ibm.com> said:
> Bryan,
>
> This sounds like an EMF specific question best asked on the EMF
> newsgroup, which I've added to the "to" list of the reply, although I'm
> sure I've seen you ask questions before. :-)
> EMF's URI implementation is simply enforcing the URI RFC's rules.
> Something like jdbc:db2 definitely isn't a scheme, it's a
> non-hierarchical URI with scheme jdbc and opaque part db2. So it's a
> valid URI, but the scheme is only the jdbc. What does a full such URI
> look like?
>
>
> Bryan Hunt wrote:
>> Why does the URI scheme disallow the ':' character? By making this
>> restriction, you cannot create a uri with the scheme jdbc:db2 which is
>> perfectly valid in jdbc.
>>
>> Bryan
|
|
|
Re: Why does the URI scheme disallow ':' ? [message #596917 is a reply to message #381140] |
Wed, 18 July 2007 21:27 |
Ed Merks Messages: 33140 Registered: July 2009 |
Senior Member |
|
|
Bryan,
Some people think EMF == Modeling, but that's not the case! (I'm sure
Rich will chuckle now.) I've resisted closing the old newsgroup and
creating a new one because I'd lose the whole history of tens of
thousands of questions and answers (except for archives that no one
would think to search). Maybe eventually we'll have time to figure out
how to copy and rename a newsgroup...
Unfortunately, this ends up being a non-hierarchical URI. The RFC is
quite clear on the need for a "/" after the ":" to make a URI
hierarchical, so it's unfortunate that so many URI-based designs were
based on a poor understanding of the RFC... :-( Even Eclipse's
platform scheme, though avoiding this flaw, would have been more
consistent if it had been of the form platform://resource/.. making it
clear that the "resource" is the authority, and what follows is a path
within that authority. Oh well, water under the bridge...
Bryan Hunt wrote:
> Sorry Ed, I thought eclipse.modeling was the "new" emf newsgroup.
>
> A full jdbc uri looks like:
>
> jdbc:db2://host:port/db_name
>
> or
>
> jdbc:mysql://host:port/db_name
>
> As a side note, I'm currently using a URI that looks like:
>
> jdbc_db2://host:port/db_name?table=TABLE_NAME,key=PRIMARY_KE Y_COLUNM
>
> and my custom URI converter changes the '_' to a ':' and strips off
> the query before opening the jdbc connection.
>
> Bryan
>
> On 2007-07-18 15:31:46 -0500, Ed Merks <merks@ca.ibm.com> said:
>
>> Bryan,
>>
>> This sounds like an EMF specific question best asked on the EMF
>> newsgroup, which I've added to the "to" list of the reply, although
>> I'm sure I've seen you ask questions before. :-)
>> EMF's URI implementation is simply enforcing the URI RFC's rules.
>> Something like jdbc:db2 definitely isn't a scheme, it's a
>> non-hierarchical URI with scheme jdbc and opaque part db2. So it's a
>> valid URI, but the scheme is only the jdbc. What does a full such
>> URI look like?
>>
>>
>> Bryan Hunt wrote:
>>> Why does the URI scheme disallow the ':' character? By making this
>>> restriction, you cannot create a uri with the scheme jdbc:db2 which
>>> is perfectly valid in jdbc.
>>>
>>> Bryan
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Re: Why does the URI scheme disallow ':' ? [message #596925 is a reply to message #381142] |
Wed, 18 July 2007 22:32 |
Bryan Hunt Messages: 366 Registered: July 2009 |
Senior Member |
|
|
Yes, I realize now that I'm trying to fit a square peg in a round hole.
Even my "trick" of using jdbc_db2 doesn't work when you use
java.net.URI. I've refined my trick and now I'm using the form:
jdbc://db2@host:port/db_name?query
so that I don't have to do the parsing myself. From there, it's
relatively easy to convert the hierarichal URI into the
non-hierarchical URI that JDBC needs.
Bryan
On 2007-07-18 16:27:53 -0500, Ed Merks <merks@ca.ibm.com> said:
> Bryan,
>
> Some people think EMF == Modeling, but that's not the case! (I'm sure
> Rich will chuckle now.) I've resisted closing the old newsgroup and
> creating a new one because I'd lose the whole history of tens of
> thousands of questions and answers (except for archives that no one
> would think to search). Maybe eventually we'll have time to figure out
> how to copy and rename a newsgroup...
>
> Unfortunately, this ends up being a non-hierarchical URI. The RFC is
> quite clear on the need for a "/" after the ":" to make a URI
> hierarchical, so it's unfortunate that so many URI-based designs were
> based on a poor understanding of the RFC... :-( Even Eclipse's
> platform scheme, though avoiding this flaw, would have been more
> consistent if it had been of the form platform://resource/.. making it
> clear that the "resource" is the authority, and what follows is a path
> within that authority. Oh well, water under the bridge...
>
>
> Bryan Hunt wrote:
>> Sorry Ed, I thought eclipse.modeling was the "new" emf newsgroup.
>>
>> A full jdbc uri looks like:
>>
>> jdbc:db2://host:port/db_name
>>
>> or
>>
>> jdbc:mysql://host:port/db_name
>>
>> As a side note, I'm currently using a URI that looks like:
>>
>> jdbc_db2://host:port/db_name?table=TABLE_NAME,key=PRIMARY_KE Y_COLUNM
>>
>> and my custom URI converter changes the '_' to a ':' and strips off the
>> query before opening the jdbc connection.
>>
>> Bryan
>>
>> On 2007-07-18 15:31:46 -0500, Ed Merks <merks@ca.ibm.com> said:
>>
>>> Bryan,
>>>
>>> This sounds like an EMF specific question best asked on the EMF
>>> newsgroup, which I've added to the "to" list of the reply, although I'm
>>> sure I've seen you ask questions before. :-)
>>> EMF's URI implementation is simply enforcing the URI RFC's rules.
>>> Something like jdbc:db2 definitely isn't a scheme, it's a
>>> non-hierarchical URI with scheme jdbc and opaque part db2. So it's a
>>> valid URI, but the scheme is only the jdbc. What does a full such URI
>>> look like?
>>>
>>>
>>> Bryan Hunt wrote:
>>>> Why does the URI scheme disallow the ':' character? By making this
>>>> restriction, you cannot create a uri with the scheme jdbc:db2 which is
>>>> perfectly valid in jdbc.
>>>>
>>>> Bryan
|
|
|
Re: Why does the URI scheme disallow ':' ? [message #596932 is a reply to message #381142] |
Thu, 19 July 2007 09:17 |
Richard Gronback Messages: 605 Registered: July 2009 |
Senior Member |
|
|
:) yup.
On 7/18/07 11:27 PM, in article f7m0ku$iq2$1@build.eclipse.org, "Ed Merks"
<merks@ca.ibm.com> wrote:
> Bryan,
>
> Some people think EMF == Modeling, but that's not the case! (I'm sure
> Rich will chuckle now.) I've resisted closing the old newsgroup and
> creating a new one because I'd lose the whole history of tens of
> thousands of questions and answers (except for archives that no one
> would think to search). Maybe eventually we'll have time to figure out
> how to copy and rename a newsgroup...
>
> Unfortunately, this ends up being a non-hierarchical URI. The RFC is
> quite clear on the need for a "/" after the ":" to make a URI
> hierarchical, so it's unfortunate that so many URI-based designs were
> based on a poor understanding of the RFC... :-( Even Eclipse's
> platform scheme, though avoiding this flaw, would have been more
> consistent if it had been of the form platform://resource/.. making it
> clear that the "resource" is the authority, and what follows is a path
> within that authority. Oh well, water under the bridge...
>
>
> Bryan Hunt wrote:
>> Sorry Ed, I thought eclipse.modeling was the "new" emf newsgroup.
>>
>> A full jdbc uri looks like:
>>
>> jdbc:db2://host:port/db_name
>>
>> or
>>
>> jdbc:mysql://host:port/db_name
>>
>> As a side note, I'm currently using a URI that looks like:
>>
>> jdbc_db2://host:port/db_name?table=TABLE_NAME,key=PRIMARY_KE Y_COLUNM
>>
>> and my custom URI converter changes the '_' to a ':' and strips off
>> the query before opening the jdbc connection.
>>
>> Bryan
>>
>> On 2007-07-18 15:31:46 -0500, Ed Merks <merks@ca.ibm.com> said:
>>
>>> Bryan,
>>>
>>> This sounds like an EMF specific question best asked on the EMF
>>> newsgroup, which I've added to the "to" list of the reply, although
>>> I'm sure I've seen you ask questions before. :-)
>>> EMF's URI implementation is simply enforcing the URI RFC's rules.
>>> Something like jdbc:db2 definitely isn't a scheme, it's a
>>> non-hierarchical URI with scheme jdbc and opaque part db2. So it's a
>>> valid URI, but the scheme is only the jdbc. What does a full such
>>> URI look like?
>>>
>>>
>>> Bryan Hunt wrote:
>>>> Why does the URI scheme disallow the ':' character? By making this
>>>> restriction, you cannot create a uri with the scheme jdbc:db2 which
>>>> is perfectly valid in jdbc.
>>>>
>>>> Bryan
>>
>>
|
|
|
Goto Forum:
Current Time: Wed Apr 24 23:41:11 GMT 2024
Powered by FUDForum. Page generated in 0.03230 seconds
|