On Wednesday 30 January 2002 12:28, you wrote:
> On Wednesday 30 January 2002 20:41, Marc-Olivier Bernard wrote:
> > Sorry for my quite basic question,
>
> This list is for all questions :)
>
> > I wanted to try to mix util and param taglibs like that :
> >
> > <util:include-file><xsp:attribute
> > name="name"><param:num/>.xml</xsp:attribute></util:include-file>
> >
> > (i get them work separatly),
> >
> > But the code produced doesn't work (I'm not surprised). Is there a way
> > to indicate the *order of XSP processing* (here param firstly, then
> > util) ?
>
> No, that can't work. XSP is a one-pass processor. You can't dynamically add
> an attribute to an element and then have it reevaluate itself (unless you
> do two passes yourself, but that you be quite messy).
>
> Most of the time however (if not always) it shouldn't be needed. Something
> like the following should do what you want:
>
> <util:include-file>
> <util:name><param:num/>.xml</util:name>
> </util:include-file>
>
> IOW, most of the params passed as attributes can also be passed as child
> elements (otherwise the taglib is probably missing a feature).
Here's a thorny problem that relates to his question
I'd like to be able to create something like the following syntax.
<soap:endpoint proxy="bar">
<soap:call uri="foo">
<soap:method name="AMethodOfFoo">
<arg1>gaga</arg1>
<arg2><param:stuff/></arg2>
</soap:method>
</soap:call>
</soap:endpoint>
Which is all well and good, except it seems not to be possible, at least not
with TaglibHelper. The reason being that the code generated by the
<soap:endpoint> call is executed AFTER the code generated by the enclosed
tags, so the endpoint hasn't been initialized at the time the <soap:call>
tag's code is invoked:(.
I can see that in the case of the example that Robin shows for
util:include-file that this is the proper behaviour, and in general you would
need to do things in that order, but there should be a way to issue some code
into the XSP module at the point of the OPENING tag.
In fact this is a general case. I could solve it for the simple example above
by just having the endpoint tag take all the rest of the stuff as input args
and figure out what to do, but what about that <param:stuff/>??? It seems
like to me there just isn't a way for TaglibHelper based taglibs to implement
this kind of syntax, or am I missing something here?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
