| Designer Local JNDI [message #249098] |
Fri, 20 July 2007 03:38  |
Eclipse User |
|
|
|
Hello,
This is a little request for feature, I think it would be nice to have a
kind of 'local' JNDI in the designer in order to simulate the runtime
engine of a server like Tomcat.
Currently we're using the BIRT Designer with some DataSources that a
linked 'in hard' to a developpment database. When we want to deploy our
report in a test or production environment, we usually modify the
"database URL" of the Datasource in order to avoid a fallback to the
development database.
Sometimes we forget to do so and sometimes Tomcat lose it's context
informations and we have a report that goes to the wrong database ...
What would be cool is to have a report file that is exactly the same in
development and in production. We would just specify a JNDI name in the
datasource and a local JNDI serveur in the designer (something like this
http://www.javaranch.com/codebarn.jsp) would serve the connexion.
Best Regards,
Tchule.
PS : A side question, what is the purpose of the <xml-property
name="designerValues"> tag in the rptdesign file. Is it some kind of
cached result for the designer ? It is necessary in a production report
engine ? Shouldn't it be in the rptconfig file ?
|
|
|
|
|
| Re: Designer Local JNDI [message #250235 is a reply to message #249098] |
Fri, 27 July 2007 18:41  |
| Eclipse User |
|
|
|
From your use case, it seems the main objective is to be able to externalize
the data source properties from your report designs. This way the
externalized properties can change in a deployment environment without
changing the report designs themselves. Using a local JNDI service would
be one way to do that, but may be an overkill.
What we do have support now in BIRT 2.2 is to use an externalized connection
profile stored in a separate file. See this link for an overview:
http://www.eclipse.org/birt/phoenix/project/notable2.2.php#j ump_22
Hope this helps.
Linda
"tchule" <tchule@hotmail.com> wrote in message
news:dada149277936c4bec482f19ddb77f69$1@www.eclipse.org...
> Hello,
>
> This is a little request for feature, I think it would be nice to have a
> kind of 'local' JNDI in the designer in order to simulate the runtime
> engine of a server like Tomcat.
>
> Currently we're using the BIRT Designer with some DataSources that a
> linked 'in hard' to a developpment database. When we want to deploy our
> report in a test or production environment, we usually modify the
> "database URL" of the Datasource in order to avoid a fallback to the
> development database.
> Sometimes we forget to do so and sometimes Tomcat lose it's context
> informations and we have a report that goes to the wrong database ...
>
> What would be cool is to have a report file that is exactly the same in
> development and in production. We would just specify a JNDI name in the
> datasource and a local JNDI serveur in the designer (something like this
> http://www.javaranch.com/codebarn.jsp) would serve the connexion.
>
> Best Regards,
>
> Tchule.
>
> PS : A side question, what is the purpose of the <xml-property
> name="designerValues"> tag in the rptdesign file. Is it some kind of
> cached result for the designer ? It is necessary in a production report
> engine ? Shouldn't it be in the rptconfig file ?
>
|
|
|
Powered by
FUDForum. Page generated in 0.06598 seconds
Home