On Thu, Jun 25, 2009 at 10:51 AM, Ate Douma <[email protected]> wrote: > > The entry is just fine, thanks.
Good :) > > I've already assigned it to myself andd will try to look at it shortly as soon as I can make some time free for this. > As I also mentioned in the issue, it might be useful to add setting portletMode as well which would merge very easily with your patch. Yes, I agree that is a good idea. I'll have a look and see what is involved. > > I have another question: as you mentioned in your initial email, you are using String 1.2.9. > When we're going to release a new version of the String Bridge, I'll have to decide which target struts 1.x version(s) to support. > The current bridge is still targeted at Struts 1.2.7. > Can you elaborate why you are using Struts 1.2.9 and for example not using a 1.3.x version (yet)? > > There might be technical/migration issues I need to consider but I haven't investigated this. > Any input you have might be very helpful to me. I'm currently in the research phase for a portlet project at work. We already have a fairly large struts 1.1 project which, due to some custom extensions, people have always been a little scared of migrating. I've implemented changes to migrate to 1.2.9, but there are quite a few deprecated methods/classes in 1.2.9 that are used in our main code base that have been removed in 1.3 and I didn't want to attempt the migration just yet - partially because it looks like a lot of work to do on a research branch and partially because the struts bridge is targeted at 1.2.7. We settled on the struts bridge early on and initially I was using 1.2.7 (since that is the supported version), but liferay ships with 1.2.9 so I moved to that version. Steve
