> Where should we go then? IMHO a XSLT stylesheet with custom XSLT
> extension should work well.
>
> Stylesheet for the view could be
>
> ...
>
>
>
> ...
>
> ...
>
> ...
>
> ...
>
>
>
> Whereas the xslt engine uses custom handlers for the tags.
> IIRC XSLT2.0 will specifiy a standard way
> 18. Factor out HTTP stuff out of the dispatcher.
> [suggested by Sven]
I guess my reference to the dispatcher was misleading here - should be
ActionFactory/ActionContext(?).
Sven
___
Webwork-user mailing list
[EMAIL PROTECTED]
https://li
> > Anyway, would it really be too hard to make a SAXFilter that clones WW's
> > core taglib functionality? Normally, the tricky part with SAX are state
> > keeping issues. But most of this state keeping stuff should be handled
by
> > the ValueStack already. Or am I wrong?
>
> It's possible but no
> > Something like that, yes. As I suggested, one could try to create a
> > SAXFilter with a functionality similar to WW's core jsp taglib. The
other
> > possibilty would be a XSLT extension. But as I said, I'd like to have
the
> > opportunity to reuse WW actions in C2. And integrating such an ex
- Original Message -
From: "Sven Kuenzler" <[EMAIL PROTECTED]>
To: "Philipp Meier" <[EMAIL PROTECTED]>
Sent: Monday, April 08, 2002 10:11 AM
Subject: Re: [Webwork-user] revised - next release features/requirements
>
> > > On the other hand,
> I did not get your point here. XSLT is currently integrated as a view
> layer - not as a dispatcher. A drawback of the implementation is that
I meant XSLT *servlet*, sorry.
> there is currently no way to call an action from a stylesheet like it is
> possible with the webwork:action tag. But t
> The XSLT view stuff should be enhanced slightly to be really useful. We
> need some XSLT java extension for URL-escaping and so on. I don't know
> if I'll have the time but I don't want to give up the XSLT thingy. So
> is their anybody except me using it? Huh?
Well, I am using it. At the moment
> What is the webwork.log4j.configfile property set to?
Is it a new feature that you have to set this option? I'm pretty sure that
it worked without it until recently.
Anyway yes, that missing option was the problem.
I attached an updated version auf XSLTServlet.java.
What I did
- updated the
Due to an urgent personal demand I've fixed a TODO in XSLTServlet.java, "a
nicer error interface".
What I have done (see attachment) works ... until I redeploy my webapp. When
redeploying, I get these log entries (Instead of the hundreds of Saxons
ambiguity warnings I expect *sigh*):
[ERROR,Defa
Well, now it does ;-)
Thx, Sven
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Im Auftrag von Matt
> Baldree
> Gesendet: Donnerstag, 31. Januar 2002 01:15
> An: Sven Kuenzler; Webwork-User
> Betreff: Re: [Webwork-user] Comma
Hello!
I am running into a problem configuring a command driven action in
actions.xml. My config file looks like this:
xslt/norm.xsl
xslt/search2.xsl
xslt/copy.xsl
When hitting http://host/context/StandardSearch.action, WebWork calls
Search2.doExecute().
11 matches
Mail list logo
