> ...
>
> > What about letting htmlunit know that it should parse this content like an
> > htmlpage, for instance with a small Groovy step before your normal test
> > steps like:
> >
> > <groovy>
> > import com.gargoylesoftware.htmlunit.*
> >
> > class MyPageCreator extends DefaultPageCreator
> > {
> > String determinePageType(contentType)
> > {
> > if ('application/vnd.wap.xhtml+xml' == contentType)
> > return 'html'
> > else
> > return super.determinePageType(contentType)
> > }
> > }
> > def webClient = step.context.webClient
> > webClient.pageCreator = new MyPageCreator()
> > </groovy>
>
> Okay, I got the general idea - but wouldn't this belong to HTMLUnit?
perhaps. I don't know enough about this content type to decide. May it contain
tags like <card> or something similar? This wouldn't work if processed as an
html page.
A feature that would probably be interesting (and flexible) would be to allow
to define on a per test basis through options or config file which content type
should be processed which way. This would belong to webtest, not to htmlunit.
Marc.
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
