Simples Assim

https://jira.jboss.org/jira/browse/JBESB-3081 (vote for it!)

https://jira.jboss.org/jira/browse/JBESB-3082 (vote for it!)

• DB Action
• File Reader Action
• HTTP Action
• Remove Message Property Action
• Set Message Property Action
• Splitter Action
• XSLT Action

https://jira.jboss.org/jira/browse/JBESB-3118 (vote for it!)

https://jira.jboss.org/jira/browse/JBESB-3125 (vote for it!)

https://jira.jboss.org/jira/browse/JBESB-3086 (vote for it!)

https://jira.jboss.org/jira/browse/JBESB-3087 (vote for it!)

https://jira.jboss.org/jira/browse/JBESB-3146 (vote for it!)

https://jira.jboss.org/jira/browse/JBESB-3089 (vote for it!)

https://jira.jboss.org/jira/browse/JBESB-3075 (vote for it!)

It still misses support for XQuery.

https://jira.jboss.org/jira/browse/JBESB-3074 (vote for it!)

If you get the java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: Service '<Category>:<Name>' does not define a Message-Aware (is-gateway='false') nor InVm Listener message, you might want to change the jboss-esb.xml file:

<service ... inVmScope="GLOBAL">
  ...
</service>

As per page 58 of the Programmers Guide, [the ServiceInvoker class] only works with native ESB Messages [or in-VM].

You may also change the default for the invmScope attribute in the <Install Dir>/server/default/deploy/jbossesb.sar/jbossesb-properties.xml file:

<esb ...>
  <properties>
    <property name="jboss.esb.invm.scope.fault" value="GLOBAL" />
  </properties>
</esb>

The Unable to complete base jmx server discovery - cause (enable DEBUG to see stack trace): java.lang.UnsupportedOperationException: No native library available - Cannot get the process table information without native support warning occurs because Embedded Jopr 1.1 ships without the SIGAR library, as noted here.

I will ask around if/how it can be installed manually.

You may want to increase the log level of org.rhq.core.pc.inventory category.AvailabilityExecutor to INFO:

<category name="org.rhq.core.pc.inventory.AvailabilityExecutor">
    <priority value="INFO" />
</category>

-Xms128m -Xmx512m -XX:PermSize=200m -XX:MaxPermSize=500m

(as per page 7 of the Getting Started Guide)

Many platforms don’t support HTTP 1.1′s chunked encoding, used by default in JBossWS 3.0.1, including Protheus 8.

http://n2.nabble.com/JBossWS-Disabling-Transfer-Encoding-chunked-in-a-client-td2977363.html

In JBossESB 4.6, the directory is <Install Dir>/server/default/deploy/jbossws.sar/META-INF.

As per section 4.4 of RFC 2616:

For compatibility with HTTP/1.0 applications, HTTP/1.1 requests containing a message-body MUST include a valid Content-Length header  field unless the server is known to be HTTP/1.1 compliant. If a request contains a message-body and a Content-Length is not given,  the server SHOULD respond with 400 (bad request) if it cannot determine the length of the message, or with 411 (length required) if  it wishes to insist on receiving a valid Content-Length.

Instead, Protheus 8 fails with the cryptic WEBSERVICE ERROR : XMLParser Error : Build <Build Number> XML Internal Error message.

https://jira.jboss.org/jira/browse/JBESB-2293

http://www.jboss.org/embjopr