You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Ted Husted <hu...@apache.org> on 2007/09/12 03:34:26 UTC

[OT] I'm Jenga for Java (Vertigo, Anvil, and PRIMA) (was Should I ...)

[Or, what Ted does while he's waiting for Struts to build ...]

On 9/11/07, Brian Pontarelli <br...@pontarelli.com> wrote:
>  I'll definitely agree on that point. In fact I've already started work on a
> system just like the one you describe. However, I selected the frameworks
> and unlike systems like AppFuse, I decided to not give choices for
> frameworks, but give more functionality. It's called Vertigo and it contains
> an entire build system with project creation (based on Ant and Savant for
> dependencies), database migrations, emailing via FreeMarker and concurrency
> utils, environment aware configuration with a hierarchy, injection via
> guice, JPA support, security (via ACEGI, which does require Spring, but that
> will soon be refactored), common actions like country drop downs, ECommerce
> transactions (currently only via authorize.net), a good set of domain
> classes and base classes, and more is being added all the time.
>
>  Take a look if you guys get a chance:
>
>  http://code.google.com/p/vertigo-java

Vertigo looks like an interesting project. Though, I have to admit all
the references to Savant and such make me a little dizzy :)

We've often talked about putting together a full Struts stack. I think
there's a lot we could do with Maven prototypes and such in terms of
setting up skeleton projects for people. Of course, we wouldn't take
the "two from column a, one from column b" approach either, since the
idea for us would be to try to support a single set of products, more
along the lines of SourceLabs or Rails.

As to comprehensive single-stacks, I've been noodling a similar idea
myself. I sometimes refer to it as my "mid-life" crisis, since it's
grandiose and calls for a five-year plan. :)

 * http://code.google.com/p/anvil/wiki/Manifesto

Getting even farther off topic ... a similar but different notion
might be to create an "integrated development infrastructure" from a
stack of Java products. By development infrastructure I mean the
platform provided by SourceForge, GoogleCode, Java.net, and others. I
tend to thing of an integrated development infrastructure as a PRIMA
system

 Portal
 Repository
 Issue Tracker
 Mailing List
 Automated build

IOW, the infrastructure that we use to develop, build, and support
other products as a group.

We're finally reaching the point where we could assemble a all-Java,
all-open-source PRIMA system, such as:

* Harmony
* Derby
* James
* Tomcat
* Daisy (or JspWiki)
* Roller
* EyeBrowse
* OpenGrok
* Scarab
* Continuum / Maven

And, well, Subversion :)

The concept here is that we could test and document the system, and
bundle it up for distribution to the general public -- perhaps relying
on Maven as a distribution mechanism, a la AppFuse. So, it would be
more like GForge or CollabNet, but all-Java (and, well, Subversion).

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org