Related content:
- The W3C specification of XQuery, which also lists implementations
- An Introduction to XQuery
- JTidy, used in the tutorial
- Process XML using XML Query, a tutorial
Besides of all the nice projects mentioned like JTidy, Tagsoup and others, i really like the idea of a proxy portlet which should enable me to put every webapplication into a portal. Is this a common feature of all portal vendors or is it just inside the product whose name i ve forgotten written by Rickard and Co.?MarcI think this is a fairly common thing to have, but the beauty of this particular approach is that it is very customizable (scraping through XSL can be arbitrarily complex) and very high-performant (due to TagSoup being an SAX-type parser).
What is a proxy portlet? Why would it require link rewriting?It's a portlet that fetches the content of a given URL. And if that content contains links to other URL's whose content should also go through the proxy, then the URL's have to be rewritten so that when the end-client clicks on them the request will go to the portal/proxy portlet instead of the original URL, which will fetch the data. In effect, the proxied URL(/application) and all related resources will never be accessed directly by the client, and the client shouldn't even know that it exists, as all of the communication goes through the portlet. This means that links needs to be rewritten, resources (like "src" attributes on the img tag) needs to be rewritten, and CSS and JavaScripts need to be rewritten, so that all requests go through the portal.
Very interesting stuff. It looks to be very close to the custom solution we came up with, except that our solution had to be platform-agnostic and therefore is implemented in Java rather than C# (or whatever .NET language it's implemented in) and uses HtmlUnit rather than IE. Since we don't use IE, we don't have the snazzy interface, either ;-)