]
Jesper Pedersen updated WFLY-1890:
----------------------------------
Summary: Missing support of unshareable JCA connections (was: JBoss EAP 6.1 :
missing support of unshareable JCA connections)
Missing support of unshareable JCA connections
----------------------------------------------
Key: WFLY-1890
URL:
https://issues.jboss.org/browse/WFLY-1890
Project: WildFly
Issue Type: Bug
Components: EE, Naming
Affects Versions: 8.0.0.Alpha4
Environment: Windows 7 and RedHat Linux with Java 6
Reporter: Martin Keller
Priority: Minor
We noticed, that JBoss EAP 6.1 handles unshareable resources not conform to the JCA 1.6
specification.
They are used in a shareable way, even when the connections are deployt to be
unshareable. Thje resource adapter is deployed without errors and doesn't support
shared connections.
Does JBoss EAP 6.1 support unshareable connections at all and if so, how is this
configured?
We noticed that this problem orrurs in two configuration:
1. When we use resource annotations
2. Also if we use the old style deployment descriptors.
Resource annotation:
@Resource(description="Resource Referenz to service KDCINF in appication SAMPLE on
Windows via UPIC",
name="eis/KDCINF_Sample_Upic",
mappedName="eis/KDCINF_SAMPLE_U",
type=net.fsc.jca.communication.EISUpicConnectionFactory.class,
authenticationType=Resource.AuthenticationType.APPLICATION,
shareable=false)
Deployment descritor:
<resource-ref>
<description>Resource Referenz to service KDCINF in appication SAMPLE on
Windows via UPIC</description>
...
<res-type>net.fsc.jca.communication.EISUpicConnectionFactory</res-type>
<res-auth>Application</res-auth>
<res-sharing-scope>Unshareable</res-sharing-scope>
...
Is thera any additional configuration to be done to support unshareable JCA connections?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: