Prevent report designs referencing report libraries by absolute path? [message #213803] |
Wed, 24 January 2007 20:51 |
Eclipse User |
|
|
|
Originally posted by: birt.hodges.id.au
Hi,
I'm using BIRT 2.1.1. I'm deploying my reports and the .rptlibrary they
reference to a J2EE server. I would like the reports not to specify any
absolute path to the library, because the path will be completely
different in my design environment from what it will be in the deployed
environment.
If I edit the XML of a .rptdesign file I find that I can make this work.
In other words, I can change
<property name="fileName">D:\lots\of\paths\my_library.rptlibrary</property >
to
<property name="fileName">my_library.rptlibrary</property>
(under the <list-property name="libraries"> section of the .rptdesign file)
and that seems to work fine, as far as running the report on the server
goes, if I put the .rptlibrary in the same directory as the .rptdesign.
I'm sure the correct solution can't involve editing the XML though!
However the report designer seems to always want to store an abolute path.
That the deployed environment may be a completely different platform,
seems an obvious enough problem, so I'm assuming I'm doing something
wrong?
But it seems that you must publish a library in order to see it in the
library explorer (and thus be able to drag elements such as embedded
images into your report designs), and it seems also that you cannot
specify a relative path for the Resource Folder where they are published
to. (Well, you can, but it ends up being relative to your eclipse
installation, and is still saved in the report design as an absolute path,
to boot!)
All I could find when googling about this was Bugzilla 116786 at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=116786 - which I think
refers to the same problem and seems to indicate it is solved, but I don't
know how to reproduce the solution.
Any advice would be much appreciated!
-Rob
|
|
|
|
Powered by
FUDForum. Page generated in 0.03567 seconds