Have at it, it's the best way to get back up to speed :)
If you need, ping me with questions. . .
David
Joe Germuska wrote:
On 1/11/07, David H. DeWolf <[EMAIL PROTECTED]> wrote:
BTW, I think what we though tiles:attribute would be, is actually
tiles:put and tiles:putList. You'd think that
On 1/11/07, David H. DeWolf <[EMAIL PROTECTED]> wrote:
BTW, I think what we though tiles:attribute would be, is actually
tiles:put and tiles:putList. You'd think that I'd remember that.
I'd propose we:
1) rename tiles:attribute to tiles:insertAttribute
+1
2) rename tiles:put to tiles:putA
BTW, I think what we though tiles:attribute would be, is actually
tiles:put and tiles:putList. You'd think that I'd remember that.
I'd propose we:
1) rename tiles:attribute to tiles:insertAttribute
2) rename tiles:put to tiles:putAttribute
I don't really like the sounds of tiles:putAttributeL
that's what I would have thought too :), I think we definately need a
rename. I was looking for the insertAttribute tag in the tld when I found:
attribute
org.apache.tiles.taglib.AttributeTag
JSP
On 1/11/07, David H. DeWolf <[EMAIL PROTECTED]> wrote:
have you tried:
Wow, I thought (from looking at the FAQ) that this defined a *new*
attribute, not inserted one already defined.
Greg
Joe Germuska wrote:
On 1/11/07, Greg Reddin <[EMAIL PROTECTED]> wrote:
Could you not just use:
Nope. "According to the TLD or the tag file, attribute template is
mandatory for tag insertTemplate"
And the value of template is passed straight on through to a
RequestDispatcher...
ha
On 1/11/07, Joe Germuska <[EMAIL PROTECTED]> wrote:
I inferred the intent. I'm not sure if I agree with it or not, but I
really haven't thought about it much. I agree there was lots of room for
simplification and clarification in Tiles, so I won't say it was the wrong
choice. Besides, simplif
On 1/11/07, Greg Reddin <[EMAIL PROTECTED]> wrote:
Could you not just use:
Nope. "According to the TLD or the tag file, attribute template is
mandatory for tag insertTemplate"
And the value of template is passed straight on through to a
RequestDispatcher...
I haven't used the new tag
On 1/11/07, Joe Germuska <[EMAIL PROTECTED]> wrote:
I'm finally getting back up to speed with Tiles 2 and Struts 2. I'm
really
pleased to see the kinds of cleanup that Tiles has gotten.
However, I'm mildly "concerned" that what used to be in my JSP as this:
Now looks something like this:
I'm finally getting back up to speed with Tiles 2 and Struts 2. I'm really
pleased to see the kinds of cleanup that Tiles has gotten.
However, I'm mildly "concerned" that what used to be in my JSP as this:
Now looks something like this:
Did I miss something in the translation? Ah, I see
Ooops, I meant to send this to dev@ rather than [EMAIL PROTECTED]
-- Forwarded message --
From: Ted Husted <[EMAIL PROTECTED]>
Date: Jan 11, 2007 12:08 PM
Subject: [S2] Caveat Emptor (was Re: I think I want to convert to S2 on user@)
To: Struts Users Mailing List
Is anyone worki
problem solved
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=56828&messageID=114279#114279
-
To unsubscribe, e-mail: [EMAIL PROTEC
On 1/11/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
Maybe I misunderstood the term "experimental", do you mean "creating a
new project under the Struts JIRA instance is the only simple way to
move the issues from the sandbox"?
No, perhaps I misunderstood the situation. I thought it was
I'm in for the Spring MVC plugin :)
musachy
Tom Schneider wrote:
So this would allow a user to write convert a S1 action over to S2,
but keep the JSP exactly the same? Or would it just allow S1 tags to
be used in
S2? WW already supports using JSTL tags out-of-the-box--I'm not sure
you would
I just added yesterday a GWT plugin that allows you to call S2 actions
using GWT RPC mechanism.
http://cwiki.apache.org/confluence/display/S2PLUGINS/GWT+Plugin
musachy
Ted Husted wrote:
Speaking of plugins, Don's been laying the groundwork for tag plugins,
so that we can create a struts-dojo
So this would allow a user to write convert a S1 action over to S2, but
keep the JSP exactly the same? Or would it just allow S1 tags to be used in
S2? WW already supports using JSTL tags out-of-the-box--I'm not sure
you wouldn't need anything special to support s1 tag. (I haven't worked
with
Speaking of plugins, Don's been laying the groundwork for tag plugins,
so that we can create a struts-dojo plugingto supercede the Ajax theme
in Struts 2.1.x.
A related idea might be S1 or Spring MVC tag plugins that exposed
another tag API but utilized the valuestack and such under the hood.
I
Both the Struts 1 and Struts 2 JARs are needed.
Here's the thing: Java web applications can support multiple servlets
and multiple filters. S1 and S2 do not overlap in terms of runtime
resources or namespaces, and so we can use both in the same web
application. You could probably also use Spring
On 1/10/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
Tiles2 is not in the parent pom for 1.3.6
OK, my mistake thats good.
Niall
Niall Pemberton wrote:
> IMO the Struts1 Tiles2 module should be excluded from the 1.3.6
> release since its dependant on the tiles sandbox SNAPSHOT which is now
>
Greg Reddin ha scritto:
On 1/10/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
Greg Reddin ha scritto:
> See the INFRA
> ticket for the Tiles TLP for info about porting existing tickets.
What experimental tool?
And anyway, is it really necessary? Since they are in the same JIRA
instance, the
20 matches
Mail list logo
