We should be able to get Fortress released real soon now.  We have some
feature enhancements in the queue, but they will be held until after
Fortress 1.0 is released.

For all you early adopters, you will undoubtedly find a few things a
little different than when you started using Fortress.  A short list
follows:

* Queue.ROLE is not the proper way to get at the Command Sink.  The
  Event package uses a Sink, which is currently a Queue.  To help avoid
  surprises later, we made the change to use Sink.ROLE to get the
  Command Sink instead.

* To help our early adopters in the transition, we will log a message
  every time you lookup Queue.ROLE to remind you, and convert your
  lookup to Sink.ROLE.  Your code will continue to work, but you will
  get INFO level log messages every time you access the

* RoleManager is a deprecated concept introduced by the Excalibur
  Component Manager.  It has been replaced by using meta information
  for components.  The MetaInfoManager is much better at handling
  dependencies.

* Cyclic dependencies are caught at build and run times.  You will be
  given a log that shows the dependency tree with the cycle.  This
  feature ONLY works if you use meta information as opposed to the
  old roles info.

* The FortressRoleManager will go away when there are new releases of
  Excalibur Monitor, Excalibur DataSource, and Excalibur SourceResolve.
  Excalibur Store and Excalibur XMLUtil will have the meta info
  installed by default.

* Nested containers grab all the kernel components from the
  ServiceManager, not the Context.  The first versions of Fortress had
  this reversed.

* Initial support for Log4J integration in the ContextManager.  If you
  have a .xlog file with an attribute of version="log4j" or a root
  element like <log4j:configuration/> then Fortress will attempt to
  use the ConfigurableLog4JLoggerManager.  This is very experimental,
  so caveat emptor and please report any bugs.

I will get another release candidate to you guys as quickly as possible.


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



Reply via email to