[JBoss JIRA] Updated: (JBMESSAGING-410) java:/JmsXA in no-tx context does not work the same way as JBossMQ
by Clebert Suconic (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-410?page=all ]
Clebert Suconic updated JBMESSAGING-410:
----------------------------------------
JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968696#3968696
> java:/JmsXA in no-tx context does not work the same way as JBossMQ
> ------------------------------------------------------------------
>
> Key: JBMESSAGING-410
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-410
> Project: JBoss Messaging
> Issue Type: Bug
> Components: Configuration and Management
> Affects Versions: 1.0.1.CR2
> Reporter: Elias Ross
> Assigned To: Clebert Suconic
> Fix For: 1.0.1.CR5
>
>
> The same code I wrote that uses java:/JmsXA in a non-transacted environment with JBossMQ does not work with JBoss Messaging. And actually the same code does work correctly with SonicMQ as well, using the JCA adaptor with the Sonic XA connection factory.
> Why allow the use java:/JmsXA without transactions? It makes sense to use a cached connection manager anyway, like you would with a database. And anyway, should be addressed for compatibility.
> The following code *should* successfully send a message to a queue running without a transaction. Currently, it doesn't seem to do anything and no usage warnings are produced.
> QueueConnectionFactory queueCF = (QueueConnectionFactory)new InitialContext.lookup("java:/JmsXA");
> ...
> QueueConnection queueConnection = queueCF.createQueueConnection();
> QueueSession queueSession =
> queueConnection.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
> QueueSender queueSender = queueSession.createSender(queue);
> ObjectMessage om = queueSession.createObjectMessage();
> queueSender.send(om);
> queueSender.close();
> queueSession.close();
> queueConnection.close();
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Commented: (JBMESSAGING-410) java:/JmsXA in no-tx context does not work the same way as JBossMQ
by Clebert Suconic (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-410?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-410:
---------------------------------------------
Please, post comments to http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968690#3968690
> java:/JmsXA in no-tx context does not work the same way as JBossMQ
> ------------------------------------------------------------------
>
> Key: JBMESSAGING-410
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-410
> Project: JBoss Messaging
> Issue Type: Bug
> Components: Configuration and Management
> Affects Versions: 1.0.1.CR2
> Reporter: Elias Ross
> Assigned To: Clebert Suconic
> Fix For: 1.0.1.CR5
>
>
> The same code I wrote that uses java:/JmsXA in a non-transacted environment with JBossMQ does not work with JBoss Messaging. And actually the same code does work correctly with SonicMQ as well, using the JCA adaptor with the Sonic XA connection factory.
> Why allow the use java:/JmsXA without transactions? It makes sense to use a cached connection manager anyway, like you would with a database. And anyway, should be addressed for compatibility.
> The following code *should* successfully send a message to a queue running without a transaction. Currently, it doesn't seem to do anything and no usage warnings are produced.
> QueueConnectionFactory queueCF = (QueueConnectionFactory)new InitialContext.lookup("java:/JmsXA");
> ...
> QueueConnection queueConnection = queueCF.createQueueConnection();
> QueueSession queueSession =
> queueConnection.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
> QueueSender queueSender = queueSession.createSender(queue);
> ObjectMessage om = queueSession.createObjectMessage();
> queueSender.send(om);
> queueSender.close();
> queueSession.close();
> queueConnection.close();
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Resolved: (JBPORTAL-585) Sorting and Localization for Navigation Portlet
by Roy Russo (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-585?page=all ]
Roy Russo resolved JBPORTAL-585.
--------------------------------
Fix Version/s: 2.6.Alpha1
(was: 2.6 Final)
Resolution: Rejected
Condensed to JBPORTAL-1014
> Sorting and Localization for Navigation Portlet
> -----------------------------------------------
>
> Key: JBPORTAL-585
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-585
> Project: JBoss Portal
> Issue Type: Patch
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2 Final, 2.4 Final
> Reporter: Doug Schnelzer
> Assigned To: Roy Russo
> Fix For: 2.6.Alpha1
>
> Attachments: default-object.xml, NavigationPortlet.java, Resource.properties
>
>
> The navigation portlet currently only supports sorting by the page name. This patch adds support for sorting by a Declared Property named "order" in the -objects.xml. This patch also supports using a resource properties file for looking up page labels. The Declared Property name for the resource properties file key is "resourceKey". An example -object.xml file is attached. The relevant section is:
> <page>
> <page-name>default</page-name>
> <properties>
> <property>
> <name>order</name>
> <value>1</value>
> </property>
> <property>
> <name>resourceKey</name>
> <value>home</value>
> </property>
> </properties>
> ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months
[JBoss JIRA] Created: (JBPORTAL-988) Sorting order for Navigation Portlet
by Mitch De Felice (JIRA)
Sorting order for Navigation Portlet
------------------------------------
Key: JBPORTAL-988
URL: http://jira.jboss.com/jira/browse/JBPORTAL-988
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Portlet
Affects Versions: 2.6 Final
Environment: Windows 2000
Reporter: Mitch De Felice
It would be nice if we could have the ability to set sorting order on the Navigation Portlet. Ideally, it would be great to be able to set the order first, numerically, then by the role.
Example:
<page-01 role "unchecked"> <page-02 role "user"> <page-03 role "user"> <page-04 role "admin"> <page-05 "admin">
This way, we can always have our admin pages at the end of the list.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 10 months