Re: [Winstone-devel] winstone / security-role

[Rick K. <ri...@kn...>]

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/)