Hi all EJB gurus,
sorry for any incovenience if my question seems stupid but I've got a
question dealing with design of my EJB (sessions):
I'd like to open my business services to as many apps as possible so I
think that getting views of my entities using XML descriptions could be
a great
way for this. SO I thought that session beans could expose such
services offering XML descriptions of underlying entities using ids or
names.
But the little confusing (for me) EJB specs tends to convince me that my
session bean should not handle IO streams.
Note:
One of my beans should provide a file (it is its only service, that 's
its job!!), is it a design fault ?
Transactions & concurrency are not a problem for this bean, is it
possible ? It seems that some containers could prevent me accessing to
local Filessytem.
All clues welcomed!!!
Am I wrong . Has someone implemented such design ? For deployment
reasons I'd like to avoid using a servlet engine for such service....
I'd like to use Castor/XML Java/XML mapping tier for such job, in order
to avoid coding writeToXML() methods.
All experience & feedback welcomed
Cheers
Jerome
PS:
excsue me for my poor english written
===========================================================================
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".
