"Ship, Howard" wrote:
>
> I have a very interesting, large scale, Web-based project that I expect to
> release as open source.
>
> It is a complete, component based web application framework based on the
> Servlet 2.1 API.
>
> It makes rigourous use of the MVC design pattern, completely seperating HTML
> and Java code. Although in most forums, I call it "servlets on steroids",
> here I would add that it addresses the same space as SPFC but tackles and
> solves a much larger problem space.
>
> A web application takes the form of a "super-servlet". The framework takes
> over all responsibility for encoding URLs (for page navigation, actions,
> form submissions, etc.) and takes care of all the dispatching issues. In
> fact, the shopping list of useful, powerful features is too long to mention
> here.
I agree with Jon. This is just like Turbine. I saw your post on
javalobby but I didn't post because I hate that type of "Slashdot",
"script kiddie" environment.
> I've set up a site with preliminary documentation, current Javadoc, UML
> diagrams and a live demo:
>
> http://cai.primix.com/tapestry
That URL is down. Would still like to take a look at the code :)
> It is quite likely that Tapestry will be released as open source somewhere
> (Apache, Enyhdra, Giant Java Tree, etc.).
I was the last person in your situation. I brought the Jetspeed project
under the Apache umbrella and the brainshare of everyone here as
certainly helped out!!! (hopefully 1.2 will be out mid may)
> A sign of external support will
> make the process go faster - the business case I'm using to justify
> releasing this big chunk o' IP is based on some degree of acceptance /
> adoption in the Java open source community.
The truth, and I have a good amount of experience in this area, is that
it won't work. James Davidson made a very good point during his talk at
ApacheCon. When they pitched SUN management to OSS Tomcat they didn't
mention cost savings. It might not come and to this day the majority of
Tomcat people are from SUN.
What you should focus on is better code and brain share. If you are
working for a small company you are in a tough situation. The bean
counters won't the right path.
Check this out ->
http://oss.software.ibm.com/developer/opensource/features/advocating.html
> I'm looking for signs of interest and support. This is a large framework
> that I've been thinking about for over a year and have been coding part-time
> since late January ... it's well over a hundred, densely documented classes.
> And yet, I feel awkward about jumping this deep into the open source pool on
> my first go. Opinions?
If I were you I would take a long, hard look at Turbine. If there isn't
something in Turbine that is in Tapestry then request CVS write and make
the features you want happen. Hopefully anything we will get the best
of both worlds. Turbine is certainly a project that has grown over the
last 9 months.
Kevin
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
Open Source -> Join the conspiracy!
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
