Merge pull request #6 from jmesnil/master

various fixes
[maven-release-plugin] prepare release 1.0.1.CR1
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release 1.0.1.Final
[maven-release-plugin] prepare for next development iteration
[#7] Do not display security credentials

in JmsActivationSpec#toString, convert the jndiParameters string to a
Properties and replaces the value for the SECURITY_CREDENTIALS by "<not
shown>".
Merge pull request #8 from jmesnil/security_credentials

[#7] Do not display security credentials
[maven-release-plugin] prepare release 1.0.2.Final
[maven-release-plugin] prepare for next development iteration
check whether a transaction is active

to ignore the transacted and acknowlegeMode if there is an active
transaction.

The check is done using the TransactionSynchronizationRegistry object
that is looked up in JNDI using the
TransactionSynchronizationRegistryLookup config property.
By default, the property is not set and a RA will consider that a
transaction is active and will create the JMS session accordingly.

To specify the TransactionSynchronizationRegistryLookup to use, add a
config-property to ra.xml. For example

   <config-property>
      <description>The JNDI name to lookup the TransactionSynchronizationRegistry.</description>
      <config-property-name>TransactionSynchronizationRegistryLookup</config-property-name>
      <config-property-type>java.lang.String</config-property-type>
      <config-property-value>java:jboss/TransactionSynchronizationRegistry</config-property-value>
   </config-property>

Remove the checkState() method that is no longer correct since the RA
can used without active transaction (and the method in
JmsSessionFactoryImpl was not doing any checks prior to the previous
commit anyway).

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1033008
Merge pull request #9 from jmesnil/transaction_active

check whether a transaction is active
[maven-release-plugin] prepare release 1.0.3.Final
[maven-release-plugin] prepare for next development iteration
Always ignore createSession parameters

The resource adapter is meant to be used from inside a Java EE
container. In that case, the parameters to createSession are ignored and
the container will manage the transaction.

From EJB 3.1 spc, 13.3.5:

> "Because the container manages the transactional enlistment of JMS
> sessions on behalf of a bean, the parameters of the
> createSession(boolean transacted, int acknowledgeMode) method
> are ignored."
Remove tx synchronization lookup

The RA no longer looks whether there is an active
transaction when the JSM session is created.
Merge pull request #10 from jmesnil/deliveryTransacted

fix transacted delivery behaviour
[maven-release-plugin] prepare release 1.0.4.Final
[maven-release-plugin] prepare for next development iteration
Fix links in documentation
Merge pull request #11 from jbertram/master

Fix links in documentation