You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Ulrich Mayring <ul...@denic.de> on 2000/05/03 13:22:05 UTC
Anyone using XMLForm?
Hi there,
I just downloaded XMLForm, however when I run the supplied example I get
(in the log files):
java.lang.NoClassDefFoundError: org/openxml/parser/HTMLParser
Thanks in advance for any pointers,
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
Re: Anyone using XMLForm?
Posted by Ulrich Mayring <ul...@denic.de>.
mayring@denic.de wrote:
>
> <news>
> <item id="1">foobar</item>
> Here you will get only ONE parameter /news/item and it will have the
> value foobar. The second and all following items are ignored. It is not
> possible to tell the items apart by their id attribute, because XMLForm
> doesn't post the attribute values.
I don't know what the issue is with either this *!#$ยง!& mail server or
my mailclient (Netscape). It keeps omitting characters every now and
then! My example actually should read (hope it comes across this time):
<news>
<item id="1">foobar</item>
<item id="2">baz</item>
</news>
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
Re: Anyone using XMLForm?
Posted by Kevin Sonney <ke...@webslingerz.com>.
On Fri, 12 May 2000, Ulrich Mayring wrote:
> You can't compare this with databases, where you have serious integrity
> issues to consider, when changing the database schema. Suppose this
> extremely simple example:
*snip*
> You can encode this in a DTD. Now one user comes and says: hey, I need a
> field for a description. Another time someone else needs he needs a
> second and third price. Then someone wants to put the manufacturer's
> address in the file, etc. etc.
Actually, I can compare this with databse, as this is, in essance, a
simple, file based database. *grin* You could easilly change the DTD to
not require the new fields.
My biggest concern is in the user space - Cocoon and XMLForm aren't
designed to handle multiple updates to a single file form multiple sources
(i.e. 5 clinets updating one XML) concurrently. I don't recall Donald
building in locks to prevent the types of data corruption you can get even
with 2 users updating the same file without exquisite timing.
> Of course at some point you really should be thinking about a database
> instead of meddling with an XML file. But the beauty of my approach is
> that it empowers the users, they can create their own documents and if
> they mess up the structure, then more power to them :) However, can you
> tell me about a tool that let's users design and change their own
> database (except FileMaker Pro)?
M$ Access, M$ Excell (hey, it's not SQL compliant, but..) Lotus
Notes/Domino, Lotus Approach. My problem has *ALWAYS* been that the more
you empower the users, the more space there is for them to break
things. *grin* I'm probably overly cynical about the typical end user,
though...
> There you have it: it's common. I don't want to be a DTD administrator,
> I want to be a software designer :-)
I can dig that. I jhave to think in terms of
> BTW, since yesterday afternoon my quick'n'dirty approach works - does
> your DTD? *evilgrin*
Hey, if you want to get snooty, no *grin*. I've been more concerned with
client related things. The DTD is mostly theory. When I have time to
code/implement it, I'm going to - just to see if it cna be done, at first
*grin*
--
- Kevin Sonney
kevin@webslingerZ.com
Re: Anyone using XMLForm?
Posted by Ulrich Mayring <ul...@denic.de>.
Kevin Sonney wrote:
>
> I gues sit amkes no sense to me why you'd need, except durring initial
> development, to change the schema (or DTD) very frequently. When I build
> an SQL table, there comes a point where it's structure is *SET* an
> dshouldn't be changed under any circumstances. Why should my DTD be any
> different?
You can't compare this with databases, where you have serious integrity
issues to consider, when changing the database schema. Suppose this
extremely simple example:
<product>
<name>foo</name>
<price>12</price>
</product>
You can encode this in a DTD. Now one user comes and says: hey, I need a
field for a description. Another time someone else needs he needs a
second and third price. Then someone wants to put the manufacturer's
address in the file, etc. etc.
Of course at some point you really should be thinking about a database
instead of meddling with an XML file. But the beauty of my approach is
that it empowers the users, they can create their own documents and if
they mess up the structure, then more power to them :) However, can you
tell me about a tool that let's users design and change their own
database (except FileMaker Pro)?
> I guess I'm coming at it from the SQL Mindset - there's a structure that
> doesn't get modified unless it's really, really, really gotta be
> done. Like mission critical gotta be done. because after the initial
> development push, it's in use, and even a minor change like adding a
> column can screw up how you expect yuor data to be returned. And in my
> experiences with XSLT, as well as SQL, that's pretty common.
There you have it: it's common. I don't want to be a DTD administrator,
I want to be a software designer :-)
BTW, since yesterday afternoon my quick'n'dirty approach works - does
your DTD? *evilgrin*
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
Re: Anyone using XMLForm?
Posted by Kevin Sonney <ke...@webslingerz.com>.
On Thu, 11 May 2000, Ulrich Mayring wrote:
> Yeah, of course you can use a DTD, but how do you edit it with XMLForm?
You don't edit the DTD with XML Form...kinda like you don't let your user
edit your SQL Tables with SQLProcessor. *grin*
I gues sit amkes no sense to me why you'd need, except durring initial
development, to change the schema (or DTD) very frequently. When I build
an SQL table, there comes a point where it's structure is *SET* an
dshouldn't be changed under any circumstances. Why should my DTD be any
different?
I guess I'm coming at it from the SQL Mindset - there's a structure that
doesn't get modified unless it's really, really, really gotta be
done. Like mission critical gotta be done. because after the initial
development push, it's in use, and even a minor change like adding a
column can screw up how you expect yuor data to be returned. And in my
experiences with XSLT, as well as SQL, that's pretty common.
> The reason why everyone wants XML Schemas is that no-one wants DTDs :)
Probably because there's not reasonable, easy to find Docs on the subject
*grin*. Trust me, I've been all over the 'net today looking for
some. *grin*
--
- Kevin Sonney
kevin@webslingerZ.com
Re: Anyone using XMLForm?
Posted by Ulrich Mayring <ul...@denic.de>.
Kevin Sonney wrote:
>
> Sorry about poking holes in it, and the rant, but it just dawned on me how
> much easier it would be is we used the DTDs, as part of the XML spec.
Yeah, of course you can use a DTD, but how do you edit it with XMLForm?
The reason why everyone wants XML Schemas is that no-one wants DTDs :)
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
Re: Anyone using XMLForm?
Posted by Kevin Sonney <ke...@webslingerz.com>.
On Thu, 11 May 2000, Ulrich Mayring wrote:
> I am a little uncomfortable with the concept as a whole, probably
> because I am too dumb to understand it. Anyway, I think we should adhere
> more to the principles of KIGS and KISS (G for Generic).
Well, yeah, Although Generic isn't always good. Simple is, though.
> So, the big question, that I have been asking myself, is how to make a
> "generic" XMLForm application. I want to have something that will work
> with any XML-file, regardless of its structure. I don't want to write
> new XSPs and XSLTs every time I have another XML document with a new
> structure, I want one generic application that can edit any XML file. A
> tall order, perhaps?
Perhaps not. I'd lvoe something that I could feed an XML document (either
as part of an XSLT/XSP process or directly) and then generate an HTML form
out of it.
> I am sure with XML Schemas or the XML skeleton idea the whole thing
> becomes doable in a nice fashion, but I was thinking of a quick XSP/XSLT
> only solution. Probably it's too dirty to be useful for anyone but me,
> but anyway here are my thoughts:
*snip*
I don't think an XSP/XSLT solution is necissarily the right answer, but I
see some merit in your ideas. However, as I'm looking it over, why use the
defs.xml file for each edit process? Isn't this what, for all intents and
purposes, the DTD is for? The only thing you don't get in a DTD is the
comment of "what this entity really means" - unless there's something
about DTDs that allos a per-tag-definition coment that I can't find. (DTD
structres and conventions are really well hidden on the 'net. Breif
mentions in the XML formats, but I'd love a DTD HOWTO...)
<rant type="minor">
Of course, thsi requires a DTD in every document. But isn't that part of
good XML syntax anyway? Shouldn't each document start with :
<?xml version="1.0" standalone="yes"?>
if we're conforming to version 1.0 of the XML recomendation and *DON'T*
specify a DTD?
</rant>
> Now I write a stylesheet to display the Camcorder info. What I do is I
> select every child of <item> and compare its name() with the @name of
> any of my defs. If I find something, then I know three things: The text
> to display, whether the field should be HTML, XML or plain text and how
> to sort this line. (The latter is important, because due to parameter
> passing XMLForm changes the order of the elements within <item> after
> editing).
Again, using the proper DTD for the file, we could parse the DTD, and come
up wth a form based on that for a document, or an element within the
document. Anything that needs a choice (a select list of five
items, say) can be set in the DTD with what each available option is.
> The good part of this idea is that there is only one central defs.xml
> file and wherever I need its data I can <util:include-file> it. The bad
> part is that I currently can't get the util taglib to work ;-)
Using the DTD would eliminate the need for any include files...
> The only thing that is still fixed and not editable with this approach
> is the structure of the XML documents up to and including the <item>
> object. I think I could live with that and also believe that this
> problem is solvable, should the need arise.
Er, again, with the DTD, you could edit the entire document, or just
subsets thereof.
> The last step would be to freeze the structure of the defs.xml file and
> create a metadefs.xml file for it, so we can edit defs.xml with XMLForm
> as well.
In toher words, a DTD for defs.xml? *grin*
> Well, so far my ad-hoc ramblings,
Sorry about poking holes in it, and the rant, but it just dawned on me how
much easier it would be is we used the DTDs, as part of the XML spec.
Now, to find complete docs on creating a DTD....
--
- Kevin Sonney
kevin@webslingerZ.com
Re: Anyone using XMLForm?
Posted by Ulrich Mayring <ul...@denic.de>.
Donald Ball wrote:
>
> Now you're poking holes at the underlying premise of XMLForm. It's not
> very easy to construct an arbitrary tree from a collection of XPath-like
> expressions. Maybe you and Jeremy should get together to work on the next
> iteration of this concept - he had the good thought of generating the form
> from a skeletal XML fragment so that it would be easier to map form
> elements to XML result nodes. If y'all want to take over maintenance of
> XMLForm, let me know.
I am a little uncomfortable with the concept as a whole, probably
because I am too dumb to understand it. Anyway, I think we should adhere
more to the principles of KIGS and KISS (G for Generic).
So, the big question, that I have been asking myself, is how to make a
"generic" XMLForm application. I want to have something that will work
with any XML-file, regardless of its structure. I don't want to write
new XSPs and XSLTs every time I have another XML document with a new
structure, I want one generic application that can edit any XML file. A
tall order, perhaps?
I am sure with XML Schemas or the XML skeleton idea the whole thing
becomes doable in a nice fashion, but I was thinking of a quick XSP/XSLT
only solution. Probably it's too dirty to be useful for anyone but me,
but anyway here are my thoughts:
First I have a central XML file called "defs.xml". It contains
definitions that describe the other XML documents, that should be edited
with XMLForm. This defs.xml is the only file I have to edit, once I
introduce new XML files into my XMLForm workflow. Of course, editing of
defs.xml should be done via XMLForm, too. My defs.xml could contain
something like:
<defs>
<def name="product" text="Product" type="text" sort="0"/>
<def name="price" text="Our Price today" type="text" sort="1"/>
<def name="description" text="Product Description" type="html"
sort="2"/>
</defs>
This basically defines that I can have XML files like:
<item>
<product>Camcorder</product>
<price>99</price>
<description>This <b>super-cool</b> Camcorder blah blah</description>
</item>
Now I write a stylesheet to display the Camcorder info. What I do is I
select every child of <item> and compare its name() with the @name of
any of my defs. If I find something, then I know three things: The text
to display, whether the field should be HTML, XML or plain text and how
to sort this line. (The latter is important, because due to parameter
passing XMLForm changes the order of the elements within <item> after
editing).
The good part of this idea is that there is only one central defs.xml
file and wherever I need its data I can <util:include-file> it. The bad
part is that I currently can't get the util taglib to work ;-)
So, to summarize, with this approach we can:
1) add new <item> objects and remove old ones
2) change the value in <item><*>value</*></item>, regardless of the
actual names of the <*>...</*> tags
3) change the names of any <*>...</*> tags
4) add new <*>...</*> tags
5) define the order in which the <*>...</*> tags are supposed to occur,
their type and whatever else
The only thing that is still fixed and not editable with this approach
is the structure of the XML documents up to and including the <item>
object. I think I could live with that and also believe that this
problem is solvable, should the need arise.
The last step would be to freeze the structure of the defs.xml file and
create a metadefs.xml file for it, so we can edit defs.xml with XMLForm
as well.
Well, so far my ad-hoc ramblings,
cheerio,
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
Re: Anyone using XMLForm?
Posted by Donald Ball <ba...@webslingerZ.com>.
On Wed, 10 May 2000, Ulrich Mayring wrote:
> svenk@Informatik.Uni-Bremen.DE wrote:
> >
> > Same for me. Indeed, this html type is almost doing too much. I don't
> > want those tags to be converted to upper case (because that's no xhtml);
> > also I don't want those HTML-Entities, now that I have proper encoding
> > ;-)
> > Guess I'll have to go trough the openxml stuff to fix this.
>
> Why not just make it type xml or no type at all? Didn't try XML, but no
> type at all preserves the Umlaute and doesn't convert them to entities.
>
> > Yet another issue: How do I make it encode the attributes of the element
> > as POST parameter as well? I tried something like
> > @*|/name[title={blabla}] as xmlform:xpath but did not succeed. Is my
> > xpath false or does XMLForm not support attributes yet?
>
> You seem to run into the exact same problems as I :-)
>
> Another thing is this:
>
> <news>
> <item id="1">foobar</item>
> <item id="2">baz</item>
> </news>
>
> Here you will get only ONE parameter /news/item and it will have the
> value foobar. The second and all following items are ignored. It is not
> possible to tell the items apart by their id attribute, because XMLForm
> doesn't post the attribute values.
Now you're poking holes at the underlying premise of XMLForm. It's not
very easy to construct an arbitrary tree from a collection of XPath-like
expressions. Maybe you and Jeremy should get together to work on the next
iteration of this concept - he had the good thought of generating the form
from a skeletal XML fragment so that it would be easier to map form
elements to XML result nodes. If y'all want to take over maintenance of
XMLForm, let me know.
- donald
Re: Anyone using XMLForm?
Posted by Ulrich Mayring <ul...@denic.de>.
svenk@Informatik.Uni-Bremen.DE wrote:
>
> Same for me. Indeed, this html type is almost doing too much. I don't
> want those tags to be converted to upper case (because that's no xhtml);
> also I don't want those HTML-Entities, now that I have proper encoding
> ;-)
> Guess I'll have to go trough the openxml stuff to fix this.
Why not just make it type xml or no type at all? Didn't try XML, but no
type at all preserves the Umlaute and doesn't convert them to entities.
> Yet another issue: How do I make it encode the attributes of the element
> as POST parameter as well? I tried something like
> @*|/name[title={blabla}] as xmlform:xpath but did not succeed. Is my
> xpath false or does XMLForm not support attributes yet?
You seem to run into the exact same problems as I :-)
Another thing is this:
<news>
<item id="1">foobar</item>
<item id="2">baz</item>
</news>
Here you will get only ONE parameter /news/item and it will have the
value foobar. The second and all following items are ignored. It is not
possible to tell the items apart by their id attribute, because XMLForm
doesn't post the attribute values.
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
Re: Anyone using XMLForm?
Posted by Sven Kuenzler <sv...@tzi.de>.
> You can quick'n'dirty hack it by adding after line 166 the line:
>
> format.setEncoding("ISO-8859-1"); // or whatever encoding you want
Yes that's fine for me. Thanks.
> So, all in all, it was getting a little too hairy for me. I'll just
> hard-code ISO-8859-1, because my XMLForm application doesn't need
> anything else.
Same for me. Indeed, this html type is almost doing too much. I don't
want those tags to be converted to upper case (because that's no xhtml);
also I don't want those HTML-Entities, now that I have proper encoding
;-)
Guess I'll have to go trough the openxml stuff to fix this.
Yet another issue: How do I make it encode the attributes of the element
as POST parameter as well? I tried something like
@*|/name[title={blabla}] as xmlform:xpath but did not succeed. Is my
xpath false or does XMLForm not support attributes yet?
Sven....
RE: Anyone using XMLForm?
Posted by Corey Krehel <co...@wellengaged.com>.
We are working on a site which will require a large amount of work with
forms.
Where can I find more information about XMLForm?
Corey Krehel
Web Development
Prospero Technologies
415.339.7000 x211
corey@wellengaged.com
www.prosperotechnologies.com
-----Original Message-----
From: ulim [mailto:ulim]On Behalf Of Ulrich Mayring
Sent: Tuesday, May 09, 2000 2:52 AM
To: cocoon-users@xml.apache.org
Subject: Re: Anyone using XMLForm?
svenk@Informatik.Uni-Bremen.DE wrote:
>
> Encoding: In order to support german "umlauts" in data.xml from the
> sample I changed the encoding in the xml-pi to Latin1. When I first edit
> the file using XMLForm, this works fine. However, after the
> adding/editing process, the encoding is set back to UTF-8 but the
> characters are not converted properly. In consequence, Xerces chockes on
> illegal characters on this file.
You can quick'n'dirty hack it by adding after line 166 the line:
format.setEncoding("ISO-8859-1"); // or whatever encoding you want
> Thus, it would be nice if XMLForm remembers the original encoding type.
> Or even better, there would be something like xmlform:encoding.
Yes, but that is a bit more complex to implement. You can get the
current encoding by adding these two lines after line 89:
InputSource inpSrc = new InputSource(filename);
String encoding = inpSrc.getEncoding();
Then you can later write format.setEncoding(encoding);
This works, but you must be aware of two special cases:
a) in the case of type="html" what encoding do we write? (currently:
none)
b) what encoding do we assume if there is none specified?
So, all in all, it was getting a little too hairy for me. I'll just
hard-code ISO-8859-1, because my XMLForm application doesn't need
anything else.
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: Anyone using XMLForm?
Posted by Ulrich Mayring <ul...@denic.de>.
svenk@Informatik.Uni-Bremen.DE wrote:
>
> Encoding: In order to support german "umlauts" in data.xml from the
> sample I changed the encoding in the xml-pi to Latin1. When I first edit
> the file using XMLForm, this works fine. However, after the
> adding/editing process, the encoding is set back to UTF-8 but the
> characters are not converted properly. In consequence, Xerces chockes on
> illegal characters on this file.
You can quick'n'dirty hack it by adding after line 166 the line:
format.setEncoding("ISO-8859-1"); // or whatever encoding you want
> Thus, it would be nice if XMLForm remembers the original encoding type.
> Or even better, there would be something like xmlform:encoding.
Yes, but that is a bit more complex to implement. You can get the
current encoding by adding these two lines after line 89:
InputSource inpSrc = new InputSource(filename);
String encoding = inpSrc.getEncoding();
Then you can later write format.setEncoding(encoding);
This works, but you must be aware of two special cases:
a) in the case of type="html" what encoding do we write? (currently:
none)
b) what encoding do we assume if there is none specified?
So, all in all, it was getting a little too hairy for me. I'll just
hard-code ISO-8859-1, because my XMLForm application doesn't need
anything else.
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
Re: Anyone using XMLForm?
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On 8/5/00 at 5:03 pm, svenk@tzi.de (Sven Kuenzler) wrote:
>Jeremy suggested a taglib for tasks like these. I think this would be
>really useful for many people. The fact that no one responded may be
>because it is hard to think about it on such an abstract level. At least
>it was for me.
Yea, I am struggling too ....
I think part of the problem was, while I was looking at it, I was supposed to be on holiday (8 days of diving in Ireland blown out by storms over Easter, what with all those lovely "soft" Irish days (it rained) and abundant supplies of Guinness, my heart was not in it :)
>However, I will be implementing some forms on XMLForm this week and then
>revisit Jeremy's propasal and comment on it.
Excellent
My proposal was far from perfect .... but I still felt I was on to something.
regards Jeremy
____________________________________________________________________
Jeremy Quinn media.demon
webSpace Design
<ma...@media.demon.co.uk> <http://www.media.demon.co.uk>
<phone:+44.[0].207.737.6831> <pa...@sms.genie.co.uk>
Re: Anyone using XMLForm?
Posted by Sven Kuenzler <sv...@tzi.de>.
Jeremy Quinn wrote:
>
> On 4/5/00 at 9:14 am, ulim@denic.de (Ulrich Mayring) wrote:
I mistakingly posted this on the dev-mailling list already, but as the
question was asked here, I'll repost it....
To get XMLForm running with Xalan > 0.19 you'll have to do the following
change to XMLForm and recompile it:
64c364
< XPath xpath = new XPath(xpath_support,null);
---
> XPath xpath = new XPath(null);
[read: remove the string "xpath," from line 364 of XMLForm.java]
This works with Cocoon 1.7.3 and thus with the latest Xalan release,
however I have found other problems:
Encoding: In order to support german "umlauts" in data.xml from the
sample I changed the encoding in the xml-pi to Latin1. When I first edit
the file using XMLForm, this works fine. However, after the
adding/editing process, the encoding is set back to UTF-8 but the
characters are not converted properly. In consequence, Xerces chockes on
illegal characters on this file.
Thus, it would be nice if XMLForm remembers the original encoding type.
Or even better, there would be something like xmlform:encoding.
Path: Under Tomcat, the way paths are evaluted is confusing. When the
context mount point is /viva and data.xml resides in
/viva/example/data.xml, xmlform:virtual expects this as
/example/data.xml while in xmlform:redirect it must ve
/viva/example/data.xml. I will work with XMLForm on JServ this week and
report what's happening there.
Jeremy suggested a taglib for tasks like these. I think this would be
really useful for many people. The fact that no one responded may be
because it is hard to think about it on such an abstract level. At least
it was for me.
However, I will be implementing some forms on XMLForm this week and then
revisit Jeremy's propasal and comment on it.
Sven....
Re: Anyone using XMLForm?
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On 4/5/00 at 9:14 am, ulim@denic.de (Ulrich Mayring) wrote:
>Stefano Mazzocchi wrote:
>>
>> BTW, I'm all ears if you guys propose to integrate XMLForm into Cocoon,
>> even if just an example... the more code we have the better, isn't it?
>
>How about a taglib?
Hmm, I proposed one on the dev-list several weeks back, no one responded .....
Subject: xml:form [long] date: 10 Apr 2000 18:08:32 -0000
>Anyway, there must be lots of need for something like that (displaying
>an XML file on the Web and editing it).
I would say there is a strong need for a generic form-handling tagset, that could also be used for site content editing.
Jeremy
____________________________________________________________________
Jeremy Quinn media.demon
webSpace Design
<ma...@media.demon.co.uk> <http://www.media.demon.co.uk>
<phone:+44.[0].207.737.6831> <pa...@sms.genie.co.uk>
Re: Anyone using XMLForm?
Posted by Ulrich Mayring <ul...@denic.de>.
Stefano Mazzocchi wrote:
>
> BTW, I'm all ears if you guys propose to integrate XMLForm into Cocoon,
> even if just an example... the more code we have the better, isn't it?
How about a taglib?
Anyway, there must be lots of need for something like that (displaying
an XML file on the Web and editing it).
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
Re: Anyone using XMLForm?
Posted by Stefano Mazzocchi <st...@apache.org>.
Mark Nickel wrote:
>
> Donald,
>
> > No, no, it's actually version 0.19.3d01. Apparantly the API has changed
> > somewhat between that and Xalan-1.0.1. I'll go back and revisit XMLForm to
> > patch this if y'all are interested. To date, I'm the only user I'm aware
> > of so I've been very easy to please.
>
> It would be nice if you could go back and revisit this because I'm really
> learning a lot from looking at your code. I don't know to much about the XPath
> stuff and you've got a nice straightforward example of how it can be used. Plus
> it's a tidy list framework for allowing various users to update XML documents w/o
> having to code a form to a database...
>
> I mean, you've got a lot of stuff going on: a Java servlet, Cocoon, XSP, writing
> out a DOM/SAX to disk as an XML file (I'm sure this could be done with Castor as
> well), and Xalan. IMHO a great learning tool.
>
> <snippet source="XMLForm Readme">
> ACKNOWLEDGEMENTS
>
> This project was inspired by Matt Sergeant's CGI::XMLForm perl module.
> This product includes software developed by the Apache Software Foundation
> (http://www.apache.org/). They rule.
> This product includes software developed by Exolab.
> (http://www.exolab.org/). They also rule.
> XMLForm itself was written by Donald A. Ball Jr. <ba...@webslingerZ.com>.
> He wishes to rule.
> </snippet>
>
> You rule! :)
Definately,
BTW, I'm all ears if you guys propose to integrate XMLForm into Cocoon,
even if just an example... the more code we have the better, isn't it?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
Re: Anyone using XMLForm?
Posted by Mark Nickel <mn...@dunsirn.com>.
Donald,
> No, no, it's actually version 0.19.3d01. Apparantly the API has changed
> somewhat between that and Xalan-1.0.1. I'll go back and revisit XMLForm to
> patch this if y'all are interested. To date, I'm the only user I'm aware
> of so I've been very easy to please.
It would be nice if you could go back and revisit this because I'm really
learning a lot from looking at your code. I don't know to much about the XPath
stuff and you've got a nice straightforward example of how it can be used. Plus
it's a tidy list framework for allowing various users to update XML documents w/o
having to code a form to a database...
I mean, you've got a lot of stuff going on: a Java servlet, Cocoon, XSP, writing
out a DOM/SAX to disk as an XML file (I'm sure this could be done with Castor as
well), and Xalan. IMHO a great learning tool.
<snippet source="XMLForm Readme">
ACKNOWLEDGEMENTS
This project was inspired by Matt Sergeant's CGI::XMLForm perl module.
This product includes software developed by the Apache Software Foundation
(http://www.apache.org/). They rule.
This product includes software developed by Exolab.
(http://www.exolab.org/). They also rule.
XMLForm itself was written by Donald A. Ball Jr. <ba...@webslingerZ.com>.
He wishes to rule.
</snippet>
You rule! :)
Mark
--
"People, like nails, lose their effectiveness when they lose
direction and begin to bend."
---- Walter Savage Landor
Re: Anyone using XMLForm?
Posted by Ulrich Mayring <ul...@denic.de>.
Donald Ball wrote:
>
> No, no, it's actually version 0.19.3d01. Apparantly the API has changed
> somewhat between that and Xalan-1.0.1. I'll go back and revisit XMLForm to
> patch this if y'all are interested. To date, I'm the only user I'm aware
> of so I've been very easy to please.
I'm the second ;-)
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
Re: Anyone using XMLForm?
Posted by Donald Ball <ba...@webslingerZ.com>.
On Wed, 3 May 2000, Mark Nickel wrote:
> Ulrich Mayring wrote:
>
> > I just downloaded XMLForm, however when I run the supplied example I get
> > (in the log files):
> >
> > java.lang.NoClassDefFoundError: org/openxml/parser/HTMLParser
>
> You need to have the openxml-1.2.jar in your Servlet engine classpath.
>
> For openxml go to here: http://www.openxml.org and click on "download" at
> the top of the screen.
>
> I have done such a thing and the cocoon portion is great but I'm getting an
> error from the XMLForm servlet:
> [03/05/2000 10:22:57:023 CDT] XMLForm: init
> [03/05/2000 10:22:58:311 CDT] java.lang.NoSuchMethodError:
> org.apache.xalan.xpat
> h.XPath: method
> <init>(Lorg/apache/xalan/xpath/XPathSupport;Lorg/apache/xalan/xp
> ath/xml/ProblemListener;)V not found
> at
> org.apache.jserv.JServConnection.processRequest(JServConnection.java:
> 320)
> at org.apache.jserv.JServConnection.run(JServConnection.java:188)
> at java.lang.Thread.run(Thread.java:475)
>
> The Xalan jar I'm using comes from the cocoon cvs for Cocoon-1.7.3-dev.
> It's from a "fairly" recent CVS build, got the mostly up-to-date sqltaglib
> stuff, (Thank's Donald! :) )
>
> The requirements state that XMLForm was created with:
> Xalan (http://xml.apache.org/xalan/) (0.19.3d01)
>
> Is that version the Xalan-1.0.1 version??
No, no, it's actually version 0.19.3d01. Apparantly the API has changed
somewhat between that and Xalan-1.0.1. I'll go back and revisit XMLForm to
patch this if y'all are interested. To date, I'm the only user I'm aware
of so I've been very easy to please.
- donald
Re: Anyone using XMLForm?
Posted by Mark Nickel <mn...@dunsirn.com>.
Ulrich Mayring wrote:
> I just downloaded XMLForm, however when I run the supplied example I get
> (in the log files):
>
> java.lang.NoClassDefFoundError: org/openxml/parser/HTMLParser
You need to have the openxml-1.2.jar in your Servlet engine classpath.
For openxml go to here: http://www.openxml.org and click on "download" at
the top of the screen.
I have done such a thing and the cocoon portion is great but I'm getting an
error from the XMLForm servlet:
[03/05/2000 10:22:57:023 CDT] XMLForm: init
[03/05/2000 10:22:58:311 CDT] java.lang.NoSuchMethodError:
org.apache.xalan.xpat
h.XPath: method
<init>(Lorg/apache/xalan/xpath/XPathSupport;Lorg/apache/xalan/xp
ath/xml/ProblemListener;)V not found
at
org.apache.jserv.JServConnection.processRequest(JServConnection.java:
320)
at org.apache.jserv.JServConnection.run(JServConnection.java:188)
at java.lang.Thread.run(Thread.java:475)
The Xalan jar I'm using comes from the cocoon cvs for Cocoon-1.7.3-dev.
It's from a "fairly" recent CVS build, got the mostly up-to-date sqltaglib
stuff, (Thank's Donald! :) )
The requirements state that XMLForm was created with:
Xalan (http://xml.apache.org/xalan/) (0.19.3d01)
Is that version the Xalan-1.0.1 version??
Thanks for any insights!! :)
Mark
Re: Anyone using XMLForm?
Posted by Rafael Oropeza <ro...@eud.com>.
When I tried to run the online example, I received the following message
Cocoon 1.6-dev
Error found handling the request.
java.lang.Exception: No processor for type "xsp"
at
org.apache.cocoon.processor.ProcessorFactory.getProcessor(ProcessorFactory.java:73)
at org.apache.cocoon.Engine.handle(Engine.java:208)
at org.apache.cocoon.Cocoon.service(Cocoon.java:144)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at
org.apache.jserv.JServConnection.processRequest(JServConnection.java:314)
at
org.apache.jserv.JServConnection.run(JServConnection.java:188)
at java.lang.Thread.run(Thread.java)
Ulrich Mayring wrote:
> Hi there,
>
> I just downloaded XMLForm, however when I run the supplied example I get
> (in the log files):
>
> java.lang.NoClassDefFoundError: org/openxml/parser/HTMLParser
>
> Thanks in advance for any pointers,
>
> Ulrich
>
> --
> Ulrich Mayring
> DENIC eG, Systementwicklung
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: Anyone using XMLForm?
Posted by Rafael Oropeza <ro...@eud.com>.
The URL is wrong. Try http://www.webslingerZ.com/balld/xmlform/
JJD wrote:
> Hi: I could not locate XMLForm. I tried
> (http:/www.webslingerZ.com/balld/xmlform/) but without success? Any other
> suggestion. Thanks JJD
>
> -----Original Message-----
> From: ulim@mx3-w.mail.home.com [mailto:ulim@mx3-w.mail.home.com]On
> Behalf Of Ulrich Mayring
> Sent: Wednesday, May 03, 2000 7:22 AM
> To: cocoon-users@xml.apache.org
> Subject: Anyone using XMLForm?
>
> Hi there,
>
> I just downloaded XMLForm, however when I run the supplied example I get
> (in the log files):
>
> java.lang.NoClassDefFoundError: org/openxml/parser/HTMLParser
>
> Thanks in advance for any pointers,
>
> Ulrich
>
> --
> Ulrich Mayring
> DENIC eG, Systementwicklung
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
RE: Anyone using XMLForm?
Posted by JJD <jj...@home.com>.
Hi: I could not locate XMLForm. I tried
(http:/www.webslingerZ.com/balld/xmlform/) but without success? Any other
suggestion. Thanks JJD
-----Original Message-----
From: ulim@mx3-w.mail.home.com [mailto:ulim@mx3-w.mail.home.com]On
Behalf Of Ulrich Mayring
Sent: Wednesday, May 03, 2000 7:22 AM
To: cocoon-users@xml.apache.org
Subject: Anyone using XMLForm?
Hi there,
I just downloaded XMLForm, however when I run the supplied example I get
(in the log files):
java.lang.NoClassDefFoundError: org/openxml/parser/HTMLParser
Thanks in advance for any pointers,
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org