Actually, I'd like to make one more semi-major change while we have the
opportunity. I've been working on revamping the configuration to
combine struts.properties into struts.xml, and use an internal
dependency injection container (Bob's Guice project [1]) to wire
internal XWork and Struts components. This change shouldn't affect most
webwork applications and will lay the groundwork for a very powerful
restructuring of XWork and Struts to allow plugins and end user
applications to easily replace any major or minor piece of Xwork/Xstruts.
I have the initial XWork integration and plan to tackle the Struts
integration this weekend. As I said before, it should be 100%
backwards compatible with struts.properties, but allow you to define
them in struts.xml as well. Also, this will allow us to move the Spring
code into a plugin, and make it easier for plugins to extend Struts.
I'd like to do this now because this does have significant implications
for internal XWork API's and a major release is the proper time to make
those types of changes.
Don
[1] http://code.google.com/p/google-guice/
Rainer Hermanns wrote:
Ted,
I think the biggest problem for xwork2 is still the fact,
that there is no retroweaver enabled build for Java 1.4.
Also the build with maven is not working as required.
I hope to get the maven build done till the mid of next week.
Toby promised to help out with the other open issues in xwork's Jira, so
that the doc and refactoring tasks should be done as well till then.
As soon as these issues are fixed, we can remove the beta qualifier
and I'll release xwork 2.0 next week.
regards,
Rainer
There are some open issues left, mostly regarding the
build and release process with maven.
That being the case, are we removing the "beta" qualifier from this XWork
2 release?
-Ted.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=49702&messageID=100017#100017
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
