[Wicket-user] mapping application to /

2006-11-05 Thread ryan mckinley
I'm trying to build my first real app using wicket and am looking for advice on how to structure it. I expect it will have moderately heavy traffic but most things can be cached with a simple ehcache Filter.The issue i see is that if i want to have wicket generated content on the root page, i need to map the application servlet to:
url-pattern/*/url-patternBut if i do that, it looks like all the static content has to go through wicket too. Is there any way to have the web server directly serve content under: /static/*?
Alternatively i guess i could map multiple application to deeper paths, but that seems like a bad idea.I've read that 2.0 will switch to a filter model, what is the best practice until then? thanks

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] mapping application to /

2006-11-05 Thread Juergen Donnerstag
There is no need to use /*. In fact it is the least favourable
solution. Take a look at the examples.

Juergen

On 11/5/06, ryan mckinley [EMAIL PROTECTED] wrote:

 I'm trying to build my first real app using wicket and am looking for advice
 on how to structure it.  I expect it will have moderately heavy traffic but
 most things can be cached with a simple ehcache Filter.

 The issue i see is that if i want to have wicket generated content on the
 root page, i need to map the application servlet to:
  url-pattern/*/url-pattern

 But if i do that, it looks like all the static content has to go through
 wicket too.  Is there any way to have the web server directly serve content
 under: /static/*?

 Alternatively i guess i could map multiple application to deeper paths, but
 that seems like a bad idea.

 I've read that 2.0 will switch to a filter model, what is the best practice
 until then?

 thanks


 -
 Using Tomcat but need to do more? Need to support web services, security?
 Get stuff done quickly with pre-integrated technology to make your job
 easier
 Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642

 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user




-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] mapping application to /

2006-11-05 Thread ryan mckinley
The examples have a static /index.html and multiple apps defined at /helloworld, /echo, etc each one has its own session (if i understand correctly)I'd like to have wicket style templates on index.html and share session attributes across the sub pages (specifically user authentication)
Do i need to map an Application to index.html also?thanks(i apologize if this is super basic)On 11/5/06, Juergen Donnerstag
 [EMAIL PROTECTED] wrote:
There is no need to use /*. In fact it is the least favourablesolution. Take a look at the examples.JuergenOn 11/5/06, ryan mckinley [EMAIL PROTECTED] wrote:
 I'm trying to build my first real app using wicket and am looking for advice on how to structure it.I expect it will have moderately heavy traffic but most things can be cached with a simple ehcache Filter.
 The issue i see is that if i want to have wicket generated content on the root page, i need to map the application servlet to:url-pattern/*/url-pattern But if i do that, it looks like all the static content has to go through
 wicket too.Is there any way to have the web server directly serve content under: /static/*? Alternatively i guess i could map multiple application to deeper paths, but that seems like a bad idea.
 I've read that 2.0 will switch to a filter model, what is the best practice until then? thanks -
 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server 
v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/wicket-user-Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___Wicket-user mailing list
Wicket-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wicket-user
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] mapping application to /

2006-11-05 Thread Juergen Donnerstag
On 11/5/06, ryan mckinley [EMAIL PROTECTED] wrote:

 The examples have a static /index.html and multiple apps defined at
 /helloworld, /echo, etc each one has its own session (if i understand
 correctly)


In case of the examples index.html is registered in web.xml as the welcome page
welcome-file-list
welcome-fileindex.html/welcome-file
/welcome-file-list
and allows you to easily select any of the example applications.
A session is created by the servlet container per user (not per
application) and can be used to stored eg user information. Because a
session is a per user object, it is available for the various pages
which make up your application.

 I'd like to have wicket style templates on index.html and share session
 attributes across the sub pages (specifically user authentication)

 Do i need to map an Application to index.html also?

 thanks

 (i apologize if this is super basic)



 On 11/5/06, Juergen Donnerstag [EMAIL PROTECTED] wrote:
  There is no need to use /*. In fact it is the least favourable
  solution. Take a look at the examples.
 
  Juergen
 
  On 11/5/06, ryan mckinley [EMAIL PROTECTED] wrote:
  
   I'm trying to build my first real app using wicket and am looking for
 advice
   on how to structure it.  I expect it will have moderately heavy traffic
 but
   most things can be cached with a simple ehcache Filter.
  
   The issue i see is that if i want to have wicket generated content on
 the
   root page, i need to map the application servlet to:
url-pattern/*/url-pattern
  
   But if i do that, it looks like all the static content has to go through
   wicket too.  Is there any way to have the web server directly serve
 content
   under: /static/*?
  
   Alternatively i guess i could map multiple application to deeper paths,
 but
   that seems like a bad idea.
  
   I've read that 2.0 will switch to a filter model, what is the best
 practice
   until then?
  
   thanks
  
  
  
 -
   Using Tomcat but need to do more? Need to support web services,
 security?
   Get stuff done quickly with pre-integrated technology to make your job
   easier
   Download IBM WebSphere Application Server v.1.0.1 based on Apache
 Geronimo
  
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
  
   ___
   Wicket-user mailing list
   Wicket-user@lists.sourceforge.net
  
 https://lists.sourceforge.net/lists/listinfo/wicket-user
  
  
  
 
 
 -
  Using Tomcat but need to do more? Need to support web services, security?
  Get stuff done quickly with pre-integrated technology to make your job
 easier
  Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
 
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
  ___
  Wicket-user mailing list
  Wicket-user@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wicket-user
 


 -
 Using Tomcat but need to do more? Need to support web services, security?
 Get stuff done quickly with pre-integrated technology to make your job
 easier
 Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
 http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642

 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user




-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] mapping application to /

2006-11-05 Thread Eelco Hillenius
 I'm trying to build my first real app using wicket and am looking for advice
 on how to structure it.  I expect it will have moderately heavy traffic but
 most things can be cached with a simple ehcache Filter.

Don't cache session internal pages though... be sure to only cache
bookmarkable pages if you really want to. Better: don't cache the
output of pages at all, but instead focus in making your
business/service layer more efficient (e.g. cache your domain model/
queries etc). If you still need a higher throughput, generating static
pages is a better solution than just caching imo.

 The issue i see is that if i want to have wicket generated content on the
 root page, i need to map the application servlet to:
  url-pattern/*/url-pattern

 But if i do that, it looks like all the static content has to go through
 wicket too.  Is there any way to have the web server directly serve content
 under: /static/*?

You can put a filter on top of the Wicket servlet, and if it matches
with static content, you just don't pass control further the chain
(Wicket).

 Alternatively i guess i could map multiple application to deeper paths, but
 that seems like a bad idea.

Is it that bad to have /app or /dyn or whatever in your path?

 I've read that 2.0 will switch to a filter model

It already has had that for quite a while.

 what is the best practice
 until then?

I don't know if there is any. Different people like different things.
Personally, I'm not worried at all by having e.g. /app for the Wicket
part of your app.

Eelco

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user