[
https://issues.apache.org/jira/browse/AXIS2-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2649:
------------------------------------
Assignee: Deepal Jayasinghe
> Simple soap request working in 1.0/1.1.1 release not working in 1.2
> -------------------------------------------------------------------
>
> Key: AXIS2-2649
> URL: https://issues.apache.org/jira/browse/AXIS2-2649
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Environment: Java/Windows/AxisHTTPServlet
> Reporter: Rakesh
> Assignee: Deepal Jayasinghe
> Priority: Minor
>
> Hi,
> 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();
> listenerManager.init(configContext);
> }
> listenerManager.start();
> 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);}
> ----
> MAIN PROBLEM:
> 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'?>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:wsa="http://www.w3.org/2005/08/addressing";
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/1999/XMLSchema";>
> <soapenv:Header>
>
> <wsa:MessageID>urn:uuid:22347A22E831E85ACF11689672899211</wsa:MessageID>
> <wsa:To>/axis2/services/<<SERVICE_NAME>></wsa:To>
> <wsa:Action>urn:executeTMCommand</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <op:executeTMCommand xmlns:op="<<THE URL>>">
> <PARAM1>XYZ</PARAM1>
> </op:executeTMCommand>
> </soapenv:Body>
> </soapenv:Envelope>
> 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.
> Thanks,
> Rakesh.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
