[ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]
Jeff Mesnil reassigned JBMESSAGING-381:
---------------------------------------
Assignee: Jeff Mesnil (was: Tim Fox)
> Add param on destination to disable persistence
> -----------------------------------------------
>
> Key: JBMESSAGING-381
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
> Project: JBoss Messaging
> Issue Type: Feature Request
> Reporter: Tim Fox
> Assigned To: Jeff Mesnil
> Fix For: 2.0.0 Beta 1
>
> Attachments: patch-JBMESSAGING-381.txt
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ]
Jeff Mesnil reassigned JBMESSAGING-375:
---------------------------------------
Assignee: Jeff Mesnil (was: Tim Fox)
> Grouping of messages with JMSXGroupId
> -------------------------------------
>
> Key: JBMESSAGING-375
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
> Project: JBoss Messaging
> Issue Type: Feature Request
> Reporter: Tim Fox
> Assigned To: Jeff Mesnil
> Fix For: 2.0.0 Beta 1
>
> Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID
--
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
Default a portlet window to maximized.
--------------------------------------
Key: JBPORTAL-1300
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1300
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: David Roberts
Priority: Optional
When adding portlets, it would be nice if there were an option where the portlet window could start out MAXIMIZED, so the entire portlet fills the screen nicely without the users having to click the maximize button. Eg. this would be very helpful when using the IFrame Portlet, so the URL being referenced fits the entire screen, and doesn't mess up the original layout of the referenced page.
--
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
Add support for exporting full CMS content (multiple language)
--------------------------------------------------------------
Key: JBPORTAL-1767
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1767
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.2 Final
Reporter: Mariusz Smykula
Assigned To: Sohil Shah
Current, after migration all data in language other than default are lost. There is no solution for full data exporting.
--
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
Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
----------------------------------------------------
Key: JBAS-4688
URL: http://jira.jboss.com/jira/browse/JBAS-4688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Transaction Manager
Reporter: Dimitris Andreadis
Assigned To: Adrian Brock
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3
Upgrade to a JBoss Transaction version that implements JTA 1.1
--
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
TECH REVIEW: Getting Started Guide - Chapter 9. Using Hibernate
---------------------------------------------------------------
Key: JBAS-4833
URL: http://jira.jboss.com/jira/browse/JBAS-4833
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.2.2.GA
Reporter: Michael Smith
Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira
It is important for track changes to be enabled so the re-write can be easily performed.
http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/
--
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
TECH REVIEW: Getting Started Guide - Chapter 7. Container-Managed Persistence
-----------------------------------------------------------------------------
Key: JBAS-4831
URL: http://jira.jboss.com/jira/browse/JBAS-4831
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.2.2.GA
Reporter: Michael Smith
Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira
It is important for track changes to be enabled so the re-write can be easily performed.
http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/
--
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
TECH REVIEW: Installation Guide - Chapter 1 - Installing JBoss
---------------------------------------------------------------
Key: JBAS-4818
URL: http://jira.jboss.com/jira/browse/JBAS-4818
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Installation Guide
Affects Versions: JBossAS-4.2.2.GA
Reporter: Michael Smith
Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira
It is important for track changes to be enabled so the re-write can be easily performed.
http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html
--
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
Upgrade jboss transactions to 4.2.3.SP6 (from 4.2.3.SP5)
--------------------------------------------------------
Key: JBAS-4759
URL: http://jira.jboss.com/jira/browse/JBAS-4759
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Transaction Manager
Reporter: Dimitris Andreadis
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.2.GA
--
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