Thread: [Winstone-devel] winstone / security-role
Status: Beta
Brought to you by:
rickknowles
From: Ralf E. <ral...@gm...> - 2006-07-11 14:14:45
|
Hi, at first, thanks a lot for Winstone... I use it as servlet container for testing my apps locally and the fact that I can start up a servlet container directly from one jar from eclipse without any troubles at all helps me a lot every day. Just wanted to tell you, I tried to use the argument realm which didn't worked for me. I debugged the winstone source and found that my web.xml was missing the security-role / role-name declaration. Probably winstone was right (no idea what the servlet spec says about this). Just wanted to tell you that Tomcat handles this differently (usage of the role seems to be enough) / that a warning message about the ignored role would help a lot finding such problems. Regards, Ralf |
From: Rick K. <ri...@kn...> - 2006-07-12 15:59:10
|
Ralf Ebert wrote: >> Hmmm ... okay. Thanks for the feedback, and for letting me know how >> tomcat handles it. Initially I had it working the same as Tomcat, but I >> remember seeing something in the spec that made me change it. Chances >> are it was a misreading on my part, so I'll switch it back for the next >> release, presuming it still passes the TCK (Sun API compliance) tests >> that way. > not sure, maybe strict checking isn't bad if you get a warning > message. Depends on the spec and I don't have an idea about that. > Maybe Tomcat is wrong :) The change to this was just committed - I added a warning like you suggested. Thanks. >> I've been thinking a little bit about a winstone eclipse plugin recently >> (which would allow per project winstone properties to be stored in >> eclipse, and be set up with source for step debugging). What do you >> think ? Is it worth it, or is just the straight Eclipse "Java >> Application" Run setup enough ? You are one of quite a few people who've >> mentioned that they use it this way, so I'm canvassing people gradually >> about maven and eclipse plugin development ideas. > Well, I use winstone especially for one reason: I don't need a plugin > to use it in Eclipse. I tried various jetty / tomcat plugins and in my > opinion, all that stuff just isn't right. I like to use winstone > because I can give it a webapp directory and get everything else > (classes / libs) directly from my classpath. I don't need to deploy > anything, I don't need configuration file(s) and I have debugging > available without any effort. As I mainly use Wicket for my > applications, I don't need anything more than a servlet container. In > my recent application there was a bunch of jsf/jsp/realmauth stuff, > but with jasper integration this worked all very nice after one hour > of setup. Glad to hear it > Only thing I mentioned is that winstone doesn't accept > <welcome-file-list><welcome-file>/pages/index.jsp</welcome-file></welcome-file-list> > > but it does accept > <welcome-file-list><welcome-file>index.jsp</welcome-file></welcome-file-list> > > (the files were in the right locations) I think this is actually one of the things clarified in the 2.5 spec, which is probably the next big thing on the priority list. The 2.4 spec didn't really cover what level of welcome page support was required, and so all the containers have differing interpretations. In any case, since I'll probably have to do it anyway I added it to the CVS version now. Please check it out and give it a try if you can. > Only thing where a plugin could help is configuring winstone, so you > don't need to type all the cmdline args. That would be nice, but > should be based on a run configuration so you can use all the java run > features and even have multiple configurations in the same project. I > think a plugin should be very simple, like having an assistant for > graphical editing of the command line arguments. I was thinking mostly along the lines of making config easy and debugging, which are the key points you mentioned. Not sure about multiple configs in a project ... at least I don't have a clear idea of an uncomplicated interface design for that. If you have any suggestions for an interface to do that, I'll certainly consider it. Key point is though that the reason for the plugin is making life less complicated for the common use case (so rarely used options should probably be moved to an "extra cmdline arg" field or something like it). I like the idea of working off a Run target as a base ... hadn't thought of that. I'll have to read up a bit more on those. I don't know much about Eclipse plugins, but what I saw last time I looked scared me. Time to dig in again perhaps. Thanks, Rick -- Servlet v2.4 container in a single 160KB jar file ? Try Winstone (http://winstone.sourceforge.net/) |
From: Ralf E. <ral...@gm...> - 2006-07-12 23:02:55
|
Hi, > The change to this was just committed - I added a warning like you > suggested. Thanks. great, thanks. > OK ... so the step debugging is a key point by the sound of it. Would > you prefer config as a Run target or as a "Project Properties" Tab / > Right click on Project submenu option (eg Winstone -> Start/Stop as a > submenu option) ? top 5 list of why winstone is great for local testing of webapps: 1) loading classes directly from classpath without the need for WEB-INF/classes or WEB-INF/lib (as this structure is usually created by a build script) 2) no need for configuration files (as configuration usually differs for each developer) 3) debugging out of the box available 4) simplicity (you can read to source if something isn't working as expected, try that with Tomcat...) 5) small jar I would prefer configuring this as Run target if this target would be an extension of the Java Run target (so you can use all Java options). Sometimes I like to do things like manually configuring the classpath or setting vm options etc. Starting winstone is not really about my project, it's about running something from my project. That's what "Run" is for :) But actually that's really no big deal, people who like to use a plugin are probably quite happy with jetty/tomcat. As mentioned, winstone is great because you don't need a plugin to get a usable eclipse setup. btw: We use Maven 2 in our project, availability of winstone from the ibiblio repository would be a nice feature (but that's no big deal as manually adding jars is quite easy) Ralf |
From: Rick K. <ri...@kn...> - 2006-07-11 15:21:28
|
Ralf, Hmmm ... okay. Thanks for the feedback, and for letting me know how tomcat handles it. Initially I had it working the same as Tomcat, but I remember seeing something in the spec that made me change it. Chances are it was a misreading on my part, so I'll switch it back for the next release, presuming it still passes the TCK (Sun API compliance) tests that way. I've been thinking a little bit about a winstone eclipse plugin recently (which would allow per project winstone properties to be stored in eclipse, and be set up with source for step debugging). What do you think ? Is it worth it, or is just the straight Eclipse "Java Application" Run setup enough ? You are one of quite a few people who've mentioned that they use it this way, so I'm canvassing people gradually about maven and eclipse plugin development ideas. I appreciate your input. Rick Ralf Ebert wrote: > Hi, > > at first, thanks a lot for Winstone... I use it as servlet container > for testing my apps locally and the fact that I can start up a servlet > container directly from one jar from eclipse without any troubles at > all helps me a lot every day. > > Just wanted to tell you, I tried to use the argument realm which > didn't worked for me. I debugged the winstone source and found that my > web.xml was missing the security-role / role-name declaration. > Probably winstone was right (no idea what the servlet spec says about > this). Just wanted to tell you that Tomcat handles this differently > (usage of the role seems to be enough) / that a warning message about > the ignored role would help a lot finding such problems. > > Regards, > Ralf > > > ------------------------------------------------------------------------- > 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=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Winstone-devel mailing list > Win...@li... > https://lists.sourceforge.net/lists/listinfo/winstone-devel > -- Servlet v2.4 container in a single 160KB jar file ? Try Winstone (http://winstone.sourceforge.net/) |
From: Matthias W. <mat...@wu...> - 2006-07-11 18:08:46
|
Hi Rick! >What do you >think ? Is it worth it, or is just the straight Eclipse "Java >Application" Run setup enough ? > I think it's definitively worth the effort. I also use Winstone from within Eclipse (and it works great as it is), but it would make things even more comfortable, especially when debugging applications. Best regards, Matthias |
From: Rick K. <ri...@kn...> - 2006-07-12 16:04:56
|
Matthias, >> What do you >> think ? Is it worth it, or is just the straight Eclipse "Java >> Application" Run setup enough ? > I think it's definitively worth the effort. I also use Winstone from > within Eclipse (and it works great as it is), but it would make things > even more comfortable, especially when debugging applications. > OK ... so the step debugging is a key point by the sound of it. Would you prefer config as a Run target or as a "Project Properties" Tab / Right click on Project submenu option (eg Winstone -> Start/Stop as a submenu option) ? Thanks for your comments (and for those of anyone else who wants to put their two cents in). Rick -- Servlet v2.4 container in a single 160KB jar file ? Try Winstone (http://winstone.sourceforge.net/) |