I got it working using java transformation. I was receiving "Missing or incorrect XSLT Namespace." because I had same html file that the transformatoin was trying to produce.

Thanks Mukul. 

Do anybody know how to make it work using xml spy?


--- On Sun, 11/30/08, sudheshna iyer <sudheshnaiyer@xxxxxxxxx> wrote:

> From: sudheshna iyer <sudheshnaiyer@xxxxxxxxx>
> Subject: Re:  Random selection
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Date: Sunday, November 30, 2008, 1:08 PM
> Thank you very much Mukul. This is exactly what I am looking
> for.
> 
> One more question.
> 
> 1. How do you do xsl transformation. When I tried to do xsl
> transformation using the following xsl and xml from xml spy,
> I am receiving the following error.
> 
> This file is not valid.
> Error in xpath expression. Function not found in
> namespace..
> 
> 2. When I tried to transformation using java:
> 
>   ByteArrayOutputStream baos = new ByteArrayOutputStream();
>     SAXTransformerFactory saxTFactory =
> ((SAXTransformerFactory) tf);
>     tHandler1 = saxTFactory.newTransformerHandler(new
> StreamSource(xsllocation)); --> Missing or incorrect XSLT
> Namespace.
>     Transformer tr1 = tHandler1.getTransformer();
>    
>     xsllocation --> this is the location of xsl file in
> your local directory.
> 
> What is the way that you recomment?
> 
> Thanks again for your help
> 
> --- On Sun, 11/30/08, Mukul Gandhi
> <gandhi.mukul@xxxxxxxxx> wrote:
> From: Mukul Gandhi <gandhi.mukul@xxxxxxxxx>
> Subject: Re:  Random selection
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Date: Sunday, November 30, 2008, 12:52 PM
> 
> Hi Dimitre,
>   I would prefer a portable solution if it's really
> required (i.e., my
> IT architecture demands it).
> 
> If I know my stylesheet will always run in a Java
> environment, what's
> the harm in using the Java extensions provided by the
> processor?
> 
> On Sun, Nov 30, 2008 at 10:32 PM, Dimitre Novatchev
> <dnovatchev@xxxxxxxxx> wrote:
> > Hi Mukul,
> >
> > What about people, who use C#, Python, VB, C++, ...,
> etc?
> >
> > I strongly believe that recommending a non-portable
> solution on this
> > list when a known, 100% XSLT, portable one exists,
> should be
> > discouraged.
> >
> >
> > --
> > Cheers,
> > Dimitre Novatchev
> 
> 
> -- 
> Regards,
> Mukul Gandhi