Has any work been done to support existing zero config applications
with this new plugin? If not, I'd kinda consider that a blocker (-1)
because a sufficiently flexible configuration system should be able to
support multiple conventions. Also, someone will have to sign up to
convert the REST
I've spoken to quiet a few people that are already using zero-config in
production. I understand that it was always experimental, but it was
also solid and now used. I'd have to agree with Don (even though my
vote is now non-binding) and vote +0 if the existing zero-config
features are
Hi,
I have a List that holds only 5 JavaBean Objects. Now I need to show the
data on the JSP but don't want to use the logic:iterate
Is there a way to manually get the List element by index and show data on
the page in specific area and then get the next element i.e. List.get(0)
then show
2008/5/14 whitesox12 [EMAIL PROTECTED]:
Hi,
I have a List that holds only 5 JavaBean Objects. Now I need to show the
data on the JSP but don't want to use the logic:iterate
Is there a way to manually get the List element by index and show data on
the page in specific area and then
+0
Personally, I'd like to see the the CodeBehind, Zero-Config, Convention and
Rest plugins better integrated and the overlap reduced. Right now there are
multiple ways to skin the same cat and that can be confusing to new and
experienced users alike. The question they will likely have is: Which
I haven't tested the latest Convention plugin yet so I can't vote yet,
but I'd probably give a [-1] because I don't like the options provided.
I support moving Convention plugin from the sandbox to become the
recommended convention for new users, replacing ZeroConfig and CodeBehind.
However, I
I reaffirm my -1. Since there is overlap between the three plugins, I
suggest either a new plugin is created that merges all their respective
features, or one of the existing plugins should absorb the others.
Paul
On Wed, May 14, 2008 at 9:05 AM, Jeromy Evans
[EMAIL PROTECTED] wrote:
I
I will take a look at the migration of the REST plugin. But I don't
see the point of supporting codebehind from convention, as they are
separate plugins, users can choose any one they like, we are just
saying that convention is the recommended one, and there won't be
more development on
FYI, I turned off 'error' notifications (which you usually can't do
anything about-- svn outage, etc.,) for the Struts 1.x builds. You'll
only get notified on 'failure' now. -Wendy
On Wed, May 14, 2008 at 6:34 AM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Online report :
FWIW, I am also against the name convention plugin. Conventions change
over time, and I don't think any one plugin should be the convention. I'd
like to have a name that explains the intent behind the convention. That's
why names like Zero Config or REST are much more affable.
Paul
On Wed, May
Anyone have any ideas for what they'd like to see in a Struts 2 Eclipse
plugin?
I'm thinking of developing a follow up to Struts Console that is
specifically targeted at Struts 2 and Eclipse.
With the move to convention over configuration it seems that a GUI interface
to the struts.xml config
It turns out that making codebehind work from convention is quite easy
(DI FTW!), but again, I think this would be a bad choice.
musachy
On Wed, May 14, 2008 at 11:18 AM, Musachy Barroso [EMAIL PROTECTED] wrote:
I will take a look at the migration of the REST plugin. But I don't
see the point
+1
Here are the goals of this plugin. Any movement to integrate plugins and
make all things compatible (which I gracefully disagree with) MUST
satisfy these goals:
- Simple API that is fixed and will not change anytime soon
- Usable with absolutely no configuration or annotations
-
We all agree on updating the REST plugin, but we can't do that until
Convention lands on trunk. If we are divided on the topic of
Convention supporting Codebehind vs keeping them as stand alone
plugins, should we then vote on that?
musachy
On Wed, May 14, 2008 at 12:46 PM, Brian Pontarelli
+1
I think that this plugin is of great worth to every day development. I would
like to echo some other people's sentiments that a unified plugin would be a
significant value add to new struts developers. I know that there is much
overlap and confusion between:
1. Zero-config
2. Code
Is there any other way other than using JSTL. As I am trying to use struts
tags only.
Thanks
Antonio Petrelli-3 wrote:
2008/5/14 whitesox12 [EMAIL PROTECTED]:
Hi,
I have a List that holds only 5 JavaBean Objects. Now I need to show the
data on the JSP but don't want to use the
EL is not the JSTL. EL can be used outside of the JSTL (assuming you are
on a recent version of the spec).
You might have better luck asking in the correct mailing list. This list
is for the development of Struts, not usage.
-Chase
whitesox12 wrote:
Is there any other way other than using
СообÑаем ÑÑо в ÑеÑи инÑеÑнеÑа поÑвилÑÑ
ÑеÑиал:
[size=22 - [color=#003366 - Ðобег из ÑÑÑÑÐ¼Ñ Ð¡ÐµÐ·Ð¾Ð½ 1,
СеÑÐ¸Ñ 1-22 (22) / Prison Break Season 1 Episode 1-22 (22)[/color - [/size
-
http://i049.radikal.ru/0712/36/4380db99a782.jpg
Has anyone made a web page comparing the plugins?, if it took a while to get
to grips with it's probably worth offering users a page with something like
a checkbox grid feature comparison.
It could also help some of us understand what each one does ;).
Al.
- Original Message -
From:
19 matches
Mail list logo
