Thanks for the suggestions. We needn't bend Wicket to the will of Adobe
just yet...
I've spent most of today cobbling together a wicket form generator that
uses the fillable fields in my PDFs as schematic. It's clunky, but has
helped me to "html-form-ify" the fields on a few of these old for
a POST request can be handled fine as long as it isn't a multiplart.Because PageParameters can't handle that therefor we need a real form component where all the multipart handling code is in.For this we need something like a BookmarkableForm i will try to look at this after
1.2So that you can pos
Johan Compagner schrieb:
you where talking about the PageParameters object so i thought you where
talking about inbound stuff.
Then every parameters will be in it.
Ofcourse no multipart stuff and ofcourse outbound only what can be presented
in a simple string can be added.
Ok, so it doesn't wo
you where talking about the PageParameters object so i thought you where talking about inbound stuff. Then every parameters will be in it.Ofcourse no multipart stuff and ofcourse outbound only what can be presented in a simple string can be added.
That seems logical to mejohanOn 4/13/06, Timo Stamm
Johan Compagner schrieb:
PageParametes will contain post params..
This comment by Martijn Dashorst sounds different:
| A note to the article: you can't use the PageParameters for types
| other than simple types such as Strings and Integers. [...]
|
| The bookmarkable links and PageParameters a
Johan Compagner schrieb:
PageParametes will contain post params..
That's great. Thanks, I wasn't aware of that.
Timo
So if for example you post to a bookmarkable page then PageParameters should
be filled with everything.
johan
On 4/13/06, Timo Stamm <[EMAIL PROTECTED]> wrote:
kurt hesto
PageParametes will contain post params..So if for example you post to a bookmarkable page then PageParameters should be filled with everything.johanOn 4/13/06,
Timo Stamm <[EMAIL PROTECTED]> wrote:
kurt heston schrieb:> I could probably extend one of the core wicket> classes instead of HttpServlet
kurt heston schrieb:
I could probably extend one of the core wicket
classes instead of HttpServlet and arrive at the same place, though I'm
not sure it would be any more elegant.
A thought: Maybe PageParameters should be available for POST requests as
well.
I don't know if it possible for
I'm passing the session id via a PDF hidden field. It seems to work
ok. I use the RequestCycle in establishing my hooks to Hibernate on the
Wicket side, not so with my Pdf servlet. I'm not sure yet whether I'm
going to regret it.
I guess I was just looking for some tighter integration tips.
kurt heston schrieb:
I've got some legacy PDFs laying around that utilize the HTTP submit
functionality available when using Acrobat fillable forms. The servlet
I have answering these Acrobat requests saves off the field names and
values submitted in a 3 column table (rec id, field name, value
Here's what my servlet does, minus the Hibernate code:
protected void doPost(HttpServletRequest arg0, HttpServletResponse arg1)
throws ServletException, IOException {
Enumeration e = arg0.getParameterNames();
while (e.hasMoreElements()) {
String parm = (String) e.nextElement();
11 matches
Mail list logo