On 2/1/07, David H. DeWolf <[EMAIL PROTECTED]> wrote:
I'm also using codebehind and zero config. Is it time to promote them
from experimental?
The best thing might be for us to update the MailReader to use all of
these features. Then it would be easier for everyone to try the
features on vario
I'm also using codebehind and zero config. Is it time to promote them
from experimental?
Patrick Lightbody wrote:
I use all of these with HostedQA.
It's exciting to see that we've added a number of
brave, new features
since Struts 2.0.1.
* codebehind plugin
* zero configuration
* REST-ful U
I use all of these with HostedQA.
> It's exciting to see that we've added a number of
> brave, new features
> since Struts 2.0.1.
>
> * codebehind plugin
> * zero configuration
> * REST-ful URLS
> * direct results
>
> As implemented, these features seem solid and useful,
> but I wonder if
> anyo
I'd really like the portlet url support to be transparent, i.e. no
separate tags. Therefore, we'd need to have the url builder stuff
refactored first, which should be ok since I'm not a _huge_ hurry to
split the portlet code off to a plugin.
Don
Nils-Helge Garli wrote:
Hi,
First of all, I
Hi,
First of all, I want to apologize to everybody for beeing away for so
long... I hope it has not caused too many problems. Hopefully, I can
still be of some help...
Don,
What's the remaining 10% you're having trouble with? We can move out
the URL and Form stuff, but it would require separate
Great! I opened a ticket for this.
* https://issues.apache.org/struts/browse/WW-1645
On 1/15/07, Don Brown <[EMAIL PROTECTED]> wrote:
I got 90% of the way once moving the portlet support out to a plugin,
but there were a couple hardcoded references in the URL component and
another internal clas
I got 90% of the way once moving the portlet support out to a plugin,
but there were a couple hardcoded references in the URL component and
another internal class that escapes me ATM, so I backed off. This could
be revisited for 2.1.
Don
Tom Schneider wrote:
Ted Husted
whttp://www.netidenti
Ted Husted wrote:
It would be great if there were a portlet plugin. I have no idea how
the support is implemented, but I expect it would not be that easy. :)
Well, the PortletDispatcher (Jsr168Dispatcher.java) and related portlet
request support classes would probably be easy to separate out. T
Since we've put the Ajax theme on the experimental list, I'd like to
do the same with portlet support.
It's very possible that the code is solid, but since we seem to have
so few people using it, it's hard to vouch for it.
Right now, we have three open portlet tickets (one being new)
* https://
I think our release notes, at a minimum, should have a list of plugins
and features that are labeled "experimental". Of this list you
provided, I would agree with all but the last one, since direct results
was a very simple change. Zero conf is based on production code from
Stripes, so an "ex
On 12/9/06, Ted Husted <[EMAIL PROTECTED]> wrote:
As implemented, these features seem solid and useful, but I wonder if
anyone has a chance to use them all beyond "proof of concept"
examples. (Wendy?)
Me? I was playing with zero xml config in a prototype, (still needed
struts.properties, but n
It's exciting to see that we've added a number of brave, new features
since Struts 2.0.1.
* codebehind plugin
* zero configuration
* REST-ful URLS
* direct results
As implemented, these features seem solid and useful, but I wonder if
anyone has a chance to use them all beyond "proof of concept"
12 matches
Mail list logo
