without seeing an input doc its hard to be sure (and hard to run on a
differebr system) but the stylesheet looks Ok to me, even if there are
errors in it getting a java exception (orther than out of memory type
things) is always a bug in the processor. XSLt errors should result in
user level xslt error messages not uncaught exceptions.

The variable use looks correct although if you always call it with
<xsl:with-param name="shippedOrder" select="."/>
in your actual code then you could drop th eparam as the current node
is still the current node in the called template, you don;t need to pass
it directly.

As writeen you do always need to pass shippedOrder in with some value as
the default
<xsl:param name="shippedOrder"/>
is actually an empty string not an empty node set and so if this
template is called without an explicit parameter you will get an error
from
($shippedOrder/ORDER_DETAIL
as you can't use / after a string.

Presumably unrelated but usual comment about // in match patterns
 match="//PACKAGE"
// isn't doing anything there you can remove it.

David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________