| properties vs. resources [message #126019] |
Tue, 09 September 2003 15:01  |
Eclipse User |
|
|
|
Originally posted by: ThisisFake.Fakeness.xyz
Still working on my database based application.
Wondering if my database connection information should be a property or a
resource. That is, should I put the DB values as property on the project
resource? or should I create my own file, and put the db values in that
file?
seems like if I use a property on the project, then it will not be easy
to package up my project because some of the projects info will be in the
..metadata file. seems like properties would be excellent for something
like build status which is not important to transfer when you move a
project.
Am I in the right line of thinking here?
Thanks once again,
CL
|
|
|
| Re: properties vs. resources [message #126296 is a reply to message #126019] |
Wed, 10 September 2003 05:50  |
| Eclipse User |
|
|
|
Hi gilbert,
> Still working on my database based application.
>
> Wondering if my database connection information should be a property or a
> resource. That is, should I put the DB values as property on the project
> resource? or should I create my own file, and put the db values in that
> file?
>
> seems like if I use a property on the project, then it will not be easy
> to package up my project because some of the projects info will be in the
> .metadata file. seems like properties would be excellent for something
> like build status which is not important to transfer when you move a
> project.
>
> Am I in the right line of thinking here?
I think so. Properties are logically linked with the plugin. You can specify
default values (by code). If you change something the change will only
saved within the current workspace. Change the workspace and the
new workspace will denie do know anything about your change property.
(you are right its in the .metadata directory and therefore the new
workbench
will have a diffrent one.)
So if you can provide default connection settings you may run for a
property.
The user may change your properties easily by using a property sheet.
If you save it as a resource you may move your project/plugin. But think
about
it. Why should someone move the plugin? What if someone expects to move
projects around? (meaning using your application not developing it). And
remember
a plugin has only one directory within every workbench its installed in. So
if you
have two users, one types Jon Doe and the other user changes the login to
Joan Doe (uses another worbench within the same mashine). Now Jon Doe hits
connect and is logged in as Joan Doe?! Strange wouldn't it be?
I think login and connection informations should be placed as
properties/mementos
for sure.
Ca
Martin (Kersten)
|
|
|
Powered by
FUDForum. Page generated in 0.02454 seconds
Home