ejb
Is Ejb really significant in enterprise applications?
Ejb was introduced to Java technology to attain some features inherent in enterprise applications. Those features include instance pooling, inbuilt security, declarative transactions, container manage more>> Ejb was introduced to Java technology to attain some features inherent in enterprise applications. Those features include instance pooling, inbuilt security, declarative transactions, container managed persistence, relationship of business objects and caching etc. Now that many people have built their applications using Ejb, let us go back and analyze if Ejb as a technology is really significant in developing enterprise applications. We are going to analyze both pros and cons of Ejb based on experience of people who have used Ejb.<<less
OSCore 2.2.5
This is a set of utility-classes that are common to other components of the OpenSymphony software more>>
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
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.
Java Tutorials, Java Ebooks, Articles and Java FAQ
Geekarticles database of technology with over 1200 in Java Technology which includes Java Applets Ebooks, Java Ebooks, EJB Ebooks, EJB Tutorials, J2EE Ebooks, J2EE Tutorials, J2ME Ebooks, J2ME Tutoria more>> Geekarticles database of technology with over 1200 in Java Technology which includes Java Applets Ebooks, Java Ebooks, EJB Ebooks, EJB Tutorials, J2EE Ebooks, J2EE Tutorials, J2ME Ebooks, J2ME Tutorials, J2SE Tutorials, Java Swing Articles, Java Web Services, JDBC Help, Jini Tutorials, JMS Tutorials, JSP Ebooks and Tutorials, Servlets Articles and Java FAQS.<<less
Java Interview Questions
Java Interview Questions: Get the Interview Questions and Frequently Asked Questions in Java related Technologies. Over 1000 Questions and Answers in J2EE subjects like Java Interview Questions, JDBC Interview Questions, EJB Interview Questions, Struts more>> Java Interview Questions: Get the Interview Questions and Frequently Asked Questions in Java related Technologies. Over 1000 Questions and Answers in J2EE subjects like Java Interview Questions, JDBC Interview Questions, EJB Interview Questions, Struts Interview Questions, JMS Interview Questions, JSP Interview Questions, Servlets Interview Questions, Core Java Interview Questions and OOPS Interview Questions. Discuss each Question in detail and prepare for your Interview.<<less
PHP Spring and Beans v 0.1
The same EJB, java beans, hibernate and spring java structure in PHP code. If you like to program in Java EJB download this tool. With this tool you can create beans and sql maps on a MVC structure. This tool already brings a cache service that runs more>> The same EJB, java beans, hibernate and spring java structure in PHP code. If you like to program in Java EJB download this tool. With this tool you can create beans and sql maps on a MVC structure. This tool already brings a cache service that runs on the background. 3 different layers: Model layer, Business rules layer and Presentation layer.<<less
NataLi
NataLi is an information system that has been developed as an University thesis. The aim of this project is to present how an information system can be written, and help other people who are intereste more>> NataLi is an information system that has been developed as an University thesis. The aim of this project is to present how an information system can be written, and help other people who are interested in J2EE development to understand this kind of technology and pass more easily through steps which are now simple but were quite painful to understand and utilize from the start. Its written in J2EE, JSP, Struts, Hibernate, and Enterprise JavaBeans(EJB), using JAAS security manager, and allows you to maintain books, magazine records, categories of readers, their addresses and reservations, borrowings, privileges, printing of reminders, and other library related items through a user-friendly Web interface.<<less
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).
- Page: 1 of 1
- 1