Jeroen,
Look through archives for discussion why Schematron was selected.
Schematron is XSLT based, writing and integrating processor is simple.
Also, validation may be done piecemeal (adding a few rules at a time as
needed).
Methinks schematron good for some kinds of *rule based* validation
sorry, that should be:
documents.forms[0].elements['cocoon-xmlform-view'].value
also, if you need these to be variable names, use an associative array:
var Vars=new Array()
Vars['cocoon-xmlform-view']="some view"
Vars['cocoon-action-prev']="some resource"
Vars['cocoon
Try
documents.form.elements['cocoon-xmlform-view'].value
cheers,
--michael
apurva zaveri
I don't understand. Is the error produced on the client or the server? Does
this markup:
get transformed by xslt into a javascript variable in the page sent to the
client? Or is it part of the markup language of the page? Can you pass an
array in the namelist? i.e.,
Sorry, that last transform for the pipeline given in 3) should be:
mratliff@collegen
Andrew,
I don't know what's wrong, but here's a few things to try:
1)
I don't get this. Why are you declaring two identical actions? Can't see why
it would hurt, but can't see how it helps either... I would do something like
this:
(you will need to change the src so
Ivelin,
>>> >>Report is supported. Report is simply a negation of assert.
>>>
>>> Just double checked this again. Report doesn't work for me. This works:
>>>
>>> but this doesn't:
>>>
>>I've tested it a bit but maybe there is a bug. Feel free to save XMLForm
>>again :)
>>The impl
Torsten,
> > > JavaScript client validation improves the user experience quite a bit,
> > > so I think a validation solution should generate both client and
> > > server side validation code.
> That's exactly the goal of the precept idea...
Hmmm... I looked at precept stuff early on, but lik
Hello,
> From: "Ovidiu Predescu" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, May 20, 2002 10:03 PM
> Subject: Re: Flow and XMLForm
> JavaScript client validation improves the user experience quite a bit,
> so I think a validation solution should gene
All,
> In the sake of fairness, exception reporting is much friendlier in 2.1 than
> before. However much remains to be improved.
>
> I was wondering if someone else shares my observations and thinks it's time
> to lay out a design for better exception reporting infrastructure.
> I think that o
Ovidiu,
> - why do you need XMLForm when you have flow control? You can do the
> same things XMLForm does in the flow layer.
> ;)
> Now seriously, I think there's a lot of overlap between the two
> implementations right now.
> What I think we need is a way to describe, using Schematron, just
Ivelin,
>Why don't you consider donating some of your "twisted" examples to the
>mount/xmlform sitemap?
I still have a lot of work to do, but plan to offer at least one
detailed example of a "non-wizard" use case. Can't really say more now.
>> 5) Overall "potential". I mention this only
Ivelin,
>Thanks for hammering on XMLForm and sending more valuable feedback.
Glad you understand I'm trying to help make XMLForm better. I plan to
be much more critical when I get caught up; I've been doing lots of
twisted things with XMLForm I haven't had time to discuss. Of course,
I wouldn
"Konstantin
Piroumian" To: <[EMAIL PROTECTED]>
Hello,
Let's say I have an instance data node called MOTHERS_STREET_ADDRESS. I want to
create a constraint that says these characters are illegal: ^ # *( ), but these
are ok . (period) @ &. The xf:caption of the xf:textbox is "Street"
I would like to write rule that looks like:
Ivelin,
I am having problems writing Schematron rules for multiple-select widgets. For
example, imagine you have an widget which presents
as a set of four checkboxes whose captions are "red", "blue", "green", and "
yellow". You want to write two validation rules 1) At least one color must be
You might try...
Assuming you have a parameter in the request object named "reportName" whose
value is "bar", this pipeline will apply the stylesheet "bar.xsl" to the xml
foun
Ivelin,
>>Now I had the output I was looking for, but when I tried to
>> submit the form I kept getting errors from jxpath.
>Can you send me the stack traces.
(see below)
>BTW, the most recent version of JXPath should be able to correctly handle
>setValue( Collection or String[] ).
>Dmitri a
Ivelin,
I'm new to java, so there are probably better ways to do this.
I'm not using CVS (yet!) so I can't supply a simple diff file.
SUMMARY:
***
1) Added accessor methods for a Collection (ArrayList) variable to the data
model.
Ivelin,
I found the places in XMLFormTransformer.java that needed filling in and hacked
a patch into Types.java. I now have xf:selectMany working well enough for
testing purposes. Let me know if you have any general advice about patching
these files...
Thanks,
--Michael
-
Ivelin,
Have you figured out how you want to handle multiple-select widgets in xmlform?
I'm doing a lot of testing/extension of xmlform and don't want to duplicate
efforts. Even work in progress, or general suggestions how to proceed would
help...
--Michael
--
Fixed by Sylvain Wallez in revision 1.2.2.1 of
org.apache.cocoon.components.treeprocessor.AbstractProcessingNodeBuilder
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Sylvain,
Fixed precept problem. Thanks!
--Michael
Sylvain Wallez
Hello,
Anybody else notice a problem with the 29-Apr nightly build and Torsten's
precept examples? I'm getting ajava.lang.ClassCastException:
java.lang.String from the treeprocessor when I
press "Next Page" . I know there was an earlier problem where parameters were
not passed to actions in
Ivelin,
I get a NoClassDefFoundError when I click on the "Next" button on the "Personal
Information" page of wizard. Seems to be a problem with the 29-Apr-2002
commons-jxpath.jar No problem when I use the 18-Apr-2002 version of this file.
Here's the stack trace:
javax.servlet.ServletExceptio
Berin Loritsch
cc:
Piroumian
Konstantin To: "'[EMAIL PROTECTED]'"
s indicating an
invalid state of data.
to which I would add (potentially)
- procedural validation
see above
Let me finish by saying that I think the work both Torsten and Ivelin have done
is
Hello,
I have just joined this news group so I'm not sure this message is
going to end up in the right thread. I'm going to cut and paste some context
from Konstantine Piroumian's latest post, just in case.
I have been following the form handling discussions for some time now ("lurking"
is th
29 matches
Mail list logo
