Using AXL as resource in a webservice

Version 1
    This document was generated from CDN thread

    Created by: Nicholas Ocket on 02-08-2013 04:58:54 AM
    Dear all, 

    I am having trouble with AXL when i try using it in a RESTful webservice. 

    Here is the scenario: 
    I have created a Restful webservice where users can get more information about the phone or where a program can fetch information about a caller and then send it to a phone. 

    I use Jersey as platform for my service, running it on Tomcat 7. The webservice works just fine, until I try to use my home made axl library. I have generated the classfiles and build a bit of a library around them, so i can reuse the library. The troubles comes at the point where i fetch the AXL port from the AXLAPIService:

    private void init(SOAPCredentials credentials){
        LOGGER.info("Initiating the axl api service...");
        axlService = new AXLAPIService();
        LOGGER.info("Initiating the axl port...");
        axlPort = axlService.getAXLPort();

        if(!hasCredentials(credentials)){
              throw new AxlPortFactoryException("Invalid credentials: missing either a username or a password!");
         }

        ((BindingProvider) axlPort).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, TVH_AXL_URL);
        ((BindingProvider) axlPort).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, credentials.getUsername());
        ((BindingProvider) axlPort).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, credentials.getPassword());
        }

    The request just times out. 
    When i write a unit test, using the restful resource that actually calls this code, then all works fine. Its just when i run the application and i use Curl to try and access the resource, then the AXLAPIService never returns an AxlPort. 

    What could be the problem here?