axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh (JIRA)" <>
Subject [jira] Created: (AXIS2-2649) Simple soap request working in 1.0/1.1.1 release not working in 1.2
Date Thu, 10 May 2007 12:47:15 GMT
Simple soap request working in 1.0/1.1.1 release not working in 1.2

                 Key: AXIS2-2649
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: kernel
    Affects Versions: 1.2
         Environment: Java/Windows/AxisHTTPServlet
            Reporter: Rakesh
            Priority: Minor


We have been using Axis2 1.0 for a while. We are now tyring to upgrade to version 1.2. We
were able to make all the changes successfully and get the code working. For testing purposes,
we are running Axis2 in a standalone mode (not deployed in tomcat).

Way we start/initialize services
			File repository = new File(args[0]);

			if (!repository.exists())
				logger.warn("Repository file does not exists .. initializing repository");

			// Start the listener manager
			String dir = repository.getAbsolutePath();
			configContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem(dir,
dir + File.separator + "conf" + File.separator + "axis2.xml");
			listenerManager = configContext.getListenerManager();
			if (listenerManager == null)
				listenerManager = new ListenerManager();

			logger.debug("Using the Repository " + repository.getAbsolutePath());

			try{while(true) {Thread.sleep(10 * 60 * 1000); logger.debug("Looping in main thread");}
}catch(Exception e) {logger.error(e);}


The following sample call used to work in both Axis2 1.0 and 1.1.1 versions, but now it doesn't.
We need to add either action at the HTTP header level or other changes are needed.

<?xml version='1.0' encoding='UTF-8'?>
		<op:executeTMCommand xmlns:op="<<THE URL>>">

This doesn't work any more, unless I explicitly add the action at HTTP header level or pass
only content of the body for the SOAPMessageBodyBasedDispatcher to work.

Can you please let me know if this is problem or am I missing something here.


This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message