[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [edt-dev] Bugzilla enhancement 369135
|
A slash was considered.
We used rfc3986 as the basis for the
proposal, the general syntax being used is binding:uri and a more detailed
for is "binding:file:"path"#"fragment. After binding:
is a URI to define how to obtain the binding and is defined as "file:"path"#"fragment.
We have used file: because we are accessing a file. After the file is the
path to the file "The path component contains data" and in our
case the data is the resource bindings. We chose fragment because it defines
a secondary element within the primary. Here the primary is the file and
the secondary is the binding within the file.
regards,
Joe Vincens
EGL Developer
Rational Software, IBM Software Group
| From:
| William A Smythe/Raleigh/IBM@IBMUS
|
| To:
| EGL Development Tools <edt-dev@xxxxxxxxxxx>,
|
| Cc:
| edt-dev@xxxxxxxxxxx, edt-dev-bounces@xxxxxxxxxxx
|
| Date:
| 01/30/2012 12:59 PM
|
| Subject:
| Re: [edt-dev] Bugzilla enhancement 369135
|
| Sent by:
| edt-dev-bounces@xxxxxxxxxxx |
The URI pattern for a binding that exists
in a different file seems a bit odd (e.g. "binding:file:ProdDD#myDB").
Any consideration to using a separator (e.g. "/") to separate
the file and binding names? For example: "binding:ProdDD/myDB"
? This would mean binding names could not contain a "/" (or whatever
the separator character is). This pattern seems more conventional and rememberable.
Will Smythe
Product Manager
EGL, Rational Business Developer, and Rational Migration Extension
IBM Rational Software, RTP, NC
919.254.8771
smythew@xxxxxxxxxx
Joseph
Vincens---01/27/2012 05:13:31 PM---If you are using 0.8.0 I2 please read.
The enhancement (bugzilla 369135) was just committed and wil
From: Joseph Vincens/New Haven/IBM@IBMUS
To: edt-dev@xxxxxxxxxxx
Date: 01/27/2012 05:13 PM
Subject: [edt-dev] Bugzilla enhancement
369135
Sent by: edt-dev-bounces@xxxxxxxxxxx
If you are using 0.8.0 I2 please read.
The enhancement (bugzilla 369135)
was just committed and will affect anyone who is using @Resource or SysLib.getResource.
The enhancement redefines resources, in 0.7.0 resources were only considered
bindings, but in the future a resource can represent just about anything.
This required an API change to @Resource and SysLib.getResource, instead
of a key these now take a URI. The details are covered in 369135,
but you will need to make some code
changes. Here are examples of what you need to change:
@Resource{bindingKey
= “myDB”} to @Resource{uri=”binding:myDB”}.
@Resource{bindingKey=”myDB”, propertyFileName=”ProdDD”}
to @Resource{uri=”binding:file:ProdDD#myDB”}
SysLib.getResource(“myDB”) SysLib.getResource(”binding:myDB”).
SysLib.getResource(”myDB”, ”ProdDD”} to SysLib.getResource(”binding:file:ProdDD#myDB”).
regards,
Joe Vincens
EGL Developer
Rational Software, IBM Software Group _______________________________________________
edt-dev mailing list
edt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/edt-dev
_______________________________________________
edt-dev mailing list
edt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/edt-dev
