I am +1 for this proposal.. also maybe the mandatory sequence could be used
to handle security for this case, which is a valid point as highlighted.
Does this mean that the user will be responsible to set up the
sequence and restrict access?
Andreas
Ruwan,
There is obviously some overlap between the proposed mechanism and
proxy services. I would be interested in getting an overview of the
differences between the two solutions and the respective advantages
and disadvantages of them (a sort of decision guide when to use which
one). Could you
Hi devs,
I would like to propose to implement the ability to dispatch messages
directly to sequences.
For the moment, all the messages which are coming in the message mediation
is going to be dispatched into the main sequence and if you want different
messages to be directed to different
Is there no security risk here? If I understand the proposal
correctly, it would be possible to invoke any named sequence, even if
it is not intended to be exposed. This could potentially be dangerous.
Andreas
On Tue, Mar 3, 2009 at 20:53, Ruwan Linton ruwan.lin...@gmail.com wrote:
Hi devs,
I
True, so to avoid that risk we could introduce an attribute to the sequence
configuration to specify whether the user wants to expose this sequence or
not. And we can make them not exposed by default.
Thanks,
Ruwan
On Wed, Mar 4, 2009 at 1:47 AM, Andreas Veithen
andreas.veit...@gmail.comwrote:
Ruwan
True, so to avoid that risk we could introduce an attribute to the
sequence configuration to specify whether the user wants to expose
this sequence or not. And we can make them not exposed by default.
I am +1 for this proposal.. also maybe the mandatory sequence could be
used to handle
On Wed, Mar 4, 2009 at 2:04 AM, Asankha C. Perera asan...@apache.orgwrote:
Ruwan
True, so to avoid that risk we could introduce an attribute to the
sequence configuration to specify whether the user wants to expose this
sequence or not. And we can make them not exposed by default.
I am +1
