coheigea merged PR #95:
URL: https://github.com/apache/directory-server/pull/95
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
coheigea opened a new pull request, #95:
URL: https://github.com/apache/directory-server/pull/95
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To
coheigea merged PR #41:
URL: https://github.com/apache/directory-ldap-api/pull/41
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
coheigea opened a new pull request, #41:
URL: https://github.com/apache/directory-ldap-api/pull/41
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To
, and the LDAP API handler
was then tryingh to send a NoticeOfDisconnect message to the remote
peer, which obviously ended in another exception to be thrown
(ByteBuffer missing method), and voilà, infinite loop.
On 11/08/2022 03:29, Jonathan Valliere wrote:
Was the fix in Mina or Directory
Was the fix in Mina or Directory?
On Wed, Aug 10, 2022 at 5:34 AM Emmanuel Lécharny
wrote:
> I confirm. I built the LDAP API with Java 11 targetting Java 8, but it's
> not enough.
>
> Fixed in trunk.
>
> On 30/07/2022 10:23, Emmanuel Lécharny wrote:
> > Seems like it
I confirm. I built the LDAP API with Java 11 targetting Java 8, but it's
not enough.
Fixed in trunk.
On 30/07/2022 10:23, Emmanuel Lécharny wrote:
Seems like it's an issue with a mixed Java version being used: the lib
built with Java 11 and running tests in Java 8, or something like that.
builds fine with Java 8.
I will create a new LXDAP API release.
On 10/08/2022 07:20, Emmanuel Lécharny wrote:
Correction, this is not a MINA issue, as we built it with the proper tag:
java-8-compilation
[9,)
8
...
We don't have
I confirm. If I add the missing profile in LDAP API pom.xml, Apache DS
builds fine with Java 8.
I will create a new LXDAP API release.
On 10/08/2022 07:20, Emmanuel Lécharny wrote:
Correction, this is not a MINA issue, as we built it with the proper tag:
java-8-compilation
Correction, this is not a MINA issue, as we built it with the proper tag:
java-8-compilation
[9,)
8
...
We don't have such a profile in the LDAP API, and we need to get it fixed...
On 10/08/2022 07:11, Emmanuel Lécharny wrote:
Ok, I
Ok, I think I found the reason.
There were some changes made in the ByteBuffer class in Java 9 (and
forward) which leads to some error in Apache DS code.
In MINA, I get an exception like:
java.lang.NoSuchMethodError: java.nio.ByteBuffer.mark()Ljava/nio/ByteBuffer;
which is badly handled
Seems like it's an issue with a mixed Java version being used: the lib
built with Java 11 and running tests in Java 8, or something like that.
Still investigating.
On 30/07/2022 10:03, Emmanuel Lécharny wrote:
Hi,
I'm currently investiagting some infinite loop in Apache DS when setting
up
Hi,
I'm currently investiagting
some infinite loop in Apache DS when setting up a LDAPS
server. I have no idea what's going on atm - but I will keep
you posted.
Here is the trace I get
when doing a kill -3:
Done !
The LDAP API and Server are now using MINA 2.2.1. I have also bumped up
dependencies and plugins, starting from the direcotory-project project.
All is committed.
On 25/07/2022 12:13, Emmanuel Lécharny wrote:
Good news: MINA 2.2.1 is out and I just ran the tests against this
version
Good news: MINA 2.2.1 is out and I just ran the tests against this
version, the LDAP API and LDAP Server are passing green.
I'm pushing the uopdated code !
On 21/07/2022 09:03, Emmanuel Lécharny wrote:
Hi,
some quick update:
there was an error in the MINA 2.2.0 MANIFEST, failing the OSGi
Hi,
some quick update:
there was an error in the MINA 2.2.0 MANIFEST, failing the OSGi tests. I
had to figure that out (took me half a day) and fix it. A vote for MINA
2.2.1 is on going.
On 19/07/2022 06:36, Emmanuel Lécharny wrote:
Hi!
I just announced the MINA 2.2.0 release. I will now
Hi!
I just announced the MINA 2.2.0 release. I will now switch to tyhis
version in Apache LDAP API and Server, then commit it.
Thanks !
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecha...@busit.com https
in LDAP Client API test that I'll now check.
On 08/03/2022 18:50, Emmanuel Lécharny wrote:
Hi !
just to keep you in the loop, I'm still fighting with the new MINA
integration.
The latest test I conducted with MINA 2.2.0-SNAPSHOT is not
conclusive, with some of the server-integ tests stalling
fighting with the new MINA
integration.
The latest test I conducted with MINA 2.2.0-SNAPSHOT is not conclusive,
with some of the server-integ tests stalling. The tests are all passing
- I'm positive on that - and that was not the case 2 weeks ago, but when
I run them all it times out.
I suspect we
Hi !
just to keep you in the loop, I'm still fighting with the new MINA
integration.
The latest test I conducted with MINA 2.2.0-SNAPSHOT is not conclusive,
with some of the server-integ tests stalling. The tests are all passing
- I'm positive on that - and that was not the case 2 weeks ago
Hi,
status: still working on it. I had spent hours (in the tens) trying to
go through a problem in MINA 2.2 relative to the TLS renegociation,
which was failing.
The decision has been made to not support TLS renegociation in MINA 2.2,
which is a sane decision due to the demonstrated MITM
Ok, some feedback regarding the StartTLS handling...
In order to have this operation working, we had to 'bend' MINA a bit. We
added an session attribute to handle the response. Let me explain.
When a startTLS request is processed by the server, we do two things:
- we setup the SSL filter
Pb solved.
I now have issue with the startTLS extended request handling on the server.
Will look at it tonite.
On 17/01/2022 14:50, Emmanuel Lécharny wrote:
Ok, beside a few tweaks, MINA 2.2 works just fine with the LDAP API.
However, there aws a removal of the SslSession from the IoSession
Ok, beside a few tweaks, MINA 2.2 works just fine with the LDAP API.
However, there aws a removal of the SslSession from the IoSession, and
it's used by the server in the ExternalSaslServer:
public byte[] evaluateResponse( byte[] initialResponse ) throws
SaslException
{
try
Hi !
this morning, I will test the LDAP API (and the server) with a new
version of MINA (2.2) which has a totally rewritten SSL handler.
Hopefully, it will solve the TLS 1.3 issue and be slightly faster.
I'll keep you informed !
--
Emmanuel Lécharny
[
https://issues.apache.org/jira/browse/DIRSERVER-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1119:
-
Fix Version/s: (was: 2.1.0)
> Use MINA statemachine code for vari
[
https://issues.apache.org/jira/browse/DIRSERVER-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-2023.
> Make the MINA configuration elements available in ApacheDS configuration f
Rahhh...
On 21/02/2019 11:29, Colm O hEigeartaigh wrote:
Wrong dev list I think :-)
Colm.
On Thu, Feb 21, 2019 at 10:19 AM Emmanuel Lécharny
mailto:elecha...@gmail.com>> wrote:
Hi !
I'm calling for a vote of Apache MINA 2.0.20 release.
It's a bug fix release
Wrong dev list I think :-)
Colm.
On Thu, Feb 21, 2019 at 10:19 AM Emmanuel Lécharny
wrote:
> Hi !
>
> I'm calling for a vote of Apache MINA 2.0.20 release.
>
> It's a bug fix release. Here are the list of bugs that have been fixed :
>
> DIRMINA-1092: Removed a spu
Hi !
I'm calling for a vote of Apache MINA 2.0.20 release.
It's a bug fix release. Here are the list of bugs that have been fixed :
DIRMINA-1092: Removed a spurious printstacktrace
DIRMINA-1098: handshakeStatus variable has been wrongly made global
DIRMINA-1088: the OrderedThreadPool
> api-ldap-net-mina bundle remains in STARTING mode
> -
>
> Key: DIRAPI-273
> URL: https://issues.apache.org/jira/browse/DIRAPI-273
> Project: Directory Client API
> Issue T
, as Stefan did, seems quite reasonable.
Thanks Stefan for the fix !
> api-ldap-net-mina bundle remains in STARTING mode
> -
>
> Key: DIRAPI-273
> URL: https://issues.apache.org/jira/browse/DIRAPI-273
>
o useful links that show that Eclipse behaves different than other OSGi envs::
* https://wiki.eclipse.org/Lazy_Start_Bundles
*
https://stackoverflow.com/questions/17590464/lazy-activation-of-eclipse-plugins/17592449#17592449
> api-ldap-net-mina bundle remains in STARTING mode
> ---
for the links and the explanation, quite frankly I'm just
starting in the OSGI world :-) a lot of this stuff is quite new to me
was (Author: ivoleitao):
Ok I understand. Thanks for the explanation, I was not aware of that, quite
frankly I'm just starting in the OSGI world :-)
> api-ldap-net-m
of that, quite
frankly I'm just starting in the OSGI world :-)
> api-ldap-net-mina bundle remains in STARTING mode
> -
>
> Key: DIRAPI-273
> URL: https://issues.apache.org/jira/browse/DIRAPI-273
>
uinox doesn't start any bundle automatically. Only if
"Bundle-ActivationPolicy: lazy" (or the older "Eclipse-LazyStart: true")
Equinox starts them at all, and then also only if some class of that bundle is
loaded. Without the "Bundle-ActivationPolicy: lazy" we need
. Only if
"Bundle-ActivationPolicy: lazy" (or the older "Eclipse-LazyStart: true")
Equinox starts them at all, and then also only if some class of that bundle is
loaded. Without the "Bundle-ActivationPolicy: lazy" we need to start the
bundles ourselves.
>
solutions. Unfortunately with that
directive it doesn't work in felix at least, i don't know about other osgi
frameworks
> api-ldap-net-mina bundle remains in STARTING mode
> -
>
> Key: DIRAPI-273
>
start in the patch aren't
actually started automatically... Are we missing something ?
> api-ldap-net-mina bundle remains in STARTING mode
> -
>
> Key: DIRAPI-273
> URL: https://issues.apache.org/jira/br
://svn.apache.org/viewvc?rev=1733998=rev
> api-ldap-net-mina bundle remains in STARTING mode
> -
>
> Key: DIRAPI-273
> URL: https://issues.apache.org/jira/browse/DIRAPI-273
> Project: Di
time with this issue. It
seems that Eclipse forces your to use such an activator to speed-up the load of
plugins at startup, as far as I understand, favoring the late load.
Howaver, I think we can probably find a way to workaround this issue.
> api-ldap-net-mina bundle remains in STARTING m
in Studio. But I think
there must be a way to fix it without the lazy ActivationPolicy.
> api-ldap-net-mina bundle remains in STARTING mode
> -
>
> Key: DIRAPI-273
> URL: https://issues.apache.org/jira/br
> api-ldap-net-mina bundle remains in STARTING mode
> -
>
> Key: DIRAPI-273
> URL: https://issues.apache.org/jira/browse/DIRAPI-273
> Project: Directory Client API
> Issue T
be added for Eclipse
(specifically Studio). I'll try to remove it to see if it works. Note that it's
also used in the api-ldap-codec-core bundle.
> api-ldap-net-mina bundle remains in STARTING mode
> -
>
> Key
of bundles
that I'm currently hosting in my felix environment
The bundle that was giving me problems is:
36|Active |1|Apache Directory LDAP API Network MINA
(1.0.0.M33)|1.0.0.M33
The complete list of bundles that I have in my system (excluding my own
bundles, only external
Ivo Leitão created DIRAPI-273:
-
Summary: api-ldap-net-mina bundle remains in STARTING mode
Key: DIRAPI-273
URL: https://issues.apache.org/jira/browse/DIRAPI-273
Project: Directory Client API
Le 20/01/16 19:24, Radovan Semancik a écrit :
> Hi,
>
> I done more Active Directory tests with the latest API trunk. There
> are two things you should know:
>
> 1. LDAP over SSL with AD fails when getting big things (such as AD
> schema). It ends up in an endless loop. It is
On 01/20/2016 07:53 PM, Emmanuel Lécharny wrote:
MINA will be fixed and released asap. Thanks for having chased to
origine of the pb... Now, would the submitted patch fix the issue ?
Yes. I believe so. It worked for my tests at the very least.
We should probably think about cutting
Le 20/01/16 20:03, Radovan Semancik a écrit :
>
>
>> We should probably think about cutting a release soon, then. I have also
>> injected some changes before taking some vacations, and I was actually
>> thinking about cutting a 1.0.0-RC1 release, instead of another milstone.
>
> OK for me.
On 01/20/2016 07:24 PM, Radovan Semancik wrote:
> Hi,
>
> I done more Active Directory tests with the latest API trunk. There are
> two things you should know:
>
> 1. LDAP over SSL with AD fails when getting big things (such as AD
> schema). It ends up in an endless loop. I
[
https://issues.apache.org/jira/browse/DIRSERVER-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-2023.
--
Resolution: Fixed
Make the MINA configuration elements available
Emmanuel Lecharny created DIRSERVER-2023:
Summary: Make the MINA configuration elements available in
ApacheDS configuration file
Key: DIRSERVER-2023
URL: https://issues.apache.org/jira/browse/DIRSERVER
[
https://issues.apache.org/jira/browse/DIRSERVER-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1119.
--
Resolution: Won't Fix
There is no added value in using MINA state Machine
.
http://svn.apache.org/viewvc?view=revisionrevision=r1444901
http://svn.apache.org/viewvc?view=revisionrevision=r1444906
http://svn.apache.org/viewvc?view=revisionrevision=r1445188
Remove all ApacheDS and Apache Mina libraries plugins from trunk in
'/libraries
[
https://issues.apache.org/jira/browse/DIRSTUDIO-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Arnaud Marcelot updated DIRSTUDIO-874:
-
Summary: Remove all ApacheDS and Apache Mina libraries plugins from
.
Thanks for the clarification.
Remove all ApacheDS and Apache Mina libraries plugins from trunk in
'/libraries'
Key: DIRSTUDIO-874
URL: https://issues.apache.org
MINA 2.0 and MINA 3.0. It
will be done later this afternon. Right now, the 2.0 sonar instance has
been fixed and reflects the current state.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Wrong list. ;)
Forwarded to Mina's dev list.
Regards,
Pierre-Arnaud
On 25 août 2012, at 05:42, Emmanuel Lécharny elecha...@gmail.com wrote:
It's been 4 days since the vote was started, it passes with 3 binding +1 and
one non binding +1 :
Emmanuel, Julien, Niklas (binding)
Alan (non
It's been 4 days since the vote was started, it passes with 3 binding +1
and one non binding +1 :
Emmanuel, Julien, Niklas (binding)
Alan (non binding)
I'll publish everything.
Thanks !
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
) and Java. The algorithm is basically the same in C++ and
Java
and handles protocols with a lot of small messages, variable message
size
protocols and large data block sizes.
I bet it's pretty much the same kind of algorihm, ACE and MINA are
based on the same logic.
Thanks for your input. I guess I
Hi guys,
yesterday, I faced a very dire issue with the way we handle SSL in MINA 2.
Basically, SSL is managed through the SslFilter, which is added in the
chain. The problem is that the filter can only be added on an existing
session. What are the consequences of such a choice ?
Basically
Hi guys,
as MINA 2.0.3 vote has been closed, I checked that ADS still works with
this version : it does. (pfffew).
I will wait for the mirrors to be updated before committing the updated
pom in Directory. Will do the commit tomorrow.
--
Regards,
Cordialement,
Emmanuel Lécharny
Thanks Em!
On Fri, Apr 15, 2011 at 8:45 PM, Emmanuel Lecharny elecha...@gmail.comwrote:
Hi guys,
as MINA 2.0.3 vote has been closed, I checked that ADS still works with
this version : it does. (pfffew).
I will wait for the mirrors to be updated before committing the updated pom
[
https://issues.apache.org/jira/browse/DIRSERVER-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-1554.
Switch to MINA 2.0.0
Key: DIRSERVER-1554
[
https://issues.apache.org/jira/browse/DIRSERVER-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1554.
--
Resolution: Fixed
Done. We even are using MINA 2.0.1 now.
Switch to MINA
[
https://issues.apache.org/jira/browse/DIRSERVER-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1554:
-
Fix Version/s: 2.0.0-RC1
Switch to MINA 2.0.0
On 9/14/10 1:49 PM, Niklas Gustavsson wrote:
On Tue, Sep 14, 2010 at 1:35 PM, Emmanuel Lécharnyelecha...@apache.org wrote:
Shouldn't we consider the download of the rxtx.jar as an active choice
already ? (just wondering)
But, with how I proposed earlier (which I now think is wrong) rxtx.jar
feature in Maven that conditionally downloads an
artifact after having the user approve the license. Perhaps we can take the
same steps for the rxtx.jar artifact?
Regards,
--
Alex Karasulu
My Blog :: http://www.jroller.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA
Wrong mailing list?
On Tue, Sep 14, 2010 at 2:11 PM, Emmanuel Lécharny elecha...@apache.org wrote:
On 9/14/10 1:49 PM, Niklas Gustavsson wrote:
On Tue, Sep 14, 2010 at 1:35 PM, Emmanuel Lécharnyelecha...@apache.org
wrote:
Shouldn't we consider the download of the rxtx.jar as an active
Yeap sorry about that did not know how this happened.
[
https://issues.apache.org/jira/browse/DIRSERVER-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-1133.
Test Case for the Mina Codec
Key
and share our opinion hat
we are the only good coders on earth ;) We decided that may be it would
be better to have a pizza and discuss about MINA 2 and 3 face to face,
instead of having good time outside, and it was really a good session.
That's what ApacheCon are good for : F2F meetings are good
Ooops, mailed to the wrong list... Forwarded to mina
On 2/20/10 12:37 PM, Ashish wrote:
expressions are a mix of :-) nd :-(
Next time just let me know when you folks plan a debugging marathon :-)
May be we can use some screen-sharing tool and I can also participate
means listen
On Sat, Feb 20, 2010 at 6:08 PM, Emmanuel Lecharny elecha...@gmail.com wrote:
Ooops, mailed to the wrong list... Forwarded to mina
On 2/20/10 12:37 PM, Ashish wrote:
expressions are a mix of :-) nd :-(
Next time just let me know when you folks plan a debugging marathon :-)
May be we can
Emm,
I thing you posted it on AD ML :-)
Anyways, its great. Have been using Analytics for more than a year to
track and analyze users on my blog.
thanks
ashish
On Fri, Dec 25, 2009 at 4:26 PM, Emmanuel Lecharny elecha...@gmail.com wrote:
Hi guys,
after months of proscratinating, we finally
Hi guys,
after months of proscratinating, we finally get Google Analytics working
on mina.apache.org (it was just a amtter of setting the correct
identifier in the main page :/).
So far, since dec 22th, 2997 pages have been viewed, and 110 downloads
have been requested. Of course, as this
[
https://issues.apache.org/jira/browse/DIRSERVER-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-1372.
Switch to MINA-2.0.0-M6 asap
Key
[
https://issues.apache.org/jira/browse/DIRSERVER-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1372.
--
Resolution: Fixed
Done.
Switch to MINA-2.0.0-M6 asap
Switch to MINA-2.0.0-M6 asap
Key: DIRSERVER-1372
URL: https://issues.apache.org/jira/browse/DIRSERVER-1372
Project: Directory ApacheDS
Issue Type: Task
Affects Versions: 1.5.4
Reporter: Emmanuel
of tomcat native
(have been fixed by now) when I started working on jSLP/MINA, so I was
forced to use my own fixed version of libtcnative and tomcat native (aka
tomcat-apr aka tomcat-jni) here. I inserted a fixed version into my
local maven repo to be able to build MINA and jSLP. I also needed tomcat
Hi guys
Sorry for the cross-post two 3 lists, but this whole jSLP issue depends
on work from all three areas...
As mentioned in the ApacheDS devlist, jSLP will be ready for release
really soon. However, jSLP relies on:
---
MINA multicasting
I
Hi
on the MINA part, I looked your patch, it need some work in both term
of doco and extracting common parts between AprSocketXXX and
AprDatagramXXX because most of the logic is the same. I plan to work on
that next week on MINA TRUNK, so if it's integrated it's going to be in
MINA 2.0.0-RC1
no-no for the
release, and which ones can be differed for a 2.0.0-RC2. I assume that
improvements and new features are to be postponed either to a 2.1 or a 3.0.
Here you are :
2.0.0-RC1 issues :
Bug DIRMINA-604 Deadlock occurs when implementing two mina StateMachine
Bug DIRMINA-632
Hi,
so here is the vote result :
5 +1 binding votes (Alex, Julien, Mark, Niklas and me)
2 +1 non binding votes (Jeff, Ashish)
Let's release the beast !!!
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
Wrong ML I think.
On Tue, Dec 9, 2008 at 9:41 AM, Emmanuel Lecharny [EMAIL PROTECTED]wrote:
Hi,
so here is the vote result :
5 +1 binding votes (Alex, Julien, Mark, Niklas and me)
2 +1 non binding votes (Jeff, Ashish)
Let's release the beast !!!
--
--
cordialement, regards,
Emmanuel
Damn ! I'm doing the same mistakes you are used to do ;)
I need some more sleep, I guess !
On Wed, Dec 10, 2008 at 4:19 AM, Alex Karasulu [EMAIL PROTECTED] wrote:
Wrong ML I think.
On Tue, Dec 9, 2008 at 9:41 AM, Emmanuel Lecharny [EMAIL PROTECTED]
wrote:
Hi,
so here is the vote result
[
https://issues.apache.org/jira/browse/DIRSERVER-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-1238.
Move to MINA 2.0 where we can make a bigger impact with the networking code
improves performance...
I wait for your moves before modify it myself.
Bye,
Alex
[EMAIL PROTECTED] wrote:
I have had a similar problems implementing broadcast, and I have
modified the ByteBuffer of MINA 8.0 making a method of
asReadOnly() that create a java.nio.ByteBuffer from
How can it be connected to Directory ? The initial problem, back in
2006, was related to MINA, which was then a subprojet to Directory.
If you have a problem with MINA, just post to the MINA mailing list.
From the stack trace you are posting, I don't think this is even a
MINA poblem, so please
to MINA 2.0 where we can make a bigger impact with the networking code
---
Key: DIRSERVER-1238
URL: https://issues.apache.org/jira/browse/DIRSERVER-1238
Project: Directory
help on this
part of the build :)
Sure. Could you give me some pointers? Which branch to use (trunk or
specific branch)? How to reproduce the issue?
So we are closed to have a ADS built on top of MINA 2 :)
That's a very cool news! :D
Regards,
Pierre-Arnaud
/branches/ads-mina2.0/
You will also need to build MINA-2.0.0-M4-SNAPSHOT :
http://svn.apache.org/repos/asf/mina/trunk/
That's it ! Have fun :)
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
issue with MAVEN. I would
appreciate some help on this part of the build :)
Sure. Could you give me some pointers? Which branch to use (trunk or
specific branch)? How to reproduce the issue?
ATM I get following error building (mina trunk and apacheds mina
branch), but I don't think
Felix Knecht wrote:
Hi Emmanuel,
Hi Felix,
this is because MINA API has just changed an hour ago :/...
I will change the code accordingly !
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
at 11:09 AM, Emmanuel Lecharny [EMAIL PROTECTED]wrote:
Felix Knecht wrote:
Hi Emmanuel,
Hi Felix,
this is because MINA API has just changed an hour ago :/...
I will change the code accordingly !
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
://svn.apache.org/viewvc/directory/apacheds/branches/ads-mina2.0/
branch is full MINA 2.0 and works well :)
Move to MINA 2.0 where we can make a bigger impact with the networking code
---
Key: DIRSERVER-1238
Hi guys,
I have fixed one major bug in MINA (I must admit that I introduced the
bug, too ;), and had to fix the LdapProcotolHandler, as the API has
changed between 1.x and 2.X (of course, the change is not documented ...)
So far, things are going way better. All the integration tests
Hi guys,
after two weeks of work on MINA, I come back to give you some feedback
about how is the porting to ADS going.
I'm not really satisfied by the results I get, atm. To be frank, I don't
think that MINA 2.0 is good enough to be used in ADS. I have some tests
blocked (only a few of them
Hi guys,
now that I'm used with MINA 2, and I have experimented it writing a
small LDAP client (something I will talk about in the next few weeks),
I'm trying to move to MINA 2 in the server. Not a piece of cake ...
The very first problem I had was to get the code to compile, by
switching
[
https://issues.apache.org/jira/browse/DIRSERVER-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny reassigned DIRSERVER-1238:
Assignee: Emmanuel Lecharny
Move to MINA 2.0 where we can make
1 - 100 of 1694 matches
Mail list logo
