Search:

If you use a ContextMapper instead of an AttributesMapper in your search, you'll have access to a DirContextOperations in your mapFromContext method (you must cast the Object yourself). The...

Have you looked at the web site?

http://static.springsource.org/spring-ldap/site/

There is a reference manual that might give you some information:
...

The PersonDao interface is part of the sample code that is included in a particular release download:
...

A custom authentication provider with @Autowired dependencies doesn't get the dependencies wired. The problem seems to be the <debug /> element. I have a small sample project that demonstrates the...

I have fixed the incorrect versions, and also added relativePath to the poms that were missing it. This should now work from trunk:



$ mvn install -Psamples

OK, I see it now. Still wrong versions in samples. I will fix this as soon as possible.

As far as I know, the problem with incorrect versions in the samples poms exists only in the released version 1.3.1. If so, there should be no reason to do this on trunk. When I pointed to trunk, I...

No, with project root I really mean the project root: https://src.springframework.org/svn/spring-ldap/trunk/

Jetty is a web server, not an LDAP server. It runs the article sample, which is a web app. Spring LDAP works on any JNDI-compliant LDAP server. The sample uses an in-memory version of ApacheDS, which...

I think your pasted stacktrace is corrupt. Some lines are incomplete. Try placing
tags around it.

Try this from the project root:



mvn versions:update-child-modules
mvn versions:commit -Psamples,sandbox,sunone,openldap
mvn install -DskipTests -Psamples


The first line will fix the...

This, I believe, is the result of us missing to include the samples in the release procedure. The version in the samples POMs were never updated to 1.3.1.RELEASE, so they're still at...

Read the announcement on the SpringSource.org site.

Nested transactions are not supported by Spring LDAP compensating transactions. I assume that this would be the case here.

I take it that there are no immediate problems that need to be fixed before release. Anyone needs more time to test? Or are you just waiting eagerly for the release and wish that I shut up and just...

I'm now at a point where I can say that 1.3.1 is pretty much ready for release. If our beloved community could take the framework for a last spin, that would be great.

Things to check, depending...

It's probably getting a new connection on the second run, thus loosing the cookie. When I test PagedResults, I configure the context source like this:



<bean id="contextSource"...

And I'm happy to say that the snapshot directory has been cleaned of old stuff. It has brand new builds there now, including the ODM mapping framework and the LDIF parsing framework.

I'm working on finalizing 1.3.1 for release within a few weeks, if everything goes according to plan. Sorry for being quiet, guys. Overwhelmed by life. :)

Searching for the error message you got, the best match seems to be a Directory Proxy Server (DPS) that prohibits controls unless explicitly allowed using the DPS property 'allowed-ldap-controls'.
...

Is there an easier way to retrieve multiple entries?

Yes.

http://static.springsource.org/spring-ldap/docs/1.3.x/reference/html/basic.html#basic-searches...

Which directory server do you use?

OK, I get it. It was the "for a dn" part that fooled me.

To my knowledge, there is no concept of batch processing in JNDI. Compare with batch insert in JDBC, where the goal is to minimize the...

That's like saying you want multiple rows for a primary key in a relational database. Not possible. You don't mean multiple values for an attribute, by any chance? If so, it's described in the...

My first impression is that this is the same symptom as when you manually create a ContextSource and forget to call afterPropertiesSet.

I just had a quick look, but it seems you override...