6:57 a.m.
JMS provider transactional support cannot be enabled
----------------------------------------------------
Key: JBESB-1879
URL: https://jira.jboss.org/jira/browse/JBESB-1879
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.2.1 CP3
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Fix For: 4.2.1 CP4
It was told that plain jms-provider now supports JTA transactions and according to code it
could but there is no transacted attribute available for jms-provider-type in XML schema
for jboss-esb.xml file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:32 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1879) JMS provider transactional support cannot be enabled
[
https://jira.jboss.org/jira/browse/JBESB-1879?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-1879:
--------------------------------
Fix Version/s: 4.2.1 CP5
(was: 4.2.1 CP4)
JMS provider transactional support cannot be enabled
----------------------------------------------------
Key: JBESB-1879
URL: https://jira.jboss.org/jira/browse/JBESB-1879
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.2.1 CP3
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Fix For: 4.2.1 CP5
It was told that plain jms-provider now supports JTA transactions and according to code
it could but there is no transacted attribute available for jms-provider-type in XML
schema for jboss-esb.xml file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:07 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1879) JMS provider transactional support cannot be enabled
[
https://jira.jboss.org/jira/browse/JBESB-1879?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-1879:
--------------------------------
Fix Version/s: 4.6
(was: 4.2.1 CP5)
JMS provider transactional support cannot be enabled
----------------------------------------------------
Key: JBESB-1879
URL: https://jira.jboss.org/jira/browse/JBESB-1879
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.2.1 CP3
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Fix For: 4.6
It was told that plain jms-provider now supports JTA transactions and according to code
it could but there is no transacted attribute available for jms-provider-type in XML
schema for jboss-esb.xml file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:48 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1879) JMS provider transactional support cannot be enabled
[
https://jira.jboss.org/jira/browse/JBESB-1879?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-1879:
--------------------------------
Fix Version/s: 4.7
(was: 4.6)
JMS provider transactional support cannot be enabled
----------------------------------------------------
Key: JBESB-1879
URL: https://jira.jboss.org/jira/browse/JBESB-1879
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.2.1 CP3
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Fix For: 4.7
It was told that plain jms-provider now supports JTA transactions and according to code
it could but there is no transacted attribute available for jms-provider-type in XML
schema for jboss-esb.xml file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:50 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1879) JMS provider transactional support cannot be enabled
[
https://jira.jboss.org/jira/browse/JBESB-1879?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1879:
-------------------------------------
Jirka, can you please confirm if this is still the case?
The attribute is present on the jms-message-filter element but it appears to have been
there since 4.2.1CP1.
JMS provider transactional support cannot be enabled
----------------------------------------------------
Key: JBESB-1879
URL: https://jira.jboss.org/jira/browse/JBESB-1879
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.2.1 CP3
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Fix For: 4.7
It was told that plain jms-provider now supports JTA transactions and according to code
it could but there is no transacted attribute available for jms-provider-type in XML
schema for jboss-esb.xml file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:17 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1879) JMS provider transactional support cannot be enabled
[
https://jira.jboss.org/jira/browse/JBESB-1879?page=com.atlassian.jira.plu...
]
Jiri Pechanec commented on JBESB-1879:
--------------------------------------
The contents of the docs/schema file is
<xsd:complexType name="jms-provider-type">
<xsd:annotation>
<xsd:documentation xml:lang="en">
A specific instance of a provider, providing JMS.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="jesb:bus-provider">
<xsd:attribute name="connection-factory"
type="xsd:string" use="required">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The connection-factory used to lookup
queues/topics in a naming directory (JNDI)
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="jndi-context-factory"
type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The context factory class the JBossESB will
use to do naming lookups.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="jndi-pkg-prefix"
type="xsd:string">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The pkg-prefix which will be used to do
naming lookups. It is left empty by default.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="jndi-URL" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The URL used to do naming lookups.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
JMS provider transactional support cannot be enabled
----------------------------------------------------
Key: JBESB-1879
URL: https://jira.jboss.org/jira/browse/JBESB-1879
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.2.1 CP3
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Fix For: 4.7
It was told that plain jms-provider now supports JTA transactions and according to code
it could but there is no transacted attribute available for jms-provider-type in XML
schema for jboss-esb.xml file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:27 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1879) JMS provider transactional support cannot be enabled
[
https://jira.jboss.org/jira/browse/JBESB-1879?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-1879.
-------------------------------
Resolution: Rejected
The attribute is in a different place from the other providers, hence the confusion. It
is actually located on the message filter.
JMS provider transactional support cannot be enabled
----------------------------------------------------
Key: JBESB-1879
URL: https://jira.jboss.org/jira/browse/JBESB-1879
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.2.1 CP3
Reporter: Jiri Pechanec
Assignee: Kevin Conner
Fix For: 4.7
It was told that plain jms-provider now supports JTA transactions and according to code
it could but there is no transacted attribute available for jms-provider-type in XML
schema for jboss-esb.xml file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5620
days inactive
6055
days old
6 comments
2 participants
participants (2)
-
Jiri Pechanec (JIRA) -
Kevin Conner (JIRA)