If anyone is interested in previewing a *snapshot* build of Struts
2.1.0 for testing purposes, a library distribution with dependencies
is available here:
*
http://people.apache.org/builds/struts/nightlies/2.x/struts-2.1.0-SNAPSHOT-lib.zip
*
http://people.apache.org/builds/struts/nightlies/2.x
Yeah, we'll do a BOF, although they are usually pretty low key, I'm up
for kicking it up a notch, especially if there is free beer :)
Don
On 10/4/07, Matt Raible <[EMAIL PROTECTED]> wrote:
> On 10/3/07, Dale Newfield <[EMAIL PROTECTED]> wrote:
> > Ted Husted wrote:
> > > ApacheCon US 2007 Atlanta
The ticket has been fixed. Basically, the patch provided would have
broken another feature, so I fixed it in such a way that everyone
wins. I didn't put it in 2.1 as I'd like to see it get more testing
before going in a stable branch, but if someone else reviews the
change and is ok with it, feel
I'll contact the conference organizers to see what's the best night
(thurs or fri) and then proceed to contact the hotel (or a nearby
bar?) to get some cost estimates. From there, I'll start contacting
potential sponsors.
Sound good? If anyone wants to assist, let me know.
Matt
On 10/4/07, Don
So this will be more of a Struts party then? I can see if I can get
Atlassian to put some money/beer in the pot.
Don
On 10/5/07, Matt Raible <[EMAIL PROTECTED]> wrote:
> I'll contact the conference organizers to see what's the best night
> (thurs or fri) and then proceed to contact the hotel (or
I've always called them BOFs, and they generally operate like a BOF -
except attendees enjoy themselves because there's beer and more people
generally show up. ;-)
Matt
On 10/4/07, Don Brown <[EMAIL PROTECTED]> wrote:
> So this will be more of a Struts party then? I can see if I can get
> Atlass
The discussion around WW-2149 [1] has been interesting as it exposed
quite different philosophies with regards to Struts 2 tags. One
thought is Struts 2 should have lots of tags in its core as they are
used by lots of people. On the other hand, other folks (me) think
Struts 2 should keep core ver
I would be hesitant about doing this - mostly because no one else does
it. It might work well for developers, but does it really enhance the
users' experience?
Matt
On 10/4/07, Don Brown <[EMAIL PROTECTED]> wrote:
> The discussion around WW-2149 [1] has been interesting as it exposed
> quite diff
I absolutely agree, I am actually in the process of writing a tag
library that is based on the old struts 1 tags but supports OGNL and
JSP EL (without any of the overhead of FreeMarker). It was a bit
daunting trying to figure out some of the in's-n-out's to get access
to the guts of Struts 2/XWork
On 10/4/07, Matt Raible <[EMAIL PROTECTED]> wrote:
> I would be hesitant about doing this - mostly because no one else does
> it. It might work well for developers, but does it really enhance the
> users' experience?
>
> Matt
>
I don't think this is a question of user experience, but developer
choi
I would very much like to be able to extend the tags in a plugin. But
how do we keep the tld file(s) in sync? If there's going to be several
tag projects, there's going to be confusion if they all define their
own attributes and tags. There should at least be a minimum
requirement of common tags an
Along those lines, I'd like to see a plugin that:
1. Replaces OGNL with the Unified EL
2. Provides tags that use deferred EL expressions
Then, an application could completely drop OGNL and have native, JSP
tags that tools understand. No more confusion over what EL you are
using and no more conf
12 matches
Mail list logo
