:
Hello,
I am putting together a collection of our own server's security details
and I was hoping to put some documentation for ApacheDS in it. I have been
unsuccessful in finding a PDF that has all of the specifications. Does one
exist?
Thanks,
Kevin
Hi Kevin,
I'm not sure which kind
On 12/5/11 2:27 PM, Kevin Hamilton wrote:
Yes that is what I was looking for, but I found the Advanced User's Guide
in PDF and was able to use some of that.
Be aware that this doco is *very* out of date :/
We have started to reorganize the complete documentation, and we even
are using a new
On Fri, 02 Dec 2011 17:46:24 +0100, Kevin Hamilton khamil...@umem.org wrote:Hello,I am putting together a collection of our own server's security details and I was hoping to put some documentation for ApacheDS in it. I have been unsuccessful in finding a PDF that has all of the specifications
Hello,
I am putting together a collection of our own server's security details and
I was hoping to put some documentation for ApacheDS in it. I have been
unsuccessful in finding a PDF that has all of the specifications. Does one
exist?
Thanks,
Kevin
On 18 oct. 2011, at 23:22, Emmanuel Lecharny wrote:
Hi,
On 9/18/11 10:20 PM, Stefan Seelmann wrote:
Hi guys,
I'd like to come back to our documentation issue:
- docu in confluence isn't versionized
- docbook in source control isn't easy to write
I did some research and found some
On 10/19/11 8:52 AM, Pierre-Arnaud Marcelot wrote:
On 18 oct. 2011, at 23:22, Emmanuel Lecharny wrote:
Hi,
On 9/18/11 10:20 PM, Stefan Seelmann wrote:
Hi guys,
I'd like to come back to our documentation issue:
- docu in confluence isn't versionized
- docbook in source control isn't easy
Hi,
On 9/18/11 10:20 PM, Stefan Seelmann wrote:
Hi guys,
I'd like to come back to our documentation issue:
- docu in confluence isn't versionized
- docbook in source control isn't easy to write
I did some research and found some interesting links [1][2][3]. I
setup an additonal user guide
Am 18.10.2011, 23:22 Uhr, schrieb Emmanuel Lecharny elecha...@gmail.com:
Hi,
On 9/18/11 10:20 PM, Stefan Seelmann wrote:
Hi guys,
I'd like to come back to our documentation issue:
- docu in confluence isn't versionized
- docbook in source control isn't easy to write
I did some research
the Docbook HTML and PDF output and it looks really really
good...
The syntax is the same we're already used to in Confluence (which
allows a lot of different styles) and the output looks perfect (like our
Docbook-written Apache Directory Studio documentation).
On my side, it is a big *+1*.
I
Thanks Stefan!
I'm checking out your PoC.
More to come...
Regards,
Pierre-Arnaud
On 18 sept. 2011, at 22:20, Stefan Seelmann wrote:
Hi guys,
I'd like to come back to our documentation issue:
- docu in confluence isn't versionized
- docbook in source control isn't easy to write
I did
Hi Stefan,
I generated the Docbook HTML and PDF output and it looks really really good...
The syntax is the same we're already used to in Confluence (which allows a lot
of different styles) and the output looks perfect (like our Docbook-written
Apache Directory Studio documentation).
On my
looks perfect (like our
Docbook-written Apache Directory Studio documentation).
On my side, it is a big *+1*.
I really love this solution. Simple, easy and convenient for everyone.
Do you know if it possible (and how) to link some text to another content
(another section, chapter or page
(which allows a
lot of different styles) and the output looks perfect (like our
Docbook-written Apache Directory Studio documentation).
On my side, it is a big *+1*.
I really love this solution. Simple, easy and convenient for everyone.
Do you know if it possible (and how) to link some text
really
good...
The syntax is the same we're already used to in Confluence (which allows a
lot of different styles) and the output looks perfect (like our
Docbook-written Apache Directory Studio documentation).
On my side, it is a big *+1*.
I really love this solution. Simple, easy
Hi guys,
I'd like to come back to our documentation issue:
- docu in confluence isn't versionized
- docbook in source control isn't easy to write
I did some research and found some interesting links [1][2][3]. I
setup an additonal user guide as PoC [4].
The idea is as follows:
1. Documenation
Hi Stefan,
no real time this week to look at the links you provided, wil do that when
I'll be back from vacations...
On Sun, Sep 18, 2011 at 10:20 PM, Stefan Seelmann
m...@stefan-seelmann.dewrote:
Hi guys,
I'd like to come back to our documentation issue:
- docu in confluence isn't
Hi guys,
I know that there's a lot of flux now in the code and that makes certain
initiatives a moving target when it comes to documentation. When you
actually finish writing the documentation the subsystem you are documenting
might have made a full 180 degree turn in direction. I'm frustrated
Unit testing documentation is out of date
-
Key: DIRSERVER-1282
URL: https://issues.apache.org/jira/browse/DIRSERVER-1282
Project: Directory ApacheDS
Issue Type: Improvement
Affects Versions: 1.5.4
numerous documentation TODOs
--
Key: DIRSERVER-550
URL: https://issues.apache.org/jira/browse/DIRSERVER-550
Project: Directory ApacheDS
Issue Type: Task
Affects Versions: 1.5.4
Reporter
Hi all
I just read following snippet in the user ML
The user documentation for Studio is
written in Docbook and under version control in SVN [2]. For the
server we also started to move the user documentation to Docbook and
SVN, but I'm not sure what's the state here. I think it needs
On 6/29/11 11:14 PM, Felix Knecht wrote:
Hi all
I just read following snippet in the user ML
The user documentation for Studio is
written in Docbook and under version control in SVN [2]. For the
server we also started to move the user documentation to Docbook and
SVN, but I'm not sure what's
Hi guys,
I have started to write the page about Bind/Unbind operations. It's
availbale on
https://cwiki.apache.org/confluence/display/DIRAPI/Binding+and+unbinding
Note that haven't wrote anything about SASL yet, it's a bit complex.
Again, writing this doco helped be to realize how buggy
require changes after M4 when we refactor the schema model to reduce
dependencies. I did not want you to needlessly waste your time there.
I understand, but don't worry too much. What I was doing focus more on
generalities than details, regarding the Schema documentation.
OK not going worry about
Hi Emmanuel,
I fixed one or two typos here and there.
The documentation looks very good. :)
Regards,
Pierre-Arnaud
On 5 avr. 2011, at 19:04, Emmanuel Lecharny wrote:
Hi guys,
I just finished to write the tutorial for the Attribute class :
https://cwiki.apache.org/confluence/display
On Sat, Apr 9, 2011 at 10:26 AM, Emmanuel Lecharny elecha...@gmail.com wrote:
Hi guys,
just to inform you that the Name and Entry packages classes have been
completely reviewed, and documentation for the classes is now completed.
I'm now moving to the Schema elements classes
On 4/12/11 12:42 AM, Alex Karasulu wrote:
On Sat, Apr 9, 2011 at 10:26 AM, Emmanuel Lecharnyelecha...@gmail.com wrote:
Hi guys,
just to inform you that the Name and Entry packages classes have been
completely reviewed, and documentation for the classes is now completed.
I'm now moving
reviewed, and documentation for the classes is now completed.
I'm now moving to the Schema elements classes and documentation, starting
with AttributeType.
It's always good to have doco on this but I think there may be some
changes in the next milestone. You might want to put this off a tiny
Hi guys,
just to inform you that the Name and Entry packages classes have been
completely reviewed, and documentation for the classes is now completed.
I'm now moving to the Schema elements classes and documentation,
starting with AttributeType.
I think we could cut a 1.0.0-M3 release
Hi guys,
I just finished to write the tutorial for the Attribute class :
https://cwiki.apache.org/confluence/display/DIRAPI/Attribute
The class itself has been cleaned up, with the useless methods removed,
and the Javadoc updated.
Please review...
I'm now dealing with the Entry class.
--
Hi guys,
I have created a new manual for the Ldap API, as we will need one as
soon as the LDAP-API will be out.
Here is a proposed structure for this manual, I probably forgot many
items, so feel free to add or reorganize it :
1.Content
2. Introduction
2.1 LDAP in a few words
2.2 Java
On Sat, Feb 12, 2011 at 1:50 AM, Emmanuel Lecharny elecha...@gmail.com wrote:
Hi guys,
I have created a new manual for the Ldap API, as we will need one as soon as
the LDAP-API will be out.
Thanks Emmanuel, this is a great start. I'm sure if we all start
filling in some parts it will fill out
[
https://issues.apache.org/jira/browse/DIRSHARED-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Karasulu closed DIRSHARED-83.
--
Add documentation and test coverage
---
Key
[
https://issues.apache.org/jira/browse/DIRSHARED-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Karasulu resolved DIRSHARED-83.
Resolution: Fixed
Add documentation and test coverage
Add documentation and test coverage
---
Key: DIRSHARED-83
URL: https://issues.apache.org/jira/browse/DIRSHARED-83
Project: Directory Shared
Issue Type: Sub-task
Reporter: Alex Karasulu
for this kind of documentation.
I have started to add/move content to
https://svn.apache.org/repos/asf/directory/apacheds-manuals/trunk
currently, in the pom.xml it states version 1.0.0-SNAPSHOT. How about
replacing it with the ApacheDS server version, in order to reflect for
which version
for this work!
So from now on please switch from confluence to the user-guide module
for this kind of documentation.
I have started to add/move content to
https://svn.apache.org/repos/asf/directory/apacheds-manuals/trunk
currently, in the pom.xml it states version 1.0.0-SNAPSHOT. How about
it in the apacheds module - if it's the
same version. How to release a bug fixed documentation for a specific
apacheds release?
I suggest having the major.minor version the same like apacheds and the
bugfix version a sequence.
For ads 1.5.x documentation version would start at 1.5.0.
Felix
Felix Knecht wrote:
If so I wonder why we can't have it in the apacheds module - if it's the
same version. How to release a bug fixed documentation for a specific
apacheds release?
Yes, currently it is side by side
https://svn.apache.org/repos/asf/directory/apacheds-manuals/trunk
https
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/29/10 21:18, Stefan Zoerner wrote:
Felix Knecht wrote:
If so I wonder why we can't have it in the apacheds module - if it's the
same version. How to release a bug fixed documentation for a specific
apacheds release?
Yes, currently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I finally finished taking over the guides from the wiki. It wasn't
always easy to guess the chapter and section sequences, anyway ...
Here's the first result:
Basic User Guide html:
http://people.apache.org/~felixk/basic-user-guide/html/book.html
On Mon, Aug 16, 2010 at 5:27 PM, Felix Knecht fel...@apache.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I finally finished taking over the guides from the wiki. It wasn't
always easy to guess the chapter and section sequences, anyway ...
np, now we have a common ground to work on
Hi Felix,
This is already looking very good. :)
Did you use any script to get and format the content from the wiki to the
DocBook format?
Thanks,
Pierre-Arnaud
On 16 août 2010, at 13:57, Felix Knecht wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I finally finished taking over the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/16/10 15:16, Pierre-Arnaud Marcelot wrote:
Hi Felix,
This is already looking very good. :)
Did you use any script to get and format the content from the wiki to the
DocBook format?
Nope :-(
I found some time and it's handmade (CP) - a
On 16 août 2010, at 15:28, Felix Knecht wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/16/10 15:16, Pierre-Arnaud Marcelot wrote:
Hi Felix,
This is already looking very good. :)
Did you use any script to get and format the content from the wiki to the
DocBook format?
On 8/16/10 3:33 PM, Pierre-Arnaud Marcelot wrote:
On 16 août 2010, at 15:28, Felix Knecht wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/16/10 15:16, Pierre-Arnaud Marcelot wrote:
Hi Felix,
This is already looking very good. :)
Did you use any script to get and format the
for this kind of documentation.
Thanks and regards
Felix
[1] http://directory.markmail.org/message/dp2jhvopfxp463f6
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxpWbsACgkQ2lZVCB08qHFfuQCfXHllX5RGZCL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/10 22:24, Alex Karasulu wrote:
This might be a bit off topic yet tangentially related but do any of you
guys know of a good WYSIWIG docbook editor that really, I mean really, works
right? IIRC, at some point docbook support was added to
On 8/12/10 4:23 PM, Felix Knecht wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/10 22:24, Alex Karasulu wrote:
This might be a bit off topic yet tangentially related but do any of you
guys know of a good WYSIWIG docbook editor that really, I mean really, works
right? IIRC, at
...@apache.org wrote:
Hi Felix,
first, thanks for starting this discussion.
yeap, thank you Felix for bringing out this dormant idea
On Mon, Aug 9, 2010 at 5:13 PM, Felix Knecht fe...@otego.com wrote:
If we want to switch documentation to docbook I think it's time to talk
about it, so we can get
On 8/11/10 4:09 PM, Felix Knecht wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I opened an issue [3], trying to summarize and split up into sub task.
Yup, saw the JIRAes :)
Thanks for dealing with this !
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
This might be a bit off topic yet tangentially related but do any of you
guys know of a good WYSIWIG docbook editor that really, I mean really, works
right? IIRC, at some point docbook support was added to open office but it
had some quirks. Anyone know if that improved as well?
--
Alex Karasulu
If we want to switch documentation to docbook I think it's time to talk
about it, so we can get documentation ready in parallel to the release
of a next release of the application.
It seems I'm not the only one playing around with docbook plugins.
I'm the same opinion like Stefan
On 09.08.2010 17:13, Felix Knecht wrote:
If we want to switch documentation to docbook I think it's time to talk
about it, so we can get documentation ready in parallel to the release
of a next release of the application.
It seems I'm not the only one playing around with docbook plugins
On 8/9/10 5:13 PM, Felix Knecht wrote:
If we want to switch documentation to docbook I think it's time to talk
about it, so we can get documentation ready in parallel to the release
of a next release of the application.
It seems I'm not the only one playing around with docbook plugins.
I'm
Hi Felix,
first, thanks for starting this discussion.
On Mon, Aug 9, 2010 at 5:13 PM, Felix Knecht fe...@otego.com wrote:
If we want to switch documentation to docbook I think it's time to talk
about it, so we can get documentation ready in parallel to the release
of a next release
documentation to docbook I think it's time to talk
about it, so we can get documentation ready in parallel to the release
of a next release of the application.
It seems I'm not the only one playing around with docbook plugins.
I'm the same opinion like Stefan, that the docbkx plugin [1] can
Hi,
I'm trying to update the documentation about Authz for 2.0 at the same
time I'm reviewing the code.
As it's not the most simpler part of the server, I think the
documentation must be realy wll written for our users to be able to
understand how the full system works.
Looking
as temporarilly been fixed (by removng the lnk) and the issue is
ôstponed to 2.0.0-RC2
No permission to read all documentation about ACL
-
Key: DIRSERVER-1467
URL: https://issues.apache.org/jira/browse/DIRSERVER
to 2.0.0-RC1
No permission to read all documentation about ACL
-
Key: DIRSERVER-1467
URL: https://issues.apache.org/jira/browse/DIRSERVER-1467
Project: Directory ApacheDS
Issue Type: Bug
Hi Frédéric!
Thanks for providing feedback. It seems to be a general problem, that
all of our example code is not displayed, e.g.
http://directory.apache.org/apacheds/1.5/141-changing-the-server-port-for-ldap.html
We generate the site from a Confluence wiki, perhaps the template
mechanism
keep the isue open so that these page is added in the near future.
No permission to read all documentation about ACL
-
Key: DIRSERVER-1467
URL: https://issues.apache.org/jira/browse/DIRSERVER-1467
No permission to read all documentation about ACL
-
Key: DIRSERVER-1467
URL: https://issues.apache.org/jira/browse/DIRSERVER-1467
Project: Directory ApacheDS
Issue Type: Bug
On 9/24/07, Alex Karasulu akaras...@apache.org wrote:
Hi all,
Here's a document I've been preparing for enabling the delegation of
authentication feature. It's
minimal for now until we flush out some of the ideas but any feedback is
going to be greatly
appreciated.
Overall I am finding
and refered to
the outdated documentation. I think it is better to have no
documentation than outdated documentation because the latter is very
frustrating for users.
Thoughts?
Kind Regards,
Stefan
update some pages where I know the current
state.
In the last days some users asked some simple questions and refered to
the outdated documentation. I think it is better to have no
documentation than outdated documentation because the latter is very
frustrating for users.
Thoughts?
Kind Regards
). I'd also update some pages where I know the current
state.
In the last days some users asked some simple questions and refered to
the outdated documentation. I think it is better to have no
documentation than outdated documentation because the latter is very
frustrating for users.
Thoughts
Hi,
I updated the Basic Users Guide [1], it should valid for ApacheDS 1.5.5 now.
I moved the page about the Spring configuration [2] to a Sandbox page,
so it isn't visible anymore. IMO such a page doesn't fit into a _Basic_
Users Guide. Additionally it is not up-to-date. If it gets updated I
Stefan Seelmann wrote:
Hi,
I updated the Basic Users Guide [1], it should valid for ApacheDS 1.5.5 now.
I moved the page about the Spring configuration [2] to a Sandbox page,
so it isn't visible anymore. IMO such a page doesn't fit into a _Basic_
Users Guide. Additionally it is not up-to-date.
Where to deploy generated documentation?
Key: DIR-248
URL: https://issues.apache.org/jira/browse/DIR-248
Project: Directory
Issue Type: Task
Reporter: Stefan Seelmann
Assignee
documentation or not.
If we decide to have only release documentation, the documentation could be
generated during the release and then being deployed to e.g.
people.apache.org:/www/directory.apache.org/documentation/{version}/, where it
can be linked from the directory site (just an idea).
Where
to 2.0.0-RC1
Unit testing documentation is out of date
-
Key: DIRSERVER-1282
URL: https://issues.apache.org/jira/browse/DIRSERVER-1282
Project: Directory ApacheDS
Issue Type: Improvement
Affects
documentation is out of date
-
Key: DIRSERVER-1282
URL: https://issues.apache.org/jira/browse/DIRSERVER-1282
Project: Directory ApacheDS
Issue Type: Improvement
Affects Versions: 1.5.4
Reporter
[
https://issues.apache.org/jira/browse/DIR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIR-222.
-
Correct Linux install documentation for ApacheDS 1.5
[
https://issues.apache.org/jira/browse/DIRSERVER-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1363:
-
Fix Version/s: 2.0.0-RC1
Update documentation for Spring configuration
FYI
I just submitted a patch (https://issues.apache.org/jira/browse/XBEAN-72) to have to documentation of the generated
schema also added to the generated reports when creating the 'mvn site'.
If the patch is accepted we may add this report in future as well :-)
Felix
[
https://issues.apache.org/jira/browse/DIRSERVER-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-1303.
closed
The documentation should mention that @ApplyLdifFiles annotation
this is fixed.
It now works like a charm... :)
Thanks Emmanuel!
The documentation should mention that @ApplyLdifFiles annotation is unused
--
Key: DIRSERVER-1303
URL: https://issues.apache.org
=rev
The documentation should mention that @ApplyLdifFiles annotation is unused
--
Key: DIRSERVER-1303
URL: https://issues.apache.org/jira/browse/DIRSERVER-1303
Project: Directory
Version/s: 1.5.5
The documentation should mention that @ApplyLdifFiles annotation is unused
--
Key: DIRSERVER-1303
URL: https://issues.apache.org/jira/browse/DIRSERVER-1303
for running tests.
The documentation should mention that @ApplyLdifFiles annotation is unused
--
Key: DIRSERVER-1303
URL: https://issues.apache.org/jira/browse/DIRSERVER-1303
The documentation should mention that @ApplyLdifFiles annotation is unused
--
Key: DIRSERVER-1303
URL: https://issues.apache.org/jira/browse/DIRSERVER-1303
Project: Directory
, but the part you are referring to has not been updated
yet :/
Work in progress...
Unit testing documentation is out of date
-
Key: DIRSERVER-1282
URL: https://issues.apache.org/jira/browse/DIRSERVER-1282
documentation is out of date
-
Key: DIRSERVER-1282
URL: https://issues.apache.org/jira/browse/DIRSERVER-1282
Project: Directory ApacheDS
Issue Type: Improvement
Affects Versions: 1.5.4
documentation ok? Should I close the issue ?
Unit testing documentation is out of date
-
Key: DIRSERVER-1282
URL: https://issues.apache.org/jira/browse/DIRSERVER-1282
Project: Directory ApacheDS
Issue Type
Saturday here tomorrow so I will be
trying this out then.
Thanks.
Unit testing documentation is out of date
-
Key: DIRSERVER-1282
URL: https://issues.apache.org/jira/browse/DIRSERVER-1282
Project: Directory
will update my code very soon and let you know if the guide works for me.
Thanks again!
Unit testing documentation is out of date
-
Key: DIRSERVER-1282
URL: https://issues.apache.org/jira/browse/DIRSERVER-1282
:
http://directory.apache.org/apacheds/1.5/42-using-apacheds-for-unit-tests.html
It will be be available in a couple of hours, as soon as the site is synced.
Unit testing documentation is out of date
-
Key: DIRSERVER-1282
[
https://issues.apache.org/jira/browse/DIRSERVER-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny reassigned DIRSERVER-1282:
Assignee: Emmanuel Lecharny
Unit testing documentation is out of date
effort.
Unit testing documentation is out of date
-
Key: DIRSERVER-1282
URL: https://issues.apache.org/jira/browse/DIRSERVER-1282
Project: Directory ApacheDS
Issue Type: Improvement
Affects
target :/
Update documentation for Spring configuration (Basic User Guide)
Key: DIR-221
URL: https://issues.apache.org/jira/browse/DIR-221
Project: Directory
Issue Type
Unit testing documentation is out of date
-
Key: DIRSERVER-1282
URL: https://issues.apache.org/jira/browse/DIRSERVER-1282
Project: Directory ApacheDS
Issue Type: Improvement
Affects Versions
On Thu, Oct 2, 2008 at 9:41 PM, Felix Knecht [EMAIL PROTECTED] wrote:
Hi all
Hi Felix,
I fiddled about using customized skins for maven site generation for the
studio documentation to see how it could look
alike using the same layout as the project page.
I saw your commits these last
Pierre-Arnaud Marcelot schrieb:
I'm curious to know how you integrate it in the build. Any hints on that ?
That's easy.
- Checkout and install locally the studio-skin from my sandbox.
- Apply patch below and run mvn site-deploy -Pintegration-tests and you
get the page generated in
Thanks, I'll give it a try ;)
Pierre-Arnaud
On Fri, Oct 3, 2008 at 9:34 AM, Felix Knecht [EMAIL PROTECTED] wrote:
Pierre-Arnaud Marcelot schrieb:
I'm curious to know how you integrate it in the build. Any hints on that
?
That's easy.
- Checkout and install locally the studio-skin from
Hi all
I fiddled about using customized skins for maven site generation for the studio
documentation to see how it could look
alike using the same layout as the project page.
Here's the result [1].
I know it's not everything working perfect and some large tables on the right
of the navigation
documentation TODOs
--
Key: DIRSERVER-550
URL: https://issues.apache.org/jira/browse/DIRSERVER-550
Project: Directory ApacheDS
Issue Type: Task
Affects Versions: 1.5.4
Reporter: Trustin Lee
. This has to be reviewed and cleaned.
Clear numerous documentation TODOs
--
Key: DIRSERVER-550
URL: https://issues.apache.org/jira/browse/DIRSERVER-550
Project: Directory ApacheDS
Issue Type: Task
hanging here.
Thanks,
Alex
On Mon, May 5, 2008 at 3:21 AM, Alex Karasulu [EMAIL PROTECTED] wrote:
David,
I've been spending an hour trying to find out how to do a map based
property with XBean and there is no documentation at all. Thought I'd find
some here but no go:
http
an hour trying to find out how to do a map based
property with XBean and there is no documentation at all. Thought
I'd find some here but no go:
http://geronimo.apache.org/xbean/using-xbean.html
I'm trying to figure out how to set a property on a bean that is a
Map. The Spring way
David,
I've been spending an hour trying to find out how to do a map based property
with XBean and there is no documentation at all. Thought I'd find some here
but no go:
http://geronimo.apache.org/xbean/using-xbean.html
I'm trying to figure out how to set a property on a bean
201 - 300 of 465 matches
Mail list logo
