[ http://issues.apache.org/jira/browse/DIRMINA-159?page=all ]
Ersin Er reopened DIRMINA-159:
--
This issue is closed but I still have the same problem *sometimes*. Here is the
error output from my last full directory build:
[surefire] Running
org.apache.m
Wrong encoding of sasl in BindRequest
-
Key: DIRSNICKERS-123
URL: http://issues.apache.org/jira/browse/DIRSNICKERS-123
Project: Directory ASN1
Type: Bug
Reporter: Emmanuel Lecharny
Assigned to: Emmanuel Lecharny
The decodin
Emmanuel,
I was finishing up referral support in the LDAP protocol provider when I
noticed that referrals are not being encoded. I think it may be Twix
but don't quote me on that. I'll take a look into it and try to figure
it out. If you don't hear from me and you get a second please ping m
It's out. Lez git it! I'm gettin it now.
Alex
--- Begin Message ---
The Maven Team is pleased to announce the release of Maven 2.0.2!
You can download everything from here:
http://maven.apache.org/download.html
You can find the change log for this release here:
http://jira.codehaus.org/secur
Norbet Reilly wrote:
Thanks.
I would have twigged to the cause of the problem earlier except that
the first failure had "../mina/mina/pom.xml" which seemed like a
maven2 bug on the surface. Thanks for your help.
No problem ... you did good (purposefully bad English :-)) figuring it
out. I w
Thanks.
I would have twigged to the cause of the problem earlier except that
the first failure had "../mina/mina/pom.xml" which seemed like a
maven2 bug on the surface. Thanks for your help.
I applied a subset of your patch. Looks like something was also broken
due to tab [mis]completion in MINA. Now you can build with JDK 1.4 but
you have to switch to just build trunks/mina/ssl using jdk 1.5. This
will be fixed as soon as this JIRA issue is handled:
http://issues.apache.org/jir
Brett Porter wrote:
+1
Another observation: it seems you are going to release a 1.0 RC1 that
is not exactly what you intend 1.0 to be.
Hmmm having trouble understanding. The release candidate is basically a
beta version of 1.0 with a feature freeze. All we do with the RC series
is fix bug
+1
Another observation: it seems you are going to release a 1.0 RC1 that
is not exactly what you intend 1.0 to be. From personal experience,
I've found that to be problematic. We now essentially copy the RC to
the final release binary where possible.
Is that right? WDYT about a different labellin
Common internal messages that can be shared by filters and transport
implementations
Key: DIRMINA-166
URL: http://issues.apache.org/jira/browse/DIRMINA-166
Project: Directory MINA
T
Excuse my typing today!
"Likes look" sounds like something from a Dr Suess book ;-)
"luke luck licks lakes"
supposed to be "Looks like" of course...
Likes look the last problem I ran into will need to be addressed by
some relection trickery, ie. if can't load SSLFilter.class then don't
attempt to refer to it in
org.apache.ldap.server.protocol.LdapProtocolProvider, or alternatively
splitting out the referenced constants into a separate class tha
here 'tis
ds_patch.patch
Description: Binary data
Cool, I'd just run into that too. I'll post a patch of what I've done
so far once I compile it (in a few minutes).
I'm now failing because of refs to SSLFilter in
org.apache.ldap.server.protocol.LdapProtocolProvider
Norbet Reilly wrote:
Yes.
I've tracked it down to the JDK1.4 profiles being wrong in
apacheds/pom.xml abd mine/pom.xml
Ok back after my last email and yes this is what it was good catch. I
commited a fix for it. Looks like too many of us are getting away from
1.4. Looks like the ldaps s
Apologies for the typo hell! I mean apacheds/pom.xml and mina/pom.xml!
Yes.
I've tracked it down to the JDK1.4 profiles being wrong in
apacheds/pom.xml abd mine/pom.xml
Alex Karasulu a écrit :
I just wanted to summarize some findings from several discussions on IRC:
(1) [OBSERVATION] Current directory JIRA configuration is out of
control with number of subprojects. Umbrella project madness is
setting in. Users and contributors alike are having problems figu
Norbet Reilly wrote:
I get the same behaviour with "mvn install". Just in case I:
a) removed the .m2/repository in my home directory
b) renamed the working directory that I had checked trunks/ out into
but still get the same problem.
Just to double check I went back to the working directo
I get the same behaviour with "mvn install". Just in case I:
a) removed the .m2/repository in my home directory
b) renamed the working directory that I had checked trunks/ out into
but still get the same problem.
Just to double check I went back to the working directory checked out
from th
Alex Karasulu wrote:
I just wanted to summarize some findings from several discussions on IRC:
(1) [OBSERVATION] Current directory JIRA configuration is out of
control with number of subprojects. Umbrella project madness is
setting in. Users and contributors alike are having problems figurin
I just wanted to summarize some findings from several discussions on IRC:
(1) [OBSERVATION] Current directory JIRA configuration is out of control
with number of subprojects. Umbrella project madness is setting in.
Users and contributors alike are having problems figuring out which JIRA
to se
[
http://issues.apache.org/jira/browse/DIRLDAP-85?page=comments#action_12362856 ]
Alex Karasulu commented on DIRLDAP-85:
--
Wow good catch. If you definately confirm incorrect substring search and have
correected it please commit at will. If you could
Stefan Zoerner wrote:
hmmm... What about the fact that the entry was correctly created with
this not existing attribute?
Isn't it weird that the server accept a creation but not a modification
in this case?
Emmanuel is right. We have definitely a problem here, but in the add op,
Norbet Reilly wrote:
Can you publish a brief blurb about any relevant Maven2 targets: I had
my build going before the target/ => targets/ SVN reorg, but now when
I try and build in the new tree at the top apacheds/trunks/ level
(Maven version: 2.0.1, java version "1.4.2_04")
Hmmm just try a
Emmanuel Lecharny wrote:
Ok, seems to be related to the schema handling. I will try to
reproduce this on my server .
I don't think this is an an error. He's using an undefined
attribute: activeFlag. Since 0.9 we have added some minimal schema
checks.
hmmm... What about the fact that
Great !!
Thanks Ceki. I will upgrade the pom.xml asap.
Ceki Gülcü a écrit :
At 11:23 PM 1/12/2006, Emmanuel Lecharny wrote:
Hi all !
Here where I'm on Log things :
- Slf4j is back. This will be the basic logging API for all the
"embedable" projets. We are waiting for 1.0 to get out, and ri
At 11:23 PM 1/12/2006, Emmanuel Lecharny wrote:
Hi all !
Here where I'm on Log things :
- Slf4j is back. This will be the basic logging API for all the
"embedable" projets. We are waiting for 1.0 to get out, and right now, as
ibiblio only has RC3, this is the current version used.
- For standa
Get rid of LdapString class when unecessary
---
Key: DIRSNICKERS-122
URL: http://issues.apache.org/jira/browse/DIRSNICKERS-122
Project: Directory ASN1
Type: Improvement
Reporter: Emmanuel Lecharny
Assigned to: Alex Karasul
Class cast exception in seraches
Key: DIRLDAP-86
URL: http://issues.apache.org/jira/browse/DIRLDAP-86
Project: Directory LDAP
Type: Bug
Reporter: Emmanuel Lecharny
Assigned to: Emmanuel Lecharny
Priority: Blocker
When tryi
Filtered searches failing
-
Key: DIRLDAP-85
URL: http://issues.apache.org/jira/browse/DIRLDAP-85
Project: Directory LDAP
Type: Bug
Reporter: Emmanuel Lecharny
Priority: Blocker
If we are trying to do a search with substring filters,
Somashish Gupta a écrit :
Sorry for bugging again.
As I had mentioned in my earlier mail, the "activeFlag" attribute was not
defined(so even though creation was successful, modification was not). As
suggested by you I tried to add this attribute in the schema using the JNDI
calls( as given in e
Sorry for bugging again.
As I had mentioned in my earlier mail, the "activeFlag" attribute was not
defined(so even though creation was successful, modification was not). As
suggested by you I tried to add this attribute in the schema using the JNDI
calls( as given in examples in JNDI tutorial at t
> hmmm... What about the fact that the entry was correctly created with
this not existing attribute?
> Isn't it weird that the server accept a creation but not a modification
in this case?
Emmanuel is right. We have definitely a problem here, but in the add op,
not in the modify op (as Alex explai
34 matches
Mail list logo
