Closed GoogleCodeExporter closed 9 years ago
Can you write the steps to test sending feedback to LASAD from outside. I
guess, I have implemented CreateFeedbackAction correctly.
Original comment by almer.bo...@gmail.com
on 14 Nov 2012 at 11:38
Do you have a working xmpp chat tool where you can monitor the xmpp channel? If
so, you should be able to directly send the appropriate xml message in the
channel, and should be able to see the feedback created. An important thing to
note is that the timestamp must be fairly current on the action (I think the
default is something like within 5 minutes of current time).
Original comment by tdragon1...@gmail.com
on 14 Nov 2012 at 11:52
I have updated the MonitoringTool project and wanted to send feedback into xmpp
channel. Toby, as you said, xml structure slightly changed. It lacks map-id
that is needed to send the feedback to specific map inside LASAD. Here is the
new structure of an action sent to the command chat room:
<action time="1355302637180">
<actiontype type="FEEDBACK" classification="create" succeed="UNKOWN" logged="false" />
<user id="Alan" role="receiver" />
<object id="0" type="MESSAGE">
<properties>
<property name="TEXT" value="Feedback message text" />
<property name="INTERRUPTION_TYPE" value="no_interruption" />
</properties>
</object>
<content>
<description />
<properties>
<property name="SENDING_TOOL" value="FEEDBACK_CLIENT" />
<property name="RECEIVING_TOOL" value="Metafora" />
</properties>
</content>
</action>
Original comment by almer.bo...@gmail.com
on 12 Dec 2012 at 9:02
A map id is not necessary if the user is currently logged into a map, the Case
tool will find the current map the user is logged into and add that map id
before sending the message to the LASAD server. THis behavior is already
working, so just ensure you join a map with the user to which you want to send
feedback, and the ID will be added.
Original comment by tdragon1...@gmail.com
on 12 Dec 2012 at 9:06
Original comment by tdragon1...@gmail.com
on 12 Dec 2012 at 9:07
Original comment by almer.bo...@gmail.com
on 22 Jan 2013 at 5:35
Original issue reported on code.google.com by
tdragon1...@gmail.com
on 10 Oct 2012 at 11:28