This thread discusses the Content article: E4SS JSR289 Support

Hi Guys,

Currently we are using Websphere 6.1 and strongly planed to use E4SS as new _frame_work for our application. By now the Websphere does not support new SIP Servlet 1.1, Is it possible in your new machines turns off support of JSR289?

Best Regards,
-- Afshin

Afshin-

Since the APIs for JSR116 and JSR289 have significant differences, we plan to offer two separate E4SS development kits. However we plan to only add new _frame_work capabilities to the JSR289 code branch, so that we can focus on enhancements rather than backwards compatibility.

So the JSR116 version of the E4SS development kit would still be available, and we would work on any high-priority bugs found in that version.

Would this meet your needs?

Thanks,
Tom.

Hello Tom

As have been mentioned in your road map , I was waiting for two major features : (a) machine synchronization (b) machine inheritance . What about these features ?

-- Afshin

a) a form of machine synchronization is already supported in the latest ECharts (and E4SS) release (see http://echarts.org/Latest/ECharts-1.3-beta-Released.html) - see the notes regarding mixed state machines - is this what you are referring to?

b) machine inheritance is not happening any time soon i'm afraid - the next release of ECharts (Q1 2009) will support machine variables, which is a pre-requisite for machine inheritance - my plan was to work on support for exception handling after that since there is a need for it in some of our projects - there hasn't been a need for inheritance which is why it's at the bottom of the priority queue at the moment - you should realize that ECharts already provides support for overriding and customizing machine behavior by using transition priorities so perhaps this would satisfy your needs (it works well for us )

Hello Tom,

About 9 months ago, I had a post about GA release of E4SS. I think in that time I saw the 'machine synchronization' feature in the road map of Echarts.
Anyway, if two machines could cause a critical section , how we can manage them?

-- Afshin

the machine synchronization feature in the roadmap you refer to is the mixed states feature that was included in the last echarts release

when you refer to two machines in a critical section, do you mean (1) two machines marked as 'concurrent' nested within another machine, or do you mean (2) two machines concurrently running with different java threads?

if you mean (1) you don't have to worry about critical sections since transitions with (concurrent) machines run sequentially - see section 4.3 of the echarts user manual for more details

if you mean (2) you may have to worry about critical sections - if the two threads attempt to run the same machine instance then, again, you don't have to worry because the run() methods are synchronized - however, if the two threads are running different machine instances but attempt to access the same data, then you are responsible for enforcing synchronization - again, see section 4.3 of the user manual