-tutorials/48-esb-performance.html
cheers
asankha
Following up on some earlier discussions of Axis2/Rampart WS-Security
performance, devWorks has now published my latest article in the Java
Web Services series, comparing Axis2/Rampart with Metro WS-Security
performance: http://www.ibm.com/developerworks
/Rampart
http://adroitlogic.org/samples-articles-and-tutorials/15-tutorials/48-esb-performance.html
cheers
asankha
Following up on some earlier discussions of Axis2/Rampart WS-Security
performance, devWorks has now published my latest article in the Java
Web Services series, comparing
of Axis2/Rampart WS-Security
performance, devWorks has now published my latest article in the Java Web
Services series, comparing Axis2/Rampart with Metro WS-Security performance:
http://www.ibm.com/developerworks/java/library/j-jws11/ The results are
very bad for Axis2/Rampart, with Metro more
Hi Amila
how many messages you sent for one scenario test?
i.e for eg 500b message with 640 threads
This depends on the concurrency, and can be found exactly by looking at
the script used to run the load test. For example, when 20 users were
being used, the iterations were 1000, while for 2560
On Thu, Feb 11, 2010 at 10:23 PM, Asankha C. Perera asan...@apache.orgwrote:
Hi Amila
how many messages you sent for one scenario test?
i.e for eg 500b message with 640 threads
This depends on the concurrency, and can be found exactly by looking at
the script used to run the load test. For
Hi Amila
In the very first scenario upto 640 concurrency level both have
same through put while for 1280 threads UE has a sudden increment
and for 2560 other ESB has a relatively high change. What could be
the reason for that?
Which set are you referring to - the
policy based validations.
Would be glad if you could please confirm it.
Thanks regards.
-Prabath
Dennis Sosnoski wrote:
Following up on some earlier discussions of Axis2/Rampart WS-Security
performance, devWorks has now published my latest article in the Java
Web Services series, comparing
Following up on some earlier discussions of Axis2/Rampart WS-Security
performance, devWorks has now published my latest article in the Java
Web Services series, comparing Axis2/Rampart with Metro WS-Security
performance: http://www.ibm.com/developerworks/java/library/j-jws11/ The
results
- it could open up holes for attacks
like XML wrapping attacks.
I found few occasions that Metro doesn't do policy based validations.
Would be glad if you could please confirm it.
Thanks regards.
-Prabath
Dennis Sosnoski wrote:
Following up on some earlier discussions of Axis2/Rampart WS
IMHO this is out of the scope of WS-Security specification and
WS-SecureConversation will be able to help.
You can authenticate the user and create the security context. Now you
can use this context in sending the subsequent messages.
Thanks,
Ruchith
On 7/10/07, Kevin TierOne [EMAIL PROTECTED]
I have a question about the capabilities of the rampart module. I would
like to create a client that sends several SOAP messages to the server. The
messages are currently authenticated using the UsernameToken in a PWCallback
class. Is it possible to create a session identifier when processing
11 matches
Mail list logo