Hi Ernst,
Not sure whether anyone else has had the chance to try this - the problem is probably just with me. I took the Xins source code and extracted it to an XP machine.
I'm using java 1.6.0_12. I was able to build it straight off from using ant.
However, going through the primer, it fails when I try to run-myapi - I get the following:

C:\dev\znerd-xins-1225133\MyProject>xins -Dorg.xins.server.config=xins.properties run-myapi
Buildfile: C:\dev\znerd-xins-1225133\src\ant\make-build.xml









Total time: 0 seconds
Buildfile: build\build.xml

[xmlvalidate] 1 file(s) have been successfully validated.
[xmlvalidate] 1 file(s) have been successfully validated.
[xmlvalidate] 1 file(s) have been successfully validated.
     [xslt] Transforming into C:\dev\znerd-xins-1225133\MyProject\build\java-fundament\myapi\com\mycompany\myapi\api

   [delete] Deleting: C:\dev\znerd-xins-1225133\MyProject\build\webapps\myapi\web.xml
[xmlvalidate] 1 file(s) have been successfully validated.
     [xslt] Processing C:\dev\znerd-xins-1225133\MyProject\apis\myapi\spec\api.xml to C:\dev\znerd-xins-1225133\MyProject\build\webapps\myapi\web.xml
     [xslt] Loading stylesheet C:\dev\znerd-xins-1225133\src\xslt\webapp\api_to_webxml.xslt
    [unjar] Expanding: C:\dev\znerd-xins-1225133\build\xins-common.jar into C:\dev\znerd-xins-1225133\MyProject\build\webapps\myapi
      [war] Building war: C:\dev\znerd-xins-1225133\MyProject\build\webapps\myapi\myapi.war
     [echo] MD5: 8e294aa1bd55abb41cbf51ac5ef16cc7
     [echo] Build time: 2010.01.25 11:13:00.133

Warning: Reference xins.classpath has not been set at runtime, but was found during
build file parsing, attempting to resolve. Future versions of Ant may support referencing ids defined in non-executed targets.
     [java]   3100 DEBUG   Changing APIServlet state from INITIAL to BOOTSTRAPPING_FRAMEWORK.
     [java]   3300 DEBUG   Initializing logging subsystem with the settings set in the "xins.properties" file.
     [java] 3305 INFO Logging subsystem has been initialized.
     [java] 3200 NOTICE Bootstrapping XINS/Java Server Framework (null). Servlet container: "XINS Servlet Test Container (Windows XP 5.1/x86)". JVM: "Sun Microsystems Inc. Java HotSpot(TM) Client VM 11.2-b01". OS: "Windows XP 5.1/x86".
     [java] 3444 ERROR The XINS/Java Server Framework failed to start.
     [java] 3444 DEBUG The XINS/Java Server Framework failed to start.
     [java] java.lang.NullPointerException
     [java]     at org.xins.server.EngineStarter.logBootMessages(EngineStarter.java:145)
     [java]     at org.xins.server.Engine.<init>(Engine.java:162)
     [java]     at org.xins.server.APIServlet.init(APIServlet.java:163)
     [java]     at org.xins.common.servlet.container.LocalServletHandler.initServlet(LocalServletHandler.java:81)
     [java]     at org.xins.common.servlet.container.LocalServletHandler.<init>(LocalServletHandler.java:49)
     [java]     at org.xins.common.servlet.container.HTTPServletHandler.addWAR(HTTPServletHandler.java:214)
     [java]     at org.xins.common.servlet.container.HTTPServletHandler.<init>(HTTPServletHandler.java:139)
     [java]     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     [java]     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     [java]     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     [java]     at java.lang.reflect.Constructor.newInstance(Constructor.java:51
     [java]     at org.xins.common.servlet.container.HTTPServletStarter.<init>(HTTPServletStarter.java:138)
     [java]     at org.xins.common.servlet.container.HTTPServletStarter.main(HTTPServletStarter.java:208)
     [java] 1504 DEBUG Query the Servlet with URL arguments: "/myapi/?_function=SayHello&_convention=_xins-std&_environment=http%3A%2%2F127.0.0.1%3A8080%2Fmyapi%2F&name=Bryan".
     [java] 1506 DEBUG Query to the Servlet succeeded with response (null) and the HTTP status 500.
     [java] 1504 DEBUG Query the Servlet with URL arguments: "/myapi/?_function=SayHello&_convention=_xins-std&_environment=http%3A%2%2F127.0.0.1%3A8080%2Fmyapi%2F&name=Bryan".
     [java] 1506 DEBUG Query to the Servlet succeeded with response (null) and the HTTP status 500.

On Sat, Jan 23, 2010 at 9:07 AM, Ernst de Haan <ernst@ernstdehaan.com> wrote:

I've just released the 3.0-alpha3 version of my XINS fork, which includes the also just released Logdoc 0.2. See:

Compared to version 0.1, Logdoc 0.2 is cleaned up: the internal logging output is now sent via Ant, meaning that the Ant options -verbose and -debug are needed to see all output. This improves usability.

XINS 3.0-alpha3 introduces lots of small changes, mostly cleanup and minor corrections. A functional change is the introduction of client-side transaction logging via the log messages 2300 and 2301. The former includes the input/output parameters, while the latter does not.

Note that my XINS 3.0 fork is based off XINS 2.2-alpha2. Porting the changes from the 2.x branch to my 3.0-fork is one of my next challenges. Help in this area would be much appreciated! If you are keen and precise and know a bit about Java coding, let me know.

Also, If you've got any issues downloading or building/running either of these, do let me know.


Ernst de Haan

Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
Xins-users mailing list