Alan D. Cabrera wrote:
Stefano Bagnara wrote, On 4/5/2006 3:19 PM:
What type of IOC is used by XBeans ?
Is it based on the Service Locator pattern like Avalon or Dependency
Injection? In the latter case, what DI type? Constructor, Setter or
Interface injection?
Constructor and Setter DI.
Currently James components uses a mix of Service Locator and Interface
injection.
In fact the "Service locator" pattern is activated by "Interface
injection" by the "Serviceable" interface that provide a
"ServiceManager" that provide dependencies lookup.
Lifecycle, Configuration, Logging and Context are provided via Interface
Injection to components implementing the specific interfaces (Startable,
Disposable, Configurable, LogEnabled, Contextualizable, etc)
How is the assembly declared? XML / Naming conventions / Annotations /
Other?
XML
Can XBean split the configuration in 2 multiple files?
We currently have assembly.xml to declare how the component
dependencies/wiring and config.xml to fill in configurations for that
components.
I can't find much docs/informations about it.
http://www.xbean.org/Home has some info.
I can't find many informations about what xbean-kernel is and
xbean-server is, how to use them, and more.
I've just downloaded sources from here:
http://svn.xbean.org/trunk/
Is this the current official/updated repository? I see no changes after
february.
Phoenix currently provide this services to James:
1) Lifecycle (start / dispose / stop)
2) Dependency management (Service wiring)
3) Centralized Services configuration
4) Centralized Logging management
5) Multiple James instances in a single JVM
Does XBean provide all of this?
I would like to have more informations on XBeans and your plan and
know the opinion of the James PMC about maven2 and xbeans before to
tell my preference on the sandbox location.
Cool. It seems like there are three efforts that we are discussing.
XBean, Maven 2, and cornerstone conversion.
If you're going to try any of those steps anyway then we just need to
discuss (vote) wether give you repository access to work on a public
sandbox.
If you expect any of this to be included in the official James
distribution we should split the conversation for each change (XBean /
Maven2) and analyze the pros/cons of the change proposed and vote about
this.
Stefano
PS: Would the usage of Maven2 simplify the introduction of an installer
similar to the one used in the Apache Directory project (InnoSetup)? I
think James windows distribution should have a similar installer/service
wrapper.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
