Maybe if you set the logging to DEBUG level you will have more
information about the problem.
One possibility is that the templates.callingconvention.source
property does not ends with '/', note that this property should look like an
the base64, there is no examples in XINS 1.4 but we're thinking on having one
for XINS 1.5.
With std calling convention I got the xml output
as below (from Primer sample prj):
<?xml version="1.0" encoding="UTF-8" ?>
with _xins_xslt calling convention, I create
Hello.xslt under myproject\apis\myApi\spec (same dir with Hello.fnc), set this
path in xins.properties, but I got the error as below.
It is IO error but looks the base path is
correct. What is wrong.
One more q, I need open a local file (10+K) from
browser and send to server api as input of my api function. I think I should
use base64. Is there any sample form page/function code to handle
<xsl:output encoding="UTF-8" method="html"
[java] 3427 INFO
Successfully loaded access rule list with 1
[java] 3406 INFO Initialized
[java] 3440 INFO XSLT template cache in the
XSLT calling convention is enab
3442 INFO Base directory for the XSLT calling convention templates i
[java] 3415 NOTICE XINS/Java Server Framework has been
[java] 1200 INFO Starting watch
thread #0 for file "xins.properties". Check
ing for modifications every 10
[java] 3521 INFO Received HTTP GET
request from 10.15.8.155, path is
[java] 3550 INFO Allowing call from 10.15.8.155 to function Hello.
matches access rule 0 ("allow 0.0.0.0/0
[java] 3540 INFO 20060412-145356008
10.15.8.155 Hello 16 0
[java] 3541 INFO
20060412-145356008 10.15.8.155 Hello 16 0
3506 ERROR The calling convention "org.xins.server.XSLTCallingConven
could not convert the result due to an I/O exception.
----- Original Message -----
Sent: Tuesday, April 11, 2006 5:59
Subject: Re: [Xins-users] xins client
The problem is that you cannot pass the
location of the XSLT file on the command line, it doesn't work.
are 2 ways to pass the location of the XSLT:
* Passing a _template
parameter to the URL.
* By setting the runtime properties (meaning
in the xins.properties). Note that the value is then the directory where the
XSLT is located. Then the name of the file should be the same as the
AJAX example also uses the XSLT calling convention:
I download XINS 1.3.0 today and following the Primer sample to setup our my
test. Thanks Ernst's details instructions, everything went really smoothly.
Instead of changing my system path for Java/Ant/Xins as in step 2/5/9, I was
running a bat in dos window under the Xins home dir. Looks it works for me.
echo Run this from your XINS home dir.
Now I am adding XSLT support to MyAPI
<calling-convention name="_xins-xslt" />
2) add page1.xslt under myproject\apis\myApi\spec
<xsl:stylesheet version = '1.0'
3) restart Xins as
"xins -Dorg.xins.server.config=xins.properties -Dtemplates.callingconvention
But I still see the xml in my browser. I believe something is wrong in my
xslt (Being lazy again, I grab a sample from internet without understanding
the syntax :-( )
Then what is wrong?
----- Original Message -----
From: "Ernst de Haan" <firstname.lastname@example.org>
To: "arthur" <email@example.com>
Sent: Monday, April 10, 2006 3:36 PM
Subject: Re: [Xins-users] xins client question
I don't want install JRE on the client side. If I code a cpp GUI to
user input then I need a cpp http client lib to make the call to XINS. Any
good (and simple as XINS) cpp client recommand?
What exactly are you trying to do? And what is your client
environment? Are you going to develop a client (Windows?) application,
e.g. using Visual C++ or are you going to develop a server-side
application that will produce HTML?
If I use a web browser as client, then how can I config XINS to let the
see the response in a web page instead of xml? As my understanding, I need
css to map the xml to xdoc. I that true. My server response is always
as "Well done, this take me 5s" or "Invalid input".
You have a host of options:
- Use CSS on the returned XML (bad idea)
- Configure the XSLT calling convention and write some XSLT (see user guide)
- Use the new XINS frontend framework (see PetStore example in XINS 1.4)
- Write a custom calling convention (see user guide)
The right choice depends on what you want, exactly... Could you elaborate?
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
Xins-users mailing list