activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: PolicyMap api is really bad :-(
Date Thu, 19 Jan 2012 07:45:43 GMT
>
> The api here is still a bit clunky IMO.  Broker service for example will
> automatically create a SystemUsage bits on demand, is there any reason why
> BrokerService.getDestinationPolicy() doesn't create the PolicyMap on
> demand?  Or why PolicyMap isn't more builder-like?  Guess most folks still
> using Spring to configure the broker and thus never need a nicer API to
> configure it?
>
>
Yeah, I guess nobody asked for it before. Most people with non-trivial
configs use XML (even for embedded brokers), so this API is only really
used for testing.


> Would be nice to see a rich fluent api as a first-class broker
> configuration mechanism one day :-)
>
>
Any contribution is appreciated :)


> Anyways, related to forQueue() and forTopic() below, I believe these will
> work to build up the entries w/o needing to build a List and
> setPolicyEntries().  Related, can you recommend the easiest way to verify
> if a policy entry has taken effect or not?


 Hm, not sure it's doable at the moment.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message