On Wednesday 26 September 2007 15:19, David Leangen wrote:
> Wicket does not provide support for https out of the box. The procedure
> is outline here:
>
> http://cwiki.apache.org/WICKET/how-to-switch-to-ssl-mode.html
These people are insane!!!
protected IRequestCycleProcessor newRequestCycleProcessor()
{
return new DefaultWebRequestCycleProcessor()
{
protected IResponseStrategy newResponseStrategy()
{
return new IResponseStrategy()
{
Who does anonymous classes inside anonymous classes?
<shrug>
> I would like to add https support to my apps. However, their method says
> to override Application, which is internal to Pax Wicket.
So, the solution should be that one can register a RequestCycle factory in
OSGi service registry, and the Application class delegates to it, if found
otherwise delegate to the Application superclass.
I think we should create a SSL bundle, which would enable SSL if
loaded/started, otherwise fallback to HTTP.
> Any objections for me to add this kind of support in Pax Wicket?
Not at all. This is a good use-case, as long as not an ultra-general hack is
provided it is Ok. Also expect some serious troubles to get this to work...
1. You need a server cert.
2. You must have one IP number per cert, i.e. no virtual hosts.
3. Pax Web or whatever must probably also be modified to support HTTPS.
Cheers
--
Niclas Hedhman, Software Developer
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
