You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Zeynep Gunal <z....@publitec.vnu.com> on 2001/04/03 17:13:49 UTC

RE: FW: Xalan-Java extensions - Is this the right mailing list to post this?

Myriam and James,

>Have you looked at:
>  http://xml.apache.org/xalan-j/extensions.html

I have, and I tried to make use of lxslt:component and lxslt:script
elements, but then I got this error message:

java.lang.reflect.InvocationTargetException: com.ibm.bsf.BSFException:
UnsatisfiedLinkError loading library:bsfactivescriptengine no
bsfactivescriptengine in java.library.path
        at
com.ibm.bsf.engines.activescript.ActiveScriptEngine.<clinit>(ActiveScriptEng
ine.java:638)
        at java.lang.Class.newInstance0(Native Method)
        at java.lang.Class.newInstance(Unknown Source)
        at com.ibm.bsf.BSFManager.loadScriptingEngine(BSFManager.java:316)
        at java.lang.reflect.Method.invoke(Native Method)
        at
org.apache.xalan.extensions.ExtensionHandlerGeneral.<init>(ExtensionHandlerG
eneral.java:196)
        at
org.apache.xalan.templates.ElemExtensionDecl.runtimeInit(ElemExtensionDecl.j
ava:229)
        at
org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j
ava:696)
        at
org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2122)
        at java.lang.Thread.run(Unknown Source)
java.lang.reflect.InvocationTargetException
        at
org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j
ava:713)
        at
org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2122)
        at java.lang.Thread.run(Unknown Source)
XSLT Error (org.apache.trax.TransformException): Could not compile extension
 (org.xml.sax.SAXException): Could not compile extension

Maybe I misinterpreted everything. Maybe Microsoft's JScript classes
(ActiveXObject in my case) cannot be accessed from within XSLT. But if it is
possible, then I was not capable of understanding the document
http://xml.apache.org/xalan-j/extensions.html.

Needless to say, I have only started learning this subject recently and I am
struggling real hard.

Cheers,

Zeynep

Re: FW: Xalan-Java extensions - Is this the right mailing list topost this?

Posted by James Melton <ja...@cylogix.com>.
I have only worked with Java extensions so I am not able to help you
with the subtleties of MS ActiveX. I assume you've looked at all the
obvious stuff mentioned on the extensions page:
  bsf.jar on your classpath,
  MSVCP60.DLL from Microsoft,
  appropriate language DLLs from Microsoft
http://msdn.microsoft.com/scripting

Sorry and good luck,
Jim.

Zeynep Gunal wrote:
> 
> Maybe Microsoft's JScript classes
> (ActiveXObject in my case) cannot be accessed from within XSLT. But if it is
> possible, then I was not capable of understanding the document
> http://xml.apache.org/xalan-j/extensions.html.
> 

____________________________________________________________
James Melton                 CyLogix
609.750.5190                 609.750.5100
james.melton@cylogix.com     www.cylogix.com

Re: FW: Xalan-Java extensions - Is this the right mailing list topost this?

Posted by Gary L Peskin <ga...@firstech.com>.
Zeynep --

Ummm.  I don't think you're going to like this because it involves some
additional work but here goes.  You need to visit this page:

http://oss.software.ibm.com/developerworks/project/showfiles.php?group_id=16&release_id=59

Download the current binary zip file distribution for BSF
(bsf-bin-2.2.zip).  Extract bsfactivescriptengine.dll from the .zip
file.  This is not supplied with the Xalan distribution but should be. 
I'd recommend placing this in your xalan-j_2_0_1/bin directory right
next to bsf.jar but you're free to place it wherever you want.

Add the directory for bsfactivescriptengine.dll to your
java.library.path.  You'll have to see your JVM documentation to
determine how java.library.path is initialized, if you can find any
documentation on this at all.  Try adding the directory containing
bsfactivescripting.dll to your PATH environment variable.

The only documentation I've been able to find on this is here:
http://java.sun.com/docs/books/tutorial/native1.1/stepbystep/_library.html

If all else fails, try adding your .dll path to the property
java.library.path.  You can do this either programmatically or by
specifying

  java -Djava.library.path=mypath (use the actual path).

Also, you could place the bsfactivescriptending.dll in the same
directory where your existing msvcp60.dll file is already located. On my
system, this is in

  c:\WINNT\system32

but you'll have to do a find on yours.

In any event, when you succeed, please let us know what worked and we'll
update the extension documentation so that others can benefit from your
pioneering.  If you have followed the steps outlined here but are still
having problems, please post those along with exactly what you've done
so far.

Gary

Zeynep Gunal wrote:
> 
> Myriam and James,
> 
> >Have you looked at:
> >  http://xml.apache.org/xalan-j/extensions.html
> 
> I have, and I tried to make use of lxslt:component and lxslt:script
> elements, but then I got this error message:
> 
> java.lang.reflect.InvocationTargetException: com.ibm.bsf.BSFException:
> UnsatisfiedLinkError loading library:bsfactivescriptengine no
> bsfactivescriptengine in java.library.path
>         at
> com.ibm.bsf.engines.activescript.ActiveScriptEngine.<clinit>(ActiveScriptEng
> ine.java:638)
>         at java.lang.Class.newInstance0(Native Method)
>         at java.lang.Class.newInstance(Unknown Source)
>         at com.ibm.bsf.BSFManager.loadScriptingEngine(BSFManager.java:316)
>         at java.lang.reflect.Method.invoke(Native Method)
>         at

RE: [Xalan 1 -> Xalan 2 migration] "SystemId Unknown; Line 0; Column 0;"

Posted by Philippe Vijghen <Ph...@forem.be>.
oops lapsus: I was not meaning "Tamino API" but of course "Java1
compatibility API" :)

> As a first step, I am planning to do it through the Tamino API:

[Xalan 1 -> Xalan 2 migration] "SystemId Unknown; Line 0; Column 0;"

Posted by Philippe Vijghen <Ph...@forem.be>.
Dear gurus,

I am trying to go from Xalan 1 to Xalan 2.

As a first step, I am planning to do it through the Tamino API:
I had to make several changes at the level of:
	- Xalan extensions
	- message generation on processor output (line number, columns, ...)
	- discovery of improted stylesheets
	- classes location (ex. XPathAPI)

OK that step is completed: everything compiles.

Now I am facing the following issue:

> [2001/04/03 17:28:57]  [ ERROR ] RenditionManager -- XSLT rendition by
'file:/d:/users/phv/FOREM/WP3_dvp/PortalDvp/HotJob/XSLDir/Error.xsl' failed:
> javax.xml.transform.TransformerException: processStylesheet not
succesfull!
>         at
org.apache.xalan.xslt.XSLTEngineImpl.error(XSLTEngineImpl.java:1528)
>         at
org.apache.xalan.xslt.XSLTEngineImpl.error(XSLTEngineImpl.java:1493)
>         at
org.apache.xalan.xslt.XSLTEngineImpl.processStylesheet(XSLTEngineImpl.java:6
67)
>         at
be.acse.xsl.XSLTCache$CachedStylesheet.refresh(XSLTCache.java:368)
>         at be.acse.xsl.XSLTCache.getStyleSheet(XSLTCache.java:172)
>         at be.acse.xsl.XSLTCache.process(XSLTCache.java:237)
>         at
be.acse.servlet.RenditionManager.render(RenditionManager.java:223)
>         at
be.acse.servlet.HttpServlet.renderHttpResponse(HttpServlet.java:758)
>         at
be.acse.servlet.HttpServlet.renderHttpResponse(HttpServlet.java:713)
>         at be.acse.servlet.HttpServlet.doMain(HttpServlet.java:564)
>         at be.acse.servlet.HttpServlet.doGet(HttpServlet.java:390)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
>	    ...

On the System.stderr, I fond the following "additional information":
	    SystemId Unknown; Line 0; Column 0;


This was working fine with Xalan 1.
Is there any new convention for System identifiers? (no more "file:/{path}"
on NT?)?

Help please,

	Philippe

---
Philippe Vijghen (phv@acse.be)
Project Manager
Software AG Belgium - ACSE, Professional Services Division