On 2/21/07, Don Brown <[EMAIL PROTECTED]> wrote:
Ah, that makes much more sense :) As for collaborating, I'm all for it, however in the case of Struts 2, it would happen probably at the XWork 2 layer. Since this code would be useful to non-Struts projects, perhaps it would be better to move it to Jakarta Commons, say commons-i18n? I believe that project is still in the sandbox and looking for developers so it may be ripe for new development. I thought there was another commons project that Struts 1 was always going to move to, commons-resources or something?
Yes, Commons Resources: https://svn.apache.org/repos/asf/jakarta/commons/dormant/resources/trunk/ As with several other Commons components, it started life as part of Struts. Several people, mostly from the Struts team, worked on it over quite a period of time, and it went through a couple of redesigns, but never got as far as a release and is now considered dormant. (Contrary to Antonio's comment, Commons Resources was originally designed for use in web apps. However, the "web-ness" of it was abstracted out so that it can be used elsewhere as well.) One thing to bear in mind when looking at sharing code between Struts 1 and other projects: Struts 1 has a requirement that its resource bundles be serialisable. This is why it is not based on the standard java.util.ResourceBundle class, which is not serialisable. Struts 2 currently uses ResourceBundle in a number of places. -- Martin Cooper Don
On 2/21/07, Paul Benedict <[EMAIL PROTECTED]> wrote: > > Ah. Good email. I didn't realize that my sentence could be read as such, > but now I can see that interpretation. Here's what I meant: > > I'd like to propose creating a sub-project (like the annotations) for > localization. Not creating annotations for localization, but a > subproject like you did for annotations. > > Is that clearer? Man, sounds confusing still. > > Paul > > Don Brown wrote: > > For the unaware like me, could you go more into the problem that > > exists in Struts 1 and 2, and the solution that involves these > > annotations? Just from this message, I'm a bit confused why we would > > use annotations for something like this. > > > > Don > > > > On 2/21/07, *Paul Benedict* <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > I'd like to propose creating a sub-project like the annotations for > > localization. I am not at the point of committing my 1.4 changes, > but > > real important classes are independent of s1 and could be used in > s2. > > > > This is all theory. I haven't spent enough time looking at s2 to > > figure > > out in-depth its localization strategies are. But I think it's a > > worthwhile effort to look into. Is anyone interested? > > > > Paul > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > > > > >
