Thanks Paolo.
Let me try this again with WLS 6.1 SP1, WLS 6.1 SP2 and probably with WLS 7.0.
It will be better if you have a tracking # with support. But I'll still try to
get some answer.
Ashish.
Vedovato Paolo wrote:
> Hi Ashish
>
> As far as I can remember the only bug left in wls6.1sp2 which
1.
Some people have been using WW for a while and have done some independent
work.
It may be interesting to include some of this stuff in WW.
Wouldn't it be nice that a process would be in place so that people could
submit their independent work, it would be evaluated by a steering comitee
and inc
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
> > It seems that tag should be thought to do the
> > escaping... ie. it would not make sense to wrap just about every usage
of
> > property tag with jet another tag. What do you think?
>
> I agree - this seems like the most sensible solution. I can't think of too
> many situations where you WOUL
Hi Rickard
Not having until now i18n in ValidationEditorSupport breaks up the concept
of be able to use all validation methods available in webwork.
What I did to get the (rudimentary) possibility to handle localized error
messages with the ValidationEditorSupport was this:
I've extended Valida
- 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, my hope is to *get rid* of XSP using WW, so th
