HP Fortify Critical Security Issues

Hello, As part of an evaluation of web frameworks, one of the checkboxes to tick is security vulnerabilities. In this case the tool being used to scan for those vulnerabilities is HP Fortify http://www8.hp.com/us/en/software-solutions/software.html?compURI=1349399#.URFMM6WbR2o I wanted to

Re: HP Fortify Critical Security Issues

Thanks Igor for the quick response. The bottom two are pretty self explanatory as to why they shouldn't be issues when you look into the codebase. The first one, I had the same response for but it's good to hear a similar echo from a wicket maintainer. -- View this message in context:

Re: Wicket Session Expiration - Ajax interactions

Just reading through the description - the components only included StatelessLink and a StatelessAjaxFallbackLink Browsing through the source code, it appears that there are stateless behaviors that can be added to other Ajax components. Best thing to do is to test it out :) -- View this

Wicket Session Expiration - Ajax interactions

I'm currently in the process of evaluating frameworks. We are currently using Wicket 1.4. The ones I've looked at so far have been Vaadin, Tapestry 5.4, and Wicket 6.0. Vaadin I ruled out for various reasons. One of the problems that our users have complained quite a bit about is the dreaded

Re: Wicket Session Expiration - Ajax interactions

It's just not efficient. We have users that will let their pages sit for hours before they come back to them. I would rather have these sessions/memory be reclaimed, and if a user has a stale page, the Ajax action continues on as normal. We also have a sudo portal that contains applications

Re: Wicket Session Expiration - Ajax interactions

You can read the Tapestry response a href=http://tapestry.1045711.n5.nabble.com/Session-Expiration-Ajax-td5719213.html;here. Essentially there are no PageMaps/versions per users session. -- View this message in context:

Re: Apache Wicket is a Flawed Framework

Again address the content and not the speaker. I prompted him to post this to get some good feedback on why Wicket is a better alternative than the UI frameworks than we have come across. Frameworks in the ui space are numerous and all serve a different need or perspective. If all you have

Re: Apache Wicket is a Flawed Framework

As gerald mentioned address the content - not the speaker, much more effective. i'll address a few of your points and bring up a few of my own. I'm sure the others can be addressed with thoughtful/intelligent responses. *Violates DRY*: There is a reason that HTML is separated from your

PageExpiredException - ajax request

I'm running into an issue with PageExpiredExceptions and ajax responses. Here's what I would like to do. 1. Have sessions timeout at 20 minutes. 2. Once a session has timed out and the user clicks an ajax link on the expired page - the link should process as normal and do whatever was tied to

Re: PageExpiredException - ajax request

, 2009 at 2:10 PM, sthomps stho...@gmail.com wrote: I'm running into an issue with PageExpiredExceptions and ajax responses. Here's what I would like to do. 1. Have sessions timeout at 20 minutes. 2. Once a session has timed out and the user clicks an ajax link on the expired page

Re: Wicket Modal Window - IFrame

Matej, Just to be clear - it's not that a modal window in Wicket App A is sourcing content from Wicket App B. It's that in this scenario Wicket App A has an generic iframe - not wicket produced - who's src is Wicket App B. The code here when run from B on modal creation pulls the Wicket.Window