---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14/#review5
---
Ship it!
I would suggest that we confine the usage of beans to config
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
Hi,
the protocol-ldap build in Gump has been failing for a while now. The
module depends on the Bouncastle JCE provider via
ReplicationTrustManager but its POM doesn't say so (this could be fixed
inside Gump but I don't want to 8-)
I guess that under normal circumstamces bcprov is pulled in as
On 2010-10-27 04:38:22, Kiran Ayyagari wrote:
I would suggest that we confine the usage of beans to config reader
only(even if they can be accessed publicly), cause we need to copy the
property values from bean to the corresponding real instance (e.x
DirectoryServiceBean -
Hi,
the protocol-ldap build in Gump has been failing for a while now. The
module depends on the Bouncastle JCE provider via
ReplicationTrustManager but its POM doesn't say so (this could be fixed
inside Gump but I don't want to 8-)
I guess that under normal circumstamces bcprov is pulled in as
Hi,
the protocol-ldap build in Gump has been failing for a while now. The
module depends on the Bouncastle JCE provider via
ReplicationTrustManager but its POM doesn't say so (this could be fixed
inside Gump but I don't want to 8-)
I guess that under normal circumstamces bcprov is pulled in as
On 2010-10-27, Emmanuel Lecharny wrote:
Just added it (http://svn.apache.org/viewvc?rev=1027963view=rev)
thank you
Stefan
An Empty cursor list blocks any other results
-
Key: DIRSERVER-1577
URL: https://issues.apache.org/jira/browse/DIRSERVER-1577
Project: Directory ApacheDS
Issue Type: Bug
Components: core
Hi guys,
I'm now trying to initialize the server after having read the
configuration, and I have some issues with the instanceLayout : it's not
possible right now to use this layout in the ConfigBuilder, as it's
associated with the DirectoryService, but as we haven't initialized it,
we can't
Hi again,
currently, the default working directory for DS is server-work, not
partitions, as defined in the InstanceLayout.
I'm all for using partitions, I find it way easier to remember, and on
line with the current configuration.
That raises some question, too :
- should we declare the
23 matches
Mail list logo
