Jack Tang wrote:
Hi Andrzej
I think javascript-function-and-url mapping is a good solution.
Say
domainName.javascript:go = http://www.a.com/b.jsp?id={0}
"go" is the javascipt function and it contains one param. And
"http://www.a.com/b.jsp?id={0}" is the URL template for "go" function.
and {0} is the exactly param, it should be merged when "go" function
is detected.
Now the problem I face is in "go" function the form is submited, and
the "action" is "POST".
Wow, that's a pretty old thread... The JS "pseudo-parser" plugin is just
that - it doesn't really understand JavaScript, it just tries to extract
urls, and does it with quite high error rate... but still better than
nothing.
If you want a full-fledged solution that can actually interpret your
scripts, then take a look at HttpUnit or HtmlUnit frameworks - both of
which can be turned into Javascript-aware crawlers.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com