I was wondering the same thing.
Along with tags like tags and using ApplicationResources for
language specifics, it seems like it would work well.
Oscar
On Mon, 27 Oct 2003, Steve Apeero
wrote:
> For what you want to do what is wrong with using a
>
>
>
> where common_tags.jsp contain all
For what you want to do what is wrong with using a
where common_tags.jsp contain all the tags and html you
wanted to declare in a seperate tag.
Stephan
From: "Lukas Bradley" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED
m tag must enable it's body to be evaluated so the Struts tag is
invoked. but other than that.
-Original Message-
From: Edgar P Dollin [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 10:51 AM
To: 'Lukas Bradley'; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE
> -Original Message-
> From: Lukas Bradley [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 27, 2003 10:25 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Tags creating Tags
>
>
> Mike emailed me this idea last night, and I think it
Mike emailed me this idea last night, and I think it's the best yet.
Brilliant solution, Mike.
Lukas
"Mike Jasnowski" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Going from your example, I'm not sure why you even need to subclass a
Struts
> tag to get the output you described.
Going from your example, I'm not sure why you even need to subclass a Struts
tag to get the output you described. You should be able to code something
like this on your JSP:
The tag handling flow would look like (similar to what you proposed
earlier):
myTag.doStartTag();
pageContext.get
I said,
> Hi Lukas,
>
> If I understand you correctly ...
But I didn't (understand that is). I guess my reading comprehension
skills at 6am just aren't up to it ;)
So just disregard my last
Mark
-
To unsubscribe, e-mail:
Hi Lukas,
If I understand you correctly you need to look into the pushBody and
popBody methods on PageContext. Basically, in doStartTag(), call
pageContext.pushBody() then in doEndTag() you call
pageContext.popBody(), retrieve the BodyContent's value, muck about with
it to your heart's conten
Lukas Bradley wrote:
Ruth, Craig, and lurkers,
I think what I'm after boils down to a method like this:
public String renderTag(PageContext pPageContext, Tag pTagToRender) throws
JspException
A look at the JSP Specification will tell you that this would not work
at all for a classic tag hand
I apologize for the original cross-post. I was hoping there might be a
Struts method to do what I wanted.
Here is something I wrote to the other group, after a post from Felipe Leme.
> I think you can accomplish what you're looking for using JSP 2.0 and tag
> files.
Yep. That's exactly what I'
I think you'll still end up with a severe performance penalty. If you
generate JSP dynamically, that JSP will have to be "pre-compiled" each
time you re-generate it.
[EMAIL PROTECTED] wrote:
Craig R.McClanahan wrote:
To accomplish what you are after, you would need another
layer of compilati
Craig R.McClanahan wrote:
>To accomplish what you are after, you would need another
>layer of compilation.
>You'll need to come up with a different approach to accomplish what you
>are after.
I think this link ( an article by Jason Diamon at xml.com) presents an
example of what Craig calls "anoth
> One way of accomplishing what you want to do, I think, is simply making
> calls to the appropriate Struts classes that are called when
> is parsed & compiled. Instead of outputting an - just call
> those methods with the arguments that you would write out as
> attributes, and you should get pr
Ruth, Craig, and lurkers,
I think what I'm after boils down to a method like this:
public String renderTag(PageContext pPageContext, Tag pTagToRender) throws
JspException
After creating the tag manually, you could pass it to this method, and have
it rendered. The return value of a String should
One way of accomplishing what you want to do, I think, is simply making
calls to the appropriate Struts classes that are called when
is parsed & compiled. Instead of outputting an - just call
those methods with the arguments that you would write out as
attributes, and you should get pretty c
Lukas Bradley wrote:
Hi all,
Maybe I'm just tired, but the answer to this is not to be found. I could me
making this harder than it is, or something might be right in front of me,
and I don't see it.
What I want is a custom tag that creates other custom tags. Here is a
simple example:
Should
16 matches
Mail list logo
