To fix this, remove these lines from spring-ws-common.xml (somewhere near lines 52 to 58): <bean id="usageInterceptor" class="com.agnitas.emm.springws.usage.UsageInterceptor"> <property name="usageLogger"> <bean class="com.agnitas.emm.springws.usage.DatabaseBasedUs...
Removed "addSubscriberEndpoint" from the context is wrong, because you remove the whole feature for subscriptions via webservices. Add the following lines to file spring-ws-common.xml: <bean id="WebserviceSubscriptionRejectionService" class="com.agnitas.emm.springws.subscrip...
Hi! The problem in your client is, that you're mixing public and non-public webservice methods. createContentModule and saveContentModuleContent are part of the non-public API. Mailings created with public API (AddMailing) will not be able to use resources created with non-public API. You have to us...
Hi! It seems, you're mixing two different webservices in your post. 1. You are creating a new mailing using the webservice AddMailingFromTemplate . 2. New content blocks are added by AddContentBlock . The error message "java.io.IOException: Server returned HTTP response code: 500 for URL" ...
it seems, that you're using the wrong data type. According to WSDL document, the data type is named "ArrayOf_xsd_anyType". The namespace should be "http://mock.dataaccess.utils.cms.agnitas.org".
One note: This is not a public API! It was used for internal use only!
Hi zanuda, your request is okay, but there is missing the timezone information in your timestamp. According to the XML schema, timezone in required and the server will reject your request when it is missing. I'm not sure, if "MESZ" is a valid time zone. Use the English abbreviations instea...
Hi! The body of your SOAP request is invalid. It is: <ns1:SendMailingRequest/> <param1>T</param1> <param2>1385636991</param2> The body should look like: <ns2:SendMailingRequest xmlns:ns2="http://agnitas.org/ws/schemas"> <ns2:mailingID>12345</ns2:mailingID> <ns2:recipientsType>world</ns2:re...
there is currently no possibility, to change settings of links by webservice.
The only way to make a link not trackable is to log in to web UI and change link settings manually.