As you may have noticed, I've started the creation of Struts plugins by
splitting apart extras, integration, and parts of core into Struts
plugins. As proposed earlier, a plugin is composed of:
1. Java classes, tests, and resources
2. Struts configuration file ('struts-plugin.xml'), which is
automatically loaded
I think there are some interesting directions we could take this, but I
choose the simplest path for now, since I think plugins mainly give
Struts a better way to organize optional integration code, and should
make it easier for users to pick-and-choose optional features. The
other side is hopefully this will give prospective Struts extension
developers a few guidelines on how to best extend Struts.
The first batch of plugins:
1. Configuration Browser
2. Jasper Reports
3. JFreeChart
4. JSF
5. Pell Multipart handler
6. Sitemesh
7. Struts 1
and I'm hoping will be next:
1. Sitegraph
2. Portlet
3. Plexus
4. Velocity (?)
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
