Be the first to post a text review of easyasap. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• File released: /easyasap/prototypes/easyasap_s5.3.8.4e.tar.gz

  posted 1469 days ago

• easyasap prototypes file released: easyasap_s5.3.8.4e.tar.gz

  When the factory is populated correctly in the service_config table, the demo server creates the service instance and data entries and runs the state machine. The client demo invokes CreateInstance and ListInstances from an Observer interface and the factory server appropriately responds. A multithreaded execution model is provided so that the factory writes to a channel consumed for the service that runs a finite state machine and writes to a channel for the instance that consumes instance requests and runs a finite state machine that controls a task (activity) which runs its own execution finite state machine. When the activity completes, the instance puts completed requests to channels for subscribed observers. In 5.2.1, the service event relay and associated processing state machine times out appropriately in the idle state and list instances responses now return the full instance uri like the create instance response, rather than just the resource reference uri. In 5.2.2, lists like observers, history events and instance responses are serialized by default as repeated elements rather than xsd arrays. Define ASAP_USE_XSD_ARRAY to revert to xsd arrays. In 5.2.3 all state changes are logged to the EVM database and sent to observers. When the task completes, the callback now puts a CompleteActivity request to the instance's queue, and the instance appropriately completes through its machine. Item Management Traits now encapsulate classification, creation, copying, destruction, and special item type creation. In 5.3 instance communication is supported. A factory_service_demo behaves like the older server demos, and the new server_asap_demo dispatches to both factory and instance handlers. The statesystem action for execution is populated to do a sleep so operations can be invoked for the instances. In the initial release, subscription is working. The factory URI in the client script and database now includes a path identifier after the port and before the query (where in java a "container" would be specified) so that the generated URI parses appropriately as a method. In 5.3.1 change state request is demonstrated. In 5.3.2 EVM data population is corrected so that open.notrunning instances may be aborted and "Instance" rather than "InstanceRs" is used as the type for ListInstanceRs elements. In 5.3.3 arbitrary context data is produced and accepted. Bind list backend uses the context for the state machine. URI grammar now compiled outside of headers. In 5.3.4, more code was pulled into separate compilation units to avoid running out of memory at compile time, the db_utility library was revised to stop leaks, and EVM database code and ddl was revised for portability to a postgres backend, some EVM/FSM logic was corrected. In 5.3.5 further leaks were fixed. NamedThreads now assume ownership of the threads, db_utility leaks fixed. 5.3.5.2 includes recovery on startup for the service_asap_demo. 5.3.5.4 includes further postgres portability changes in the schema and code: the code now demonstrably works as well with postgres as the original backend db. 5.3.5.5 provides support for GetProperties for instances. 5.3.6 provides ASAP's GetProperties for factories and EVM time-interval guards on actions. 5.3.6w contains edits to facilitate compilation with VC7 and provides some NMakefiles for use with nmake (use cygwin to gunzip). 5.3.6.1 contains 5.3.6w changes and now requires jwsmtp to support an SMTP client action type. Further messaging tools were added for the backend. Improved build/Makefile to simplify the build. 5.3.6.5 uses the new namespace uri and has been tested with a .net client. Variable values can now be serialized based on a different bind list. Optionally supports a statesystem action that dynamically loads and runs a shared object module, and stateful service instance data contains a map of any to allow arbitrarily complex data structures to be passed between such actions. 5.3.6.6 includes minor corrections for sending the completed request result data verbatim and widening the context and result data fields in the database. 5.3.6.7 includes corrections to service_asap_demo to reset fault data and corrected Instance Response serialization back to pre-5.3.6.6 status. 5.3.6.8 is the version showcased at the BPM conference 7/23/04: includes SoapSessionType corrections for buffered HTTP service reads, support for xsd:date, and history event reporting constrained by the schema. 5.3.7 includes reconnection to the database if it goes down (turn off INI caching if using unixODBC), corrects zero-or-more element parsing, allows for the new namespace, and corrects the Spirit URI parser for hyphenated domain labels. 5.3.7.1 has only EVM changes: it supports statesystem action override by service and provides a demonstration instance purge example. 5.3.8 additionally includes a preliminary WS-Addressing implementation and shows early development work for WS-Context and WSR, and revisions to EasySoap to support OneWay messages. 5.3.8.1 revises the FiniteStateMachine and backend framework to consider unhandled exception events failures, and reflect failures in the ASAP state for the activity. In 5.3.8.2, requests for cancellation now work, correcting previous concurrency problems, and requests for suspension return a transition-not-supported fault by default since many platforms do not support pthread_suspend. In 5.3.8.3, the EVM backend deals with bind lists more flexibly, the easysoap distribution was modified to support the one-way message exchange pattern, a WS-Addressing implementation is provided and code has been generalized for easier adoption of the next version of ASAP, and WS-Context prototype code is provided. In 5.3.8.4, the EVM backend has amenities like setting environment variables for actions, multiple recipients for mail actions, a simple file availability example and parsing utilities for legacy file formats.

  posted 1469 days ago

• File released: /easyasap/prototypes/easyasap_s5.3.8.3.tar.gz

  posted 1673 days ago

• easyasap prototypes file released: easyasap_s5.3.8.3.tar.gz

  When the factory is populated correctly in the service_config table, the demo server creates the service instance and data entries and runs the state machine. The client demo invokes CreateInstance and ListInstances from an Observer interface and the factory server appropriately responds. A multithreaded execution model is provided so that the factory writes to a channel consumed for the service that runs a finite state machine and writes to a channel for the instance that consumes instance requests and runs a finite state machine that controls a task (activity) which runs its own execution finite state machine. When the activity completes, the instance puts completed requests to channels for subscribed observers. In 5.2.1, the service event relay and associated processing state machine times out appropriately in the idle state and list instances responses now return the full instance uri like the create instance response, rather than just the resource reference uri. In 5.2.2, lists like observers, history events and instance responses are serialized by default as repeated elements rather than xsd arrays. Define ASAP_USE_XSD_ARRAY to revert to xsd arrays. In 5.2.3 all state changes are logged to the EVM database and sent to observers. When the task completes, the callback now puts a CompleteActivity request to the instance's queue, and the instance appropriately completes through its machine. Item Management Traits now encapsulate classification, creation, copying, destruction, and special item type creation. In 5.3 instance communication is supported. A factory_service_demo behaves like the older server demos, and the new server_asap_demo dispatches to both factory and instance handlers. The statesystem action for execution is populated to do a sleep so operations can be invoked for the instances. In the initial release, subscription is working. The factory URI in the client script and database now includes a path identifier after the port and before the query (where in java a "container" would be specified) so that the generated URI parses appropriately as a method. In 5.3.1 change state request is demonstrated. In 5.3.2 EVM data population is corrected so that open.notrunning instances may be aborted and "Instance" rather than "InstanceRs" is used as the type for ListInstanceRs elements. In 5.3.3 arbitrary context data is produced and accepted. Bind list backend uses the context for the state machine. URI grammar now compiled outside of headers. In 5.3.4, more code was pulled into separate compilation units to avoid running out of memory at compile time, the db_utility library was revised to stop leaks, and EVM database code and ddl was revised for portability to a postgres backend, some EVM/FSM logic was corrected. In 5.3.5 further leaks were fixed. NamedThreads now assume ownership of the threads, db_utility leaks fixed. 5.3.5.2 includes recovery on startup for the service_asap_demo. 5.3.5.4 includes further postgres portability changes in the schema and code: the code now demonstrably works as well with postgres as the original backend db. 5.3.5.5 provides support for GetProperties for instances. 5.3.6 provides ASAP's GetProperties for factories and EVM time-interval guards on actions. 5.3.6w contains edits to facilitate compilation with VC7 and provides some NMakefiles for use with nmake (use cygwin to gunzip). 5.3.6.1 contains 5.3.6w changes and now requires jwsmtp to support an SMTP client action type. Further messaging tools were added for the backend. Improved build/Makefile to simplify the build. 5.3.6.5 uses the new namespace uri and has been tested with a .net client. Variable values can now be serialized based on a different bind list. Optionally supports a statesystem action that dynamically loads and runs a shared object module, and stateful service instance data contains a map of any to allow arbitrarily complex data structures to be passed between such actions. 5.3.6.6 includes minor corrections for sending the completed request result data verbatim and widening the context and result data fields in the database. 5.3.6.7 includes corrections to service_asap_demo to reset fault data and corrected Instance Response serialization back to pre-5.3.6.6 status. 5.3.6.8 is the version showcased at the BPM conference 7/23/04: includes SoapSessionType corrections for buffered HTTP service reads, support for xsd:date, and history event reporting constrained by the schema. 5.3.7 includes reconnection to the database if it goes down (turn off INI caching if using unixODBC), corrects zero-or-more element parsing, allows for the new namespace, and corrects the Spirit URI parser for hyphenated domain labels. 5.3.7.1 has only EVM changes: it supports statesystem action override by service and provides a demonstration instance purge example. 5.3.8 additionally includes a preliminary WS-Addressing implementation and shows early development work for WS-Context and WSR, and revisions to EasySoap to support OneWay messages. 5.3.8.1 revises the FiniteStateMachine and backend framework to consider unhandled exception events failures, and reflect failures in the ASAP state for the activity. In 5.3.8.2, requests for cancellation now work, correcting previous concurrency problems, and requests for suspension return a transition-not-supported fault by default since many platforms do not support pthread_suspend. In 5.3.8.3, the EVM backend deals with bind lists more flexibly, the easysoap distribution was modified to support the one-way message exchange pattern, a WS-Addressing implementation is provided and code has been generalized for easier adoption of the next version of ASAP, and WS-Context prototype code is provided. In 5.3.8.4, the EVM backend has amenities like setting environment variables for actions, multiple recipients for mail actions, a simple file availability example and parsing utilities for legacy file formats.

  posted 1673 days ago

• File released: /easyasap/prototypes/easyasap_s5.3.8.2.tar.gz

  posted 1821 days ago

• easyasap prototypes file released: easyasap_s5.3.8.2.tar.gz

  When the factory is populated correctly in the service_config table, the demo server creates the service instance and data entries and runs the state machine. The client demo invokes CreateInstance and ListInstances from an Observer interface and the factory server appropriately responds. A multithreaded execution model is provided so that the factory writes to a channel consumed for the service that runs a finite state machine and writes to a channel for the instance that consumes instance requests and runs a finite state machine that controls a task (activity) which runs its own execution finite state machine. When the activity completes, the instance puts completed requests to channels for subscribed observers. In 5.2.1, the service event relay and associated processing state machine times out appropriately in the idle state and list instances responses now return the full instance uri like the create instance response, rather than just the resource reference uri. In 5.2.2, lists like observers, history events and instance responses are serialized by default as repeated elements rather than xsd arrays. Define ASAP_USE_XSD_ARRAY to revert to xsd arrays. In 5.2.3 all state changes are logged to the EVM database and sent to observers. When the task completes, the callback now puts a CompleteActivity request to the instance's queue, and the instance appropriately completes through its machine. Item Management Traits now encapsulate classification, creation, copying, destruction, and special item type creation. In 5.3 instance communication is supported. A factory_service_demo behaves like the older server demos, and the new server_asap_demo dispatches to both factory and instance handlers. The statesystem action for execution is populated to do a sleep so operations can be invoked for the instances. In the initial release, subscription is working. The factory URI in the client script and database now includes a path identifier after the port and before the query (where in java a "container" would be specified) so that the generated URI parses appropriately as a method. In 5.3.1 change state request is demonstrated. In 5.3.2 EVM data population is corrected so that open.notrunning instances may be aborted and "Instance" rather than "InstanceRs" is used as the type for ListInstanceRs elements. In 5.3.3 arbitrary context data is produced and accepted. Bind list backend uses the context for the state machine. URI grammar now compiled outside of headers. In 5.3.4, more code was pulled into separate compilation units to avoid running out of memory at compile time, the db_utility library was revised to stop leaks, and EVM database code and ddl was revised for portability to a postgres backend, some EVM/FSM logic was corrected. In 5.3.5 further leaks were fixed. NamedThreads now assume ownership of the threads, db_utility leaks fixed. 5.3.5.2 includes recovery on startup for the service_asap_demo. 5.3.5.4 includes further postgres portability changes in the schema and code: the code now demonstrably works as well with postgres as the original backend db. 5.3.5.5 provides support for GetProperties for instances. 5.3.6 provides ASAP's GetProperties for factories and EVM time-interval guards on actions. 5.3.6w contains edits to facilitate compilation with VC7 and provides some NMakefiles for use with nmake (use cygwin to gunzip). 5.3.6.1 contains 5.3.6w changes and now requires jwsmtp to support an SMTP client action type. Further messaging tools were added for the backend. Improved build/Makefile to simplify the build. 5.3.6.5 uses the new namespace uri and has been tested with a .net client. Variable values can now be serialized based on a different bind list. Optionally supports a statesystem action that dynamically loads and runs a shared object module, and stateful service instance data contains a map of any to allow arbitrarily complex data structures to be passed between such actions. 5.3.6.6 includes minor corrections for sending the completed request result data verbatim and widening the context and result data fields in the database. 5.3.6.7 includes corrections to service_asap_demo to reset fault data and corrected Instance Response serialization back to pre-5.3.6.6 status. 5.3.6.8 is the version showcased at the BPM conference 7/23/04: includes SoapSessionType corrections for buffered HTTP service reads, support for xsd:date, and history event reporting constrained by the schema. 5.3.7 includes reconnection to the database if it goes down (turn off INI caching if using unixODBC), corrects zero-or-more element parsing, allows for the new namespace, and corrects the Spirit URI parser for hyphenated domain labels. 5.3.7.1 has only EVM changes: it supports statesystem action override by service and provides a demonstration instance purge example. 5.3.8 additionally includes a preliminary WS-Addressing implementation and shows early development work for WS-Context and WSR, and revisions to EasySoap to support OneWay messages. 5.3.8.1 revises the FiniteStateMachine and backend framework to consider unhandled exception events failures, and reflect failures in the ASAP state for the activity. In 5.3.8.2, requests for cancellation now work, correcting previous concurrency problems, and requests for suspension return a transition-not-supported fault by default since many platforms do not support pthread_suspend. In 5.3.8.3, the EVM backend deals with bind lists more flexibly, the easysoap distribution was modified to support the one-way message exchange pattern, a WS-Addressing implementation is provided and code has been generalized for easier adoption of the next version of ASAP, and WS-Context prototype code is provided. In 5.3.8.4, the EVM backend has amenities like setting environment variables for actions, multiple recipients for mail actions, a simple file availability example and parsing utilities for legacy file formats.

  posted 1821 days ago

• File released: /easyasap/prototypes/easyasap_s5.3.8.1.tar.gz

  posted 1823 days ago

• easyasap prototypes file released: easyasap_s5.3.8.1.tar.gz

  When the factory is populated correctly in the service_config table, the demo server creates the service instance and data entries and runs the state machine. The client demo invokes CreateInstance and ListInstances from an Observer interface and the factory server appropriately responds. A multithreaded execution model is provided so that the factory writes to a channel consumed for the service that runs a finite state machine and writes to a channel for the instance that consumes instance requests and runs a finite state machine that controls a task (activity) which runs its own execution finite state machine. When the activity completes, the instance puts completed requests to channels for subscribed observers. In 5.2.1, the service event relay and associated processing state machine times out appropriately in the idle state and list instances responses now return the full instance uri like the create instance response, rather than just the resource reference uri. In 5.2.2, lists like observers, history events and instance responses are serialized by default as repeated elements rather than xsd arrays. Define ASAP_USE_XSD_ARRAY to revert to xsd arrays. In 5.2.3 all state changes are logged to the EVM database and sent to observers. When the task completes, the callback now puts a CompleteActivity request to the instance's queue, and the instance appropriately completes through its machine. Item Management Traits now encapsulate classification, creation, copying, destruction, and special item type creation. In 5.3 instance communication is supported. A factory_service_demo behaves like the older server demos, and the new server_asap_demo dispatches to both factory and instance handlers. The statesystem action for execution is populated to do a sleep so operations can be invoked for the instances. In the initial release, subscription is working. The factory URI in the client script and database now includes a path identifier after the port and before the query (where in java a "container" would be specified) so that the generated URI parses appropriately as a method. In 5.3.1 change state request is demonstrated. In 5.3.2 EVM data population is corrected so that open.notrunning instances may be aborted and "Instance" rather than "InstanceRs" is used as the type for ListInstanceRs elements. In 5.3.3 arbitrary context data is produced and accepted. Bind list backend uses the context for the state machine. URI grammar now compiled outside of headers. In 5.3.4, more code was pulled into separate compilation units to avoid running out of memory at compile time, the db_utility library was revised to stop leaks, and EVM database code and ddl was revised for portability to a postgres backend, some EVM/FSM logic was corrected. In 5.3.5 further leaks were fixed. NamedThreads now assume ownership of the threads, db_utility leaks fixed. 5.3.5.2 includes recovery on startup for the service_asap_demo. 5.3.5.4 includes further postgres portability changes in the schema and code: the code now demonstrably works as well with postgres as the original backend db. 5.3.5.5 provides support for GetProperties for instances. 5.3.6 provides ASAP's GetProperties for factories and EVM time-interval guards on actions. 5.3.6w contains edits to facilitate compilation with VC7 and provides some NMakefiles for use with nmake (use cygwin to gunzip). 5.3.6.1 contains 5.3.6w changes and now requires jwsmtp to support an SMTP client action type. Further messaging tools were added for the backend. Improved build/Makefile to simplify the build. 5.3.6.5 uses the new namespace uri and has been tested with a .net client. Variable values can now be serialized based on a different bind list. Optionally supports a statesystem action that dynamically loads and runs a shared object module, and stateful service instance data contains a map of any to allow arbitrarily complex data structures to be passed between such actions. 5.3.6.6 includes minor corrections for sending the completed request result data verbatim and widening the context and result data fields in the database. 5.3.6.7 includes corrections to service_asap_demo to reset fault data and corrected Instance Response serialization back to pre-5.3.6.6 status. 5.3.6.8 is the version showcased at the BPM conference 7/23/04: includes SoapSessionType corrections for buffered HTTP service reads, support for xsd:date, and history event reporting constrained by the schema. 5.3.7 includes reconnection to the database if it goes down (turn off INI caching if using unixODBC), corrects zero-or-more element parsing, allows for the new namespace, and corrects the Spirit URI parser for hyphenated domain labels. 5.3.7.1 has only EVM changes: it supports statesystem action override by service and provides a demonstration instance purge example. 5.3.8 additionally includes a preliminary WS-Addressing implementation and shows early development work for WS-Context and WSR, and revisions to EasySoap to support OneWay messages. 5.3.8.1 revises the FiniteStateMachine and backend framework to consider unhandled exception events failures, and reflect failures in the ASAP state for the activity. In 5.3.8.2, requests for cancellation now work, correcting previous concurrency problems, and requests for suspension return a transition-not-supported fault by default since many platforms do not support pthread_suspend. In 5.3.8.3, the EVM backend deals with bind lists more flexibly, the easysoap distribution was modified to support the one-way message exchange pattern, a WS-Addressing implementation is provided and code has been generalized for easier adoption of the next version of ASAP, and WS-Context prototype code is provided. In 5.3.8.4, the EVM backend has amenities like setting environment variables for actions, multiple recipients for mail actions, a simple file availability example and parsing utilities for legacy file formats.

  posted 1823 days ago

• easyasap prototypes file released: easyasap_s5.3.7.1.tar.gz

  When the factory is populated correctly in the service_config table, the demo server creates the service instance and data entries and runs the state machine. The client demo invokes CreateInstance and ListInstances from an Observer interface and the factory server appropriately responds. A multithreaded execution model is provided so that the factory writes to a channel consumed for the service that runs a finite state machine and writes to a channel for the instance that consumes instance requests and runs a finite state machine that controls a task (activity) which runs its own execution finite state machine. When the activity completes, the instance puts completed requests to channels for subscribed observers. In 5.2.1, the service event relay and associated processing state machine times out appropriately in the idle state and list instances responses now return the full instance uri like the create instance response, rather than just the resource reference uri. In 5.2.2, lists like observers, history events and instance responses are serialized by default as repeated elements rather than xsd arrays. Define ASAP_USE_XSD_ARRAY to revert to xsd arrays. In 5.2.3 all state changes are logged to the EVM database and sent to observers. When the task completes, the callback now puts a CompleteActivity request to the instance's queue, and the instance appropriately completes through its machine. Item Management Traits now encapsulate classification, creation, copying, destruction, and special item type creation. In 5.3 instance communication is supported. A factory_service_demo behaves like the older server demos, and the new server_asap_demo dispatches to both factory and instance handlers. The statesystem action for execution is populated to do a sleep so operations can be invoked for the instances. In the initial release, subscription is working. The factory URI in the client script and database now includes a path identifier after the port and before the query (where in java a "container" would be specified) so that the generated URI parses appropriately as a method. In 5.3.1 change state request is demonstrated. In 5.3.2 EVM data population is corrected so that open.notrunning instances may be aborted and "Instance" rather than "InstanceRs" is used as the type for ListInstanceRs elements. In 5.3.3 arbitrary context data is produced and accepted. Bind list backend uses the context for the state machine. URI grammar now compiled outside of headers. In 5.3.4, more code was pulled into separate compilation units to avoid running out of memory at compile time, the db_utility library was revised to stop leaks, and EVM database code and ddl was revised for portability to a postgres backend, some EVM/FSM logic was corrected. In 5.3.5 further leaks were fixed. NamedThreads now assume ownership of the threads, db_utility leaks fixed. 5.3.5.2 includes recovery on startup for the service_asap_demo. 5.3.5.4 includes further postgres portability changes in the schema and code: the code now demonstrably works as well with postgres as the original backend db. 5.3.5.5 provides support for GetProperties for instances. 5.3.6 provides ASAP's GetProperties for factories and EVM time-interval guards on actions. 5.3.6w contains edits to facilitate compilation with VC7 and provides some NMakefiles for use with nmake (use cygwin to gunzip). 5.3.6.1 contains 5.3.6w changes and now requires jwsmtp to support an SMTP client action type. Further messaging tools were added for the backend. Improved build/Makefile to simplify the build. 5.3.6.5 uses the new namespace uri and has been tested with a .net client. Variable values can now be serialized based on a different bind list. Optionally supports a statesystem action that dynamically loads and runs a shared object module, and stateful service instance data contains a map of any to allow arbitrarily complex data structures to be passed between such actions. 5.3.6.6 includes minor corrections for sending the completed request result data verbatim and widening the context and result data fields in the database. 5.3.6.7 includes corrections to service_asap_demo to reset fault data and corrected Instance Response serialization back to pre-5.3.6.6 status. 5.3.6.8 is the version showcased at the BPM conference 7/23/04: includes SoapSessionType corrections for buffered HTTP service reads, support for xsd:date, and history event reporting constrained by the schema. 5.3.7 includes reconnection to the database if it goes down (turn off INI caching if using unixODBC), corrects zero-or-more element parsing, allows for the new namespace, and corrects the Spirit URI parser for hyphenated domain labels. 5.3.7.1 has only EVM changes: it supports statesystem action override by service and provides a demonstration instance purge example. 5.3.8 additionally includes a preliminary WS-Addressing implementation and shows early development work for WS-Context and WSR, and revisions to EasySoap to support OneWay messages. 5.3.8.1 revises the FiniteStateMachine and backend framework to consider unhandled exception events failures, and reflect failures in the ASAP state for the activity. In 5.3.8.2, requests for cancellation now work, correcting previous concurrency problems, and requests for suspension return a transition-not-supported fault by default since many platforms do not support pthread_suspend. In 5.3.8.3, the EVM backend deals with bind lists more flexibly, the easysoap distribution was modified to support the one-way message exchange pattern, a WS-Addressing implementation is provided and code has been generalized for easier adoption of the next version of ASAP, and WS-Context prototype code is provided. In 5.3.8.4, the EVM backend has amenities like setting environment variables for actions, multiple recipients for mail actions, a simple file availability example and parsing utilities for legacy file formats.

  posted 1911 days ago

• File released: /easyasap/prototypes/easyasap_s5.3.7.1.tar.gz

  posted 1911 days ago