Hi Stefan,
As promised I have placed a build at [1] and you may try the feature
according to the configuration described in this thread. Please note
that there is no UI to change this for the moment and you have to go to
the Configuration tab and edit the raw configuration and update it to
see it working. I will be adding the UI for this soon.
[1] -
http://builder.wso2.org/download/ESB-NIGHTLY/artifacts/build-63/ESB-nightly-zip
Thanks,
Ruwan
Ruwan Linton wrote:
stlecho wrote:
Ruwan,
Any idea that the issue you've filed is linked to the following one:
http://www.nabble.com/-Axis2-Rampart--Using-Rampart-for-OutFlow%2C-but-not-for-InFlow-td15689307.html#a15709088
http://www.nabble.com/-Axis2-Rampart--Using-Rampart-for-OutFlow%2C-but-not-for-InFlow-td15689307.html#a15709088
?
Hi Stefan,
It does relate (actually it is the same) but when the message is going
through synapse we have a set of pre-constructed services and we don't
want to create services for each and every message that we are sending
out (due to the performance). Because of that we cannot set policies
to the message of that pre-constructed services (they are used by many
other messages as well). There fore we need a mechanism to dynamically
set this policy at the message level using a message property. (we can
do that for service level for the moment, so I have requested the same
for message level as well).
AFAIK, Nandana is working on that and I will be able to give you a
build by the end of this week.
Thanks,
Ruwan
Regards, Stefan.
Ruwan Linton-3 wrote:
Ruwan Linton wrote:
stlecho wrote:
Ruwan,
Not sure I've understood your explanation. Anyway, the referenced
Jira issue
(SYNAPSE-355) exactly describes my problem. I thought that the
earlier in
this post mentioned SYNAPSE-127 issue solved my issue, but
apparantly it is
not :o(.
Any idea when this fix will be made available ?
We are planing on a quick point release of ESB/Synapse and it will
be available within next 3 weeks, but I will be fixing this by the
end of this week or early next week.
Hi Stefan,
I tried to fix this issue and found there is an issue in Rampart
which permits the behavior being implemented on Synapse, and filed
an issue for that. Once it has been fixed there, we can fix the
issue and you can use this as follows;
If you want to apply service level policies, (that is the same
policy for both in and out messages) you can use the existing behavior;
<enableSec policy="key"/>
If you need message level policies after the Rampart fix you should
be able to specify different policies for messages as follows;
<enableSec inboundPolicy="key" outboundPolicy="key"/>
In effect if you need only messages going to the service to be
signed and expect unsigned messages from the actual service, then
you can drop the inboundPolicy attribute and provide the policy key
for signing to the outboundPolicy attribute.
Thanks,
Ruwan
Thanks,
Ruwan
Regards, Stefan.
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
