I love Stripes Framework and have used it heavily, but my needs are a 
bit bigger than the framework itself provides. I thought of extending 
Stripes, but what I'm trying to accomplish, doesn't turn out to be 
simple when based on vanilla Stripes. So, I've decided to give it a try 
and create my own framework.

Please, do not comment about the hundredth JavaEE web framework. I know 
it's hell and I know about NIH syndrome, but I'll create it anyway, 
because I have ideas that no framework I've tried implements and that 
are not easily integrated on top of existing framework. It's probably 
going to be just for my internal use, I'm considering open sourcing it 
or selling it.

I'd love to reuse some of Stripes' code (about 5 or 10 classes, I guess) 
and therefore I'd like to know what is your take on licensing. Is it OK 
if I just leave the classes, along with all licence and author 
information in the comments, untouched? What if I need to modify the 
code? Do I give my changes back, what if they're not beneficial to 
Stripes? Do I HAVE TO open source whole my framework (I'm thinking of 
doing it, but not yet sure)? Can I sell it? Can I move classes to 
another package? What credit will be considered enough when I distribute 
my framework and what credit would users of my framework give to Stripes?

I've never done that and don't want to go wrong or insult anyone in any 
way :-) I don't feel like reinventing the wheel though and am not sure I 
understand Apache 2 license enough to answer my questions myself...

------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users

Reply via email to