May be David can give us some insight as to how these properties would be properly encoded in XBean terms.
I too have not tried it. Perhaps between Martin and David we can figure this out.
Thanks a lot!
I completely understand the configuration now.
About the peerReplicas property, you're right and I'm not sure either the given example would work.
Did anyone tested it?
But I think we can mix xbean and spring syntaxes to get something that will work and could look like:<replicationInterceptor><spring:property name="peerReplicas">
Pierre-ArnaudOn Fri, May 16, 2008 at 4:25 PM, Martin Alderson <Martin.Alderson@salfordsoftware.co.uk> wrote:
I haven't tried the new xbean form of the replication configuration -
I'm not really sure if anyone has!
I'm not sure if peerReplicas="instance_b@localhost:10392" will work,
since peerReplicas is actually a set. In my old style config I have:
Each ApacheDS replica needs to be given a unique and permanent case
insensitive ID. It should never change for a given ApacheDS instance
unless the backend data is wiped out (effectively giving you a fresh
install). I think that in the future we would want to make this
auto-generated by default to simplify the configuration. The replica ID
in your snippet is instance_a - the rest is just necessary cruft that we
should cut down in the future. The replica ID must match the regular
The replication service listens on the port specified with "serverPort"
for connections from other replicas. All the other replicas must be
specified with "peerReplicas". Each peer replica is specified with
Hope this helps,
>>> "Pierre-Arnaud Marcelot" <email@example.com> 16/05/2008 13:37 >>>
Thanks for your answers.
I'd like the configuration editor to be able to edit basic replication
settings for the replication interceptor.
Can I get a little explanation on what these lines doplease?
> <replicationConfiguration serverPort="10390"
> <replicaId id="instance_a"/>
Especially the serverPort, peerReplicas, replacaId attributes or
Thanks a lot.
On Thu, May 15, 2008 at 12:19 PM, Alex Karasulu <firstname.lastname@example.org>
> Hey Pierre,
> Sorry for taking so long to respond on this one.
> On Wed, May 14, 2008 at 5:04 AM, Pierre-Arnaud Marcelot
>> Hi again Alex,
>> On Tue, May 13, 2008 at 5:19 PM, Alex Karasulu
>>> $B!|(B It seems that each declared protocol must be referenced in the
>>>> 'apacheDS' bean. Am I right?
>>>> If yes, then if I want to enable the DNS server inside Apache DS,
>>>> need to uncomment the 'dnsServer' bean, add an 'id' to it and
>>>> in the 'apacheDS' bean?
>>> Yep you're right.
>> Are you sure about that...?
>> Actually, I had a closer look to the ApacheDS class
>> (org.apache.directory.server.configuration.ApacheDS) and I've not
>> dnsServer, kdcServer, changePasswordServer or ntpServer field. I
>> how Spring could make any association...
> Yeah it was there before. I may have an older version in mind.
> where we should keep a reference to all these protocol
> Must have changed when we did this XBean thing.
>> How do I enable these protocols? Maybe by setting an 'enable'
>> set to true to each protocol bean?
>> I think so but I'd need to look at the code. I think there's a
> method but it only gets or shoudl only get invoked or startup the
> when this enabled flag is set. I'd need to look at the logic there.