Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Can we see your web.xml also please? I am surprised to see the word <em>"spring"</em> in the endpoint URL. My endpoints have always looked like </p> <pre><code>url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf" </code></pre> <p>E.g.: I think your services-config.xml should look more like this.</p> <pre><code> &lt;channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel"&gt; &lt;endpoint url="http://{server.name}/dashboard-server/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/&gt; &lt;/channel-definition&gt; </code></pre> <p>I would also suggest not hardcoding the end-point URL so much. Just go with</p> <pre><code> &lt;channel-definition id="my-amf" class="mx.messaging.channels.AMFChannel"&gt; &lt;endpoint class="flex.messaging.endpoints.AMFEndpoint" url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf" /&gt; &lt;/channel-definition&gt; </code></pre> <hr> <h1>Update:</h1> <p>OK, so your web.xml looks OK, as does having the <code>spring</code> in your URL. What I don's see in your Spring configuration file (<code>application-config.xml</code>) is the Spring URL mapping. For example, in my Spring config files, in addition to the the bean definitions, there is a mapping. E.g.:</p> <pre><code>&lt;bean class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping"&gt; &lt;property name="mappings"&gt; &lt;value&gt; /histogram/**=bean.HistogramController /counter/**=bean.CounterController &lt;/value&gt; &lt;/property&gt; &lt;/bean&gt; &lt;bean id="bean.HistogramController" class="ch.comp.app.HistogramXportController" /&gt; &lt;bean id="bean.CounterController" class="ch.comp.app.CounterXportController" /&gt; </code></pre> <p><em>(I have one app that is Spring-based, and another that uses BlazeDS, but not both...so I might be missing something. That said, what I'm asking still should be valid. In theory. But take it with a grain of salt.)</em></p> <p>Maybe some some super basic debugging is in order. Can you check to see if the calls to your server are returning <code>HTTP 404</code> or not on theses problem endpoints? A couple ways to do this:</p> <ul> <li>Check the access logs for <code>GET /dashboard-server/spring/messagebroker/amf</code>. What is the HTTP status code for these requests? <em>(Free, easy, no new tools.)</em></li> <li>If you are using FireFox as a browser, add the <strong><a href="https://addons.mozilla.org/en-US/firefox/addon/966" rel="nofollow noreferrer">Tamper Data</a></strong> plug in. You don't have to tamper with the data, but it shows you what is being called, what is returned, and all the HTTP headers.</li> <li>Use a full on Flash/Flex oriented protocol sniffer tool, like <strong><a href="http://www.charlesproxy.com/" rel="nofollow noreferrer">Charles Web Debugging Proxy</a></strong>. </li> </ul> <p>It will very helpful to narrow down the problem to know if where these requests are failing on the communications stack. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload