Home
Login
Contact
Articles
Newsletter
Bookmark and Share
XSLT
CSS
Javascript
Java
Linux
Username
Password
Annuler
Connexion

Recent Articles

javascript print partial pages

In developping web applications and designing websites, you've probably come accross a situation where you wanted the user to be able to press a print...

Marquee in javascript

The Marquee Element has been deprecated by the W3C and is commonly ill-advised but nevertheless, if you really want to do it, then javascript is the w...

Sending an email in Java

Sending an email in Java is actually quite simple, as always, there is an API that will do most of the work for you and it becomes just a matter of im...

Opacity in Firefox 3.5

If you've upgraded to Firefox 3.5 and you've been using -moz-opacity in your CSS, then you will see that the transparency or opacity (depending on ho...

Installing Tomcat on Linux in a few minutes

Installing tomcat is actually very quick and easy. Assuming you already have the JDK installed, this will only take a few minutes. In my years of exp...

Testing for a specific xpath without using a for-each in XSLT

30 May at 05:06PM published by Matt Castonguay

There will be many occasions while programming in XSLT where you have a long xpath, or you're inside a template and have a relative set of elements that you want to test for a specific condition. The idea of doing an xsl:for-each in order to find a specific element is an overkill (since you cannot break out of a loop in xslt) and in this article we will see how we can avoid that using the double negation trick.

xsl include vs import

03 March at 09:18PM published by Matt Castonguay

I've recently been asked by a friend to explain the difference between include and import and how it would affect the templates being matched in these files. The answer is very simple, but you also must understand that there are other ways to foce which template will be called in the case that were are identical matchings.

The "mode trick" for identical XMLs

27 January at 10:09AM published by Matt Castonguay

There is a common problem in XSLT where you have two XML of the same xPath (whether it be absolute or relative) that end up taking the same template. In many scenarios you do not have the ability to modify the XML so that it suits your XSLT and you must therefore turn to the mode trick to create seperate templates.

Random Tags

proxypass    offsetleft    weakhashmap    firefox    min-width    print    position    optimization    url mapping    tinymce    math    hashmap    xml    clear    ie6    tomcat    template    modproxy    marquee    xsl:include    iframe    textarea    uniques    custom css    apply-templates    apache    offsetleft    function    xsl:import    library    xsl:if    wysiwyg    hashmap    javamail    svn    min-height    memory    offsettop    offsettop    double negation   
MG2 Media Inc. - A Web Development Company
Top