Steve Gardell wrote:
>
> We have an application that deals with a large
> quantity of multi-media data associated with a
> relational database. The multi-media files are stored
> directly on the file system. Conceptually they are
> columns in a database schema; however the reality
> is that relational databases are not really "up the task"
> of managing this data, so the relational database
> contains pathnames.
>
> We would like to manage these associated files via
> EJB. Basically this means creating, deleting, and
> returning pathnames. The EJB server would (at
> least typically) never be concerned with the contents
> of the files.
>
> We understand that the spec prohibits this but are
> at a loss to understand why. They are really just an
> element of our persistent store... We are hesitant to
> just cheat since we understand that access to file
> system might be "yanked" at any time.
One way round this problem is to write yourself some helper classes to access
the file system, then instruct your application server to load these classes
using the server's own class loader. This will ensure that it is not subject to
the same restrictions as an EJB. It is server-specific how to this - read your
server documentation.
What you must NOT do is package this class in the ejb jar, as this makes the
class, in effect, part of the EJB.
Ian McCallion
Alexis Systems Limited
Romsey, UK
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
