B E N J A M I N | BROLL wrote:
>
> > I think Benjamin should extend Rickard's proposition with Helper
> > classes. Just
> > like you can have a bunch of "external" (server-classloader-loaded) helper
> > classes, you could have similar classes that parse, load and store an XML
> > file.
>
> Right, that's what I thought of. But since I don't want to write a tool like
> XML-Spy, which is able to abstract the XML-source from the editing person
> and gives a clearer picture of the document, I just want to present the
> source of the XML which should be manipulated. Thus I would have to retrieve
> and return plain text and _not_ manipulate the internal JDOM representation
> of the document.
>
> So in the end the bean would have to have methods for directly storing and
> loading documents thus somehow serving as a proxy for the client to the
> files - and I'm not sure whether I should implement the system this way ...
My simple idea is that you create a table in a database, where the key is the
"filename" of the XML file you want to access. You surround your tools by a
command file which automatically copies the file into a row of the database, and
you use JDBC to extract the "file" from the database. Features:
- no complex middleware coding
- scaleable
- secure
- reliable
- good performance
- portable
Honestly, you'll spend far longer than you want writing the "helper" classes
initially and "improving" them later to meet all the needs you seem to have.
Ian McCallion
Alexis Systems Limited
===========================================================================
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".
