SSDN - XSLT and Java: Passing parameters to java functions

XML Editor

Sign Up

Search

Options

Chat

Help

News

Log in

Not Logged in

Topic

Topic Page 1 2 3 4 5 6 7 8 9

Kenneth Johansson

Subject: XSLT and Java: Passing parameters to java functions
Author: Kenneth Johansson
Date: 14 Jun 2004 05:58 PM

I am trying to pass external (runtime specific context) parameters to XSL(T) java functions.

My approach was to use the "setParameter" method on the transformer (javax.xml.transform.Transformer) object to be passed in to my java functions.

For example:

In my java code:
transformer.setParameter("osp", new String("UKJ"));

In my stylesheet:
<xsl:param name="osp"/>
<xsl:if test="Entity:isTest($osp)">

In my java function:
public static Object isTest(String context) {
return new Boolean(...);
}

The above example works fine. The problem is how to make the context parameter of the isTest method an Object and not a String. The "Stylus Studio" only seems to recognize string data types?

In other words:

public static Object isTest(Object context) {
return new Boolean(...);
}

The problem is then that "Stylus Studio" doesn't load the function anymore?

I would like to be able to set the parameter like the following and use the object in my java function:
transformer.setParameter("osp", new UserDefiendContext(...));

Any ideas?

Thanks in advance,
/Kenneth

Minollo I.

Subject: Re: XSLT and Java: Passing parameters to java functions
Author: Minollo I.
Date: 14 Jun 2004 07:34 PM

First of all: the Stylus Studio Java extension functions only accept a
limited set of valid signatures; for more details, take a look at
http://www.developxml.com/d_xslt36.html#wp486413 for more details on the
data types accepted as extension function arguments.

Second, in the parameters property page in an XSLT scenario setting dialog
you can only specify primitive data types or XPath expressions. As the
programming interface is not exposed at the UI level, it would be tricky to
let you specify something like "new UserDefiendContext(...)". As a
workaround you may want to consider using a static map in Java that allows
you to map string/number parameter values to non primitive Java types.

Hope this helps,
Minollo

Kenneth Johansson

Subject: Re: XSLT and Java: Passing parameters to java functions
Author: Kenneth Johansson
Date: 15 Jun 2004 06:06 PM

Hi Minollo,

Thanks for your quick reply. Your suggestion is pretty much inline with what I also had in mind. I hoped there would be a more elegant solution.

Today I found a another way of doing it which almost meets my requirements. I came up with the following solution. The only problem (that I can think of now) is that it doens't work in Stylus

Studio when mixing with other XSLT components (e.g. xsl:if, xsl:for-each,...). It does work fine for regular mappings.

//Keep the param declaration in the stylesheet (in other words):
<xsl:param name="osp" select="'default'"/>

//Add a variable to be used when mixing external parameters with source attributes
<xsl:variable name="name" select="Name"/>

//Add to the attribute mapping (directly directly in the XSL document and not in the Mapper view).
<xsl:value-of select="Entity:processName($osp, $name)"/>

//Change the java signature
public static Object processName(Object context, String name) {
UserDefiendContext c = (UserDefiendContext) context;
//Delegate to proper object.
return c.processName(name);
}

//Change the java code:
transformer.setParameter("osp", new UserDefiendContext(...));

All of this works just fine (if I fool the Stylus Studion program and add it directly to the stylesheet view) using the XALAN processor but the xsltc can not compile the stylesheet.

Any comments? Is this a violation of the XSLT spec?

/Kenneth

Minollo I.

Subject: Re: XSLT and Java: Passing parameters to java functions
Author: Minollo I.
Date: 19 Jun 2004 11:10 PM

>...
>Today I found a another way of doing it which almost meets my
>requirements. I came up with the following solution. The only problem
>(that I can think of now) is that it doens't work in Stylus Studio when
>mixing with other XSLT components (e.g. xsl:if, xsl:for-each,...). It does
>work fine for regular mappings.

What do you mean with "it doesn't work"? What's the problem you see? The
mapping is not rendered graphically?

>...
>//Add to the attribute mapping (directly directly in the XSL document and
>not in the Mapper view).
><xsl:value-of select="Entity:processName($osp, $name)"/>

I'm not sure I see the value of using a variable ($name) rather than the
XPath expression (Name).

>...
>All of this works just fine (if I fool the Stylus Studion program and add
>it directly to the stylesheet view) using the XALAN processor but the
>xsltc can not compile the stylesheet.
>
>Any comments? Is this a violation of the XSLT spec?

Any use of Java virtual functions is a potential violation of the XSLT
specs; but I would guess that if xsltc is giving you problems with this,
you are hitting an xsltc limitation. What is the error you get?

Minollo

Topic Page 1 2 3 4 5 6 7 8 9

Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!

Go to Conference:

Log In Options Username: Password:

Site Map | Privacy Policy | Terms of Use | Trademarks

Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.