You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <tu...@ws.apache.org> on 2006/05/11 17:01:05 UTC

[jira] Commented: (TUSCANY-351) New FAQ Entry: Getting a null pointer for HelloWorldWeb

    [ http://issues.apache.org/jira/browse/TUSCANY-351?page=comments#action_12379081 ] 

Simon Laws commented on TUSCANY-351:
------------------------------------

I did a bit more investigation as to why my test server was not being set up properly. Basically is was user error but useful to know anyhow. The build/test instructions say (somewhere!) that to run the hello worl tomcat test you got to testing/tomcat and run mvn. When I do this everything works fine. Result happiness. However for some reason when I was playing at creating my own examples I ignored this instruction and used the "prepareTomcat" ant target that the maven pom refers to. This fails to run the XSLT script as it can't find XslpLiaison and TraXLiaison. So maven must set up some environment that makes this work.

The twist is that there is a flag in the ant file that only allows it to run the XSLT conversion once based on the presence of the service.xml.original file (the backup copy). Hence when you run ant again no errors are reported and all looks well, except that the tomcat configuration is incorrect.



> New FAQ Entry: Getting a null pointer for HelloWorldWeb
> -------------------------------------------------------
>
>          Key: TUSCANY-351
>          URL: http://issues.apache.org/jira/browse/TUSCANY-351
>      Project: Tuscany
>         Type: Improvement

>     Versions: Java-M1
>  Environment: all
>     Reporter: Simon Laws
>     Assignee: haleh mahbod
>      Fix For: Java-M1

>
> If you get null pointers for all of the samples that use Tomcat then check that the <Host> element in the conf/server.xml has been updated in accordance with the instructions here: java/sampleSetup.htm. For some reason the xslt script that does this from the build.xml failed on my fedora setup and didn't report and error. I will chase it a bit further and raise a seaprate JIRA if it seems to be a bug. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira