Lab 6

XML and XSLT

 

 

Introduction

 

This week we learned how to use XSLT to leverage XML data in your web applications.  In this lab, you will use this knowledge to manipulate XML that you extract from your database. In future labs, you will then use XSLT to exploit other kinds of XML.

 

Instructions:

 

  1. Copy your Lab04 files (or Lab05, if you continued your theme in Lab05) to a new Lab06 directory. Your main file should still be called index.html

2.      Here is what you what you want to have when you are finished.  Suggested plan of attach for getting there is below (read it before you start!):

    1. Deadline for waivers: If you think that a particular detail of this lab should be modified for you, because you can achieve the same educational objective in a different way that works better with your theme, you must request a waiver, via email, before the end of the lab period when this lab is started. State clearly why an exception should be made and what you propose instead.  You can talk to the instructor first, but it must be finalized via email.
    2. Warning!!  Firefox will sometimes cache old versions of the files you use (especially your sample XML and your XSL files).  If things aren’t working right, try this:  Tools->Clear Recent History.  Select “Everything” for time range.  Click to open the details (if necessary) then select just “Cache” and click “Clear Now”.  This is likely to happen to you, so make note of this issue!!!
    3. Everything from previous labs should still work. Per your feedback, this will NOT be required – you just need enough working to demonstrate the functionality described below.  Note that this will include the ability to insert things into your database from your web page.
    4. There should be a button or something to click or interact with such that when you click the following happens:
      1. You use AJAX, which invokes a Perl (PHP okay) script to query your DB. Synchronous AJAX is okay.
      2. The Perl returns a XML document (see details below.  You do not actually save this file, just use “print” from Perl). Namespaces are not required for this XML (but you can use if you like).
      3. You transform that XML with XSLT (see details below).
      4. You display part of the transformed XML in your page.
      5. All of this should happen within your original index.html (e.g. the URL up top should not change)
    5. The details of the XML produced by your DB are up to you. It should however at a minimum contain:
      1. Results for at least 3 distinct “things” (e.g. people, products, events) (including all items from your DB is okay too)
      2. Contain at least 2 distinct attributes or sub-elements “about” each thing (e.g., if your “thing” is a person, then the name and company of each person would each count here).
      3. Adding new results to the DB (using your existing functionality) should cause the XML result to change (e.g., if you add a new person, that person should appear in the XML produced).
    6. The details of the XSLT transformation are up to you.  It should however at a minimum:
      1. Do some re-orderings (e.g. not display things in exactly the same order as the XML file)
      2. Insert some HTML markup
      3. Contains results for at least 3 distinct “things”
      4. Show the info from at least 2 distinct attributes/elements “about” each thing
      5. Your XSLT should not be too similar to the given examples.
    7. For testing and grading purposes, you must make (and keep around) two test files. You must keep this up to date if you change your XML later!
      1. test1.xml – sample XML in exactly the same format that your Perl program produces.
      2. test2.xml – identical to test1.xml, except it has the line in it that causes the browser to transform it with your XSL file before displaying the results.
    8. As always, your code must be commented!
    9. On your default.htm page, provide some instructions for a user (e.g. the instructor) on how to use your site.  This should be specific to this lab – e.g. how can I see that your site meets the requirements for this lab? For instance, what exactly to click, what to enter, etc. Don’t assume that the user will have any idea what movies, people, things, etc. your system knows about.
    10. On your default.htm page, have the following links:
      1. Link to test1.xml
      2. Link to test2.xml
      3. Link to invoke to your Perl file that generates the XML. Provide arguments (if necessary) – so if you click on this link, you should see XML appear in the browser, and the XML should be in the same format as test1.xml and test2.xml (it’s okay if the data is a little different).

 

  1. Suggested plan of attack (see also helpful info at end)
    1. Do NOT follow the requirements above in order. Instead…
    2. First create the dummy XML file (test1.xml) that approximates what you WANT to produce from your database. You do not have to have namespaces in this file.
    3. Verify that test1.xml is valid by loading it in a browser. A complaint about namespaces is okay, but it should be rendered as valid XML.
    4. Create your XSLT file. Suggestion: start with the “Example 0.5” XSL from the online example page.
    5. COPY test1.xml to test2.xml.  Now test your XSLT file by adding the appropriate line to your test2.xml XML file (not test1.xml) and loading it in a browser.
    6. Write the JavaScript to load the XML (from your test1.xml), apply the XSLT to it, then insert some of the result in your page. Note: test2.xml will not work here because of the processing instruction that you added to it! Note: for this it’s perfectly fine to re-use the sample JavaScript given in class.
    7. Once all that works, then write the Perl code to actually produce real XML based on querying your DB. Test this script alone via the browser! (you want to ensure a.) the script runs b.) it produces valid XML)
    8. Modify your JavaScript to get the dynamically generated XML from the Perl script (instead of using the static XML).
    9. Make sure that the user can add content to the database and have that content show up in the results of the transformed XML.
    10. Write the default.htm instructions
    11. In default.htm, add the links to test1.xml, test2.xml, and to invoke Perl to generate XML (see details in requirements above)
    12. Important:: go back and check that
      1. test1.xml and test2.xml have identical content (only differ in a processing instruction)
      2. test1.xml and test2.xml match the XML format produced by your Perl program
      3. test1.xml renders as valid XML in the browser
      4. test2.xml shows the transformed result (e.g. changed by XSLT) when loaded in the browser

4.      Ensure your page works with Firefox. Having it work on IE is encouraged but not required.

5.      Ensure all your pages validate and that you have met all requirements.

     

NOTE: all HTML files must validate as XHTML without errors for full credit.  The penalty for a file that does not validate is 10%.

Helpful stuff

  1. See the plan of attack above!
  2. For problems with perl, see tips about creating Perl files.
  3. As always, the “Error Console” in Firefox is invaluable.
  4. On the command line, database errors will usually appear automatically.  From the browser, they won’t – instead insert this as a debug:
         print $DBI::errstr;
  5. Useful SQL examples:
    1. CREATE TABLE comments (USER_NAME VARCHAR(20), TIMESTAMP DATETIME, COMMENT MEDIUMTEXT, PAGE INTEGER);
    2. INSERT INTO comments (USER_NAME, TIMESTAMP, COMMENT, PAGE) VALUES ('Jamie', '2006-09-27 11:30:00', 'hi', 2);
    3. CREATE TABLE topics (TOPIC VARCHAR(20), OWNER VARCHAR(20));
    4. INSERT INTO topics (TOPIC, OWNER) VALUES ('Cars', ‘Jamie’);
    5. Note: ID is automatically created with the table, no need to specify it.
  6. Do not use the die() function alone – the error it generates can’t be seen from your web page.

 

Deliverables

1)      All of your files for Lab06 should be in a folder called "Lab06" (without the quotes) on the Web drive.

2)      Your main page for Lab06 should be called "index.html" (without the quotes) and placed inside the folder Lab01.

3)      All files must be complete and saved to your Web drive before you submit the hardcopy of your assignment. Do NOT modify your files after you have submitted your assignment.

4)      Turn in the following hardcopy on or before the due date, stapled together in the following order (coversheet on top):

a)      A completed assignment coversheet.  Your comments will help us improve the course.

b)      The first page of the output of the W3C validator, as run on the final version of your Lab06/index.html.  This should show that your document correctly validated, but turn it in anyway if you can’t get your page to validate. 

c)      A printout of the source to your Lab06/index.html file (not the rendered page that you normally see with Internet Explorer/Firefox).   Truncated lines are not acceptable – use Crimson Editor vice Notepad if needed for printing.  You could also paste into Microsoft Word etc. if needed.

i)        NOTE – turning in just the JavaScript fragment that does the transformation and insertion is acceptable if you wish.

d)      Printouts of external JavaScript files, if any.

e)      Printout of your Perl/PHP file that generates XML.

f)        Printout of test2.xml

g)      Printout of your XSL file