rudy750
commented
6 years ago I could not get it to work either. I had to make some changes to the SDK. Here is what I did:
-
In
com.amazon.speech.speechlet.SpeechletRequest@JsonTypeInfo(use = Id.NAME, include = As.PROPERTY, property = "type") @JsonSubTypes({ // The sub types that extend the SpeechletRequest class. ... @Type(value = MessageReceivedRequest.class)added MessageReceivedRequest class to the bottom of the list.
-
In
com.amazon.speech.speechlet.SpeechletRequestDispactherelse if(speechletRequest instanceof MessageReceivedRequest) { @SuppressWarnings("unchecked") SpeechletRequestEnvelope<IntentRequest> parameterizedRequestEnvelope = (SpeechletRequestEnvelope<IntentRequest>) requestEnvelope; speechletResponse = speechlet.onIntent(parameterizedRequestEnvelope); }Now I put the response as an IntentRequest, based on what I read here:
This does cause some issues in your onIntent method. For now I am only handling Message requests. I don't think this will be the final way. I had a version that added a new onMessageReceived but that resulted in extensive refactoring of the SDK.
Let me know if you have any questions.
[EDIT] FYI, Here is how I handle this on the onIntent method in my speechlet:
public class MessageSpeechlet implements SpeechletV2 {
...
@Override
public SpeechletResponse onIntent(SpeechletRequestEnvelope<IntentRequest> requestEnvelope) {
Context cont = requestEnvelope.getContext();
SystemState messageContext= cont.getState(SystemInterface.class, SystemState.class);
SpeechletRequest request = requestEnvelope.getRequest();
String requestId = request.getRequestId();
String apiToken = messageContext.getApiAccessToken();
//You will use those to build your request and finally send the notification to the device
sendMessage(requestId, apiToken);
thomas-frenken
Hi all,
we currently try to implement notifications using the alexa Java SDK. This involves three steps: 1) Request access token from oauth api 2) Request consent token from messaging api 3) Send notification to messaging api
We already implemented that successfully using the node.js SDK. The first two steps also work with the Java SDK. At the beginning of step 3, we get an
com.fasterxml.jackson.databind.exc.InvalidTypeIdExceptionfrom a base class of the SDK.Explanation: The answer from the messaging api to step 2) is a
Messaging.MessageReceivedmessage which is not directly contained in the response object from the request of step 2) but is send as a new request from amazon towards our web service. Since we host the service ourselves, our backend relies on using thecom.amazon.speech.speechlet.servlet.SpeechletServletclass to wrap our implementation of the SpeechletV2 itself. This class pre-processes every request made towards our service in itsdoPostmethod. That message throws the mentioned exception when trying to parse theMessaging.MessageReceivedrequest containing the consent token:I think the Java SDK should already support these messages since I found the
com.amazon.speech.speechlet.interfaces.messaging.request. MessageReceivedRequest. If that is no supported yet, the api should at least no throw an exception because inside my spring boot filter chain that leads to the problem that I cannot process the request further.So I have two questions: 1) Does the Java SDK already support
Messaging.MessageReceivedand if, why is the exception thrown? 2) If it does not support these messages how can I prevent the SDK from trying to process this message?Cheers, Thomas