I found some SIP message types missing in org.echarts.servlet.sip.messages package.
Our application needs support for

• PUBLISH


• SuccessResponce202


• more sufficticated 4xx responses (481, 404, 487, ...)

I mean this would eliminate heavy usage of transition gaurds in E4SS machines.


P.S. I'd be happy to know if any IDE support (syntax highlighting, code completion, ...) is available (or is planned) for E4SS machines (for example in Eclipse).

I'm glad you are trying to reduce the reliance on guard evaluations, as this can make the code much more maintainable. You can provide your own message factory within your application to provide any custom message classes you wish.

You can subclass EChartsSipServlet and override the createRequest and createResponse methods. Something like:

Code: :

protected Request createRequest(SipServletRequest req) {   if( req.getMethod().equals("PUBLISH") )     ....   else     return super.createRequest(req); }

Hope this helps,
Tom.

P.S. Nothing on our roadmap for IDE support, though we would welcome any help in this area! The only thing I can offer at this time is vim syntax highlighting. The files are in $EDK_HOME/etc/vimtools.

Thank you Tom for your reply.
Let's see if I got your point correctly:

We don't want to override EChartsSipServlet behavior and look for it's default processing (featurebox dispatching, ...) for PUBLISH, 4xx, ... messages to work.

I am afraid we can't have something like

Code: :

transition S1 - p ? PUBLISH / blah_blah -> S2;

in our machines since it needs E4SS to be aware of that kind of messages as EChartsSipServlet is now.
or we should have current EChartsSipServlet.doRequest and doResponse source code to extend E4SS-like behavior.

Greg points out that you are using the JSR116 code _base_ (_base_d on your posting from another thread on this forum). In that case, the option to extend override the createRequest and createResponse methods of EChartsSipServlet will not work, as that is only present in the JSR289 release. (With that code, once you create your own custom message classes and customize the message factory, the messages are first-class citizens in any E4SS machine.)

Since you are using the JSR116 branch, the only way to customize the message creation behavior is to modify a local copy of the E4SS source code. This is straightforward: add new message classes in org.echarts.servlet.sip.messages.*, and revise the conditional logic in the Request.createRequest() and Response.createResponse() methods to produce the new message classes you want.

No chance you can use the JSR289 code _base_?

I unfortunately couldn't find the JSR289 _base_d code in your site! We may port to 289 someday.

When you are ready for JSR289, the development kit downloads, as well as the subversion trunk, are JSR289-compliant.