| Resource Resolution and Persistence [message #506] |
Mon, 13 December 2004 14:10  |
Eclipse User |
|
|
|
Originally posted by: csetera.spss.com
Hello,
I've spent a bit of time looking through the BIRT ROM documents and the
code that has been placed in CVS to this point. Excellent work thus
far. I am looking forward to seeing continued progress.
In the ROM Design Spec, section 7.5 "Resolving Resource References"
discusses the way that resources are located within a filesystem. I
also see that the DesignSession class supports the setting of an
instance of IFileLocator that appears to be used for resolving
references. Can I infer from this interface that by using a custom
IFileLocator implementation, one could use something other than a file
system for persistence of design and runtime resources? Will the
designer tool honor the IFileLocator instance in effect?
On a related note. Could I suggest adding a DesignSession constructor
that takes an IFileLocator instance in addition to the current Locale
constructor? It is likely that we will need this support and having a
default file locator created when we will never use it seems somewhat
wasteful... although not a huge problem.
Thanks,
Craig
|
|
|
| Re: Resource Resolution and Persistence [message #520 is a reply to message #506] |
Tue, 14 December 2004 21:31  |
 Paul Rogers
Messages: 152
Registered: July 2009 |
Senior Member |
|
|
Craig,
Thanks for your kind comments on the ROM documents.
The IFileLocator, as currently implemented, works only with file system
files. Its purpose is to customize the search path as needed for any given
installation. Extending the class for other storage mechanisms is possible
and is a good idea. Several code adjustments would be needed to provide a
user-defined way to open the "file" in a location other than the file
system.
On the other point, the DesignSession class is an "internal" class. The API
representation is SessionHandle in model.api. One gets a SessionHandle as
follows:
SessionHandle handle = DesignEngine.newSession( locale );
It is possible to extend the above to allow:
SessionHandle handle = DesignEngine.newSession( locale, fileLocator );
We've forwarded both enhancement requests to the development team.
Thanks,
- Paul
Paul Rogers
Actuate Corporation
Eclipse BIRT PSC
"Craig Setera" <csetera@spss.com> wrote in message
news:cpk7sr$4bn$1@www.eclipse.org...
> Hello,
>
> I've spent a bit of time looking through the BIRT ROM documents and the
> code that has been placed in CVS to this point. Excellent work thus far.
> I am looking forward to seeing continued progress.
>
> In the ROM Design Spec, section 7.5 "Resolving Resource References"
> discusses the way that resources are located within a filesystem. I also
> see that the DesignSession class supports the setting of an instance of
> IFileLocator that appears to be used for resolving references. Can I
> infer from this interface that by using a custom IFileLocator
> implementation, one could use something other than a file system for
> persistence of design and runtime resources? Will the designer tool honor
> the IFileLocator instance in effect?
>
> On a related note. Could I suggest adding a DesignSession constructor
> that takes an IFileLocator instance in addition to the current Locale
> constructor? It is likely that we will need this support and having a
> default file locator created when we will never use it seems somewhat
> wasteful... although not a huge problem.
>
> Thanks,
> Craig
|
|
|
Powered by
FUDForum. Page generated in 0.03117 seconds
] 
Search
Help
Register
Login
Home
