> -----Original Message-----
> From: Giampaolo Tomassoni [mailto:[EMAIL PROTECTED]
>
> From these "Developing" pages it seems that 'data' is something has few to
> do
> with Avalon. It seems that Components supply the enterprise/business
> methods,
> which may eventually accept/result in data. As a result, every effort in
> maintain data instances unique would be from the user application. It
> seems
> to me that Avalon has no support for primary-key/data bindings, in
example.
> 
> Also, I found few words about transactional support in Avalon. It seems to
> me
> that it is not possible to enforce a Commit-All-Or-Rollback-All design to
> Avalon Components, at least with the current design of connections and
> components relationships.
> 
> I'm asking this because I have to face the design of an application which
> strongly relies on a db as a data repository. I was first tempted to use a
> J2EE container system (OpenEJB) to develop it, next I 'discovered' the
> Avalon
> Project and I was wondering about the limits of both frameworks.
> 
> Thank you,

Hello!

None of the current Avalon containers provide built in transactional
support.  You could certainly design an extension to support transactions
though. 

Avalon provides a more low-level framework than what you generally find in
the J2EE specifications like EJB's.  In other words, someone might use
Avalon to _build_ something like OpenEJB.  However, that doesn't mean that
Avalon is out of the question for your project.  In fact, Avalon may provide
a _better_ design.

While slightly dated, you may want to look at this:
      http://wiki.apache.org/avalon/AvalonYouMakeTheDecision
Which compares Avalon to J2EE.

For starting out, Avalon Merlin provides a number of examples and tutorials:
http://avalon.apache.org/merlin/starting/index.html

For an Avalon based Application Server, see EOB: Enterprise Object Broker:
http://enterpriseobjectbroker.org/

If you have any other more specific questions, please ask!

J. Aaron Farr
  SONY ELECTRONICS
  DDP-CIM
  (724) 696-7653

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to