Hi Rahul,
rahul.soa wrote:
> Hello Stefan,
>
> This time build was successful but the old problem still persists :(
> (i.e. failure in integration tests). * The build was successful before
> as well but the main problem was with running tests.
>
> message="org.apache.directory.shared.ldap.schem
[
https://issues.apache.org/jira/browse/DIRSTUDIO-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seelmann resolved DIRSTUDIO-335.
---
Resolution: Fixed
Fix Version/s: 1.4.0
Assignee: Stefan Seelmann
R
Support for parentOfEntry userClass in ACI Editor
-
Key: DIRSTUDIO-474
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-474
Project: Directory Studio
Issue Type: New Feature
Compo
Here's my take on this. I subclassed DefaultDirectoryService, then overrode
startup(). In startup, I first call super.startup() to ensure that the
directory is properly initialized, then I populate the schema directly,
using the underlying API.
Doing this is a little involved, but it works quite
Error java.lang.reflect.InvocationTargetException with IPv6 Addresses
-
Key: DIRSTUDIO-475
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-475
Project: Directory Studio
Hi guys,
I have no idea why we are stuck with in
the server.xml file instead of . I guess that it's
because we moved to xbeans quickly, and didn't finished the work one
year ago.
What about using ? It's just a matter of adding
'element="directoryService"' in the DefaultDirectoryService c
[
https://issues.apache.org/jira/browse/DIRSTUDIO-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682831#action_12682831
]
Stefan Seelmann commented on DIRSTUDIO-475:
---
You need to use square brackets a
Hello Devs,
I will work on the LDAP proxy project (*Develop a LDAP proxy GUI
*[1]*) *for my gsoc project [2], I got to learn from Emmanuel that
there is already
some work done in this area so am wondering from where I can import the code
of LDAP proxy as I dont find it in the present studio code?
- Documentation : This is also an something we must deliver.
Documentation is not only good for our users, it's also good for us,
as developpers, because writtng documentation helps to see where the
API is not consistent.
Main problem is the configuration, which has changed with each minor
Hi Stefan,
I did everything from the beginning:
1. deleted repository from ~/.m2/repository
2. svn co http://svn.apache.org/repos/asf/directory/studio/trunk studio
3. cd studio
4. svn up MAVEN_OPTS="-Xmx256m" mvn clean install
5. update the /.m2/settings.xml with the eclipse home
6. MAVEN_
On Mar 17, 2009, at 4:07 PM, Emmanuel Lecharny wrote:
- Documentation : This is also an something we must deliver.
Documentation is not only good for our users, it's also good for
us, as developpers, because writtng documentation helps to see
where the API is not consistent.
Main probl
Ok. Today, I spent something like 5 hours trying to get some new
classes injected into LdapService, and make them work nicely with
xbeans. So far, it's a plain failure.
And your requests for help and complaints about specific problems are
where?
It was a long time ago but 5 hours was the s
Emmanuel Lecharny wrote:
That's the main issue... Xbeans is trying to alleviate the pain it is to
manipulate class names in a Spring file. As I already said, it creates a
decoupling which is painfull, as you have no clue about what is what in
the Spring file when you have decoupled those two p
Graham Leggett wrote:
Emmanuel Lecharny wrote:
That's the main issue... Xbeans is trying to alleviate the pain it is
to manipulate class names in a Spring file. As I already said, it
creates a decoupling which is painfull, as you have no clue about
what is what in the Spring file when you hav
Emmanuel Lecharny wrote:
The name of the principle you are currntly violating by using Spring
is called the "Don't repeat yourself" principle:
http://en.wikipedia.org/wiki/Don%27t_repeat_yourself
By storing class names in two places (the Java class file, and the
Spring bean definition XML fi
Graham Leggett wrote:
That said, both Fedora and OpenLDAP use the DIT for config, so that
may be an XML free option :)
FDS doesn't exactly use the DIT. We had the same argument that you're
having, in 1997 or so, and
decided to write an 'ldif back end' for the server, specifically for
config (th
The trouble with properties is that they are not always that good at
expressing hierarchies of concepts (something XML does well), and if
you accidently spell a property wrong, that property silently
vanishes, leaving the end user staring at the config for hours trying
to figure out why it
David Boreham wrote:
Graham Leggett wrote:
That said, both Fedora and OpenLDAP use the DIT for config, so that
may be an XML free option :)
FDS doesn't exactly use the DIT. We had the same argument that you're
having, in 1997 or so, and
decided to write an 'ldif back end' for the server, specif
I've got to say it :
JUST SAY NO TO SPRING.
(I can't remember ever using all-caps before in a post, during my 25
years using e-mail..)
Emmanuel Lecharny wrote:
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'ldapService' defined in URL
[file:/home/elecharny/apacheds/replication/apacheds/server-xml/target/classes/serverReplication.xml]:
Cannot create inner bean '(inner bean)' of type
[o
David Boreham wrote:
Graham Leggett wrote:
That said, both Fedora and OpenLDAP use the DIT for config, so that
may be an XML free option :)
FDS doesn't exactly use the DIT. We had the same argument that you're
having, in 1997 or so, and
decided to write an 'ldif back end' for the server, specif
21 matches
Mail list logo
