Explore topic-wise InterviewSolutions in .

STRINGBUILDER is unsynchronized WHEREAS STRINGBUFFER is synchronized. So when the application needs to be RUN only in a single thread then it is better to USE StringBuilder. StringBuilder is more efficient than StringBuffer.

StringBuilder is unsynchronized whereas StringBuffer is synchronized. So when the application needs to be run only in a single thread then it is better to use StringBuilder. StringBuilder is more efficient than StringBuffer.

The jBPM GPD is an eclipse PLUGIN that targets usage by MULTIPLE roles. Both the business analyst and developer are able to use the same TOOL in different ways. The main reason why we think it is important to integrate those two in one single environment is because in MANY teams, these two roles are done by one person. Then it becomes very important that the tool can support both roles and gradually shift from being a diagramming tool to an implementation tool.

The jBPM GPD is an eclipse plugin that targets usage by multiple roles. Both the business analyst and developer are able to use the same tool in different ways. The main reason why we think it is important to integrate those two in one single environment is because in many teams, these two roles are done by one person. Then it becomes very important that the tool can support both roles and gradually shift from being a diagramming tool to an implementation tool.

Basically starting JBoss with the ’all’ configuration contains EVERYTHING needed for clustering:

It has all the LIBRARIES for clustering:

• JGroups.jar, jboss-cache.jar
• Clustered BEANS (cluster-service.xml)
• HA-JNDI
• HTTP session replications (tc5-cluster-service.xml)
• Farming

Basically starting JBoss with the ’all’ configuration contains everything needed for clustering:

It has all the libraries for clustering:

A rule engine MAY be viewed as a sophisticated if/then statement interpreter. The if/then statements that are INTERPRETED are CALLED rules.

A rule engine may be viewed as a sophisticated if/then statement interpreter. The if/then statements that are interpreted are called rules.

The jBPM GPD is an eclipse plugin that targets usage by multiple roles. Both the business ANALYST and developer are able to use the same TOOL in different ways. The main reason why we think it is important to integrate those TWO in one single environment is because in many teams, these two roles are done by one person. Then it BECOMES very important that the tool can support both roles and gradually shift from being a diagramming tool to an implementation tool.

The jBPM GPD is an eclipse plugin that targets usage by multiple roles. Both the business analyst and developer are able to use the same tool in different ways. The main reason why we think it is important to integrate those two in one single environment is because in many teams, these two roles are done by one person. Then it becomes very important that the tool can support both roles and gradually shift from being a diagramming tool to an implementation tool.

jBPM5 provides a DIFFERENT computational model for business process and rule. This model is based on a KNOWLEDGE-oriented approach, where the application is not process-oriented or rules-oriented, but the end users can simply select between different paradigms to represent their business logic. All tools and INTERFACES the user is confronted with SUPPORT this idea of a unified environment throughout the entire knowledge life cycle.

jBPM5 provides a different computational model for business process and rule. This model is based on a knowledge-oriented approach, where the application is not process-oriented or rules-oriented, but the end users can simply select between different paradigms to represent their business logic. All tools and interfaces the user is confronted with support this idea of a unified environment throughout the entire knowledge life cycle.

• Visual user friendly editor: Users can choose between a WEB BASED editor (Oryx) or an Eclipse based one. You can choose depending on the end user and if you are going to use the project’s BRMS (Guvnor) where you can store all your business assets such as processes, rules and documentation in a central location.
• BPMN2 standard support: This allows you to choose a different editor to generate your business processes and run them in JBPM5. There’s no 100% support for the standard yet, but progress is being made on this matter.
• Human Task features: JBPM5 has a native notion of a Human task, an activity that needs to be completed by an actual person and has a lifecycle: it can be started, suspended, completed, etc. It is also a standard spec.
• Process Console: You can interact with the engine through this console where you can start processes, complete human tasks, fill forms, etc. This console is GWT based.
• JPA persistence method: it enables you to choose any database and persistence schema to store the processes variables and history log.
• Designed for domain specific workflows: this means that you can create your own business domain specific tasks such as (Receive Claim, Approve loan , Check Blood Pressure, etc) and build a palette for end users that is very natural to their environment. This is combination with a visual modeler is a pretty explosive combination, allowing a very productive as-is process knowledge gathering and to-be process DESIGN across a whole line of business.
• Business Activity Monitoring built in: what’s a BPM’s worth if you can’t monitor your processes? JBPM5 allows you to make reports (including tables and charts) over the process instance data and history log. This is useful for higher level users that as C-level executive who need process information to make decisions. It also enables you to use BIRT to generate your reports, so your imagination is the limit when it comes to the amount of information you can present.
• Console Custom forms integration: By using a template framework, JBPM5 allows your users to interact with their processes using the same console to start the process and make actions to it within a custom form for each activity. For example you can have a client’s data gathering activity in your process and a custom form can be built to fill that information into the workflow.
• Powerful rules language: To make decisions within the process you can use Drools rule syntax to for example change a path according to a business condition, such as a credit score.