You are welcome :)
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Jun 19, 2014 at 3:46 PM, Marian Muller
wrote:
> Hi all,
>
> Just giving you an update. I have been re-assigned to a priority task which
> will keep me busy for a little while.
> I will
Hi all,
Just giving you an update. I have been re-assigned to a priority task which
will keep me busy for a little while.
I will come back to you when I can work on this topic again. I am
definitely looking forward to it !
Marian.
--
Marian MULLER
SERLI
On Fri, Jun 6, 2014 at 10:13 AM, Marian
Great !
Thanks for the tip.
--
Marian MULLER
SERLI
On Fri, Jun 6, 2014 at 10:04 AM, Romain Manni-Bucau
wrote:
> In pseudo code you can do:
>
> class MyFactory {
>private Properties properties; // + setter
>
>public XXX create() {
> // use properties to build your instance
>
In pseudo code you can do:
class MyFactory {
private Properties properties; // + setter
public XXX create() {
// use properties to build your instance
// properties will match resources properties
}
}
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpr
Hi,
Do you think there is a way to configure queues and topics in tomee.xml
using a property key that contains the destination name ? From what I see,
the property key is used to match a setter or field. Any way to write
configuration like this ?
queues.foo = read=..., write=..., admin=...
queue
Basically provide what you need (or what you think you'll need) - and
what you find fun ;). If sby needs more we'll add it later.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibuc
The AuthorizationPlugin would also require to specify the destination type.
And maybe the support for temp destinations configuration.
This plugin also supports different kinds of "authorization maps",
including LDAP and CachedLDAP. But maybe this is out of the scope for now.
Regarding the generic
Depend but if you think to authorizationplugin something like it could work:
queue1 = read=user;admins,write=admin;sudo,admin=admin
We can still support a generic resource factory understading $ as
a lookup to do on . This way you can wire beans together
genericly.
That said not su
Hi,
Thanks for the tip. Using a factory is the way to go.
After adding a factory/service provider in service-jar.xml, I can use the
following configuration:
> UserPasswords = user1=password1 \n user2=password2 \n
> manager=password3
> UserGroups= user1=users \n user2=users \n mana
For these advanced cases we provide a factory in openejb users rely on (all
container are done this way for instance). So just use the config you want,
get properties injected in your factory and declare the class-name
attribute of your resource with the value of the qualified name of the
factory.
Hi Romain,
I had a look at the XBean property editors to configure AMQ plugins from
TomEE configuration file. I can easily set the userPasswords for the
SimpleAuthenticationPlugin
class (it is a simple Map), but the userGroups property is
not as easy (it is a Map>). Which makes me wonder if
XBean
Hi
I think the solution without activemq.xml is great. We could make a default
jars.txt a user could drop in conf/ to add all the required dependencies if
it helps but putting spring is the container is not a good idea as default
solution. In particular for this case where we know how to get it pr
Hi Andy,
Thanks for the insight. I think we need to take some time and discuss the
topic, before going further.
I understand your point about the simple "built-in" solution being what its
name suggests: a simple solution for running localhost/vm-only broker. This
makes much sense! And I also beli
Hi Marian,
I have always been of the opinion that the default configuration is the
simple way, and more complex scenarios need a more complex solution,
and a really deep understanding of ActiveMQ configuration.
The simple solution is seen as a localhost/vm only solution which never
goes outsi
Wow! That is a hell of an answer! :-) Thanks.
OK, so I understand the realms or not a good option.
I think you are right about making this a generic way to configure AMQ
plugins. I will have a look at the whole resource adapters / plugins /
XBean configuration stuff.
About the resource-lookup an
Hi
great to hear!
About using realm I'm -1 since it has to work with openejb (without tomcat)
since that's a very current usage.
Now how to impl it: we have to reuse AMQ logic as much as possible. You
just need to add the authenticator plugin
in org.apache.openejb.resource.activemq.ActiveMQ5Fact
16 matches
Mail list logo
