The versatile EIP framework is implemented in routing and transformation processes for faster and more efficient integration solutions.

A high performance messaging broker supports messaging patterns such as publish-subscribe, point-to-point, and store-forward, and multiple cross language clients.

The web services framework exposes integration assets as services and calls external services, supporting all major web services standards. It also supports RESTful calls.

A lightweight service development framework provides full life-cycle support for developing, deploying, and managing service-based applications.

Manage the life-cycle of services from design, development, and deployment by defining, exposing, and enforcing rules or policies.

Capture service activity information, define and collect metrics, and define alerts and SLAs.

SwitchYard leverages the power of Java EE6 and CDI to allow Java objects become services by adding an @Service annotation to your bean. Beans are automatically registered at runtime and references to other services can be injected as CDI beans using the @Inject annotation. Use CDI in your JSP and JSF applications to inject enterprise services into the web tier.

With declarative transformation in SwitchYard, you can define the transformation and types to which it applies. SwitchYard automatically registers and executes the transformation. Choose from Smooks, Java, XSLT, JSON, and more.

Encapsulate business rules as decision services using the JBoss Rules component in SwitchYard. Each service has a well-defined contract with protocol binding details and marshaling details abstracted away by SwitchYard.

This transformation engine can be used in conjunction with Red Hat JBoss Fuse Service Works to process messages.

You can use web services to orchestrate business rules using this language. It is included with Red Hat JBoss Fuse Service Works for the execution of business process instructions.

This is the rules engine that is packaged with Red Hat JBoss Fuse Service Works. It can infer data from the messages it receives to determine which actions need to be performed.

Comprehensive unit test support is provided to allow you to test services as you develop them.

SwitchYard is a lightweight service delivery framework providing full life-cycle support for developing, deploying, and managing service-oriented applications.

You can use web services to orchestrate business rules using this language. It is included with Red Hat JBoss Fuse Service Works for the execution of business process instructions.

This transformation engine can be used in conjunction with Red Hat JBoss Fuse Service Works to process messages. It can also be used to split messages and send them to the correct destination.

This is the rules engine that is packaged with Red Hat JBoss Fuse Service Works. It can infer data from the messages it receives to determine which actions need to be performed.

Red Hat JBoss Fuse Service Works utilises BPEL and BPMN 2 for graphical business process definition. Contract-based service invocation allows you to keep your business processes free of implementation and binding details.

The product allows you to abandon procedural approaches to the problem of data transformation in integration and JBoss Fuse Service projects. With declarative transformation, you define the transformation and the types to which it applies: transformations are automatically registered and executed using such Smooks, Java, XSLT, JSON, and more.

You can encapsulate business rules as decision services using JBoss Rules . Each rule service has a well defined contract with protocol binding details and marshalling details abstracted as part of the service delivery framework

You can define service pipelines using the flexible, EIP-based routing engine from the Apache Camel integration framework. You can use Camel directly or take advantage of the wide variety of Camel components as gateway bindings for an abstract service.

Red Hat JBoss Fuse Service Works provides a set of Red Hat JBoss Developer Studio-based tools and other plug-ins to aid in the rapid development of Maven-based applications. Create and configure your application using visual tools or the included sample code.

The product also provides comprehensive unit test support to allow you to test services as you develop them, rather than waiting until the end of the development cycle.

The Kermit password found in the policy-security-* quick starts does not comply with the password policy. As a result, users can be misled about password policies and security best practice. To work around this issue, change the Kermit password to make it conform with JBoss password policies in the following demos: policy-security-basic policy-security-wss-username

In Red Hat JBoss Fuse Service Works 6.0, when you deploy any service with self reference implementation property set, the application throws the StackOverflow error message.

In Quickstarts camel-jms-binding and demos/policy-transaction, the manifest entry in the pom.xml file fails to generate comma separated dependencies as expected. Only the last

 <Dependencies>

element text node sets the dependency value.

The domain configuration does not support any component that is deployed as a WAR or EAR application. There are not yet any sample configurations for these deployments or any sets of CLI scripts that could be used to set up domains in machines.

When you import SwitchYard quickstarts into Red Hat JBoss Developer Studio, warning messages appear. These may cause confusion for new users. They are caused by a reference to a non-existent .dtd file. To work around this problem, open the quickstarts' log4j.xml file and replace

 <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

with

 <log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'>

When you run SwitchYard quickstarts, you will encounter a series of http-binding JBoss Developer Studio warning messages. To work around this, modify the switchyard.xml file so that items are listed in this order:

contextMapper
messageComsoser
contextPath

You will see warning messages in JBoss Developer Studio's "Problems" view after you import a validate-xml quick start as a Maven project.

The camel-quartz-binding quartz:name cannot contain underscores at the moment. If it does, an exception is thrown: org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:85). This is because the name is used as a URI. To work around this issue, avoid underscores in the quartz:name field.

If you activate a Camel component, it sets the component properties. If there is more than one Camel implementation, the component properties set for each Camel component effectively overrides the previous setting.

If you try to execute the policy-security-wss-signencrypt quickstart, you will encounter ClassCastException. This is due to a bug in Red Hat JBoss Enterprise Application Platform's PicketLink module. This modules causes a conflict between classes provided by the Java Development Kit and others provided through the xmlsec module. To workaround this issue, edit the PicketLink modules/system/layers/base/org/picketlink/main/module.xml file and switch the sequence of xmlsec and javax.api dependencies so that the javax.api comes first.

        <module name="javax.api"/>
        <module name="org.apache.santuario.xmlsec"/>

When you run the application using Maven, the SwitchYard runtime displays the error messages due to the incorrect version of switchYard plugin located under the maven-metadata.xml file.

The BPEL integration tooling allows you to configure a transformer between WSDL and the Java interface as a JAXB transformer. This results in an error. This happens because JAXB transformations are only valid for data objects that contain JAXB annotations or include an ObjectFactory in a configured context path. A string does not qualify, so using JAXB in this context is invalid. More constraints need to be added to the tooling to ensure that only valid data is input.

When SOA is launched, links to the consoles are not displayed. This results in users being unable to access consoles directly from the welcome page. To work around this, enter the links manually into your browser.

If the user quits the installer during the post-installation step, and then tries to re-run the installer an error message appears stating that "product.conf file is either malformed or does not exist." This is because EAP becomes malformed, so you cannot use the same EAP directory for the reinstallation. Or If you force exit the install during the post installations steps while installing Red Hat JBoss Fuse Service Works on an previously installed EAP, you may end up with a broken EAP installation. Work around is to install into a different location or clean up your installation and start over.

There is a performance impact if you use the same stateful knowledge session across multiple process instances. This is because the one-session-for-all-processInstances model is inherently single threaded. When the transaction is started, it will pessimistically lock the SessionInfo table, blocking other threads. To avoid this, create mapping so that a session is only ever used for one process instance and use a unique JPA entity manager.

If you launch the S-RAMP command line interface via s-ramp.sh, you will see a JarClassLoader warning. This is because both commons-beanutils and commons-collections are included in the JAR file for the command line interface and the commons-beanutils library includes the FastHashMap class causing a classname conflict. This warning has no impact on product operation for users and can be ignored.

If you hover over chart points in the Security Response Time gadget, information pops up. Unfortunately, if these points overlap, the hover function does not work and details do not pop up.

The SRT Gadget forgets its data filtering setting. A user can click on the Min, Max or Average captions and only the requested metric will be shown. Unfortunately, if they then refresh the gadget, this setting is forgotten and all three metrics are displayed again.

The product lacks a working sample cluster configuration file for RTGov. As a result, users do not have an example to study or use.

The "show-metrics" operation allows the caller to retrieve the metrics for promoted services and references but does not allow one to retrieve the metrics for the component services or component references. This is because it does not collecting metrics for component services that are not promoted and, additionally, if a component service is promoted more than once, the metrics may not be accurate for the composite services promoting it.

HttpMixin will throw an IllegalArgumentException if used with a rest service that returns void. This is because the httpResponse.getEntity() is null, which causes a problem in the EntityUtils.toString() method.

The JON plug-in's out-of-bound metrics portlet shows the time instead of out-of-bound values. As a result, users cannot see the correct information.

If you stop a service from either the JON UI or the Admin console and then check the service state, you will see that it is reported as being NONE. This is due to SwitchYard reporting back the incorrect value.

The DTGov sample workflow project is located in a data directory. It needs to be moved to a quick starts directory to provide consistency for users.

The installation process should only make relevant quick starts available. At the moment, users can choose both RTGov client and RTGov server in the same installation. It should not be possible to do this and, furthermore, only those quick starts relevant to the option selected should be made installed.

The camel-service quick start runs correctly but does not produce any output. This is inconsistent with what is stated in the quick start's ReadMe file and may confuse users.

The http-binding and rest-binding quick starts do not deploy. If users try to run them, they will encounter an java.net.BindException. To work around this issue, use the following command: mvn -DskipTests jboss-as:deploy

If you start the server with the -c standalone-full-ha.xml options, the start-up process hangs. This is because the CONSOLE logging handler has been omitted from the standalone-full-ha.xml configuration. To work around this, avoid using this start-up configuration.

If the user issues a GET request against an end-point, they will encounter an exception. This is due to a JBossWS/CXF fault.

The standalone database configuration tool is not currently available. This means that users do not have a simple means of configuring databases post-installation.

Users cannot set dates in OnAlarm (Pick) and Wait in the BPEL Editor. This affects both the Date and Duration radio button options.

The wording of the switchyard/demos/orders Readme.md file was inconsistent with those of the other quick starts. To see amended instructions, please refer to the bug ticket.

If you try to deploy the camel-example-cxf-tomcat quick start, you will encounter a warning with an exception. The example application will work, so impact on the user is minimal.

The policy-security-wss-signencrypt will not run if the RTGov client and server are both installed. It will work if you install Red Hat JBoss Fuse Service Works with the RTGov client only or install it with both the RTGov client and server, then undeploy all of the WAR files in the deployments/overlord-rtgov directory.

The async policy is only applicable to the RTGov server profile. At the moment, however, the installer includes all quick starts, not just those that are relevant to the profile the user is trying to install. If a user tries to run the order-app quick start in the rtgov-client only environment with the async policy deployed on the RTGov server, then it ignores the policy.

If you create a component, service or reference in the SwitchYrad editor you will see details of it the Properties view. After saving, though, this view is cleared. This is due to a refresh error. It tries to refresh to show properties for the text, for which there is none.

Unproductized JAR files are present in the Governance deployments. All JARs should be productized to ensure they are fully tested and stable for users.

If you try to deploy the camel-example-cxf-tomcat quick start, an exception is raised. As a result, users cannot run this quick start.

Under the BPEL Console's Execution History tab, if you select any of the previous execution, the application throws an exception message.

There is no way to set the Expiration Time on a task instance at creation time from a BPMN2 process. This functionality should be made available in Red Hat JBoss Business Process Manager 6.1. As a result of this, users cannot currently fill in a DTGov user task's 'Due Date' field (found under Task Details). The Task Form does not allow you to change this field.

An "Installation has Failed" message appears after the Installer's "Processing" screen has run on MacOS X. This is caused by Tomcat-based applications encontering java.net.SocketExceptions on Mac OS.

The 'remote invoker' quick start should be renamed to 'hello world'. At the moment, it is not obvious to users which is the most basic quick start with which to begin exploring functionality. Changing the name would make this clearer to new users.

When the user first loads the RT Governance console, it is blank. There is a risk that users might not see the "+" button because it is small. This presents a usability problem.

The ReadMe file for demos/multiApp is missing detailed instructions on usage. As a result, users maybe unsure of how to use this demonstration code. To workaround this, please see the detailed instructions attached to this bug ticket.

In some cases, the MVEL expression in a BPM process extracts the 'fault' process variable contents and returns null instead of the value of the fault variable.

Design-Time Governance and Run-Time Governance generate incorrect column type for uuids in the database tables. It generates varchar instead of uniqueidentifier data type. This causes extra space usage by the varchar type, however has no functional impact.

The SwitchYard sub-deployments included in an EAR file are not currently deployed in order. This is because the EAR configuration's initialize-in-order flag is not currently utilized.

If you attempt to add a new a new artifact reference with the SwitchYard Editor, an artifact element is added to the switchyard.xml file without formatting it. It will also still be on the same line as artifacts created previously. To work around this, users will have to format it manually.

If you run the functional test for one of JCA quickstarts or transaction-policy, you will encounter an ArchiveExportException. This is caused by the version of ShrinkWrap supplied with the Red Hat JBoss Enterprise Application Platform. To work around this issue, add the following code to the quick start's POM file:

 
<dependency>
            <groupId>org.jboss.shrinkwrap</groupId>
            <artifactId>shrinkwrap-api</artifactId>
            <scope>test</scope>
            <version>1.2.0</version>
        </dependency>
        <dependency>
            <groupId>org.jboss.shrinkwrap</groupId>
            <artifactId>shrinkwrap-impl-base</artifactId>
            <scope>test</scope>
            <version>1.2.0</version>
        </dependency>
        <dependency>
            <groupId>org.jboss.shrinkwrap</groupId>
            <artifactId>shrinkwrap-spi</artifactId>
            <scope>test</scope>
            <version>1.2.0</version>
        </dependency>

On Red Hat Enterprise Linux machines, if you attempt to open the SwitchYard Editor's Printing dialog box, attempt to change printers and then cancel, the following dialog appears: "Unhandled event loop exception No more handles". It is followed by a prompt requesting you to exit the workspace. To work around this issue, avoid trying to cancel after attempting to change printers.

If you open a .drl rule file and try to switch to the Rete review, you will encounter an error. As a result, users cannot see the Rete tree view.

The domain functionality is currently unavailable to users.

If you add a THREADED_FILE or FILE Logger to a rule service, an "ava.lang.ClassNotFoundException: org.xmlpull.v1.XmlPullParserException" is recorded in the log file when you attempt to process your rules. There is a detailed workaround available on the bug ticket.

Red Hat does not support changing the name of the local cache. If you attempt to do so, you will find that no artifacts will be displayed in the S-RAMP UI Repository Browser.

If the user has also purchased a Red Hat JBoss Data Grid subscription, Modeshape should be able to use this cache remotely. However, the remote cache does not support transactions that are required by S-RAMP. Users will encounter an S-RAMP exception.

The RTGov sample "samples-jbossas-sla-report" throws errors about a missing persistence.xml file. Due to this, RTGov quickstarts can not be built OOTB in JBoss Developer Studio. To workaround this problem, change the error message to a warning in Preferences/Java Persistence/JPA/Errors/Warnings.

Multi-module applications are not handled correctly by the deployment workflow of DTGov. Although the example s-ramp-demos-switchyard-multiapp quickstart application provided can be deployed in the DTGov dashboard, demonstrating the S-RAMP grouping feature, the workflow fails to successfully deploy the multi-module application to the JBoss EAP instance.

The period attribute is mandatory for SQL service bindings but the wizard does not validate whether or not it has been set. If you do not set it, you will encounter this exception: "Period attribute is mandatory for SQL service bindings".

The "Fuse Tooling Routes Editor" is present in the "Open With" list for switchyard.xml files. The Routes Editor should be constrained to applicable files. If you attempt to click it, an empty canvas is opened. To work around this issue, avoid clicking on this option.

The RTGov Call Time widget does not work with Apple's Safari 6.1 web browser. If you enter a value into the selector, a result of 'null' will be displayed in the widget.

If you try to import the ear-deployment quick start into Red Hat JBoss Developer Studio, you will encounter errors. This is because the SwitchYard Validator cannot handle projects with a number of sub-projects. To work around this issue, So import each sub-project (artifacts, order-consumer, order-service and ear-deployment) individually, before importing the parent POM file.

The soap-addressing quick start cannot be imported into Red Hat JBoss Developer Studio. If you try to do so, you will encounter errors.

If you attempt to layer installations, the later installations may fail as pre-existing configurations are not detected. Layering with default options results in no issues. The problem arises when the user chooses to add additional configuration options in the earlier layers. For instance, if a user sets a custom password vault in Red Hat JBoss Fuse Service Works and then tries installs Red Hat JBoss Data Virtualization and attempts to create a password vault for it as well, this will result in a failed installation for the latter, since the vault already exists.

Due to a problem with the secure-request.xml file, users will see errors after trying to import the policy-security-wss-signencrypt quick start into JBoss Developer Studio. This is a test message and does not impact on users.

The security-domain.xml file does not contain valid XML. As a result, if users try to import the policy-security-saml quick start in the Red Hat JBoss Developer Studio, it will fail with errors.

The SwitchYard Editor's binding tab input area is not resized properly in the Properties view after you click on the Source tab in Editor view. As a result, users cannot fill in all of the fields as they are not visible onscreen.

org.apache.camel.Exchange is missing from Milyn. This causes errors when Smooks is used. To work around this, add the following dependency to JBOSS_HOME/modules/system/layers/soa/org/milyn/main/module.xml:

<module name="org.apache.camel.core" />

The Milyn type converters are not correctly registered in Smooks. As a reult of this, the transformer does not work. To work around this issue, in milyn-smooks-all-1.5.1.jar's JBOSS_HOME/modules/system/layers/soa/org/milyn/main change /META-INF/services/org/apache/camel/TypeConverter and replace org.milyn.smooks.camel.converters with org.milyn.smooks.camel.converters.EDITypeConverter, org.milyn.smooks.camel.converters.ResultConverter, and org.milyn.smooks.camel.converters.SourceConverter.

The "Honour all schema locations" setting is not disabled when the user creates a new project in the SwitchYard Editor. This occurs if the project was created using a version that cannot be resolved from any configured Maven repositories. If the version specified in the wizard can be located, the preference is disabled appropriately. The user will encounter XML errors. To work around this fix the version and update the project, as this will install the SwitchYard facet, which will disable the XML validation setting.

The TransactionMixIn class does not configure the JTAEnvironmentBean used by the TransactionSynchronizationRegistry. Instead, it registers in JNDI. As soon as you use TransactionSynchronizationRegistry directly or indirectly an exception is thrown. As a workaround, you will find a proposed patch attached to the bug ticket.

The BPEL console may fail to load if you are using Internet Explorer 10 due to the version of GWT supplied. The failure is caused by a check to determine whether Adobe Flash is present or not. To workaround this issue please upgrade to Internet Explorer 11 or install Flash. If that fails, see the bug ticket for an alternative possible workaround.

If you go into the Gadget Console in Microsoft Internet Explorer 10 both vertical and horizontal scrollbars are present even when not necessary. They allow the user to scroll the gadget behind the displayed graph.

If you do not add a JNDI name to reference bindings when using the SwitchYard editor, then you will encounter an following exception when it is compiling. This error is due to lack of validation that should require a user to add a JNDI name. At the moment it is only required for connection factory reference bindings. To work around this issue, ensure you always add a JNDI name to reference bindings.

If you attempt to edit a component service with an ESB interface by using the SwitchYard editor, it removes the service name. To workaround this issue, avoid editing services with ESB interfaces with the editor.

The HTTP Authorization header is not honored by the RESTEasy gateway component. This means users cannot use this authentication at present.

The "org.switchyard.component.common.knowledge.util.Listeners" class refers to a deprecated API "WorkingMemoryEventListener".

The Governance WAR files are not distributable by default. To work around this, users must add the

 <distributable/> 

tag to all Design Time Governance web applications.

The installer does not configure the S-RAMP repository for clustering environment in the *-ha.xml profile setting files. Because of this, the Infinispan cache container contains a local cached instead of a replicated cache. The Modeshape repository used by S-RAMP is not configured to be clustered either. The installer should configure the *-ha.xml profiles for clustering and one shared S-RAMP repository. This is due to a problem with the S-RAMP configuration.

The text accompanying the lines between methods in the Service Overview Gadget is potentially confusing for customers. The text line represents the service and operation being invoked but it could be misinterpreted to imply the link is going from the service to the method. A better way of representing this needs to be found so that users are not confused.

If you add the switchyard-component-bpel dependency to a service, the SwitchYardTestKit throws a null-pointer exception. To work around this, you need to add bpel.properties.

If you try to deploy a BPEL process to a SwitchYard project, it will always return NULL instead of the expected SOAP message.

The Rt Governance Gadget Web displays two vertical scrollbars when more than one call trace is displayed, irrespective of the web browser used. This is because the outside scrollbar is displayed even if the Gadget displays just one calltrace.

There is a race condition in the Red Hat JBoss Enterprise Application Platform's launch code whereby the LogManager can be initialised to the java.util.logging.LogManager rather than the org.jboss.logmanager.LogManager. On the rare occasions that this happens, the Red Hat JBoss Fuse Service Works server will fail to launch and will require you to try again.

If two bean services try to implement the same interface via the SwitchYard Editor, errors will occur.This is possibly due to the explicit definition of the service name in the @Service annotation. Users will see errors are written to the log.

The NMTOKEN type in XSD prevents the use of properties in the switchyard.xml file, because NMTOKEN does not allow you to use certain character symbols that are needed for properties. If you do try to use them, you will encounter an error during compilation.

Up to twenty percent of the messages in the error log are warnings, stemming from multiple parts of the product. As a result, the log is very cluttered and of limited use to users.

BPAF is misconfigured to call for a library it does not use (jboss.naming.context.java.jboss.BPELEMFactory). A s a result of this, users will see errors in the log.

The user interface uses the label "Design Time" in several places. This term is not particularly meaningful for those not already familiar with service oriented architecture concepts. A more descriptive label is needed to help new users understand the functionality on offer.

Maven plugin creates empty switchyard.xml when using resources filtering. As a result, Maven resource filtering does not work as expected. A workaround for this is generating the filtered resource to another directory and including that in the Mojo configuration.

If the user attempts to import the rules-interview-container quick start and removes local DRL resources, they cannot load rules from the Maven repository. The users will instead encounter a NoClassDefFoundError.

When you upgrade the configuration version from 1.0 to 1.1, the switchyard.xml file created after you build the project contains only generated transformers or validators.

You cannot set a resource adapter archive for a generic resource adapter in the JCA binding. If you try to do so, it will not be written to the switchyard.xml file. You will also encounter errors when you try to specify it.

RT Governance's SO gadge does not zoom out properly when non-wired services are invoked. When non-zoomed, it contains only a detail of one service, hiding the second one completely. The SO gadget canvas should be zoomed-out for non-wired services as is the case with wired services.

If you use JAX-RS annotations on the interface implemented by your bean service, you may encounter an error. It is a good idea not to use binding annotations directly on service interfaces as it clutters the abstract service contract with binding-specific details. Separate JAX-RS annotations into a distinct interface to avoid confusing CDI/Weld.

For projects using a BPEL service, switchyard-plugin adds an invalid namespace definition "xmlns:xmlns namespace". To workaround this problem, assign the default namespace explicitly in your project using BPEL.

You cannot import the RTGov quick start policy into Red Hat JBoss Developer Studio. If you try to do so, you will encounter errors.

If you attempt to run an Idempotent JPA consumer, ClassNotFoundExceptions will be raised for the Spring and Hibernate components. To work around this problem, you must make two changes, the first being to a Camel module within the server and the second to your application: Edit the JBOSS_HOME/modules/system/layers/soa/org/apache/camel/jpa/main/module.xml file to include the following module dependencies:

        <module name="org.hibernate"/>
        <module name="org.javassist"/>

Secondly, modify your application so that it contains a APP/src/main/resources/META-INF/jboss-deployment-structure.xml file, (specifying a dependency on the Spring framework).

<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">  
    <deployment>  
        <dependencies>  
            <module name="org.springframework"/>  
        </dependencies>  
    </deployment>
</jboss-deployment-structure>

Secured service with http binding does not require authentication header. This causes basic security failure as the service can be requested without security.

If you use the ReferenceInvoker class to reference a component, an error message appears ("Reference Interface Mismatch"). To work around this issue, use the service interface to reference components instead.

You cannot import the soap-attachment quick start into Red Hat JBoss Developer Studio. If you try to do so, you will encounter errors.

You cannot import the soap-binding-rpc quick start into Red Hat JBoss Developer Studio. If you try to do so, you will encounter errors. To work around this issue, swap the following lines in the switchyard.xml file from this:

 <soap:contextPath>soap-attachment</soap:contextPath>
        <soap:socketAddr>:${jettyPort}</soap:socketAddr>

to this:

        <soap:socketAddr>:${jettyPort}</soap:socketAddr>
        <soap:contextPath>soap-attachment</soap:contextPath>

You cannot import the soap-mtom quick start into Red Hat JBoss Developer Studio. If you try to do so, you will encounter errors.

You cannot import the dtgov-demos-switchyard into Red Hat JBoss Developer Studio due to an unresolved reference. You will encounter error messages.

The BPEL Console will not load in Microsoft Internet Explorer versions 8, 9 and 10. This is due to an issue with GWT and the version of Adobe Flash supplied. Try upgrading to the latest versions of Microsoft Internet Explorer and Adobe Flash to work around this issue.

Note that the ReadMe file for the quick starts refers to a "Helpdesk" quick start. This quick start does not actually come with the product.

The Camel Splitter does not close the Closable Iterator if a RuntimeException occurs during its iteration. Thus the splitter does not close cleanly.

The org.apache.camel.component.sql.SQLProducer class is not able to differentiate an SQL select statement from a procedure call, and then it always creates a PreparedStatement instead of CallableStatement. If you are using DB2, this results in an org.switchyard.SwitchYardException.

If you try to build the bpm-service quickstart, you will encounter an java.lang.ExceptionInInitializerError. To work around this, add the Red Hat JBoss Fuse Service Works Maven repository as a profile in your settings.xml file. This profile must contain the following setting:

<activeByDefault>true</activeByDefault>

For more information about this issue, please refer to the section entitled "About the Maven Setting File" in the Red Hat JBoss BRMS 6 Development Guide.

An error occurs when users attempt to deploy the quickstart camel-ftp-binding quick start. Users will see error messages written to the log file.

THe browser icons are inconsistent, which may confuse users. Every web console is represented by a Red Hat JBoss Enterprise Application Platform 6 icon except s-ramp-ui which has its own Overlord icon.

If you are viewing the Gadget Web interface with Google's Chrome browser, the whole browser tab will freeze if you leave your mouse pointer hovering over one of the graph components in the expanded version when the graph representation widget tries to refresh. To work around this issue, use an alternative web browser.

If you view the Gadget Web in Google's Chrome browser, the values in the expanded version of the graph representation widget do not render correctly. To work around this, use another web browser.

Possibly due to a timing error, users may occassionally see this error during server installation and start-up: exception: java.util.MissingResourceException: Can't find bundle for base name org.jboss.errai.bus.ErraiService, locale en_US This does not have a functional impact on users.

If the user shuts down the system whilst logged into the BPEL Console, multiple warnings and errors are written to the log. This has no functional impact but, to avoid, log out of the BPEL Console before shutting down the server.

When a user accesses the BPEL Console via http://localhost:8080/bpel-console the SSO screen shared with the Governance feature is presented. This forces users to go through the log-in, which should not be the case.

Users cannot change the route implementation in the SwitchYard Editor's Properties view. This is true for both the Route Builder Class and the XML Route file. To work around this issue, change them through the Properties dialog instead.

Setting the Java Security Manager to run with a totally permissive policy and -Djava.security.debug=access:failure results in successful accesses being logged as ERRORs. As well as providing misleading information, this can impact on users by generating very large error logs.

The behaviour of the links in the SwitchYard Editor is inconsistent. Clicking on most of them will result in a new file or class opening but the Route XML file is an exception. If you click on it, a dialog that allows you to create a new route file appears. The behaviour is inconsistent for users.

Calling a remote Red Hat JBoss Business Process Management System instance requires use of "kie-services-client" in "org.kie.remote". This module is not provided with the product, If users try to call the remote server, a "class not found" exception is recorded in the log.

Some dependencies are missing from the Maven repository. As a result, not all needed files may be available to users, breaking projects.

The Maven repository POM file contains incorrect references to repositories. This should not impact on users but the file should only contain valid tags.

The org.drools:drools-bom:6.0.0-redhat-7 contains a hardcoded version of org.drools:drools-wb-rest-defaultapprover:0.9. Hardocded dependencies should not exist within the Maven respository as they can potentially break updates.

The Maven repository contains some signed artifacts. These should not be present. No distributed artifacts should be signed. This is unlikely to impact on users.

Some artifacts' source JAR files are missing from the Maven repository. All source JAR files should be available to users.

The Maven repository contains some artifacts with non-standard POM files. These can trigger ModelBuildingExceptions.

The Maven repository contains The repository contains various files that are not needed by a developer. These present a risk so users should be aware of them.

Multiple versions of some artifacts appear in the Maven respository. Each one should contain only one version.

The Maven repository contains non-productized artifacts. Each distributed artifact should be productized to limit risk to the user.

Exception when installing on Windows 2008 In Fuse Service Works 6.0, the installer throws an exception when installing on Windows 2008.

If there are two or more consecutive spaces in the Java Development Kit install path, installation will fail on the Red Hat Enterprise Linux 6 platform. To work around this issue, please change names on the install path to ensure that there are not two or more consecutive spaces in any directory names.

If you use the sqljdbc.jar driver when installing Fuse Service Works with MS-SQL 2008R2, you will encounter this error: SEVERE: Java Runtime Environment (JRE) version 1.7 is not supported by this driver. Use the sqljdbc4.jar class library, which provides support for JDBC 4.0. Exception in thread "AWT-EventQueue-0" java.lang.UnsupportedOperationException: Java Runtime Environment (JRE) version 1.7 is not supported by this driver. Use the sqljdbc4.jar class library, which provides support for JDBC 4.0. To work around this issue, use the sqljdbc4.jar instead. The database test connection will then work successfully.

The .bat files for Microsoft Windows misleading state you cannot install in directories with any spaces. Please be aware that this is incorrect: you can have one space but not two consecutive ones.

If you run a large number of RTGov activities with the same identifier, the Call Trace Gadget will show null and a number of exceptions will be logged. This is because the calltrace widget has problems when there is a very large number of business transactions for a single id.

If the user starts two servers on different ports and opens a BPEL Console instance on each, an exception will occur. To work around this issue, avoid using opening two BPEL Consoles concurrently.

The JON plug-in name is hard-coded. As a result, JON can only be deployed to certain products at present. Users cannot specify other choices.

If you configure the DTGov target to deploy to JON, an exception will occur. Users can ignore this message since the deployment is still successfully created in JON and deployed to the appropriate managed servers.

The ReadMe file for dtgov-demos-project/project-service-impl does not currently tell users that you must first run mvn install from quickstarts/overlord/dtgov/ before running the quick start. If you do not do this, demonstration will not run.

If you try to add a Data Type definition to a process, the BPMN 2 editor will create the item definition as expected, but it will generate many extraneous messages. It will also create a number of operation definitions which fail BPMN 2 validation. As a result, you will see errors in the Problems view.

The Situations gadget does not function as expected in some browsers. Users are unable to collapse the gadget after it has been expanded. This causes it to remain onscreen. You can make the menu go away by expanding one of the other situation windows in the interface.

If you try to install Red Hat JBoss Data Virtualization in combination with Red Hat JBoss Enterprise Application Platform and Red Hat JBoss Fuse Service Works with SSL security enabled, the installation will fail in the processing phase. In the console, though, the user is requested to accept a certificate. An error is written to the log. The workaround would be to ensure that SSL security is not enabled in Red Hat JBoss Fuse Service Works and Red Hat JBoss Data Virtualization if you are installing these in combination with each other.

The Audit Security Manager currently impacts on the system due to the number of accesses it makes. This results in reduced performance for users.

The S-RAMP product is meant to be generic in nature, and not tied specifically to any one product, so the references to Red Hat JBoss Fuse Service Works in the installer is therefore, not an indication that S-RAMP can only be used with Red Hat JBoss Fuse Service Works. It can be used in conjunction with other products. This will be corrected in the next release of the installer.

If a user tries to import the s-ramp-demos-switchyard quick start in Red Hat JBoss Developer Studio, an error occurs. This is because there is no implementation in the switchyard.xml file for this service.

RTGov analytics can thrown a null-pointer exception when processing a message from a misconfigured service. To avoid this, ensure that transformers are correctly configured on your service.

Camel cannot currently marshal or unmarshal CSV files. This will impact on any Smooks users who make use of the CSV format.

The XPath operation selector does not work on Camel bindings. It reports an error even if the message is correct. To work around this issue, use a custom Java operation selector and execute the XPath there.

Operation selectors are used in combination with a service binding to help SwitchYard determine the target operation for a service invocation. When a service only has a single operation, an operation selector should not be used. If an operation selector is, however, used for a service with a single operation, failure to assign an operation in the selector will not result in an error. If an operation selector fails to assign an operation for a service with multiple operations, an error is reported.

s-ramp.sh and s-ramp.bat do not work when a directory contains spaces. As a result, users cannot launch S-RAMP on Red Hat Enterprise Linux or Microsoft Windows if they have spaces in directory names. This is because the scripts do not protect themselves against JAVA_HOME or DIRNAME variables containing spaces. To work around this issue, rename directories so that they do not contain spaces.

When you launch s-ramp.bat on Microsoft Windows, you will encounter an java.lang.NoClassDefFoundError. This exception does not impact on the user. It simply means that the native library failed to load and that it has fallen back to the Java code that handles unsupported screens.

The KieJarArchive is not automatically recognised in the DTGov or S-RAMP interfaces. The KieExpander recognises it as JarArchive instead of KieJarArchive. This can be worked around by explicitly setting the type to KieJarArchive when you open the archive. As a result, the default "Document" type will be overridden and the archive will appear.

The s-ramp.sh file will not run unless JAVA_HOME is set. To do this, run the command cat ~/.bash_profile and locate the JAVA_HOME property. Remove the # to enable it. s-ramp.sh will now run as expected.

If you set the org.apache.ode log category to DEBUG it starts to flood the log with error messages. As a result, the log becomes hard to read and uses up drive space.

There is no pagination in the DTGov TaskInbox .As a result, users cannot navigate the list.

An error is thrown when deleting certain JAR files on Windows systems. When users attempt to delete JAR files that are being used by the classloader, a message will appear reading "java.lang.RuntimeException: Unable to delete file". This behaviour is only apparent in a Windows environment. To work around this, ensure the files are not in use when you are attempting to delete them.

The jboss-cli tool will not launch successfully on the Microsoft Windows operating system if JBoss EAP is installed in a directory that has spaces or other special characters such as parentheses in its path. The following error message is the outcome if JBoss EAP is installed in the directory C:\JBoss EAP\jboss-eap-6.2: ---- Error: Could not find or load main class EAP\jboss-eap-6.2\bin\jboss-cli-logging.properties ---- This can be worked around by editing the jboss-cli.bat file and editing line 62 of jboss-cli.bat to move the first “ character from the beginning of JAVA_OPTS to after the assignment so it looks like the following. ---- set JAVA_OPTS="%JAVA_OPTS% -Djboss.modules.system.pkgs=com.sun.java.swing -Dlogging.configuration=file:%JBOSS_HOME%\bin\jboss-cli-logging.properties" ---- This error can also be avoided by not installing JBoss EAP 6 in a directory with spaces or parentheses in its name. This will be fixed in a future release.

An error is logged when the BPEL console is idle. After 5-10 minutes of inactivity, the console produces a non-fatal error message.

When executing on IBM JVMs (1.6 and 1.7), a BPM process that contains XPath constraint (for example when using an exclusive gateway) with a constraint expression containing the bpmn2 namespace (for example bpmn2:getVariable), the constraint will fail to execute.