> 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
On Mon, Apr 15, 2002 at 07:37:37PM +0200, Sven Kuenzler wrote:
> > > 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
>
> > 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
On Mon, Apr 15, 2002 at 09:12:03AM +0200, Sven Kuenzler wrote:
> > > 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
>
> > 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
On Mon, Apr 08, 2002 at 10:36:56AM +0200, Sven Kuenzler wrote:
> 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
> opportuni
- 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,
On Sun, Apr 07, 2002 at 05:55:40PM +0200, Sven Kuenzler wrote:
> > there is currently no way to call an action from a stylesheet like it is
> > possible with the webwork:action tag. But this should be easy using
> > xslt extensions. On the other hand one should consider using XSP and
> > special
> 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
On Sun, Apr 07, 2002 at 11:04:06AM +0200, Sven Kuenzler wrote:
> Well, I am using it. At the moment, it's only part of a small prototype
> application, though. We also have a somewhat larger webwork app which could
> benefit from xsl views someday.
> To achieve this, it would be necessary to get
> 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
Philipp Meier wrote:
>> Enhancements
>> 1. More velocity macros, etc.
>> 2. WML tags
>> 3. XHTML tags (possible move our existing tags to be XHTML compliant)
>> 4. Chain actions
>
> The XSLT view stuff should be enhanced slightly to be really useful. We
> need some XSLT java extension for URL-es
On Wed, Apr 03, 2002 at 08:04:16PM -0600, Matt Baldree wrote:
> Enhancements
> 1. More velocity macros, etc.
> 2. WML tags
> 3. XHTML tags (possible move our existing tags to be XHTML compliant)
> 4. Chain actions
The XSLT view stuff should be enhanced slightly to be really useful. We
need
Patrick Lightbody wrote:
> What about Swing as a view technology. I've always wanted to see that in
> action, but I can imagine there might not be a "standard" way to do it.
There's an example of this in the dist (an applet version of the
HelloWorld applet). It needs to be more advanced, but
Mike Cannon-Brookes wrote:
> Also I'd like to get more info on the ClientAction that runs over RMI. Is it
> possible to build other 'remote' actions - ie SOAPAction?
I see no reason why it *wouldn't* work.
BTW, I think that Flash support could work out of the box with the
current ClientServle
ActionA is ActionB?
>
> -Pat
>
>
>> From: "Matt Baldree" <[EMAIL PROTECTED]>
>> To: <[EMAIL PROTECTED]>,
>> <[EMAIL PROTECTED]>
>> Subject: [Webwork-user] revised - next release features/requirements
>> Date: Wed, 3 Apr 2002 20:0
ctionA when the result of
ActionA is ActionB?
-Pat
>From: "Matt Baldree" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>,
><[EMAIL PROTECTED]>
>Subject: [Webwork-user] revised - next release features/requirements
>Date: Wed, 3 Apr 2002 20:04:16 -0600
>
&
So here is a revised list of possible next release feature/requirements
based on what people have posted. Other ideas?
Documentation
1. Better velocity documentation
2. A more detailed section describing the view mapping focusing on using
actions.xml and views.properties with an example contai
18 matches
Mail list logo
