On Fri, 7 Sep 2012 08:46:46 +0200 Andreas Veithen <[email protected]> wrote:
> On Thu, Aug 16, 2012 at 4:54 PM, Marc Giger <[email protected]> wrote: > > On Thu, 16 Aug 2012 10:08:56 +0100 > > Colm O hEigeartaigh <[email protected]> wrote: > > > >> WSS4J 2.0 will support streaming WS-Security as well as the existing DOM > >> based implementation. This will allow a web service to implement > >> WS-Security with a low memory footprint, albeit with a slight performance > >> tradeoff. > > > > ...albeit with a slight performance tradeoff for small SOAP-Documents... :-) > > Is there some information (with empirical data) available about the > relative performance of both implementations? You can run `mvn test -Dtest=PerformanceTimingTest,PerformanceMemoryTest -pl ws-security-stax` and then execeute the ws-security-stax/etc/plot.sh script to see how it performs. > > >> > >> Colm. > >> > >> On Wed, Aug 15, 2012 at 4:34 PM, Gary Gregory > >> <[email protected]>wrote: > >> > >> > Hi Colm, > >> > > >> > What can we expect in 2.0? > >> > > >> > Thank you, > >> > Gary > >> > > >> > > >> > On Wed, Aug 15, 2012 at 11:27 AM, Colm O hEigeartaigh > >> > <[email protected] > >> > > wrote: > >> > > >> >> Hi all, > >> >> > >> >> WSS4J trunk has now moved to 2.0-SNAPSHOT, and I have moved the > >> >> artifacts > >> >> from the SWSSF branch over. > >> >> > >> >> Colm. > >> >> > >> >> > >> >> -- > >> >> Colm O hEigeartaigh > >> >> > >> >> Talend Community Coder > >> >> http://coders.talend.com > >> >> > >> >> > >> > > >> > > >> > -- > >> > E-Mail: [email protected] | [email protected] > >> > JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 > >> > Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK > >> > Blog: http://garygregory.wordpress.com > >> > Home: http://garygregory.com/ > >> > Tweet! http://twitter.com/GaryGregory > >> > > >> > >> > >> > >> -- > >> Colm O hEigeartaigh > >> > >> Talend Community Coder > >> http://coders.talend.com > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
