Re: [Stripes-users] Security and Authentication

[Thomas Menke]

On 09/18/2010 10:06 PM, Grzegorz Krugły wrote:
>
>
> I'm not sure about this, but try removing dispatcherservlet from web.xml
> and use dynamicmappingfilter as described in
> http://stripes.sourceforge.net/docs/current/javadoc/net/sourceforge/stripes/controller/DynamicMappingFilter.html
> like this:
> [..]

Now I am getting:
Throwable occurred: 
net.sourceforge.stripes.exception.StripesServletException: Could not get 
a reference to StripesFilter from the servlet context. The dynamic 
mapping filter works in conjunction with StripesFilter and requires that 
it be defined in web.xml

Here is my web.xml:
http://pastebin.org/1069117

Thomas

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Evan Leonard]

Freddy, I hear what you're saying.  I think I may have steering things in the 
wrong direction using words like "autocratic". I actually agree with what 
you're saying here, that there is a need for a lead. My question to Ed should 
probably be restated more simply as, "Would you tell us a little bit about how 
you would run things?"  That seems like a fair question to ask I think before 
"voting" or anything like that.  Not to mention that Ben still seems invested 
from his email this morning as well.  (Correct me if I'm wrong Ben).

Evan



On Sep 21, 2010, at 2:07 PM, Freddy Daoud wrote:

> Just my 2c, I hope this doesn't make things "worse" in terms of
> misunderstandings.
> 
>> I am not interested in taking a leading role, I am interested in
>> taking *the lead*.  Yes, I am aware of how this comes across and no I
>> will not apologize for it.  As I have stated before, what Stripes
>> needs most is leadership, plain and simple.
> 
> Personally, I was thrilled when I read Ed's comment. I did not read
> any "dictatorship" into it. All I read was that someone was willing
> to step up to the plate, stating it clearly, no two ways about it.
> I respect that very much.
> 
> I agree that Stripes needs leadership. Again, I don't see this as
> a synonym of "dictatorship", nor an opposite to "consensus". What I
> do see in this is someone, Ed, who has the skill and the will to
> assume the role of Stripes lead.
> 
> This does not mean to rule out other participants. But, IMHO, we
> do *need* someone that decides and makes things happen. Sure,
> it's all teamwork, but at the end of the day, when someone submits
> a patch, asks when the next release will be, asks if a feature
> belongs in the framework, and so on, there has to be *someone*
> who is *committed* to addressing and responding.
> 
> It's not a one-man show. But the problem with a team of
> contributors without someone who is the lead, is that for some
> issues, everyone looks at everyone else and no one responds.
> 
> This is why I applaud Ed's statement that he is willing to take
> on this responsibility for Stripes.
> 
> First on the list, I think, is to plan out the release of
> Stripes 1.5.x and Stripes 1.6, and work from there.
> 
> Again, just my 2c. I hope I didn't create more than resolve
> "conflict", and please also know that I don't mean to speak
> for you, Ed. I'm just expressing what I read into it, and I
> hope it rings true with your intentions. I'm pretty sure you
> didn't mean that you would become a dictator, nor that you
> wouldn't encourage teamwork and healthy discussions about
> Stripes' future.
> 
> Personally, I say thanks, Ed. You have my vote.
> 
> Cheers,
> Freddy
> 
> --
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> ___
> Stripes-users mailing list
> Stripes-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/stripes-users


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Freddy Daoud]

Just my 2c, I hope this doesn't make things "worse" in terms of
misunderstandings.

>I am not interested in taking a leading role, I am interested in
>taking *the lead*.  Yes, I am aware of how this comes across and no I
>will not apologize for it.  As I have stated before, what Stripes
>needs most is leadership, plain and simple.

Personally, I was thrilled when I read Ed's comment. I did not read
any "dictatorship" into it. All I read was that someone was willing
to step up to the plate, stating it clearly, no two ways about it.
I respect that very much.

I agree that Stripes needs leadership. Again, I don't see this as
a synonym of "dictatorship", nor an opposite to "consensus". What I
do see in this is someone, Ed, who has the skill and the will to
assume the role of Stripes lead.

This does not mean to rule out other participants. But, IMHO, we
do *need* someone that decides and makes things happen. Sure,
it's all teamwork, but at the end of the day, when someone submits
a patch, asks when the next release will be, asks if a feature
belongs in the framework, and so on, there has to be *someone*
who is *committed* to addressing and responding.

It's not a one-man show. But the problem with a team of
contributors without someone who is the lead, is that for some
issues, everyone looks at everyone else and no one responds.

This is why I applaud Ed's statement that he is willing to take
on this responsibility for Stripes.

First on the list, I think, is to plan out the release of
Stripes 1.5.x and Stripes 1.6, and work from there.

Again, just my 2c. I hope I didn't create more than resolve
"conflict", and please also know that I don't mean to speak
for you, Ed. I'm just expressing what I read into it, and I
hope it rings true with your intentions. I'm pretty sure you
didn't mean that you would become a dictator, nor that you
wouldn't encourage teamwork and healthy discussions about
Stripes' future.

Personally, I say thanks, Ed. You have my vote.

Cheers,
Freddy

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[VANKEISBELCK Remi]

Edward,

Really I didn't mean to be harshe. My poor english + all this story...

Anyway. I just want to know what you mean by "project lead".

If it's about coordinating things, managing releases, organizing bugs, doing
some marketing, keeping people up-to-date and organized, well, we certainly
need that. Freddy did some of that job very well, he's been quite a good
representative for us, and the book has made Stripes a lot more popular than
it's ever been. Yes, we might need other profiles than coding monkeys like
the core team currently is (no pun intended), if we want Stripes to be
really popular. Note that I don't really understand why everyone wants this
to happen so badly, but anyway...

On the other hand, if it's about deciding of the future of the framework
without commonn agreement (I'm expecially concerned about the design and
APIs, I don't really care about the markting aspect - again, it works for
me), then we have a problem. As I already said, I believe in consensus.
And if you really need to be the only one deciding for the choices made in
the framework, then fork and do whatever you like. Who knows ? Maybe you'll
eventually come up with a better Stripes, and I'll use yours.

Until then, well, I personally refer sticking to the good old community way,
where everyone has his word to say, and we all try to understand each
other's view. Not only it's productive, I find it very enjoyable :)

Cheers

Remi

2010/9/21 Edward Smith 

>  "Any transfer in stewardship should probably be to a committer, or a
> regular submitter at the very least"
>
>
>
> +1 from me.
>
>
>
> Anything else I say on the matter will just confuse things even more.
>
>
>
> *Edward Smith*
>
> *Senior Software Developer*
>
> *214-272-5225 (direct)*
>
> *esm...@peopleanswers.com** *
>
> *PeopleAnswers**®** **
>  ** *Better Insight.  Better People. **
>
>  *Check out our blog: blog.peopleanswers.com*
>
> CONFIDENTIALITY NOTE: This email (including any attachments) is
> confidential and may be protected by legal privilege. If you are not the
> intended recipient, be aware that any disclosure, copying, distribution, or
> use of the information contained herein is prohibited.  If you have received
> this message in error, please notify the sender by replying to this message
> and then delete this message in its entirety. Thank you for your
> cooperation.
>
>
>
> *From:* Brandon Atkinson [mailto:brandon.n.atkin...@gmail.com]
> *Sent:* Tuesday, September 21, 2010 1:54 PM
> *To:* r...@rvkb.com; Stripes Users List
>
> *Subject:* Re: [Stripes-users] IMPORTANT:: Developing stripes (Future...
> Part DEUX)
>
>
>
> "I must admit I'm confused as well... starts with a new website and ends up
> in a dictatorship ? This thread's really getting more and more interesting
> :P"
>
>
>
> +1 to that. Love the drama :)
>
>
>
> Any transfer in stewardship should probably be to a committer, or a regular
> submitter at the very least.
>
>
>
> Otherwise, just fork, and let the best team win.
>
>
>
> On Tue, Sep 21, 2010 at 2:28 PM, VANKEISBELCK Remi  wrote:
>
> I must admit I'm confused as well... starts with a new website and ends up
> in a dictatorship ? This thread's really getting more and more interesting
> :P
>
> Until now we (stripes users) always have reached consensus. I think the
> whole core team and other "usual suspects" are legit to speak on any
> decision, because they have proven dedication over the years. Even like
> this, nobody never abused, people were always ok to discuss things and not
> impose anything to others by force. Until then, this system has had an
> excellent impact on the quality of the framework.
>
> Now why would Stripes suddenly need a single responsible person as THE
> project lead ?
>
> Don't get me wrong, again, all efforts are appreciated. But just to get
> things clear, what would you do exactly as THE project lead ? What's the
> void you're trying to fill ?
> And most of all, why do you think you need to be the only lead ? What's
> your problem in sharing this responsibility ? Ain't this kind of "proposal"
> at the opposite of the Open Source philosophy (groups of people sharing
> common interests and working together to get things done) ?
>
> Cheers
>
> Remi
>
>  2010/9/21 Edward Smith 
>
>
>
> Evan,
>
>
>
>I am not interested in taking a leading role, I am interested in taking
> *the lead*.  Yes, I am aware of how this comes across and no I will not
> apologize for it.  As I have stated before, what Stripes needs most is
> leadership, plain and simple.
>
>
>
>If you or anyone else has the capability to lead a project, then great.
> Go for it.  Knock yourself out.  It sounds like you have some leadership
> acumen so it wouldn't bother me a bit if *you* want to take the reigns.  If
> not, then I'm offering my services free of charge to the Stripes community.
> All I'm interested in is that *somebody* do it.  Period.  This ad hoc crap
> just ain't gonna cut it.
>
>
>
> Ed
>
>
>
> *Edward Smith*
>
> *Senior So

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Edward Smith]

"Any transfer in stewardship should probably be to a committer, or a regular 
submitter at the very least"

+1 from me.

Anything else I say on the matter will just confuse things even more.

Edward Smith
Senior Software Developer
214-272-5225 (direct)
esm...@peopleanswers.com
PeopleAnswers®
  Better Insight.  Better People.
 Check out our blog: blog.peopleanswers.com
CONFIDENTIALITY NOTE: This email (including any attachments) is confidential 
and may be protected by legal privilege. If you are not the intended recipient, 
be aware that any disclosure, copying, distribution, or use of the information 
contained herein is prohibited.  If you have received this message in error, 
please notify the sender by replying to this message and then delete this 
message in its entirety. Thank you for your cooperation.

From: Brandon Atkinson [mailto:brandon.n.atkin...@gmail.com]
Sent: Tuesday, September 21, 2010 1:54 PM
To: r...@rvkb.com; Stripes Users List
Subject: Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part 
DEUX)

"I must admit I'm confused as well... starts with a new website and ends up in 
a dictatorship ? This thread's really getting more and more interesting :P"

+1 to that. Love the drama :)

Any transfer in stewardship should probably be to a committer, or a regular 
submitter at the very least.

Otherwise, just fork, and let the best team win.

On Tue, Sep 21, 2010 at 2:28 PM, VANKEISBELCK Remi 
mailto:r...@rvkb.com>> wrote:
I must admit I'm confused as well... starts with a new website and ends up in a 
dictatorship ? This thread's really getting more and more interesting :P

Until now we (stripes users) always have reached consensus. I think the whole 
core team and other "usual suspects" are legit to speak on any decision, 
because they have proven dedication over the years. Even like this, nobody 
never abused, people were always ok to discuss things and not impose anything 
to others by force. Until then, this system has had an excellent impact on the 
quality of the framework.

Now why would Stripes suddenly need a single responsible person as THE project 
lead ?

Don't get me wrong, again, all efforts are appreciated. But just to get things 
clear, what would you do exactly as THE project lead ? What's the void you're 
trying to fill ?
And most of all, why do you think you need to be the only lead ? What's your 
problem in sharing this responsibility ? Ain't this kind of "proposal" at the 
opposite of the Open Source philosophy (groups of people sharing common 
interests and working together to get things done) ?

Cheers

Remi

2010/9/21 Edward Smith 
mailto:esm...@peopleanswers.com>>

Evan,

   I am not interested in taking a leading role, I am interested in taking *the 
lead*.  Yes, I am aware of how this comes across and no I will not apologize 
for it.  As I have stated before, what Stripes needs most is leadership, plain 
and simple.

   If you or anyone else has the capability to lead a project, then great.  Go 
for it.  Knock yourself out.  It sounds like you have some leadership acumen so 
it wouldn't bother me a bit if *you* want to take the reigns.  If not, then I'm 
offering my services free of charge to the Stripes community.  All I'm 
interested in is that *somebody* do it.  Period.  This ad hoc crap just ain't 
gonna cut it.

Ed

Edward Smith
Senior Software Developer
214-272-5225 (direct)
esm...@peopleanswers.com
PeopleAnswers®
  Better Insight.  Better People.
 Check out our blog: blog.peopleanswers.com

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Brandon Atkinson]

"I must admit I'm confused as well... starts with a new website and ends up
in a dictatorship ? This thread's really getting more and more interesting
:P"

+1 to that. Love the drama :)

Any transfer in stewardship should probably be to a committer, or a regular
submitter at the very least.

Otherwise, just fork, and let the best team win.

On Tue, Sep 21, 2010 at 2:28 PM, VANKEISBELCK Remi  wrote:

> I must admit I'm confused as well... starts with a new website and ends up
> in a dictatorship ? This thread's really getting more and more interesting
> :P
>
> Until now we (stripes users) always have reached consensus. I think the
> whole core team and other "usual suspects" are legit to speak on any
> decision, because they have proven dedication over the years. Even like
> this, nobody never abused, people were always ok to discuss things and not
> impose anything to others by force. Until then, this system has had an
> excellent impact on the quality of the framework.
>
> Now why would Stripes suddenly need a single responsible person as THE
> project lead ?
>
> Don't get me wrong, again, all efforts are appreciated. But just to get
> things clear, what would you do exactly as THE project lead ? What's the
> void you're trying to fill ?
> And most of all, why do you think you need to be the only lead ? What's
> your problem in sharing this responsibility ? Ain't this kind of "proposal"
> at the opposite of the Open Source philosophy (groups of people sharing
> common interests and working together to get things done) ?
>
> Cheers
>
> Remi
>
>
> 2010/9/21 Edward Smith 
>
>  Evan,
>>
>>
>>
>>I am not interested in taking a leading role, I am interested in taking
>> *the lead*.  Yes, I am aware of how this comes across and no I will not
>> apologize for it.  As I have stated before, what Stripes needs most is
>> leadership, plain and simple.
>>
>>
>>
>>If you or anyone else has the capability to lead a project, then
>> great.  Go for it.  Knock yourself out.  It sounds like you have some
>> leadership acumen so it wouldn't bother me a bit if *you* want to take the
>> reigns.  If not, then I'm offering my services free of charge to the Stripes
>> community.  All I'm interested in is that *somebody* do it.  Period.  This
>> ad hoc crap just ain't gonna cut it.
>>
>>
>>
>> Ed
>>
>>
>>
>> *Edward Smith*
>>
>> *Senior Software Developer*
>>
>> *214-272-5225 (direct)*
>>
>> *esm...@peopleanswers.com** *
>>
>> *PeopleAnswers**®** **
>>  ** *Better Insight.  Better People. **
>>
>>  *Check out our blog: blog.peopleanswers.com*
>>
>
>
> --
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> ___
> Stripes-users mailing list
> Stripes-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/stripes-users
>
>
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[VANKEISBELCK Remi]

I must admit I'm confused as well... starts with a new website and ends up
in a dictatorship ? This thread's really getting more and more interesting
:P

Until now we (stripes users) always have reached consensus. I think the
whole core team and other "usual suspects" are legit to speak on any
decision, because they have proven dedication over the years. Even like
this, nobody never abused, people were always ok to discuss things and not
impose anything to others by force. Until then, this system has had an
excellent impact on the quality of the framework.

Now why would Stripes suddenly need a single responsible person as THE
project lead ?

Don't get me wrong, again, all efforts are appreciated. But just to get
things clear, what would you do exactly as THE project lead ? What's the
void you're trying to fill ?
And most of all, why do you think you need to be the only lead ? What's your
problem in sharing this responsibility ? Ain't this kind of "proposal" at
the opposite of the Open Source philosophy (groups of people sharing common
interests and working together to get things done) ?

Cheers

Remi


2010/9/21 Edward Smith 

>  Evan,
>
>
>
>I am not interested in taking a leading role, I am interested in taking
> *the lead*.  Yes, I am aware of how this comes across and no I will not
> apologize for it.  As I have stated before, what Stripes needs most is
> leadership, plain and simple.
>
>
>
>If you or anyone else has the capability to lead a project, then great.
> Go for it.  Knock yourself out.  It sounds like you have some leadership
> acumen so it wouldn't bother me a bit if *you* want to take the reigns.  If
> not, then I'm offering my services free of charge to the Stripes community.
> All I'm interested in is that *somebody* do it.  Period.  This ad hoc crap
> just ain't gonna cut it.
>
>
>
> Ed
>
>
>
> *Edward Smith*
>
> *Senior Software Developer*
>
> *214-272-5225 (direct)*
>
> *esm...@peopleanswers.com** *
>
> *PeopleAnswers**®** **
>  ** *Better Insight.  Better People. **
>
>  *Check out our blog: blog.peopleanswers.com*
>
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Søren Pedersen]

Hi Ben and others

I have recently become a Stripes user and have joined the users list.
I must say that I am very impressed by the framework and the users mailing
list.
Seldom have I used a framework which is so intuitive to understand and use,
and there is a lot of good answers on the list.

At the moment I am working to introduce Stripes as the new framework in a
very heavy webapplication with several hundred thousand of users. To do this
I need to hook into an old CMS that handles the layout of the pages and
create hooks to other parts of the old framework which contains
functionality that we still have a need for, even though we use Stripes.
Totally we are about 20-30 developers who will use Stripes once we are done.
Until now, the ride with Stripes has been smooth and elegant and the need
for extending Stripes has been fulfilled with ease and with a fealing of
"hahhaa, this is cool... :-)" - "whoouuw, it can also do that...". Just
as promised in Freddys book :-)

A little about myself will be that I have been working with J2EE/JEE since
2000 and I have created a lot of "large" systems with heavy database
backends. I consider myself to be quite experienced, although I may not be
able at cite all JEE specs while sleeping.

I will be delighted to blog about my experience with integrating Stripes
into a large legacy web application.
I will also be glad to help chasing bugs in Stripes, and if I get the
chance, help implementing features.

With deep respect for the work that the community has done in developing
Stripes...

Thank you

Søren


2010/9/21 Ben Gunter 

> Excellent. I'll be keeping a running log of volunteers, and when we've
> heard from everybody I'll post a summary to the list and start looking at
> getting people the access they need.
>
> 2010/9/21 Grzegorz Krugły 
>
>  I can offer some of my time in testing and fixing bugs and/or
>> implementing new stuff - especially if they are on Glassfish. This will
>> come for me as a small overhead because I use Stripes on a daily basis
>> in my commercial projects and have been browsing its source code a few
>> times already to fix some little annoyances I encountered.
>>
>> I can also review some of incoming patches and changes before they get
>> merged into the trunk, I've quite a bit of experience in JavaEE and
>> overall software development, even though I'm sure there are people way
>> better than I am.
>>
>> >From time to time I should be able to write blog posts about using
>> Stripes, on my site or on Stripe's Blog.
>>
>> Best regards,
>> Grzegorz
>>
>>
>
>
> --
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> ___
> Stripes-users mailing list
> Stripes-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/stripes-users
>
>
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Evan Leonard]

Yeah the dedication is the necessary ingredient for sure!

Once we've got that, tools can help though :-)

Personally, I'm a fan of Mercurial, for much of the same reason that Google 
Code is:
http://googlecode.blogspot.com/2009/04/mercurial-support-for-project-hosting.html

Evan


On Sep 21, 2010, at 9:57 AM, VANKEISBELCK Remi wrote:

> Yeah, been busy !
> 
> Well, I guess that (even at my young age !), I'm kinda old fashioned... :P
> 
> Actually I wasn't speaking about the tool. What I meant is that whetever the 
> hosting platform, you can always contribute in various ways. No need to have 
> all privileges for that, it's only a matter of goodwill. 
> 
> We've had countless contribs in the past, using just SVN, patches, plus the 
> good old mailing list. It's our dedication that paid off. Not the tools we 
> used.
> 
> For anyone interested in contributing : build that damn website, send patches 
> for bug fixes, propose your ideas on the ML, advertise to your 
> friends/colleagues, post in blogs... this is what will keep Stripes alive 
> (when Ben will retire on a beach in Tahiti... :P). 
> 
> Cheers
> 
> Remi
> 
> 
> 2010/9/21 Jeppe Cramon 
> Hi Remi
> 
> Long time :)
> 
> IMO forking is a good thing, IF it's done in Git style where it easy to keep 
> up with those who have forked the master and push/pull between those 
> interested :)
> It makes it so much easier to experiment and do patches and leave them for 
> everyone to see, including the Stripes comitter, if it's hosted in you own 
> GitHub repository.
> Having to fetch Strips sourcecode from SVN, create a patch file and send it 
> in and hope that someone will accept it, is just too 2000 ;)
> 
> /Jeppe
> 
> On Tue, 21 Sep 2010 16:25:19 +0200, VANKEISBELCK Remi  wrote:
> 
> Hi folks
> 
> I've been following this thread not really knwoing how to responde, Ben, you 
> took the words out of my mouth :)
> 
> I'm also perfeclty happy with Stripes as is. Sure more developers would be 
> agood thing. But forking like crazy etc... not sure this will help. Nothing 
> prevents anyone to experiment with the codebase, and send their contribs. I 
> have no doubts they will be accepted if they are worth it, and inline with 
> the Stripes spirit.   
> 
> Cheers
> 
> Remi
> 
> 2010/9/21 Ben Gunter 
> Well, it looks like life picked a bad time to get busy for me. I just now got 
> around to catching up on this thread. I'm sure my silence caused some 
> concern. Sorry about that.
> 
> I completely agree with the sentiment that we need eager new developers to 
> contribute to the project. Those who know me know that I'm not about politics 
> or control or ego. I would love to bring some eager new developers in to help 
> rejuvenate the project.
> 
> There was a time a few years ago when I had that same enthusiasm for 
> developing Stripes. I answered lots of questions on the mailing list with 
> tons of code samples. I started the Stripes Extras project to add some 
> security to the binding stage so developers wouldn't have to worry about evil 
> stuff getting poked into their ActionBeans. I had bigger plans for Stripes 
> Extras, but Tim took notice of my activity and invited me to contribute 
> directly to the Stripes core. I accepted, and the features of Stripes Extras 
> were merged in for Stripes 1.5. Freddy and Aaron and a few others joined in 
> on the 1.5 effort, and we finally released what I think is a pretty nice 
> product: binding security, clean URLs, DynamicMappingFilter, minimal 
> configuration, improved type conversion and formatting. Not too shabby.
> 
> What we were then was a great group of developers with a clear vision for 
> what we wanted Stripes to be and a singular focus on making it happen. What 
> we are now is a great group of developers who have a framework with which 
> we're quite satisfied. I remember clearly that when Tim brought me in he said 
> -- I think it was on IRC -- that he was happy with Stripes as it was. That is 
> where I stand now. Like Tim was then, I am happy to hand over the reins to 
> someone who can drive the project forward, while offering any help I can 
> along the way.
> 
> Over the last few years, I have heard time and time again the chorus of "we 
> should do this" or "we should do that." What I have learned, though, is that 
> more often than not it really means "you should do this" or "you should do 
> that." I have poured hours and hours into finding and fixing bugs that do not 
> affect me personally. Generally, it's very difficult to get cooperation from 
> people in testing patches to ensure the bug they've reported is fixed. 
> Complaints about how something works or does not work are rarely accompanied 
> by a solution to the perceived problem.
> 
> My point is that talk is cheap. Who out there is really willing to dig in and 
> learn the Stripes code and dedicate a good chunk of time on a regular basis 
> to make it better? Who is willing to design a new web site? Who is willing to 
> review a

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Evan Leonard]

I put a draft of the needed activities list here to more easily update it:

http://groups.google.com/group/stripeswebsite/web/needed-activites-proposal

When replying to Ben's call for help, have a look at this list and see which 
activities you can sign-up for, or suggest new activities that need to be 
added, removed, updated!

Evan



On Sep 21, 2010, at 9:36 AM, Jeppe Cramon wrote:

> Hi Remi
> 
> Long time :)
> 
> IMO forking is a good thing, IF it's done in Git style where it easy to keep 
> up with those who have forked the master and push/pull between those 
> interested :)
> It makes it so much easier to experiment and do patches and leave them for 
> everyone to see, including the Stripes comitter, if it's hosted in you own 
> GitHub repository.
> Having to fetch Strips sourcecode from SVN, create a patch file and send it 
> in and hope that someone will accept it, is just too 2000 ;)
> 
> /Jeppe
> 
> On Tue, 21 Sep 2010 16:25:19 +0200, VANKEISBELCK Remi  wrote:
> 
> Hi folks
> 
> I've been following this thread not really knwoing how to responde, Ben, you 
> took the words out of my mouth :)
> 
> I'm also perfeclty happy with Stripes as is. Sure more developers would be 
> agood thing. But forking like crazy etc... not sure this will help. Nothing 
> prevents anyone to experiment with the codebase, and send their contribs. I 
> have no doubts they will be accepted if they are worth it, and inline with 
> the Stripes spirit.   
> 
> Cheers
> 
> Remi
> 
> 2010/9/21 Ben Gunter 
> Well, it looks like life picked a bad time to get busy for me. I just now got 
> around to catching up on this thread. I'm sure my silence caused some 
> concern. Sorry about that.
> 
> I completely agree with the sentiment that we need eager new developers to 
> contribute to the project. Those who know me know that I'm not about politics 
> or control or ego. I would love to bring some eager new developers in to help 
> rejuvenate the project.
> 
> There was a time a few years ago when I had that same enthusiasm for 
> developing Stripes. I answered lots of questions on the mailing list with 
> tons of code samples. I started the Stripes Extras project to add some 
> security to the binding stage so developers wouldn't have to worry about evil 
> stuff getting poked into their ActionBeans. I had bigger plans for Stripes 
> Extras, but Tim took notice of my activity and invited me to contribute 
> directly to the Stripes core. I accepted, and the features of Stripes Extras 
> were merged in for Stripes 1.5. Freddy and Aaron and a few others joined in 
> on the 1.5 effort, and we finally released what I think is a pretty nice 
> product: binding security, clean URLs, DynamicMappingFilter, minimal 
> configuration, improved type conversion and formatting. Not too shabby.
> 
> What we were then was a great group of developers with a clear vision for 
> what we wanted Stripes to be and a singular focus on making it happen. What 
> we are now is a great group of developers who have a framework with which 
> we're quite satisfied. I remember clearly that when Tim brought me in he said 
> -- I think it was on IRC -- that he was happy with Stripes as it was. That is 
> where I stand now. Like Tim was then, I am happy to hand over the reins to 
> someone who can drive the project forward, while offering any help I can 
> along the way.
> 
> Over the last few years, I have heard time and time again the chorus of "we 
> should do this" or "we should do that." What I have learned, though, is that 
> more often than not it really means "you should do this" or "you should do 
> that." I have poured hours and hours into finding and fixing bugs that do not 
> affect me personally. Generally, it's very difficult to get cooperation from 
> people in testing patches to ensure the bug they've reported is fixed. 
> Complaints about how something works or does not work are rarely accompanied 
> by a solution to the perceived problem.
> 
> My point is that talk is cheap. Who out there is really willing to dig in and 
> learn the Stripes code and dedicate a good chunk of time on a regular basis 
> to make it better? Who is willing to design a new web site? Who is willing to 
> review and correct and improve the documentation? Who is willing create and 
> maintain a Stripes-centric blog with regular articles?
> 
> If you are willing and able *right now* to start making a real contribution 
> to the project, then respond to this email and commit to it. Let us know your 
> name, your history with Stripes, how you want to contribute, and any other 
> information that you think is relevant. If you can't contribute now but hope 
> to be able to in the future, then please wait until that time comes to speak 
> up. What I want is to know who we have in this group who can help breathe new 
> life into Stripes starting today. Let's hear it.
> 
> -Ben
> 
> 
> On Sun, Sep 19, 2010 at 2:51 PM, Jeppe Cramon  wrote:
> Hi guys
> 
> I've been following this res

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[VANKEISBELCK Remi]

Yeah, been busy !

Well, I guess that (even at my young age !), I'm kinda old fashioned... :P

Actually I wasn't speaking about the tool. What I meant is that whetever the
hosting platform, you can always contribute in various ways. No need to have
all privileges for that, it's only a matter of goodwill.

We've had countless contribs in the past, using just SVN, patches, plus the
good old mailing list. It's our dedication that paid off. Not the tools we
used.

For anyone interested in contributing : build that damn website, send
patches for bug fixes, propose your ideas on the ML, advertise to your
friends/colleagues, post in blogs... this is what will keep Stripes alive
(when Ben will retire on a beach in Tahiti... :P).

Cheers

Remi


2010/9/21 Jeppe Cramon 

> Hi Remi
>
> Long time :)
>
> IMO forking is a good thing, IF it's done in Git style where it easy to
> keep up with those who have forked the master and push/pull between those
> interested :)
> It makes it so much easier to experiment and do patches and leave them for
> everyone to see, including the Stripes comitter, if it's hosted in you own
> GitHub repository.
> Having to fetch Strips sourcecode from SVN, create a patch file and send it
> in and hope that someone will accept it, is just too 2000 ;)
>
> /Jeppe
>
> On Tue, 21 Sep 2010 16:25:19 +0200, VANKEISBELCK Remi 
> wrote:
>
> Hi folks
>
> I've been following this thread not really knwoing how to responde, Ben,
> you took the words out of my mouth :)
>
> I'm also perfeclty happy with Stripes as is. Sure more developers would be
> agood thing. But forking like crazy etc... not sure this will help. Nothing
> prevents anyone to experiment with the codebase, and send their contribs. I
> have no doubts they will be accepted if they are worth it, and inline with
> the Stripes spirit.
>
> Cheers
>
> Remi
>
> 2010/9/21 Ben Gunter 
>
>> Well, it looks like life picked a bad time to get busy for me. I just now
>> got around to catching up on this thread. I'm sure my silence caused some
>> concern. Sorry about that.
>>
>> I completely agree with the sentiment that we need eager new developers to
>> contribute to the project. Those who know me know that I'm not about
>> politics or control or ego. I would love to bring some eager new developers
>> in to help rejuvenate the project.
>>
>> There was a time a few years ago when I had that same enthusiasm for
>> developing Stripes. I answered lots of questions on the mailing list with
>> tons of code samples. I started the Stripes Extras project to add some
>> security to the binding stage so developers wouldn't have to worry about
>> evil stuff getting poked into their ActionBeans. I had bigger plans for
>> Stripes Extras, but Tim took notice of my activity and invited me to
>> contribute directly to the Stripes core. I accepted, and the features of
>> Stripes Extras were merged in for Stripes 1.5. Freddy and Aaron and a few
>> others joined in on the 1.5 effort, and we finally released what I think is
>> a pretty nice product: binding security, clean URLs, DynamicMappingFilter,
>> minimal configuration, improved type conversion and formatting. Not too
>> shabby.
>>
>> What we were then was a great group of developers with a clear vision for
>> what we wanted Stripes to be and a singular focus on making it happen. What
>> we are now is a great group of developers who have a framework with which
>> we're quite satisfied. I remember clearly that when Tim brought me in he
>> said -- I think it was on IRC -- that he was happy with Stripes as it was.
>> That is where I stand now. Like Tim was then, I am happy to hand over the
>> reins to someone who can drive the project forward, while offering any help
>> I can along the way.
>>
>> Over the last few years, I have heard time and time again the chorus of
>> "we should do this" or "we should do that." What I have learned, though, is
>> that more often than not it really means "you should do this" or "you should
>> do that." I have poured hours and hours into finding and fixing bugs that do
>> not affect me personally. Generally, it's very difficult to get cooperation
>> from people in testing patches to ensure the bug they've reported is fixed.
>> Complaints about how something works or does not work are rarely accompanied
>> by a solution to the perceived problem.
>>
>> My point is that talk is cheap. Who out there is really willing to dig in
>> and learn the Stripes code and dedicate a good chunk of time on a regular
>> basis to make it better? Who is willing to design a new web site? Who is
>> willing to review and correct and improve the documentation? Who is willing
>> create and maintain a Stripes-centric blog with regular articles?
>>
>> If you are willing and able *right now* to start making a real
>> contribution to the project, then respond to this email and commit to it.
>> Let us know your name, your history with Stripes, how you want to
>> contribute, and any other information that you think is rel

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Evan Leonard]

Ben, good to hear from you!

As I mentioned before my concern mainly is that there's a well understood 
process for participating and contributing. I appreciate your points also about 
"we should" versus "you should". Getting a list of available people, skills, 
and time is a good first step toward combating that. Here's a page on the new 
website group where a few people have volunteered already:  
http://groups.google.com/group/stripeswebsite/web/available-resources

If I may make a suggestion, a good second step would be to list all the 
activities that need to happen. This list can be published on the site to show 
the open opportunities to jump in an contribute. The community can update this 
list as needed. We can then assign available people to each so that we know who 
to talk with when we have a question about any particular activity. And people 
can de-assign themselves or find a replacement when they can no longer fill the 
role. Here's the activities I've heard so far:

* Triaging incoming issues
* Reviewing patches & maintaining Stripes focus
* Fixing identified issues 
* Blogging about stripes
* Publishing builds to Maven Central
* Designing a new website (visual & interaction design)
* Building a new website (programming and deployment)
* Updating documentation on website
* Organizing extensions projects
* Maintaining this activity list and associated assignments

What have I missed?


Oh, and here's what I can help with: I definitely would be on the list of 
people to fix some issues. I can write a blog post or two about my usage of 
Stripes. I can facilitate the  maintenance the activities list and associated 
assignments. And I'm interested in discussing how to organize the extensions 
projects too.


Evan
 


On Sep 21, 2010, at 8:16 AM, Ben Gunter wrote:

> Well, it looks like life picked a bad time to get busy for me. I just now got 
> around to catching up on this thread. I'm sure my silence caused some 
> concern. Sorry about that.
> 
> I completely agree with the sentiment that we need eager new developers to 
> contribute to the project. Those who know me know that I'm not about politics 
> or control or ego. I would love to bring some eager new developers in to help 
> rejuvenate the project.
> 
> There was a time a few years ago when I had that same enthusiasm for 
> developing Stripes. I answered lots of questions on the mailing list with 
> tons of code samples. I started the Stripes Extras project to add some 
> security to the binding stage so developers wouldn't have to worry about evil 
> stuff getting poked into their ActionBeans. I had bigger plans for Stripes 
> Extras, but Tim took notice of my activity and invited me to contribute 
> directly to the Stripes core. I accepted, and the features of Stripes Extras 
> were merged in for Stripes 1.5. Freddy and Aaron and a few others joined in 
> on the 1.5 effort, and we finally released what I think is a pretty nice 
> product: binding security, clean URLs, DynamicMappingFilter, minimal 
> configuration, improved type conversion and formatting. Not too shabby.
> 
> What we were then was a great group of developers with a clear vision for 
> what we wanted Stripes to be and a singular focus on making it happen. What 
> we are now is a great group of developers who have a framework with which 
> we're quite satisfied. I remember clearly that when Tim brought me in he said 
> -- I think it was on IRC -- that he was happy with Stripes as it was. That is 
> where I stand now. Like Tim was then, I am happy to hand over the reins to 
> someone who can drive the project forward, while offering any help I can 
> along the way.
> 
> Over the last few years, I have heard time and time again the chorus of "we 
> should do this" or "we should do that." What I have learned, though, is that 
> more often than not it really means "you should do this" or "you should do 
> that." I have poured hours and hours into finding and fixing bugs that do not 
> affect me personally. Generally, it's very difficult to get cooperation from 
> people in testing patches to ensure the bug they've reported is fixed. 
> Complaints about how something works or does not work are rarely accompanied 
> by a solution to the perceived problem.
> 
> My point is that talk is cheap. Who out there is really willing to dig in and 
> learn the Stripes code and dedicate a good chunk of time on a regular basis 
> to make it better? Who is willing to design a new web site? Who is willing to 
> review and correct and improve the documentation? Who is willing create and 
> maintain a Stripes-centric blog with regular articles?
> 
> If you are willing and able *right now* to start making a real contribution 
> to the project, then respond to this email and commit to it. Let us know your 
> name, your history with Stripes, how you want to contribute, and any other 
> information that you think is relevant. If you can't contribute now but hope 
> to be able to in the future, t

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Jeppe Cramon]

Hi RemiLong time :)IMO forking is a good thing, IF it's done in Git style where it easy to keep up with those who have forked the master and push/pull between those interested :)It makes it so much easier to experiment and do patches and leave them for everyone to see, including the Stripes comitter, if it's hosted in you own GitHub repository.Having to fetch Strips sourcecode from SVN, create a patch file and send it in and hope that someone will accept it, is just too 2000 ;)/JeppeOn Tue, 21 Sep 2010 16:25:19 +0200, VANKEISBELCK Remi  wrote:Hi folksI've been following this thread not really knwoing how to responde, Ben, you took the words out of my mouth :)I'm also perfeclty happy with Stripes as is. Sure more developers would be agood thing. But forking like crazy etc... not sure this will help. Nothing prevents anyone to experiment with the codebase, and send their contribs. I have no doubts they will be accepted if they are worth it, and inline with the Stripes spirit.   
CheersRemi2010/9/21 Ben Gunter 
Well, it looks like life picked a bad time to get busy for me. I just now got around to catching up on this thread. I'm sure my silence caused some concern. Sorry about that.I completely agree with the sentiment that we need eager new developers to contribute to the project. Those who know me know that I'm not about politics or control or ego. I would love to bring some eager new developers in to help rejuvenate the project.


There was a time a few years ago when I had that same enthusiasm for developing Stripes. I answered lots of questions on the mailing list with tons of code samples. I started the Stripes Extras project to add some security to the binding stage so developers wouldn't have to worry about evil stuff getting poked into their ActionBeans. I had bigger plans for Stripes Extras, but Tim took notice of my activity and invited me to contribute directly to the Stripes core. I accepted, and the features of Stripes Extras were merged in for Stripes 1.5. Freddy and Aaron and a few others joined in on the 1.5 effort, and we finally released what I think is a pretty nice product: binding security, clean URLs, DynamicMappingFilter, minimal configuration, improved type conversion and formatting. Not too shabby.


What we were then was a great group of developers with a clear vision for what we wanted Stripes to be and a singular focus on making it happen. What we are now is a great group of developers who have a framework with which we're quite satisfied. I remember clearly that when Tim brought me in he said -- I think it was on IRC -- that he was happy with Stripes as it was. That is where I stand now. Like Tim was then, I am happy to hand over the reins to someone who can drive the project forward, while offering any help I can along the way.


Over the last few years, I have heard time and time again the chorus of "we should do this" or "we should do that." What I have learned, though, is that more often than not it really means "you should do this" or "you should do that." I have poured hours and hours into finding and fixing bugs that do not affect me personally. Generally, it's very difficult to get cooperation from people in testing patches to ensure the bug they've reported is fixed. Complaints about how something works or does not work are rarely accompanied by a solution to the perceived problem.


My point is that talk is cheap. Who out there is really willing to dig in and learn the Stripes code and dedicate a good chunk of time on a regular basis to make it better? Who is  willing to design a new web site? Who is willing to review and correct and improve the documentation? Who is willing create and maintain a Stripes-centric blog with regular articles?


If you are willing and able *right now* to start making a real contribution to the project, then respond to this email and commit to it. Let us know your name, your history with Stripes, how you want to contribute, and any other information  that you think is relevant. If you can't contribute now but hope to be able to in the future, then please wait until that time comes to speak up. What I want is to know who we have in this group who can help breathe new life into Stripes starting today. Let's hear it.


-BenOn Sun, Sep 19, 2010 at 2:51 PM, Jeppe Cramon  wrote:





Hi guysI've been following this resurrection thread for a while and even though I contributed some core parts to Stripes in the early days I haven't really had the need for something like Stripes in a long time (for instance it lacks proper REST and Comet style support).


IMO Stripes has faded because it has been too difficult to participate, add patches and features.I like that the core of Stripes is kept tight, with focus on extensibility and what's the core things for an Action based MVC framework.


The low learning curve and the easy extensibility was what attracted me to Stripes in the first place, but the lack of progre

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Ben Gunter]

Excellent. I'll be keeping a running log of volunteers, and when we've heard
from everybody I'll post a summary to the list and start looking at getting
people the access they need.

2010/9/21 Grzegorz Krugły 

>  I can offer some of my time in testing and fixing bugs and/or
> implementing new stuff - especially if they are on Glassfish. This will
> come for me as a small overhead because I use Stripes on a daily basis
> in my commercial projects and have been browsing its source code a few
> times already to fix some little annoyances I encountered.
>
> I can also review some of incoming patches and changes before they get
> merged into the trunk, I've quite a bit of experience in JavaEE and
> overall software development, even though I'm sure there are people way
> better than I am.
>
> >From time to time I should be able to write blog posts about using
> Stripes, on my site or on Stripe's Blog.
>
> Best regards,
> Grzegorz
>
>
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Edward Smith]

Thanks for letting us know where you stand, Ben.  I have been waiting for you 
to chime in and appreciate the input.

My name is Edward Smith, been a user, mentor, and evangelist of Stripes since 
June 2006.  Currently am in a Struts 1.2.x environment with a nearly 19,000 
line struts-config.xml file.  We're looking to rearchitect the application and 
I'm pushing Stripes over Spring MVC and Groovy on Grails as the framework of 
choice.  Very difficult to do considering the factors that have been discussed 
over the past couple weeks.

If you are truly willing to hand over the reigns to Stripes, I am willing to 
take those reigns and run with it.

For a couple years now I've had my own plans for Stripes.  What those plans are 
cannot be disclosed at this time for strategic reasons.  I figure though if I'm 
eventually going to do what I'm going to do with Stripes, I might as well make 
sure any new activity going forward does not deviate from the standards Tim, 
you, Freddy, Aaron, and others have set thus far.

I won't speak about what my qualifications are to take the lead on Stripes.  
Melinda can chime in on my abilities to lead a project if she so chooses.  I 
know I am weakest in the 'marketing' aspects of running an open source project 
simply because I don't have one to advertise.  Other than that, I've got the 
rest of the duties and responsibilities covered.

Anyway, just throwing my hat in the ring.

Ed

Edward Smith
Senior Software Developer
214-272-5225 (direct)
esm...@peopleanswers.com
PeopleAnswers(r)
  Better Insight.  Better People.
 Check out our blog: blog.peopleanswers.com
CONFIDENTIALITY NOTE: This email (including any attachments) is confidential 
and may be protected by legal privilege. If you are not the intended recipient, 
be aware that any disclosure, copying, distribution, or use of the information 
contained herein is prohibited.  If you have received this message in error, 
please notify the sender by replying to this message and then delete this 
message in its entirety. Thank you for your cooperation.

From: Ben Gunter [mailto:gunter...@gmail.com]
Sent: Tuesday, September 21, 2010 9:16 AM
To: Stripes Users List
Subject: Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part 
DEUX)

Well, it looks like life picked a bad time to get busy for me. I just now got 
around to catching up on this thread. I'm sure my silence caused some concern. 
Sorry about that.

I completely agree with the sentiment that we need eager new developers to 
contribute to the project. Those who know me know that I'm not about politics 
or control or ego. I would love to bring some eager new developers in to help 
rejuvenate the project.

There was a time a few years ago when I had that same enthusiasm for developing 
Stripes. I answered lots of questions on the mailing list with tons of code 
samples. I started the Stripes Extras project to add some security to the 
binding stage so developers wouldn't have to worry about evil stuff getting 
poked into their ActionBeans. I had bigger plans for Stripes Extras, but Tim 
took notice of my activity and invited me to contribute directly to the Stripes 
core. I accepted, and the features of Stripes Extras were merged in for Stripes 
1.5. Freddy and Aaron and a few others joined in on the 1.5 effort, and we 
finally released what I think is a pretty nice product: binding security, clean 
URLs, DynamicMappingFilter, minimal configuration, improved type conversion and 
formatting. Not too shabby.

What we were then was a great group of developers with a clear vision for what 
we wanted Stripes to be and a singular focus on making it happen. What we are 
now is a great group of developers who have a framework with which we're quite 
satisfied. I remember clearly that when Tim brought me in he said -- I think it 
was on IRC -- that he was happy with Stripes as it was. That is where I stand 
now. Like Tim was then, I am happy to hand over the reins to someone who can 
drive the project forward, while offering any help I can along the way.

Over the last few years, I have heard time and time again the chorus of "we 
should do this" or "we should do that." What I have learned, though, is that 
more often than not it really means "you should do this" or "you should do 
that." I have poured hours and hours into finding and fixing bugs that do not 
affect me personally. Generally, it's very difficult to get cooperation from 
people in testing patches to ensure the bug they've reported is fixed. 
Complaints about how something works or does not work are rarely accompanied by 
a solution to the perceived problem.

My point is that talk is cheap. Who out there is really willing to dig in and 
learn the Stripes code and dedicate a good chunk of time on a regular basis to 
make it better? Who is willing to design a new web site? Who is willing to 
review and correct and improve the documentation? Who

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Grzegorz Krugły]

I can offer some of my time in testing and fixing bugs and/or
implementing new stuff - especially if they are on Glassfish. This will
come for me as a small overhead because I use Stripes on a daily basis
in my commercial projects and have been browsing its source code a few
times already to fix some little annoyances I encountered.

I can also review some of incoming patches and changes before they get
merged into the trunk, I've quite a bit of experience in JavaEE and
overall software development, even though I'm sure there are people way
better than I am.

>From time to time I should be able to write blog posts about using
Stripes, on my site or on Stripe's Blog.

Best regards,
Grzegorz


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[VANKEISBELCK Remi]

Hi folks

I've been following this thread not really knwoing how to responde, Ben, you
took the words out of my mouth :)

I'm also perfeclty happy with Stripes as is. Sure more developers would be
agood thing. But forking like crazy etc... not sure this will help. Nothing
prevents anyone to experiment with the codebase, and send their contribs. I
have no doubts they will be accepted if they are worth it, and inline with
the Stripes spirit.

Cheers

Remi

2010/9/21 Ben Gunter 

> Well, it looks like life picked a bad time to get busy for me. I just now
> got around to catching up on this thread. I'm sure my silence caused some
> concern. Sorry about that.
>
> I completely agree with the sentiment that we need eager new developers to
> contribute to the project. Those who know me know that I'm not about
> politics or control or ego. I would love to bring some eager new developers
> in to help rejuvenate the project.
>
> There was a time a few years ago when I had that same enthusiasm for
> developing Stripes. I answered lots of questions on the mailing list with
> tons of code samples. I started the Stripes Extras project to add some
> security to the binding stage so developers wouldn't have to worry about
> evil stuff getting poked into their ActionBeans. I had bigger plans for
> Stripes Extras, but Tim took notice of my activity and invited me to
> contribute directly to the Stripes core. I accepted, and the features of
> Stripes Extras were merged in for Stripes 1.5. Freddy and Aaron and a few
> others joined in on the 1.5 effort, and we finally released what I think is
> a pretty nice product: binding security, clean URLs, DynamicMappingFilter,
> minimal configuration, improved type conversion and formatting. Not too
> shabby.
>
> What we were then was a great group of developers with a clear vision for
> what we wanted Stripes to be and a singular focus on making it happen. What
> we are now is a great group of developers who have a framework with which
> we're quite satisfied. I remember clearly that when Tim brought me in he
> said -- I think it was on IRC -- that he was happy with Stripes as it was.
> That is where I stand now. Like Tim was then, I am happy to hand over the
> reins to someone who can drive the project forward, while offering any help
> I can along the way.
>
> Over the last few years, I have heard time and time again the chorus of "we
> should do this" or "we should do that." What I have learned, though, is that
> more often than not it really means "you should do this" or "you should do
> that." I have poured hours and hours into finding and fixing bugs that do
> not affect me personally. Generally, it's very difficult to get cooperation
> from people in testing patches to ensure the bug they've reported is fixed.
> Complaints about how something works or does not work are rarely accompanied
> by a solution to the perceived problem.
>
> My point is that talk is cheap. Who out there is really willing to dig in
> and learn the Stripes code and dedicate a good chunk of time on a regular
> basis to make it better? Who is willing to design a new web site? Who is
> willing to review and correct and improve the documentation? Who is willing
> create and maintain a Stripes-centric blog with regular articles?
>
> If you are willing and able *right now* to start making a real contribution
> to the project, then respond to this email and commit to it. Let us know
> your name, your history with Stripes, how you want to contribute, and any
> other information that you think is relevant. If you can't contribute now
> but hope to be able to in the future, then please wait until that time comes
> to speak up. What I want is to know who we have in this group who can help
> breathe new life into Stripes starting today. Let's hear it.
>
> -Ben
>
>
> On Sun, Sep 19, 2010 at 2:51 PM, Jeppe Cramon  wrote:
>
>> Hi guys
>>
>> I've been following this resurrection thread for a while and even though I
>> contributed some core parts to Stripes in the early days I haven't really
>> had the need for something like Stripes in a long time (for instance it
>> lacks proper REST and Comet style support).
>>
>> IMO Stripes has faded because it has been too difficult to participate,
>> add patches and features.
>> I like that the core of Stripes is kept tight, with focus on extensibility
>> and what's the core things for an Action based MVC framework.
>> The low learning curve and the easy extensibility was what attracted me to
>> Stripes in the first place, but the lack of progress & new releases is
>> hurting Stripes.
>>
>> Since this thread has appeared and have started a good discussion, I think
>> it's important to reach a consensus on where to take Stripes.
>> IMO if this thread dies out with any clear forward action, then Stripes is
>> going to whither.
>>
>> I agree with Rick, forking would be a good way to move forward.
>>
>> My suggestion is to put Stripes on GitHub and allow people for Fork it
>> like craz

Re: [Stripes-users] IMPORTANT:: Developing stripes (Future... Part DEUX)

[Ben Gunter]

Well, it looks like life picked a bad time to get busy for me. I just now
got around to catching up on this thread. I'm sure my silence caused some
concern. Sorry about that.

I completely agree with the sentiment that we need eager new developers to
contribute to the project. Those who know me know that I'm not about
politics or control or ego. I would love to bring some eager new developers
in to help rejuvenate the project.

There was a time a few years ago when I had that same enthusiasm for
developing Stripes. I answered lots of questions on the mailing list with
tons of code samples. I started the Stripes Extras project to add some
security to the binding stage so developers wouldn't have to worry about
evil stuff getting poked into their ActionBeans. I had bigger plans for
Stripes Extras, but Tim took notice of my activity and invited me to
contribute directly to the Stripes core. I accepted, and the features of
Stripes Extras were merged in for Stripes 1.5. Freddy and Aaron and a few
others joined in on the 1.5 effort, and we finally released what I think is
a pretty nice product: binding security, clean URLs, DynamicMappingFilter,
minimal configuration, improved type conversion and formatting. Not too
shabby.

What we were then was a great group of developers with a clear vision for
what we wanted Stripes to be and a singular focus on making it happen. What
we are now is a great group of developers who have a framework with which
we're quite satisfied. I remember clearly that when Tim brought me in he
said -- I think it was on IRC -- that he was happy with Stripes as it was.
That is where I stand now. Like Tim was then, I am happy to hand over the
reins to someone who can drive the project forward, while offering any help
I can along the way.

Over the last few years, I have heard time and time again the chorus of "we
should do this" or "we should do that." What I have learned, though, is that
more often than not it really means "you should do this" or "you should do
that." I have poured hours and hours into finding and fixing bugs that do
not affect me personally. Generally, it's very difficult to get cooperation
from people in testing patches to ensure the bug they've reported is fixed.
Complaints about how something works or does not work are rarely accompanied
by a solution to the perceived problem.

My point is that talk is cheap. Who out there is really willing to dig in
and learn the Stripes code and dedicate a good chunk of time on a regular
basis to make it better? Who is willing to design a new web site? Who is
willing to review and correct and improve the documentation? Who is willing
create and maintain a Stripes-centric blog with regular articles?

If you are willing and able *right now* to start making a real contribution
to the project, then respond to this email and commit to it. Let us know
your name, your history with Stripes, how you want to contribute, and any
other information that you think is relevant. If you can't contribute now
but hope to be able to in the future, then please wait until that time comes
to speak up. What I want is to know who we have in this group who can help
breathe new life into Stripes starting today. Let's hear it.

-Ben

On Sun, Sep 19, 2010 at 2:51 PM, Jeppe Cramon  wrote:

> Hi guys
>
> I've been following this resurrection thread for a while and even though I
> contributed some core parts to Stripes in the early days I haven't really
> had the need for something like Stripes in a long time (for instance it
> lacks proper REST and Comet style support).
>
> IMO Stripes has faded because it has been too difficult to participate, add
> patches and features.
> I like that the core of Stripes is kept tight, with focus on extensibility
> and what's the core things for an Action based MVC framework.
> The low learning curve and the easy extensibility was what attracted me to
> Stripes in the first place, but the lack of progress & new releases is
> hurting Stripes.
>
> Since this thread has appeared and have started a good discussion, I think
> it's important to reach a consensus on where to take Stripes.
> IMO if this thread dies out with any clear forward action, then Stripes is
> going to whither.
>
> I agree with Rick, forking would be a good way to move forward.
>
> My suggestion is to put Stripes on GitHub and allow people for Fork it like
> crazy - see what the community can come up with and harvest the best ideas
> by pulling from the best contributers.
> But IMO it's important that someone like Ben, Aaron or Freddy be the one(s)
> maintaining the "official" Git Master and decide what gets pulled into the
> official Stripes release.
> Perhaps someone will come by and create a fork that blows everyone away -
> let's see what could happen ;)
>
> /Jeppe
>
> On Sun, 19 Sep 2010 20:27:21 +0200, Rick Grashel 
> wrote:
>
> Evan,
>
> Regarding your comment about forking the code being a last resort, I'm not
> too sure about that.  In fact, I think forks a

Re: [Stripes-users] MockRoundtrip doesn't work with wizard action beans, kinda

[Poitras Christian]

Thanks!
It would be great to add the solution to the wiki too!

Christian

De : Damien Bastin [mailto:banana.ch...@rocketmail.com]
Envoyé : September-21-10 4:17 AM
À : Stripes Users List
Objet : Re: [Stripes-users] MockRoundtrip doesn't work with wizard action 
beans, kinda

Thanks for your suggestion Christian.
I guess I was just being lazy by not looking at the code myself. :-)
For posterity, the solution is as follows...

Just say you have a Thingy in a Wizard like this...

@Wizard
public SomeActionBean implements ActionBean {

  @ValidateNestedProperties({
   @Validate(field = "field1", required = true),
   @Validate(field = "field2", required = true),
   @Validate(field = "field3", required = true)
  })
  private Thingy thingy;

  @DefaultHandler
  public Resolution something() {
   return new ForwardResolution("/WEB-INF/jsp/somePage.jsp");
  }

  public void setThingy(Thingy thingy) {
   this.thingy = thingy;
  }

  ...
}

In your test you add delimited encrypted field names to the "__fp" param that 
you want field validation to fire for, like this...

String[] fields = new String[] {"thingy.field1", "thingy.field2", 
"thingy.field3"};
trip.setParameter("__fp", fieldGenerator.generate(fields));
trip.execute("something");

... and "fieldGenerator" looks like this...

import net.sourceforge.stripes.util.CryptoUtil;

public class DefaultHiddenFieldGenerator implements HiddenFieldGenerator {
public String generate(String[] fields) {
String result = concat(fields);
return CryptoUtil.encrypt(result);
}

private String concat(String[] fields) {
String result = "";
for (String field : fields) result += "||" + field;
result.replaceFirst("\\|\\|", "");
return result;
}
}

Just a quick moosh of code, but I hope you get the idea if you ever need to do 
this!

Kind Regards

Damien


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Re: [Stripes-users] MockRoundtrip doesn't work with wizard action beans, kinda

[Damien Bastin]

Thanks for your suggestion Christian.
I guess I was just being lazy by not looking at the code myself. :-) 
For posterity, the solution is as follows...

Just say you have a Thingy in a Wizard like this...

@Wizard
public SomeActionBean implements ActionBean {...@validatenestedproperties({ 
@Validate(field = "field1", required = true), @Validate(field = "field2", 
required = true), 
@Validate(field = "field3", required = true)
}) 
private Thingy thingy; 

@DefaultHandler
public Resolution something() {
return new ForwardResolution("/WEB-INF/jsp/somePage.jsp");
}

public void setThingy(Thingy thingy) {
this.thingy = thingy;
}

...
}

In your test you add delimited encrypted field names to the "__fp" param that 
you want field validation to fire for, like this...


String[] fields = new String[] {"thingy.field1", "thingy.field2", 
"thingy.field3"};
trip.setParameter("__fp", fieldGenerator.generate(fields));
trip.execute("something");

... and "fieldGenerator" looks like this...

import net.sourceforge.stripes.util.CryptoUtil;

public class DefaultHiddenFieldGenerator implements HiddenFieldGenerator {
public String generate(String[] fields) {
String result = concat(fields);
return CryptoUtil.encrypt(result);
}

private String concat(String[] fields) {
String result = "";
for (String field : fields) result += "||" + field;
result.replaceFirst("\\|\\|", "");
return result;
}
}

Just a quick moosh of code, but I hope you get the idea if you ever need to do 
this!

Kind Regards

Damien


  --
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev___
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users