opensymphony
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 8
PropertySet 1.3
This Java module can be used to fulfill storage requirements in applications that change constantly more>>
PropertySet 1.3 is considered as a smart and useful Java module that can be used to fulfill storage requirements in applications that change constantly.
It is backed by EJB, Ofbiz, JDBC, Castor JDO, XML or any other persistence-agnostic mechanisms that can handle a typed key-value pair implementation.
Usage examples for this module can be a user preference feature, a game profile page, or any kind of application that needs storage and has a fast rhythm of updates and changes.
Enhancements
- Bug in AbstractPropertySet.getAsActualType() doe snot handle text property type.
- AggregatePropertySet is not Serializable.
- Patch for propertyset-default.xml.
- com.opensymphony.module.propertyset.hibernate.PropertySetItem should implement an interface.
- JDBCPropertySet with Sybase.
- Bug @ package com.opensymphony.module.propertyset.database.JDBCPropertySet, method setValues.
- Throw InvalidPropertyTypeException if propertyset tries to persist object with TEXT type (ie string.length > 255).
- Improve classloading of propertysets.
- Default use javac not jikes.
- Unit Tests and Fixes to HibernatePropertySet.
- Make datasource protected in JDBCPropertySet.
- Extensible JDBCPropertySet (refactored).
- Proper Management of PreparedStatement.
- Patch: more descriptive error message.
- Mutable property sets shall allow bulk removal of properties.
- OJB Implementation.
Added: 2009-06-27 License: Other Free / Open Source License - Apache License Price: OtherFreeOpenSourceLicenseApacheLicense
14 downloads
OSCore 2.2.5
This is a set of utility-classes that are common to other components of the OpenSymphony software more>>
OSCore 2.2.5 is a very serviceable set of utility-classes that are common to other components of the OpenSymphony software
Contains essential functionality for any J2EE application. From these basic classes, other applications or programming algorithms can be built upon.
Installation:
There are two different ways to install OSCore: using oscore.jar as a library in your application or deploying oscore.jar as an EJB module to an application server.
Major Features:
- TextUtils useful functions for manipulating Strings. Examples include: extracting primitive types, verifying e-mail addresses, splitting and joining, escaping characters, hyperlinking text, indentation, etc.
- XMLUtils common XML functions such as parsing and printing DOM documents, performing XSL transformations and selecting nodes using XPATH.
- EJBUtils common EJB and JNDI based functions such as looking up and narrowing home interfaces and looking up entity-beans directly.
- BeanUtils useful methods for accessing values of objects using reflection.
- MultipartException a special type of Exception designed to be subclassed for holding many child Exceptions. Useful if validation can throw many Exceptions and they all need to be wrapped up into and report (for example).
- Data an Object wrapper for binary data.
- OrderedMap a java.util.Map implementation that retains the order items were added in.
- DataUtil a small class that helps convert Objects to their primitive types.
- DateUtil a small class for handling ISO 8601 International Date formats.
Enhancements:
- Bug
-
- [CORE-63] - TextUtils.br() does not generate XHTML
- [CORE-65] - URL is not linked if the last URL on the page is "http://"
- [CORE-67] - URLs with quotes are valid, but URLUtils does not show them as valid
- Improvement: [CORE-71] - Allow overriding of the encoding of high bit characters in htmlEncode
Added: 2009-06-27 License: Other Free / Open Source License - Apache License Price: OtherFreeOpenSourceLicenseApacheLicense
16 downloads
Compass 2.2.0
This Java Framework enables the power of Search Engine semantics on different applications more>>
Compass 2.2.0 This Java Framework enables the power of Search Engine semantics on different applications.
The framework was built on top of the Lucene Search Engine and it integrates easily to other ORM development frameworks.
Major Features:
- Simple Compass provides a simple API for working with Lucene. If you know how to use an ORM, then you will feel right at home with Compass with simple operations for save, and delete & query.
- Lucene Building on top of Lucene, Compass simplifies common usage patterns of Lucene such as google-style search, index updates as well as more advanced concepts such as caching and index sharding (sub indexes). Compass also uses built in optimizations for concurrent commits and merges.
- Mapping Compass provides support for mapping of different data "formats" - indexing and storing (caching) them in the Search Engine: Object to Search Engine Mapping (using annotations or xml), JSON to Search Engine Mapping (explicit or dynamic), XML to Search Engine Mapping (using simple xpath expressions), and the low level Resource to Search Engine Mappping.
- Tx Compass provides a transactional API on top of the Search Engine supporting different transaction isolation levels. Externally, Compass provides a local transaction manager as well as integration with external transaction managers such as JTA (Sync and XA), Spring, and ORM ones.
- ORM Compass integrates seamlessly with most popular ORM frameworks allowing automatic mirroring, to the index, of the changes in data performed via the ORM tool. Compass has generic support for JPA as well as embedded support for Hibernate, OpenJPA, TopLink Essentials, and EclipseLink allow to add Compass using three simple steps.
- Spring Compass integrates seamlessly with Spring. Compass can be easily configured using Spring, integrates with Spring transaction management, has support for Spring MVC, and has Spring aspects built in for reflecting operations to the search engine.
- Distributed Compass simplifies the creation of distributed Lucene index by allowing to store the Lucene index in a database, as well as storing the index simply with Data Grid products such as GigaSpaces, Coherence and Terracotta.
Added: 2009-06-27 License: Other Free / Open Source License - Apache License Price: OtherFreeOpenSourceLicenseApacheLicense
15 downloads
Added: 2009-06-26 License: Other Free / Open Source License - Apache License Price: OtherFreeOpenSourceLicenseApacheLicense
13 downloads
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).
Added: 2009-06-27 License: Other Free / Open Source License - Apache License Price: OtherFreeOpenSourceLicenseApacheLicense
12 downloads
Added: 2009-06-27 License: Other Free / Open Source License - Apache License Price: OtherFreeOpenSourceLicenseApacheLicense
13 downloads
XWork 2.1.4
This is a command-pattern framework that is used to power Struts 2 more>>
XWork 2.1.4 offers users a powerful command-pattern framework that is used to power Struts 2. Users can define action classes by using an Action interface, then XWork will setup and run the users actions. XWork provides an Inversion of Control container, a powerful expression language, data type conversion, validation, and pluggable configuration. XWork is most widely known from the web MVC framework called Webwork.
Major Features
- Flexible and customizable configuration based on a simple Configuration interface, allowing you to use XML , programmatic, or even product-integrated configuration
- Core command pattern framework which can be customized and extended through the use of interceptors to fit any request / response environment
- Built in type conversion and action property validation using OGNL
- Powerful validation framework based on runtime attributes and a validation interceptor
Enhancements
- XWork 2.1.2 message Parameters Validator Config bug
- NPE if running in JVM without java.home (Google App Engine)
- xwork-2.1.2.jar contains AspectJ class files, leading to build failures in applications that use other versions of AspectJ
- Throwing Missing Dependency Exception once migrated from xwork-2.1.2 to xwork-2.1.3
- Default Validator Factory throws exception
- Ognl Value Stack.se tValue() writes to System.out on OgnlException before throwing an XWork Exception
- New constructor for UrlSet with custom ClassLoader protocols. (Allows WebLogic deployment)
- Link to xwork v2.1.3 on downloads page
Added: 2009-06-26 License: Other Free / Open Source License - Apache License Price: OtherFreeOpenSourceLicenseApacheLicense
19 downloads
Quartz 1.6.5
This job scheduling system can be integrated with, or used along side virtually any J2EE or J2SE application more>>
Quartz 1.6.5 brings you a useful scheduling system that can be integrated with, or used along side virtually any J2EE or J2SE application
Applications can vary from the largest e-commerce system to the smallest stand-alone application. Quartz can be used to create simple or complex schedules for executing tens, hundreds, or even tens-of- tousands of jobs; jobs whose tasks are defined as standard Java components or EJBs.
The Quartz Scheduler includes many enterprise-class features, such as JTA transactions and clustering.
Major Features
- Job Scheduling:
- At a certain time of day (to the millisecond)
- On certain days of the week
- On certain days of the month
- On certain days of the year
- Not on certain days listed within a registered Calendar (such as business holidays)
- Repeated a specific number of times
- Repeated until a specific time/date
- Repeated indefinitely
- Repeated with a delay interval
- Job Execution:
- Jobs can be any Java class that implements the simple Job interface, leaving infinite possibilities for the work the Jobs can perform.
- Job class instances can be instantiated by Quartz, or by the applications framework.
- When a Trigger occurs, the scheduler notifies zero or more Java objects implementing the JobListener and TriggerListener interfaces (listeners can be simple Java objects, or EJBs, or JMS publishers, etc.). These listeners are also notified after the Job has executed.
- As Jobs are completed, they return a JobCompletionCode which informs the scheduler of success or failure. The JobCompletionCode can also instruct the scheduler of any actions it should take based on the success/fail code such as immediate re-execution of the Job.
- Job Persistence:
- The design of Quartz includes a JobStore interface that can be implemented to provide various mechanisms for the storage of jobs.
- With the use of the included JDBCJobStore, all Jobs and Triggers configured as "non-volatile" are stored in a relational database via JDBC.
- With the use of the included RAMJobStore, all Jobs and Triggers are stored in RAM and therefore do not persist between program executions but this has the advantage of not requiring an external database.
- Transactions:
- Quartz can participate in JTA transactions, via the use of JobStoreCMT (a subclas of JDBCJobStore).
- Quartz can manage JTA transactions (begin and commit them) around the execution of a Job, so that the work the Job does happens within a JTA transaction.
- Clustering:
- Fail-over.
- Load balancing.
- Listeners & Plug-Ins:
- Applications can catch scheduling events to monitor or control job/trigger behavior by implementing one or more listener interfaces.
- The Plug-In mechanism can be used add functionality to Quartz, such keeping a history of job executions, or loading job and trigger definitions from a file.
- Quartz ships with a number of "factory built" plug-ins and listeners.
- Runtime Environments:
- Quartz can run embedded within another free standing application
- Quartz can be instantiated within an application server (or servlet container), and participate in XA transactions
- Quartz can run as a stand-alone program (within its own Java Virtual Machine), to be used via RMI
- Quartz can be instantiated as a cluster of stand-alone programs (with load-balance and fail-over capabilities)
Enhancements
- Records in QRTZ_TRIGGER_LISTENERS table are deleted when trigger is paused and resumed
- Logging Trigger History Plugin.trigger Misfired writes incorrect message
- Send Destination Message Job throws naming exception
- Send Queue Message Job throws Class Cast Exception when used with xml plugin acquire Next Trigger executing on Managed Tx Connection when using JobStoreCMT and configured not to acquire triggers within lock
Added: 2009-06-26 License: Other Free / Open Source License - Apache 2.0 License Price: OtherFreeOpenSourceLicenseApache2.0License
21 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above opensymphony search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
