Hi again,
After looking at things closer, I think that all callback handlers,
etc (including existing ones) should be moved to the jaas module and
all of the authentication brokers should stay where they are in core.
The callbacks should move since they are no necessary for core and
moving them
Deadlock in ActiveMQ Failover Worker
Key: AMQ-897
URL: https://issues.apache.org/activemq/browse/AMQ-897
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.0.1
On 8/25/06, Sepand M <[EMAIL PROTECTED]> wrote:
Hi,
I'm almost done coding for the SSL transport support project (refer to
the "Creating a secure connection system and using JMSXUserID support"
thread).
Great
I was just wondering how I would submit the patch for approval, how
long approval w
Hi,
I'm almost done coding for the SSL transport support project (refer to
the "Creating a secure connection system and using JMSXUserID support"
thread).
I was just wondering how I would submit the patch for approval, how
long approval would take, when the code might make it into a release,
etc
Ok. So, to confirm, I shouldm ove all Jaas* classes to the jaas module?
On 8/25/06, James Strachan <[EMAIL PROTECTED]> wrote:
On 8/25/06, Sepand M <[EMAIL PROTECTED]> wrote:
> Well there's already a JaasAuthenticationBroker in core, shouldn't the
> JaasCertificateAuthenticationBroker (that's the
[ https://issues.apache.org/activemq/browse/AMQ-884?page=all ]
Greg Wilkins resolved AMQ-884.
--
Resolution: Fixed
Applied patch and tested against chat demo.
Also updated to jetty 6.0.0rc2
> Ajax should support non-XML messages
> --
[
https://issues.apache.org/activemq/browse/AMQ-826?page=comments#action_36849 ]
james strachan commented on AMQ-826:
Great - thanks for the heads up. Good luck :)
> LDAP based authorization support
>
>
>
[
https://issues.apache.org/activemq/browse/AMQ-826?page=comments#action_36848 ]
Nikola Goran Cutura commented on AMQ-826:
-
I've been working on ApacheDS integration and found some issues there. Those
are planned to be fixed in RC4 which
