Thanks a lot Marnie. I will have a look at it.

Danushka

On Sat, Jun 12, 2010 at 12:45 PM, Marnie McCormack <
[email protected]> wrote:

> Hi Danuska,
>
> There's just been a complete revamp of the trunk 0-10 Java Broker's ACLs:
> https://issues.apache.org/jira/browse/QPID-2476
>
> If you take a look some of the sub-task JIRAs have the dev discussions on
> the new approach.
>
> The new ACL info has been written up here with some examples:
> http://qpid.apache.org/andrew-acl-proposal.html
>
> The new Java ACLs are very close to the v2 ACL model already supported by
> the C++ broker:
> http://qpid.apache.org/acl.html
>
> I don't have my IDE up just now, but Andrew Kennedy provided some system
> tests for the new ACL plugin which should let you pick up an example ACL
> file in the new format from svn.
>
> I'm sure Andrew will be help you out on Monday if there's anything you
> need.
>
> Hth,
> Marnie
>
> On Fri, Jun 11, 2010 at 2:53 PM, Danushka Menikkumbura <[email protected]
> >wrote:
>
> > Hi devs,
> >
> > I have configured the broker has explained in [1] but I do not see the
> > clients being checked for authorization other than virtualhost-level
> > permissions. I am using a trunk build. Please let me know if the doc is
> > up-to-date and possible goofs that I may have made.
> >
> > [1] - http://qpid.apache.org/java-xml-acls.html
> >
> > Thanks,
> > Danushka
> >
>



-- 
Danushka Menikkumbura
Technical Lead & Product Manager, WSO2 SOA Enablement Server

WSO2, Inc.; http://wso2.com
Lean . Enterprise . Middleware

phone : +94 77 364 1754
blog : http://danushka-menikkumbura.blogspot.com/

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.

Reply via email to