rhizophora mangle
Sethi Family Guestbook 3.0.0
Sethi Family Guestbook is a clean-interfaced guestbook script written in PHP. It features: Page spanning; (Optional) private guestbook comment; User can select the number of entries per page to display, guestbook format (elegant, simple, or standard), more>> Sethi Family Guestbook is a clean-interfaced guestbook script written in PHP. It features: Page spanning; (Optional) private guestbook comment; User can select the number of entries per page to display, guestbook format (elegant, simple, or standard), and background color; and Uses a text file. Now supports image verification using random text as part of a CAPTCHA system. It incorporates elements designed to foil bots by confusing OCR software, and also uses strong PHP session security in order to disallow them getting around it (e.g., preventing brute force attacks, slip-through attempts, etc.). It also disallows blank sessionIDs (a great anti-spam technique for guestbooks, etc. to use against spambots that exploit PHPs vulnerability to fake requests with blank sessionIDs). It supports multiple formats, mangled email display, and a fully customizable interface.<<less
License:GPL
OSWorkflow 2.8.0
This is a low level workflow implementation written in Java more>>
OSWorkflow 2.8.0 is considered as a smart and useful application that is known as a "low level" workflow implementation written in Java. It does not use a graphical tool for developing workflows, but can be configured by writing a xml file as the main conf file for the workflow process.
Graphical solutions dont provide the flexibility to properly fulfill all requirements in a full-blown application. In this way the programmer can go in and customize the OSWorkflow after his specific needs.
Situations like "loops" and "conditions" that might be represented by a graphical icon in other workflow systems must be "coded" in OSWorkflow.
Major Features:
Compiling from CSV: To get the latest version of OSWorkflow,it is recommend that the source via CSV is to be downloaded and compiled using the Jakarta Ant build script provided there. Compiling OSWorkflow from source is trivial with the following ant targets:
- jar (default) - compiles the library osworkflow.jar
- example-war - compiles and assembles osworkflow-2.8.0-example.war, which is configured to use memory persistence and should deploy without any configuration into most web containers.
- example-ear - compiled and assembles osworkflow-2.8.0-example.ear, which is a J2EE application that is configured to use osworkflow with the EJB persistence store. Some configuration of data sources is required, as well as a full J2EE application server.
- client-jar - compiled and assembles designer.jar, which is a Swing GUI workflow designer application that can be used to visually inspect and edit workflows.
Enhancements
- AbstractWorkflow.getVariablesFromMaps unsafe use of PropertySet
- transientVars currentSteps list not updated soon enough after step transition for post-functions
- Tutorials code snippets
- AbstractWorkflow fails to load XML configuration after redeployment on BEA Weblogic 7.0.2
- The test case should not depend on mckoi lib
- Actions tag shoukld alow just only common-action
- No results at all from designer
- Bug with Websphere Application Server 5.1..0.4, error creating new workflow instance
- Exception orrured when invoking getAvailableActions() and doAction()
- Common actions written out as duplicates
- NPE in initial action if conditionalResult is not empty
- Cant use input parameters in workflow
- Creating Trigger Functions via API does not work
- Order of results from Workflow.getHistorySteps(long) is variable
- Multiple evaluations of action restrict-to conditions
- Cant get the tutorial to work. Please help !
- (Conditional)ResultDescriptor does not write due-date to xml
- canModifyEntryState dont manage COMPLETED entry state
- Workflow does not escape XML entities when saving itself
- null getAction of initial-action
- getAvailableActions return false on exception
- Scheduled workflow doesnt get the right config
- Designer can not display join condition editor
- moveToHistory bug in implicit finish step
- Broken compatibility with previous versions
- Documentation or DefaultConfigurator error
- CreateNewStep even actions finish attribute is set to true
- Bug in cache management
- AbstractWorkflow NPE: cache.put(action, result);
- HibernateWorkflowStore/SpringHibernateWorkflowStore problem
- JDBCWorkflowFactory: getWorkflow(name) doesnt work unless in debug mode
- com.opensymphony.workflow.designer.WorkflowGraphModel has classcastexception
- Persistence JDBCStore with Mysql fail
- Cannot KILL a Workflow instance
- Defining a conditional-result in an initial-action causes an NPE
- Problems with doAction
- Manifest entry in latest OSWorkflow violates spec
- Join transition failure
- Inconsistency between MemoryWorkflowStore & JDBCWorkflowStore w.r.t step functions
- Selecting the Conditions Type throws a NoSuchMethodException
- beanshell condition can not access transientVars
- Duplicate entry constraint with MySQLWorkflowStore
- Patch to SpringTypeResolver.setFunctions
- Inconsistent transientVars behaviour
- Unable to compile OSWorkflow from Ant script
- ClassCastException in LocalEJBCondition
- Incorrect javadoc for the com.opensymphony.workflow.util.Caller class.
- Incorrect javadoc for the com.opensymphony.workflow.util.MostRecentOwner class.
- The value of the attribute "auto" of the element "action" is being checked ONLY for the value "true".
- Implicit calls cannot update the transientVars Map
- Due date does not supported in queries (HibernateStore+Spring)
- XMLWorkflowFactory.WorkflowConfig doesnt implement Serializable interface
- New load signatures on WorkflowLoader break compatibility with code complied with 2.7
- Actions within workflow descriptior should escape invalid characters.
- Designer doesn`t show the join ID
- Improve javadocs for Configuration
- WorkflowException does not show stack trace of inner exception
- Eclipse project classpath fix
- Add isModifiable() method to AbstractWorkflowFactory
- Add "createdStep" to transientVars
- Query OS_CURRENTSTEP instead of OS_WFENTRY in JDBCWorkflowStore.java
- Query Speed w/ JDBCWorkflowStore.java can be abysmal
- Mangled stacktraces from BSH scripts
- AbstractWorkflow private methods could be protected
- Due Date Queries and Duplicate Code Reduction
- MemoryWorkflowStore fixes to work with Due Date
- Persistence Updates for Due Date
- Role/Group attribute for result
- Separate Thread to execute auto actions in transitionWorkflow
- currentSteps is empty for pre-functions at the first step
- Interface WorkflowFactory instead of class AbstractWorkflowFactory
- Pluggable ScriptVariableParser
- Consolidation of three identical Conditions
- Conditions and condition xml element order in Workflow description
- Limitation while inheriting MySQLWorkflowStore
- Visibility of the inner class com.opensymphony.workflow.loader.XMLWorkflowFactory.WorkflowConfig
- Adding version into jar manifest
- The inner com.opensymphony.workflow.JoinNodes$DummyStep class should be made private.
- The attribute "step" of both the elements "result" and "unconditional-result" could be made #REQUIRED instead of #IMPLIED.
- There should exist a mechanism that allows removing of all the info about unnecessary workflow entry from the store.
- Add setter for beanProvider to DefaultVariableResolver.
- Request for global actions that do not change workflow step.
- Plugin model for fucntion and condition (Spring/BeanShell).
- Global condition/function.
- Dynamic number of split states.
- actionId in getAvailableActions.
- Display a live graph.
- Function and Conditions to be displayed on the Edge(Action).
- Type base -> Instance base.
- BSF doesnt work with new Jakarta package.
- SQL Script for OSWorkflow for DB2 Databases.
- Hibernate 3 support.
- TransientVars supplied to conditions in external-permission.
Requirements:
- OSCore 2.0.1+.
- PropertySet 1.2+.
- Jakarta commons-logging.
- BeanShell (optional).
- BSF (optional).
- EJB interfaces.
- XML parser (Not required for JDK 1.4).
Libcwd 0.99.46
Libcwd is a thread-safe, full-featured debugging support library for C developers. more>>
Major Features:
- End-users of an application don't need to install libcwd.
- The use of name-spaces prevents name collisions between debug channels of different libraries.
- Debug channels and devices can be turned on or off on a per thread basis.
- All debug code can be omitted from the executable by not defining a single CWDEBUG macro.
- Code using libcwd looks clean and is surveyable as a result of using a few well-defined macros, avoiding the need of disturbing #ifdef CWDEBUG ... #endif constructs.
- Debug output is written to an ostream and as such type-safe and customizable as is usual for C ostreams.
- An arbitrary number of debug channels and debug devices can be created without any penalty in terms of cpu usage.
- Full support for all forms of iterative and recursive calls.
- Page: 1 of 1
- 1