[
https://issues.apache.org/jira/browse/DIRSERVER-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1578:
-
Fix Version/s: 2.0.0-RC1
The index values must have been normalized before
[
https://issues.apache.org/jira/browse/DIRSERVER-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1584:
-
Fix Version/s: 2.0.0-RC1
document how to limit the available ciphers for
[
https://issues.apache.org/jira/browse/DIRSERVER-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1587:
-
Affects Version/s: 1.5.7
Fix Version/s: 2.0.0-RC1
Shutdown fails
[
https://issues.apache.org/jira/browse/DIRSERVER-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1575:
-
Fix Version/s: 2.0.0-RC1
AbstractLdapTestUnit fails with more than one
Hi guys,
I'm resuming the APs implementation. I have had a new idea this morning
about the best way to handle them.
Currently, we had devised about too possible options
1) Processing the entries while adding a new AP
The idea is that when we add a new AP (or delete an existing one, or
Hi Emmanuel,
Interesting idea!
A great combination of both original solutions into a single one...
I like the idea of lazy evaluation and the fact that the administrator can, if
he wants it, go back to solution #1 by simply searching (objectClass=*) under
the newly created/updated AP after it
[
https://issues.apache.org/jira/browse/DIRSHARED-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-70:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
Bug when switching
[
https://issues.apache.org/jira/browse/DIRSHARED-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-61:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
Cleaning
[
https://issues.apache.org/jira/browse/DIRSHARED-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-59:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
Replace public
[
https://issues.apache.org/jira/browse/DIRSHARED-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-34:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
[
https://issues.apache.org/jira/browse/DIRSHARED-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-54:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
Replace all the
[
https://issues.apache.org/jira/browse/DIRSHARED-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-58:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
Interface
[
https://issues.apache.org/jira/browse/DIRSHARED-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-28:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
Need a feature like
[
https://issues.apache.org/jira/browse/DIRSHARED-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-4:
--
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
RDN length and start
[
https://issues.apache.org/jira/browse/DIRSHARED-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-71:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
[
https://issues.apache.org/jira/browse/DIRSHARED-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-46:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
The
[
https://issues.apache.org/jira/browse/DIRSHARED-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-63:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
LDIFEntry does not
[
https://issues.apache.org/jira/browse/DIRSHARED-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-40:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
DN parser, LdapDN,
[
https://issues.apache.org/jira/browse/DIRSHARED-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-60:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
Equality matching
[
https://issues.apache.org/jira/browse/DIRSHARED-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-36:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
Attribute type
[
https://issues.apache.org/jira/browse/DIRSHARED-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-68:
---
Fix Version/s: (was: 0.9.20)
1.0.0-RC1
schema extensions
Hi Emmanuel,
the lazy evaluation sounds interesting, great idea.
Just to clarify:
You are talking only about the process to determine which AP and ACIs
are applied to an entry (which is done by evaluating all AP subtree
specifications), right?
The concrete evaluation of the ACI must always be
On 12/13/10 1:28 PM, Stefan Seelmann wrote:
Hi Emmanuel,
the lazy evaluation sounds interesting, great idea.
Just to clarify:
You are talking only about the process to determine which AP and ACIs
are applied to an entry (which is done by evaluating all AP subtree
specifications), right?
[
https://issues.apache.org/jira/browse/DIRSHARED-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSHARED-65.
Resolution: Fixed
Fixed http://svn.apache.org/viewvc?rev=1045161view=rev
Hi dev,
our current partition implementations use different fields/methods to
configure the location where partition data is persisted:
- BTreePartition defines a 'partitionDir' with getter/setter, this is
used by the JdbmPartition
- AbstractLdifPartition defines a 'workingDirectory' with
Hi guys,
we currently have a shared-ldap-jndi module containing two classes :
- JndiUtils
- UniversalContextFactory
The fist one of those class is duplicated in shared-ldap, as we need
many of the methods it contains for the SP sub-system. We can't remove
it from shared-ldap, as
On 12/13/10 4:39 PM, Stefan Seelmann wrote:
Hi dev,
our current partition implementations use different fields/methods to
configure the location where partition data is persisted:
- BTreePartition defines a 'partitionDir' with getter/setter, this is
used by the JdbmPartition
-
On Mon, Dec 13, 2010 at 4:44 PM, Emmanuel Lecharny elecha...@gmail.com wrote:
Hi guys,
we currently have a shared-ldap-jndi module containing two classes :
- JndiUtils
- UniversalContextFactory
The fist one of those class is duplicated in shared-ldap, as we need many of
the methods it
On Mon, Dec 13, 2010 at 5:04 PM, Emmanuel Lecharny elecha...@gmail.com wrote:
On 12/13/10 4:39 PM, Stefan Seelmann wrote:
Hi dev,
our current partition implementations use different fields/methods to
configure the location where partition data is persisted:
- BTreePartition defines a
On 12/13/10 5:09 PM, Stefan Seelmann wrote:
On Mon, Dec 13, 2010 at 4:44 PM, Emmanuel Lecharnyelecha...@gmail.com wrote:
Hi guys,
we currently have a shared-ldap-jndi module containing two classes :
- JndiUtils
- UniversalContextFactory
The fist one of those class is duplicated in
This may be something we can just toss. Also shared-ldap is getting
seriously huge: we need to figure out something with respect to this before
a 1.0.
Alex
On Mon, Dec 13, 2010 at 6:28 PM, Emmanuel Lecharny elecha...@gmail.comwrote:
On 12/13/10 5:09 PM, Stefan Seelmann wrote:
On Mon, Dec 13,
On Mon, Dec 13, 2010 at 5:39 PM, Stefan Seelmann seelm...@apache.orgwrote:
Hi dev,
our current partition implementations use different fields/methods to
configure the location where partition data is persisted:
- BTreePartition defines a 'partitionDir' with getter/setter, this is
used by
On 12/13/10 5:53 PM, Alex Karasulu wrote:
This may be something we can just toss. Also shared-ldap is getting
seriously huge: we need to figure out something with respect to this before
a 1.0.
Yeah, there is some reorganization to do. Right now, we have 7 remaining
issues for shared, I'm
On Mon, Dec 13, 2010 at 12:41 PM, Emmanuel Lecharny elecha...@gmail.comwrote:
Hi guys,
I'm resuming the APs implementation. I have had a new idea this morning
about the best way to handle them.
Currently, we had devised about too possible options
1) Processing the entries while adding a
On 12/13/10 5:55 PM, Alex Karasulu wrote:
On Mon, Dec 13, 2010 at 5:39 PM, Stefan Seelmannseelm...@apache.orgwrote:
Thoughts?
+1
I thought about making the partitionPath a URL but just saw your email.
Consistency is good but why is using a URL so complex?
I have the same question. Using
On Mon, Dec 13, 2010 at 7:00 PM, Alex Karasulu akaras...@apache.org wrote:
To think this through let me just for the record go through the way search
interacts with the administrative model subsystem. I won't consider
base/object scoped searches.
(1) On the way into the server a search
On Mon, Dec 13, 2010 at 6:59 PM, Emmanuel Lécharny elecha...@apache.orgwrote:
On 12/13/10 5:53 PM, Alex Karasulu wrote:
This may be something we can just toss. Also shared-ldap is getting
seriously huge: we need to figure out something with respect to this
before
a 1.0.
Yeah, there is
+1
Regards,
Pierre-Arnaud
On 13 déc. 2010, at 17:09, Stefan Seelmann wrote:
On Mon, Dec 13, 2010 at 4:44 PM, Emmanuel Lecharny elecha...@gmail.com
wrote:
Hi guys,
we currently have a shared-ldap-jndi module containing two classes :
- JndiUtils
- UniversalContextFactory
The fist one
On Mon, Dec 13, 2010 at 6:00 PM, Emmanuel Lecharny elecha...@gmail.com wrote:
On 12/13/10 5:55 PM, Alex Karasulu wrote:
On Mon, Dec 13, 2010 at 5:39 PM, Stefan
Seelmannseelm...@apache.orgwrote:
Thoughts?
+1
I thought about making the partitionPath a URL but just saw your email.
On 12/13/10 6:00 PM, Alex Karasulu wrote:
On Mon, Dec 13, 2010 at 12:41 PM, Emmanuel Lecharnyelecha...@gmail.comwrote:
Hi guys,
I'm resuming the APs implementation. I have had a new idea this morning
about the best way to handle them.
Currently, we had devised about too possible options
1)
On 12/13/10 6:25 PM, Stefan Seelmann wrote:
On Mon, Dec 13, 2010 at 6:00 PM, Emmanuel Lecharnyelecha...@gmail.com wrote:
On 12/13/10 5:55 PM, Alex Karasulu wrote:
On Mon, Dec 13, 2010 at 5:39 PM, Stefan
Seelmannseelm...@apache.orgwrote:
Thoughts?
+1
I thought about making the
On Mon, Dec 13, 2010 at 7:35 PM, Emmanuel Lecharny elecha...@gmail.comwrote:
On 12/13/10 6:25 PM, Stefan Seelmann wrote:
On Mon, Dec 13, 2010 at 6:00 PM, Emmanuel Lecharnyelecha...@gmail.com
wrote:
On 12/13/10 5:55 PM, Alex Karasulu wrote:
On Mon, Dec 13, 2010 at 5:39 PM, Stefan
On 12/13/10 6:00 PM, Alex Karasulu wrote:
On Mon, Dec 13, 2010 at 12:41 PM, Emmanuel Lecharnyelecha...@gmail.comwrote:
Hi guys,
I'm resuming the APs implementation. I have had a new idea this morning
about the best way to handle them.
Currently, we had devised about too possible options
1)
[
https://issues.apache.org/jira/browse/DIRSHARED-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSHARED-67:
---
Fix Version/s: (was: 1.0.0-RC1)
1.0.0
It will be a bit
[
https://issues.apache.org/jira/browse/DIRSERVER-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12970944#action_12970944
]
Emmanuel Lecharny commented on DIRSERVER-1556:
--
This is nothing close the
On 12/13/2010 06:35 PM, Emmanuel Lecharny wrote:
On 12/13/10 6:25 PM, Stefan Seelmann wrote:
On Mon, Dec 13, 2010 at 6:00 PM, Emmanuel
Lecharnyelecha...@gmail.com wrote:
On 12/13/10 5:55 PM, Alex Karasulu wrote:
On Mon, Dec 13, 2010 at 5:39 PM, Stefan
Seelmannseelm...@apache.orgwrote:
46 matches
Mail list logo
